The Solar Sales Pipeline: Stages, Exit Criteria, and Automations That Keep Deals Moving

A solar sales pipeline should do more than arrange opportunities in columns. It should give the entire company a shared definition of where each opportunity stands, what must happen next, and who owns that next step.

That matters more in solar than it does in a simple transactional sale. A project may need utility data, site information, a system design, financial assumptions, equipment choices, financing, a proposal, revisions, signatures, and an operational handoff before it becomes installable work. If the pipeline only records that a deal is “open,” it is not helping the team manage any of that complexity.

This playbook explains how to build a solar sales pipeline with meaningful stages, objective exit criteria, useful automation, and a clean handoff into design and operations.

Why generic sales stages break down in solar

Many sales pipelines begin with labels such as New, Contacted, Proposal, and Won. Those labels are easy to understand, but they are usually too broad to manage a real solar opportunity.

Consider a project sitting in Proposal. Has the utility bill been reviewed? Is the roof information trustworthy? Has a designer completed the system? Is pricing approved? Has the customer received the proposal? Did they open it? Are they waiting for a financing answer or a revision?

If several different realities share the same stage, managers cannot forecast accurately and team members cannot tell what should happen next. The result is usually a mixture of stale deals, repeated data entry, private spreadsheets, and follow-up that depends on individual memory.

Build the pipeline around customer and project decisions

A useful stage should answer a specific question. The opportunity advances when the answer becomes clear, not because somebody wants the board to look tidier.

• New inquiry: Has this opportunity been assigned and acknowledged?
• Contacted: Has meaningful two-way contact occurred?
• Qualified: Is there a real project worth designing?
• Information ready: Do we have the site, utility, and customer data required to prepare a credible design?
• Design and pricing: Is the proposed system technically and commercially ready?
• Proposal delivered: Has the customer received a complete proposal?
• Decision: Are the customer’s questions, revisions, financing, and contract steps actively being resolved?
• Closed: Was the opportunity won, lost, or deferred for a known reason?

This structure is only a starting point. A residential installer, commercial EPC, roofing partner, and battery specialist may use different stages. The important part is that every stage represents a distinct condition the team can recognize.

A practical solar sales pipeline

Define five rules for every stage

A stage name is not enough. Document these five rules so the whole team uses the pipeline consistently.

1. Entry condition: What must already be true before a record enters the stage?
2. Exit criteria: What evidence allows it to move forward?
3. Owner: Which role is responsible while the record is here?
4. Required information: Which fields, files, or decisions must be recorded?
5. Expected timing: How long should a healthy opportunity normally remain here?

Objective rules are especially important when sales, design, and operations share the same customer journey. A designer should not receive a project marked ready when the utility bill is still missing. Operations should not receive a signed deal whose equipment, site assumptions, or promised scope exist only in a salesperson’s notes.

Automate time, not judgment

Good automation removes predictable administrative work. It does not pretend every customer conversation can be reduced to a sequence.

Useful solar pipeline automations

• Send an immediate acknowledgement after a website or field lead is created.
• Assign the opportunity by territory, branch, project type, or round-robin rules.
• Create a call task when a new lead arrives.
• Remind the owner when no activity has occurred within the expected response window.
• Request missing utility or site information after qualification.
• Notify the salesperson when a proposal is opened for the first time.
• Stop an automated follow-up sequence when the customer replies or the stage changes.
• Create a revision task when the customer requests a different system or financing option.
• Start the operational handoff when the agreement is accepted.
• Create a future nurture task when a project is deferred rather than permanently lost.

Keep these moments human

• Determining whether the project is genuinely suitable for the customer.
• Explaining production, savings, financing, storage, and technical tradeoffs.
• Responding to objections or circumstances the automation did not anticipate.
• Approving material pricing or scope changes.
• Confirming that the final agreement matches what the company can deliver.

The best automation makes a thoughtful salesperson more consistent. It should never make the customer feel trapped inside a campaign that no longer reflects the conversation.

Use activity and age to expose stalled opportunities

A deal does not become healthy because it still appears on the board. Every open opportunity should have a recent activity, a next action, and an owner.

Track how long records remain in each stage and how long it has been since the last meaningful action. A proposal that was sent yesterday is different from one that has been untouched for six weeks, even if both occupy the same column.

Useful review filters include:

