Solar Project Lifecycle: The Complete Workflow From Lead to Cash

A solar project is not finished when the system reaches PTO. It is finished as a business transaction when the company has delivered the agreed work, created the right billing event, collected what is due, closed the project record, and handed the installed system into service.

That is the difference between lead to PTO and lead to cash. Lead to PTO explains delivery. Lead to cash connects sales, project execution, cost, billing, receivables, collection, closeout, and the next phase of the customer relationship.

The practical goal is simple: every important project event should change the right operational and financial state without another team rebuilding the story from email, spreadsheets, or memory.

What does lead to cash mean in a solar project lifecycle?

Lead to cash is the complete business workflow from the first qualified sales opportunity through contract, project delivery, invoicing, collection, and closeout. For a solar installer, that workflow also has to carry site data, design decisions, permit and utility approvals, materials, field evidence, inspections, PTO, job cost, and customer commitments.

The phrase matters because a project can be operationally far along and financially unfinished. Installation can be complete while an inspection is still open. PTO can be received while the final invoice has not been issued. An invoice can be posted while the payment is still outstanding. Those are different business states.

A useful lifecycle therefore does not ask only, “What stage is the project in?” It also asks, “What was proven at this stage, what is allowed to happen next, what cost or commitment changed, and what financial action became possible?”

Why should the lifecycle extend beyond PTO?

PTO is one of the most important milestones in many distributed-solar workflows because it confirms the utility has allowed the system to operate. But PTO is not a universal definition of commercial completion. Contracts, financing arrangements, billing schedules, customer obligations, and closeout requirements vary.

That means the operating system should never assume that “PTO received” automatically means “project paid.” For one project, PTO may release a final invoice. For another, billing may depend on installation, inspection, a financing milestone, customer acceptance, or another contractual event.

The safer model is to treat PTO as a verified operational event. The applicable contract or billing rule then decides what financial action follows.

Think of the lifecycle as three connected rails

A complete solar project moves on three rails at the same time. The first is the commercial rail: lead, opportunity, proposal, contract, approved changes, and customer commitments. The second is the delivery rail: survey, design, permits, interconnection, procurement, installation, inspection, PTO, and closeout.

The third is the cash rail: deposits, purchasing commitments, job costs, invoice-ready milestones, invoices, receivables, collections, credits, and financial closeout. Problems appear when one rail advances without the others.

For example, sales changes equipment but procurement still buys from the old scope. The field completes work but finance does not receive the evidence required for billing. PTO arrives but the receivable remains invisible to operations. A lead-to-cash system keeps those states connected without pretending they are the same thing.

What is the complete solar project lifecycle from lead to cash?

There is no single stage sequence that fits every residential, commercial, community-solar, or EPC project. AHJ rules, utility processes, project type, contract structure, financing, equipment, and company policy can change the order or allow work to overlap.

Still, a practical control map can follow nine major business transitions. The point is not to force every project into identical dates. It is to define what becomes true before the company treats the project as ready for the next business state.

1. Lead capture and qualification: decide whether this opportunity should consume delivery effort

The lifecycle begins before there is a project. A lead becomes operationally meaningful when the company has enough information to decide whether the opportunity deserves the next level of effort. That may include customer and site identity, service territory, property or facility information, utility data, basic project fit, ownership or decision-maker information, and financing or commercial constraints where relevant.

The financial question at this stage is not invoice readiness. It is acquisition efficiency and exposure. How much time and money is the company spending on opportunities that never become viable projects? That is why qualification belongs in the lifecycle instead of being treated as a separate marketing activity.

NREL’s residential-solar research describes customer acquisition as a distinct phase that includes lead generation, initial contact, sales work, early site assessment, proposal development, negotiation, and contract signing. The same report shows why pre-install work has real cost even before equipment reaches a site.

2. Proposal and contract: create the commercial baseline

A signed contract should create more than a “won” sales status. It should create a controlled commercial baseline that delivery and finance can understand. The baseline may include sold scope, system configuration or referenced design, price, payment schedule, financing path, customer commitments, exclusions, assumptions, approved documents, and any conditions that still need verification.

This is where the cash rail first becomes concrete. The company now knows which deposits or milestones may become due, what customer or financing conditions matter, and what commercial changes will require formal approval later.

A proposal should not silently become a field-ready technical record. Preliminary design assumptions may still need final survey, engineering, code review, or utility validation after contract. The lifecycle should preserve what was sold while making unverified conditions visible.

3. Contract to execution-ready project: convert a sale into controlled work

The sale-to-project transition is where the company decides that the job is ready to enter delivery. That does not mean every permit, material, or install condition is already satisfied. It means the project record has enough validated commercial information, ownership, documents, and next actions for operations to accept responsibility.

