Making Your Business Run Without You

Understanding the Franchise Rule

The Franchise Rule is the idea that your solar installation company should run like a great franchise: the business keeps moving even when you’re not in the room. Not because people “guess,” but because the work is covered by clear steps, checklists, and decision rules. Think of it like a solar crew on a roof—if the lead installer gets sick, the job still needs to be completed safely and correctly. The system should carry the load.

The Importance of Systems

In solar, consistency is everything. A missed step in permitting, a wrong spec on an inverter, or an incomplete site note can cause rework, delays, or safety problems. Systems make sure your company installs the same way every time—whether it’s a new hire or your best installer. Your goal is that the right process happens automatically:

- Sales-to-install handoff (what must be true before scheduling)
- Survey and design documentation (what gets recorded, and where)
- Permit submission and resubmission workflow (who checks what)
- Installation day execution (materials, wiring, labeling, torque checks)
- QA/QC and commissioning (what gets verified before you close)

Building a Self-Sufficient Business

To make your company self-sufficient, find where you personally slow things down. In solar, the bottleneck is often your “knowledge”—the decisions only you know how to make. Examples:

- You are the only one who knows why a permit got kicked back.
- You are the only one who can approve design changes when the roof condition surprises the crew.
- You are the only one who can calm down a customer when utility paperwork is delayed.

Now convert that knowledge into steps other people can follow. Start with the simplest high-frequency cases:

- Create scripts for common customer questions (timeline, inspections, financing, utility interconnect).
- Write decision rules for change orders (when a roof issue requires a design adjustment vs. when it doesn’t).
- Build a “permit trouble” checklist (what to verify before resubmitting, and the exact info your city typically requests).

This is how you stop being the single point of failure.

Real-World Scenario

Imagine a mid-size solar company where you personally review every installation-day issue. One day you’re unavailable, and the crew runs into a real-world problem: the roof has older flashing that doesn’t match the photo from the survey. If you’re not reachable, the crew either pauses (expensive) or makes a guess (riskier). The Franchise Rule approach is to have a documented decision tree for roof condition surprises:

- If flashing is intact and compatible → proceed with labeled parts and standard method.
- If flashing is corroded or mismatched → pause and escalate to QA with photos.
- If roof structure needs reinforcement → generate an engineering request package using your template.

The crew isn’t improvising. They’re following a system.

The Role of Documentation

Documentation is how you turn “tribal knowledge” into a company asset. In solar, you want documentation that is usable on a phone or tablet, not buried in a folder.

Good documentation answers three questions fast:

1. What is the exact next step?
2. What evidence proves it’s done? (photo, checklist item, document upload)
3. Who decides when it’s not standard?

Document the workflows your team actually touches—survey form requirements, design approval checklist, permitting packet contents, and installation QA checklist.

The Benefits of a Franchise Model

When your solar business follows the Franchise Rule, you get:

- Fewer last-minute surprises because handoffs are controlled.
- Faster decisions because the rules are written.
- Less downtime because installers and PMs can move forward without waiting on you.
- Better customer experience because timelines are managed consistently.

You also reduce your stress. You stop “holding the whole system together” and start leading growth instead.

Conclusion

The Franchise Rule is about building a solar installation company that doesn’t depend on you to function. You do it by mapping bottlenecks, building step-by-step systems, documenting them clearly, and giving your team decision rules they can trust.

*Example Scenario: Picture a solar office where a PM can handle a permit resubmission without calling you every time. They use a “permit resubmission packet” template, a checklist of common city corrections, and a clear escalation rule. When you’re out, the jobs still move forward and customers still get answers on time.*