• New leads without a first contact attempt.
• Qualified opportunities still missing required documents.
• Designs waiting longer than the normal turnaround.
• Delivered proposals without a scheduled follow-up.
• Open opportunities with no recent activity.
• Deals repeatedly moved backward without a recorded reason.
• Deferred projects whose future contact date has arrived.

Forecast from evidence, not optimism

Pipeline value is useful only when stages are used consistently. If salespeople move weak opportunities forward to improve the appearance of their pipeline, every forecast built on those stages becomes fiction.

Start with actual conversion history. Measure how often opportunities in each stage eventually close, how long they take, and whether results differ by branch, salesperson, lead source, project type, or financing method. Use that evidence to set stage probabilities and expected close windows.

Forecasting should also distinguish between total system price, expected contract value, and any revenue measure the business actually uses. Pick one definition and apply it consistently.

Preserve lead source and referral context

A good pipeline records where the opportunity came from at the moment of capture. Website form, paid campaign, referral, event, partner, repeat customer, and field activity should not be collapsed into “internet” or “other.”

Source data lets the company compare lead quality, not just lead quantity. A channel that creates fewer inquiries may still produce more qualified projects, larger contracts, or shorter sales cycles.

Keep the original source intact even if the customer later interacts with another campaign. First-touch and recent-touch context answer different questions, and both can be useful.

Design the operational handoff before the first sale

Closed Won should not be a storage bin. It should be the point where a complete project enters a defined installation or fulfilment workflow.

Agree on the handoff requirements with the people who receive the work. A useful checklist may include:

• Signed agreement and accepted terms.
• Final system design and selected option.
• Customer and site contact details.
• Utility account and consumption information.
• Equipment, racking, storage, and electrical assumptions.
• Site photos, survey files, measurements, and known constraints.
• Financing status, deposit, and payment schedule.
• Promises, exclusions, and customer-specific commitments.
• Permit, interconnection, and incentive requirements.
• The next customer communication and its owner.

When the sales record, design, proposal, files, and activity history remain connected, the operations team can verify the handoff instead of reconstructing the sale.

Measure the pipeline as a system

Closed revenue matters, but it arrives too late to explain where the process is failing. Review the leading indicators as well.

• Speed to first response: How quickly does a new inquiry receive a real response?
• Contact rate: How many inquiries become two-way conversations?
• Qualification rate: How many contacted leads become credible projects?
• Design turnaround: How long does a qualified project wait for a proposal-ready design?
• Proposal follow-up coverage: How many delivered proposals have a scheduled next action?
• Stage conversion: Where do opportunities most often stop or leave?
• Sales-cycle length: How long do won projects take from inquiry to acceptance?
• Handoff completeness: How often does operations need to chase missing information after the sale?
• Source quality: Which channels create qualified projects and signed work?
• Loss reasons: Why are real opportunities not moving forward?

Common pipeline mistakes

• Too few stages: Important work becomes invisible inside broad labels.
• Too many stages: The board turns into a detailed task list nobody maintains.
• Subjective stage movement: Records advance because someone feels positive rather than because an event occurred.
• No next action: The team knows where the deal is but not what happens next.
• Automation without exit rules: Customers keep receiving messages after replying, declining, or signing.
• Design outside the customer record: Technical changes and commercial promises drift apart.
• Won deals without a handoff standard: Operations inherits missing data and preventable surprises.
• Lost deals without reasons: The company cannot distinguish pricing, timing, fit, financing, competition, or poor follow-up.

How Powerlily connects the pipeline

Powerlily’s solar CRM and workflow tools connect lead capture, configurable pipelines, activity, automation, design, proposals, messaging, branches, and operational handoffs to the same customer and project record.

That connected model matters because pipeline stages are not isolated labels. A form submission can create and route the lead. A stage change can create a task, schedule a reminder, send an appropriate message, or start another workflow. The design and proposal remain attached to the opportunity, and an accepted project can move into installation without rebuilding the customer somewhere else.

For the wider operating model, read Run your solar EPC on Powerlily. You can also explore the complete Powerlily feature set or review pricing.

Start with one honest pipeline

Do not begin by modelling every exception your company has ever encountered. Build the main sales path, define its exit criteria, assign ownership, and run real opportunities through it. Review where the team hesitates, where information goes missing, and where customers wait.

Then improve the process deliberately. A strong solar sales pipeline is not the board with the most columns. It is the one that makes the next responsible action clear and carries a complete, trustworthy project into operations.