This is deliberately different from a handoff checklist. The handoff question is what one team must transfer to the next. The lifecycle question is broader: what business record exists now, who owns it, which baseline governs it, and what financial exposure begins when execution starts?

Once the project enters execution, labor, engineering, permit fees, purchasing commitments, subcontractor cost, and other job costs can start accumulating. Finance should not have to wait until the final invoice to understand that exposure.

4. Survey, design, permitting, and interconnection: turn assumptions into approved project facts

After contract, the project moves from sold assumptions toward buildable and approvable facts. Final site data, engineering where required, design revisions, equipment decisions, permit packets, AHJ corrections, utility applications, and interconnection requirements all belong to this control phase.

DOE identifies design, permitting, installation, interconnection, financing, customer acquisition, supply-chain activity, inventory control, and operating overhead among solar soft-cost areas. In other words, a large amount of business work occurs around the hardware itself, and inefficient process adds cost.

DOE also notes that permitting and inspection requirements vary among local governments and that administrative errors and backlogs can delay projects. That is why this phase should track both external waiting and internal response work rather than hiding everything under one “permitting” label.

The cash implication is often indirect but important. Costs are accumulating, customer expectations are aging, equipment decisions may create commitments, and later billing milestones may depend on approvals completed here.

5. Procurement and install readiness: turn an approved project into executable work

Procurement should follow the current approved basis, not the version somebody remembers from the sale. The team needs to know what equipment is required, what has been ordered, what is committed, what is received, what is allocated to the project, and whether substitutions change design, permit, utility, cost, or customer scope.

Install readiness then combines more than a crew date. The company defines the conditions that must be true before a project is allowed to consume field capacity. Depending on the job, those conditions may include permit status, current field plans, material availability, site readiness, customer access, prerequisite work, qualified crew capacity, and open exceptions.

The financial rail becomes more visible here because committed purchasing cost and project allocations can be compared with the sold and budgeted basis before the installation is complete.

6. Installation: convert scheduled work into verified completion evidence

Installation is not just a stage change from “scheduled” to “complete.” The field should create evidence that other teams can use. Required photos, checklist completion, installed equipment, serial information, time, material usage, issues, punch items, substitutions, and completion signoff should update the project record as the work happens.

This is where many companies create unnecessary finance delay. The crew knows the work happened, the project manager knows the work happened, but finance cannot verify that the applicable billing condition is satisfied.

A stronger lifecycle defines the operational event and its evidence. Once the event is verified, the system can mark the relevant milestone as invoice-ready if the contract allows it. That is different from automatically sending an invoice.

7. Inspection and PTO: close regulatory work without losing the financial thread

After installation, the project may still require local inspection, corrections, utility review, meter work, interconnection completion, or PTO before the agreed delivery path is complete. DOE describes permitting and inspection as steps that occur before a rooftop array can receive permission to interconnect and operate, while exact rules and fees vary by jurisdiction.

This stage can create long periods where the physical work looks finished but the business is still waiting. A clean lifecycle shows who controls the next event, what evidence has been received, what internal follow-up is due, and whether the waiting state blocks a customer commitment, final billing, closeout, or cash.

The 2026 SolarAPP+ performance review offers a useful example of how much one workflow stage can affect cycle time. In 2024, 861 installers submitted 37,393 permits through SolarAPP+, and a typical participating project was permitted and inspected 12 business days sooner than projects using traditional processes. Those are SolarAPP+ results, not a Solar1 performance claim.

8. Billing and collection: separate work complete from cash collected

This is the step that lead-to-PTO maps often understate. A project can be operationally complete and still have unfinished financial work. The lifecycle should distinguish at least four states: milestone not yet billable, milestone verified and invoice-ready, invoice issued and receivable open, and payment collected.

Those states should not be collapsed into one “paid” checkbox. Finance may need to review the contract, change orders, credits, taxes, financing documentation, customer disputes, or other conditions before an invoice is correct. Collection can then follow its own payment terms and follow-up process.

The operating benefit is that finance does not have to ask the project team whether something happened. The verified project event already exists, and the financial workflow can act on the evidence appropriate to that project.

9. Closeout and service: turn the finished job into a managed installed asset

Lead to cash should not mean the company forgets the customer the moment payment arrives. Closeout should confirm that the project record, financial state, customer handoff, warranties, installed equipment, final documents, and service history are ready for the next phase.

For some companies, service is a separate business line. For others, it is mainly warranty response and customer support. Either way, the asset should not be reconstructed from old project folders years later.

The lifecycle therefore changes identity over time: first a lead, then a commercial opportunity, then an execution project, then an installed system with a financial and service history.

What happens when scope changes in the middle of the lifecycle?

