The Solar Growth Capacity Model: Leads, Designs, Proposals, Installs, and Cash

A solar growth-capacity model connects possible demand to the work it creates, the roles able to release it, external readiness gates, and cash timing. It should reveal where a growth scenario fails rather than convert a lead target directly into an installation promise.

This page owns the scenario worksheet. The quarterly capacity-planning checklist owns the recurring cross-functional review, decisions and reopen triggers. Neither supplies universal conversion, utilization, productivity or staffing norms.

Define the Planning Boundary

Choose the observation date, planning periods, project segments, geographic scope, accepted work, resources and decision use. Identify what is already committed before adding new lead scenarios. Record whether a count means unique opportunities, quote versions, design tasks, installed projects or other objects.

A project can create several designs and proposal revisions. Those tasks consume work, but they are not additional customers. Installed capacity in kWdc, number of completed projects, and labor hours are different measures; a mixed project portfolio needs its actual work-content assumptions.

DOE’s solar soft-cost overview identifies non-hardware business and process costs and discusses delays involving jurisdictions and utilities. It provides solar context, not a throughput or staffing benchmark.

Keep Cohorts and Current Queues Separate

A historical conversion cohort follows the same opportunities through defined states over enough time to observe outcomes. A current-period activity report may contain designs for old leads, proposals for existing designs, and installations sold earlier. Multiplying those unrelated monthly ratios creates an unreliable growth model.

For each transition, record its entry definition, outcome definition, observation period, cohort maturity, cancellations, duplicates, open cases and source. A lead-to-qualified assumption does not by itself describe qualification effort. Unsuccessful or incomplete opportunities can still consume survey, design and follow-up work.

Use scenario labels such as current commitments, additional qualified demand, delayed readiness and changed scope. They are planning assumptions, not promises that future outcomes occur.

Map Work by Stage and Qualified Role

Add returned work and exceptions to the stage that performs them. Identify any shared reviewer whose work crosses stages. Do not double-count that person’s calendar as available capacity for each team.

NASA’s technical-planning guidance connects scope, workflows, resources, interfaces and changed constraints. This is a planning analogy, not a governing solar process or a source for solar task durations.

Compare Load and Capacity in Compatible Units

For a named role and period, a simple workload scenario can sum task quantities multiplied by supported hours per task, plus separately defined coordination or exception work. Use the company’s observations or explicitly labeled assumptions. Do not include an activity twice through both task time and an extra overhead factor.

Compare that load with hours actually authorized and usable for the same role, tasks and period after recorded duties and absences. Qualification, authority, equipment access and dependencies can restrict capacity even when time is open. A positive hour balance is not proof that a feasible construction schedule exists.

A Reproducible Hypothetical Role Scenario

These invented inputs demonstrate arithmetic only; they are not actual team performance or recommended task times.

Load is 20 × 1.5 + 10 × 0.5 = 35 hours. Available time after the named exclusions is 40 − 12 = 28 hours. The arithmetic gap is 7 hours. This says nothing about safe overtime, additional staffing, permit readiness, installation volume or a customer date. The same review role must not be counted elsewhere without reconciliation.

If the scenario removes five preliminary tasks, load becomes 15 × 1.5 + 10 × 0.5 = 27.5 hours, leaving 0.5 hours in this simplified role view. Other roles, shared work, timing and authorization still require review. Removing tasks is a scope scenario, not a claim that software saves their time.

Make Installation Readiness Its Own Gate

A signed agreement, completed design and ready-to-install project are different states. Track applicable evidence, equipment, site access, customer work, qualified releases, permits and utility conditions. Record expected dates as conditional assumptions with their source.

Use the installation-readiness review to test the package rather than assuming every released proposal becomes an install in the same period. More preliminary designs can enlarge the downstream queue when procurement or qualified review is constrained.

Model Cash Timing Without Calling It Revenue

Use the same scenario identities in the finance view. Record opening cash, dated expected receipts, planned payments, uncertainty and approved financing through the responsible finance process. Deposits, invoices, recognized revenue, profit, borrowing and available cash are distinct.

Separate hypothetical cash-period check: 20,000 opening currency units + 5,000 expected receipts − 8,000 payments = 17,000 closing units, assuming those events occur in the period. It does not establish adequate cash throughout the period: payments could precede receipts. It excludes taxes, borrowing, restrictions and every unlisted flow. Test event timing and downside collection through the finance owner before funding growth actions.

Keep this simple cash bridge separate from the broader solar business forecast. Capacity arithmetic cannot approve hiring, debt, customer financing or individual accounting treatment.

Copy-Ready Scenario Record

1. Scenario identity, observation date, periods, scope and decision owner.
2. Existing commitments and current readiness states.
3. Additional demand cohorts, definitions, maturity and assumptions.
4. Stage tasks, returns, exception categories and supported work-content inputs.
5. Qualified role availability, shared assignments, duties, leave and exclusions.
6. External gates, source dates, owners and conditional timing.
7. Load versus usable capacity by role and period, with checked units.
8. Dated cash events and finance-authorized constraints.
9. Candidate scope, sequencing, process, support or staffing actions.
10. Permitted customer commitments, unresolved conditions and reopen triggers.

Monitor actual movements against the same definitions. A changed queue, return reason or source assumption should lead to an explained successor scenario, not an overwritten historical baseline. NASA’s technical-assessment guidance discusses periodic review and indicators; it does not choose the company’s metrics or cadence.

Frequently Asked Questions

What does a solar growth-capacity model connect?

It connects defined demand states with stage tasks, returned work, qualified role capacity, external readiness and dated cash constraints. It should show limits by role and period rather than turn a lead count into an installation promise.

Can current monthly funnel counts be multiplied into a forecast?

Only with compatible definitions, cohorts and timing assumptions. This month’s proposals and installations may originate from earlier leads. Keep cohort transitions separate from current queues and include work from incomplete or unsuccessful opportunities.

Does a positive capacity balance establish a safe schedule?

No. The arithmetic must match qualified roles, tasks and periods, and actual execution depends on dependencies, sequencing, equipment, technical and safety processes, authority decisions and finance. Open time does not approve work.

Is projected closing cash the same as revenue or profit?

No. A cash bridge shows assumed dated inflows and outflows. Revenue recognition, accounting profit, borrowing, restricted cash and payments follow separate rules and review. Closing cash alone also hides timing shortages within the period.