Install the 7-Power Contractor Framework

01

Name the owner bottleneck without romanticizing it

Al begins with the skilled owner who still believes they are the best person for every important job. That belief may be accurate on a particular repair and destructive as an operating model. When every exception, approval, estimate, hire, and customer concern returns to one person, the business cannot build judgment elsewhere. The owner also loses the chance to see which responsibilities were never clearly assigned or taught.

For two weeks, log interruptions instead of relying on memory. Record the trigger, role that should own it, information missing, decision made, and whether the event recurred. Sort the list into policy gaps, training gaps, authority gaps, capacity gaps, and genuine executive decisions. The goal is not for the owner to vanish. It is to reserve the owner's attention for work that truly requires it and build a reliable path for everything else.

“When you ask who's the best person to do this job, the answer is always you're going to put your hand up, but you're automatically going to choke the size of your business and keep your people from going and growing.”

Al Levi, episode timestamp 05:24

02

Treat the seven powers as one operating model

Al's official framework names Planning, Operating, Financial, Staffing, Marketing, Selling, and Sales Coaching Power. Each one supplies or constrains another. Marketing can fill the schedule beyond capacity. Staffing without operating standards reproduces inconsistent work. A sales process without coaching decays. Financial reporting without operational ownership describes the past but may not change the next job. Installing one power means checking its inputs and downstream effects across the others.

Draw the connections before buying software or starting a program. For the chosen problem, identify the plan, role, procedure, required skill, customer communication, coaching check, demand implication, and financial measure. This one-page map prevents a department from optimizing its own metric at the expense of the whole company. It also reveals when the solution is not another document; sometimes the process is sound and the constraint is staffing, pricing, equipment, or decision authority.

03

Use Planning Power to choose the order

In the interview, Al defines planning as working on the right thing, at the right time, in the right way, with emphasis on execution rather than another idea. Build a short implementation queue. Rank recurring failures by customer harm, safety or compliance exposure, financial impact, frequency, and the team's ability to change them. Choose one primary system and set a review date before adding the next.

A rollout brief should name the owner, desired behavior, evidence of success, affected roles, training method, start date, feedback path, and rollback or correction plan. Keep other ideas in a visible backlog so saying “not yet” does not mean losing them. This pacing matters because a system is not installed when the manual is published. It is installed when people can demonstrate the behavior, supervisors can coach it, and the record shows it survives normal workload.

04

Build Operating Power from roles and manuals

Al places the organization chart and operating manual at the center of ownership. Begin with boxes, not personalities: each box has a purpose, decisions it may make, work it owns, handoffs it receives and sends, and a small set of meaningful indicators. A talented employee can fill more than one box, but the responsibilities should not blur. This makes it possible to see an overloaded role before calling the person unproductive.

Document the current best method for the high-frequency work in each box. Use checklists, examples, screenshots, forms, and escalation rules where they improve performance. Al says a manual cannot cover every imagined detail, so build for the common case and a safe exception path. Version the procedure, name its owner, and put the update date where users can see it. Documenting a home-service business is a maintenance discipline, not a one-time binder project.

Al also warns that modern software can display far more data than an owner should manage. His recording-time recommendation is four or five indicators for each role box. Treat that as a design constraint, not a magic count: choose measures tied to the box's purpose, define the formula and owner, and remove a metric when nobody can explain which decision it changes.

“Every box needs four to five KPIs.”

Al Levi, episode timestamp 06:22

05

Turn Staffing Power into a qualification path

Al describes taking willing apprentices through a structured path and moving senior technicians toward field supervision through qualification, competition, and training rather than promotion by reputation alone. Translate that into a role ladder. For each level, define prerequisites, supervised tasks, knowledge checks, observed demonstrations, safety limits, customer-service expectations, and who may sign off. Time served can support learning but should not substitute for demonstrated competence.

Train with the operating system the person will actually use. Explain the reason, demonstrate the procedure, let the learner practice, observe performance, and give specific feedback. Separate permission to practice under supervision from authorization to work independently. Supervisors need their own preparation for coaching, scheduling, documentation, and escalation; the best technician is not automatically ready to manage. This is how staffing expands capacity without merely moving the founder bottleneck into a field supervisor.

06

Pair ethical Selling Power with coaching

Al repeatedly qualifies sales as ethical communication and says the customer should not be sold something outside their best interest. Operationalize that standard. Require evidence before scope, plain-language options, complete price and material terms, truthful urgency, authorized warranties, and the ability to compare, pause, or decline. Measure comprehension, callbacks, cancellations, complaints, and fulfilled scope along with revenue. A system that rewards only ticket size can defeat the stated ethic.

Sales Coaching Power keeps the process alive after training. Review a sample of calls and proposals, ask the employee to self-assess, compare the work with the documented standard, and choose one behavior to practice. Managers should also fix unclear forms, authority rules, or pricing structures exposed by the review. Building systems before franchising requires exactly this loop: standard, demonstration, observation, feedback, correction, and proof that another leader can sustain it.

“Sales to me has always been great communication, ethical selling, because I don't believe you ever have the right to sell anything that's not in the customer's best interest.”

Al Levi, episode timestamp 10:27

07

Connect Marketing Power to Financial Power

Al describes Marketing Power as bringing the right amount of calls from the right customers at the right time. The important operating word is right. Demand that exceeds qualified capacity produces missed calls, long waits, rushed work, and callbacks. Demand for the wrong service or geography consumes dispatch time without creating useful work. Define the services, customers, area, schedule, and capacity a campaign should support before setting the media objective.

Financial Power then tests whether the model works. Build a budget from labor, burden, materials, vehicles, facilities, systems, warranty and callback allowance, marketing, overhead, and desired resilience rather than copying a competitor's price. Compare plan with actual results by service line, and trace variances to operating causes. The interview's tax and accounting comments are general discussion, not financial advice. A qualified accounting professional should shape the company's reporting, tax, and compliance practices.

08

Install, observe, revise, then add the next power

A staged implementation has five gates. The role owner and team agree on the current problem. The procedure and authority are documented. A representative group trains and demonstrates it. The system runs under normal workload while feedback and exceptions are captured. The owner reviews customer, employee, operational, and financial evidence and revises the standard. Only then does the next system enter active rollout.

Keep a change log and retire obsolete versions so the team does not face competing instructions. Schedule an audit after the novelty fades. Interview the people doing the work, inspect records, and observe a real handoff. Track exceptions by type and ask whether the procedure, training, authority, staffing, or measure created them. Publish the revision and retrain only the affected behavior instead of relaunching the whole program. At a quarterly review, rate each power from its own evidence and choose the next constraint; do not average seven weak scores into one reassuring dashboard number. Record why the priority changed so a later leader can distinguish a deliberate sequence from abandoned work. The named framework is Al Levi's, and his site includes promotional claims about stress, success, and results. Those are not guarantees here. The useful promise is smaller and testable: each installed system should make ownership, expected behavior, and evidence clearer than they were before.