A lifecycle map is useful only if it can survive change. Solar projects change. Customers add storage, site conditions differ from the initial assumption, an AHJ requests a revision, equipment availability changes, a utility adds a requirement, or the field discovers something that needs a commercial decision.

The wrong response is to update one department’s record and let the project continue. A meaningful change should reopen the affected control points. The current design may need review, procurement may need to pause, the permit basis may change, customer approval may be required, job cost may move, and the billing basis may need an approved change order.

The lifecycle should preserve both the original baseline and the approved change. That is how the company can later explain why scope, cost, schedule, or margin moved.

How should finance know when a solar milestone becomes billable?

Do not make finance infer billability from a project stage name. “Installed,” “inspection passed,” or “PTO received” may be important evidence, but the applicable contract decides whether that event creates a billing right.

A better model has three parts: the contractual billing rule, the verified operating event, and the finance review. When the rule and evidence match, the project creates an invoice-ready state. Finance can then review exceptions and issue the invoice without chasing operations for basic proof.

This keeps operational truth and accounting judgment connected without making them identical. It also avoids a risky shortcut where software assumes every project uses the same milestone schedule.

What should owners measure across the lead-to-cash lifecycle?

Owners do not need fifty lifecycle KPIs. They need enough measures to see where demand, delivery, cost, and cash are separating. Useful measures include qualified-to-contract conversion, contract-to-execution acceptance, stage cycle time, work in progress, install-ready backlog, correction or rework frequency, committed cost against project baseline, and time from verified milestone to invoice.

Finance-facing measures can include invoice-ready value not yet invoiced, open receivables by aging bucket, time from invoice to collection, approved change orders not reflected in billing, and projects that are operationally closed but financially open.

The key is to preserve definitions. “Ready to invoice” must mean the same thing every week. “Collected” must mean cash actually received, not simply an invoice sent. “Project closed” should not hide an unresolved receivable or missing closeout requirement.

A simple way to measure cash stuck in the workflow

The project plan for this article suggests a useful internal calculation: delayed projects multiplied by the average applicable milestone amount. I would make it more precise by measuring projects whose contractual milestone is already verified but whose financial action is still pending.

For example, suppose eight projects have completed and documented a milestone worth an average of $12,500, but the invoices have not yet been issued. That creates $100,000 of invoice-ready exposure. It is not lost revenue, not collected cash, and not automatically recognized revenue. It is a management queue showing where completed operational work has not yet become an invoice.

The same logic can be applied later in the cash cycle by separating invoice-ready exposure from open receivables. That tells the owner whether the delay is inside the operations-to-finance handoff or inside collection.

Where do lead-to-cash workflows usually break?

They usually break where one team believes its work is finished but the next business state has not actually been created. Sales marks the deal won but operations cannot accept it. Permit approval arrives but install readiness is never recalculated. The crew finishes but billing evidence is incomplete. PTO arrives but nobody checks the final invoice condition.

Those failures look like different departmental problems, but they share one root cause: the project stage changed without the required record, evidence, ownership, or financial consequence moving with it.

That is why a complete lifecycle is more than a horizontal timeline. Every transition needs a release condition and a consequence.

How is Solar1 being designed around lead to cash?

Solar1 is being built as a complete solar-specific ERP for installers and EPC companies. The product direction is to connect the commercial, project, material, workforce, and financial records that define the lifecycle rather than treating PTO as the point where operational visibility ends.

The intended model begins with lead and sales records, carries accepted commercial scope into project execution, connects survey and design workflow with permitting and interconnection, links procurement and inventory to project readiness, captures field evidence, follows inspection and PTO, and connects verified milestones to finance, job cost, billing, receivables, closeout, service, and warranty history.

Specialist services can still integrate where they provide a genuinely specialized capability, such as advanced design, aerial imagery, financing, payments, utility data, or monitoring. The core business records and ownership should remain connected so the installer does not have to rebuild the project at every boundary.

Solar1 is still under development. This describes the operating model the product is being designed around, not a claim that every lifecycle workflow, automation, integration, billing rule, or service capability described here is currently production-ready.

Do not let PTO hide unfinished business

PTO is a major project milestone. It is not the same thing as a complete business lifecycle.

A strong lead-to-cash workflow shows how the opportunity became a contract, how the contract became controlled delivery, how delivery changed cost and billing readiness, how verified milestones became invoices, how invoices became cash, and how the finished job became a serviceable installed asset.

If those transitions are visible, the owner can see not only where projects are stuck, but where money is stuck and why.

Use the Lead-to-Cash Workflow Map to mark the release event, owner, evidence, cost impact, and financial state at every major step in your own process. Then bring that map into a Solar1 demo and test whether the system can follow one real job all the way through cash and closeout.