Solar Business Operations Playbook: Systems, KPIs & Weekly Cadence

Every solar business has operations. The question is whether they live in a document or in the owner’s head. In the head, the business runs fine at 10 jobs a month and collapses at 30 — not from lack of demand, but from dropped balls: the permit nobody filed, the design nobody checked, the final invoice nobody sent.

This playbook is the operating system we have seen work across residential and C&I installers: the 6-stage pipeline, the 8 numbers that matter, the SOP structure that people actually use, and the meeting cadence that keeps it all honest. It is deliberately boring. Boring operations are what profitable looks like from the inside.

In this playbook:

• The 6-stage pipeline and stage exit criteria
• The 8 KPIs and how to run the Monday review
• SOP structure: the 1–2 page format that gets used
• Meeting cadence that does not waste the field’s time
• The software stack and single source of truth
• Systematization order: what to fix first
• Common failure modes at 10, 30, and 60 jobs a month

The 6-Stage Pipeline

Everything in a solar business belongs to one of 6 stages. If a job can be “between stages” with no owner, your pipeline leaks.

Two rules make the board work. First, every job has exactly one stage and one owner at all times. Second, exit criteria are objective — “design done” means the QA checklist is signed, not that the designer feels finished.

The pipeline board belongs in your CRM or project tool, visible to the whole company, reviewed every Monday. Our solar CRM workflow automation guide covers the automation side of this board.

The 8 KPIs

Track these weekly. Monthly tracking discovers problems 4 weeks too late.

1. Lead response time (median minutes). Speed wins contacts; see our solar lead response time analysis for the data.
2. Survey-to-proposal hours (median). Under 48 hours is the benchmark that wins competitive bids. A solar design platform with built-in shading and financials is the main lever here.
3. Proposal close rate (by rep, by lead source).
4. Gross margin per closed job (actuals). Residential target: 20%+.
5. Install days per kW (per crew). Deviations trace to design quality.
6. Rework rate (jobs with a return visit ÷ total).
7. Days to PTO (install-complete to permission to operate, per utility).
8. Cash conversion cycle (equipment payment to final collection).

One dashboard, one owner per metric, reviewed in 30 minutes every Monday. The meeting rule: any metric drifting 2 consecutive weeks gets a countermeasure and a name attached — not a discussion about why the number is unfair.

SOP Structure That Actually Gets Used

Most SOPs fail because they are written like manuals. Field teams do not read manuals. The format that survives contact with reality:

• 1–2 pages maximum. If it needs 10 pages, it is 3 SOPs.
• Checklist-first. Numbered steps with checkboxes, photos where a picture beats a paragraph.
• Named owner and revision date at the top. SOPs without owners rot.
• Stored where the work happens. The install checklist lives in the crew’s app or truck binder, not in a shared drive nobody opens.

The minimum viable set: lead intake, site survey, design standards, proposal standards, permit submission, install day, QA/commissioning, closeout/PTO. Write them in that order if starting from zero. Our solar EPC SOP templates post provides ready structures for each.

Meeting Cadence

Meetings are the enforcement mechanism for everything above. Three standing meetings cover a solar business up to about 60 jobs a month:

Daily install huddle — 15 minutes, field leads. Today’s jobs, yesterday’s problems, blocked materials. Standing, no slides.

Monday KPI review — 30 minutes, leadership. The 8 KPIs, last week vs. trailing 4-week average. Countermeasures assigned for anything drifting 2 weeks.

Monthly financial review — 60 minutes, owner plus finance. Job-cost variance, margin by segment, 13-week cash forecast, pipeline coverage for next month.

That is it. A solar business does not need more meetings; it needs these 3 to happen without exception. Cancel the Monday review 3 times and the KPIs become decoration.

The Software Stack and Single Source of Truth

The stack question has a wrong answer before it has a right one. The wrong answer: best-of-breed everything, glued with exports. Every export-import between CRM, design tool, proposal tool, and project management is a version-error factory.

The right answer for most installers:

• CRM — pipeline stages 1–2 and 4, follow-up automation.
• Design + proposal platform — stages 3–4 in one workspace. SurgePV’s solar software combines 3D design, shadow analysis, financials, and branded proposals, which removes 2 of the usual handoffs.
• Project management — stages 5–6, install scheduling, checklists.
• Accounting — invoicing, job costing, payroll.

The rule above all: one system is the source of truth for customer and job status. Everything else references it. Two sources of truth means zero.

For Indian EPC operations, the stack also needs DISCOM application tracking and subsidy documentation — QuickEstimate’s CRM comparison for Indian solar businesses covers tools built for that workflow.

Systematization Order: What to Fix First

You cannot document everything at once. Fix stages in order of error cost:

1. Design. A design error costs a change order, an install delay, or a callback — the most expensive mistakes in the business. Design standards and QA first.
2. Closeout. Slow PTO traps cash. Milestone billing and a closeout checklist recover working capital fastest.
3. Install. Checklists cut rework rate, which protects margin directly.
4. Survey. Better survey data prevents design errors upstream — but only matters once design standards exist to consume it.
5. Sales and lead intake. Important, but sales chaos is cheaper than install chaos. Document last.

This order is counterintuitive — most owners start with sales because sales feels like growth. Start where mistakes cost money, not where activity feels good.

Failure Modes by Volume

Operations break at predictable volumes. Knowing the pattern lets you fix the stage before it snaps.

At 10 jobs a month: the owner is the system. Everything works because one person touches everything. The risk: nothing is documented, and the first hire inherits chaos. Fix: write the 8 SOPs now, while volume is low enough to think.

At 30 jobs a month: handoffs break. The survey-to-design and design-to-install transitions drop information. Symptoms: change orders, wrong BOMs, crews waiting on missing parts. Fix: stage exit criteria, the Monday KPI review, and one source of truth for job status.

At 60+ jobs a month: middle management breaks. Crew leads and coordinators make inconsistent calls because standards were never written. Symptoms: margin variance by crew, rework clustering around specific teams, PTO backlog. Fix: QA ownership per stage and a monthly SOP revision cycle driven by the failure data itself.

The pattern across all 3: volume does not create operational problems, it reveals them. The businesses that scale are the ones that documented before they needed to.

Data Discipline: Where the Numbers Come From

KPI reviews fail when the data is assembled by hand the night before. Instrument the sources instead:

• Lead response time comes from the CRM timestamp on first touch, not rep memory.
• Survey-to-proposal hours comes from stage-change timestamps on the pipeline board.
• Gross margin comes from job-cost actuals in accounting, closed within 30 days of PTO.
• Install days per kW and rework come from crew logs and QA checklists.
• Days to PTO comes from utility application and approval dates in the closeout checklist.

If a number takes more than 10 minutes to pull, the process is not instrumented — fix the tool, not the analyst. This is why the single-source-of-truth rule matters: data scattered across 4 tools produces 4 versions of every KPI, and meetings degrade into arguments about whose spreadsheet is right.

Roles and Accountability: Who Owns What

KPIs without owners are weather reports. The accountability map for a 15–40 person installer:

One person can hold 2 roles below 15 jobs a month. What never works is a KPI owned by “the team.” Shared ownership is no ownership with extra meetings.

When a role changes hands, the SOPs are the handover document. This is the hidden payoff of documentation: a crew lead leaving costs you 2 weeks of ramp-up instead of 6 months of rediscovery.

The Monthly SOP Revision Cycle

SOPs are living documents or dead ones. The revision cycle that keeps them alive:

1. Collect failure data all month. Every change order, callback, rework visit, and PTO rejection gets tagged to a stage.
2. First week of the month: the stage owner reviews their tagged failures and proposes SOP edits — a missing checklist step, an unclear photo example, a wrong part number.
3. Approve and republish with a new revision date. Announce changes in the daily huddle, not by email.
4. Retire steps that never catch anything. Checklists grow by addition and die by length; prune ruthlessly.

This loop — failure data driving SOP edits — is what separates a playbook from a binder. After 6 months of revision cycles, your SOPs encode more operational knowledge than any single employee carries.

What Most Owners Get Wrong

The core misconception is that operations is overhead — time taken from selling and installing. Operations is the multiplier on selling and installing. A 2-point rework reduction on 40 jobs a month at $18,000 each is worth more than most marketing spends, and it compounds.

Second misconception: hire an ops manager to “do operations.” Systems come before managers. An ops manager hired into an undocumented business spends 6 months discovering what the owner already knows, then quits. Document first, then hire someone to run and improve the documents.

The exception: if you are pre-revenue or under 5 jobs a month, ignore most of this playbook. Sell and install. Come back when dropped balls start costing real money — you will know the moment.

Conclusion

Solar operations is 6 stages, 8 numbers, 8 SOPs, and 3 meetings — run without exception. Three actions this week:

• Draw your pipeline board with exit criteria and one owner per stage.
• Pick the 8 KPIs and hold the first Monday review, even if the data is ugly. Ugly data is the point.
• Write your first SOP — design QA — using the 1–2 page checklist format.

If survey-to-proposal turnaround is your weakest KPI, that is a tooling problem with a fast fix. Book a SurgePV demo and see the design-to-proposal workflow on one of your real addresses. Then read our solar EPC guide for the margin side of this system.

Frequently Asked Questions

What are solar business operations?

Solar business operations cover every repeatable process between a lead arriving and a system receiving permission to operate: sales pipeline, site survey, design, permitting, procurement, installation, inspection, and closeout. Good operations make each stage measurable and repeatable.

What KPIs should a solar company track?

Track 8 weekly KPIs: lead response time, survey-to-proposal hours, proposal close rate, gross margin per job, install days per kW, rework rate, days to PTO, and cash conversion cycle. Review them in one weekly meeting with named owners for any metric drifting 2 weeks in a row.

What SOPs does a solar installer need?

The minimum viable SOP set: lead intake, site survey checklist, design standards, proposal standards, permit submission checklist, install day checklist, QA/commissioning checklist, and closeout/PTO checklist. Each SOP is 1–2 pages with a named owner and a revision date.

How do you scale solar operations?

Scale operations by systematizing before hiring: document SOPs, hold margin above 20% for 2 quarters, then add capacity one crew or one rep at a time. Adding people to undocumented processes multiplies variance, and variance is what kills margin at scale.

What software does a solar business need?

The core stack is a CRM for pipeline, a design and proposal platform, a project management tool for installs, and accounting software. Consolidation matters more than features: every export-import between tools is a chance for version errors and lost data.

How long should solar permitting and PTO take?

Permitting typically takes 1–6 weeks depending on the jurisdiction, and utility permission to operate adds another 1–4 weeks. Track both as KPIs per jurisdiction. Slow closeout traps working capital and is the most under-managed stage in most solar businesses.