Why Solar Deals Die After the Proposal: 6 Fixes

The proposal has been sent. It includes a system concept, modeled outputs, equipment, pricing, and a next-step button. The customer viewed an email, asked one financing question, and then stopped replying. The pipeline still says “proposal sent.” Sales calls it a dead deal. Nobody can say which decision is actually unresolved.

Silence is an event, not a diagnosis. It does not prove that the buyer rejected solar, chose another company, disliked the price, lost trust, missed the email, or needs more pressure. Those are possible interpretations, but they are not interchangeable facts. The useful task is to reconstruct the decision from records and, when permission allows, ask the customer a bounded question.

This page uses “die” to mean that an opportunity reaches an authorized lost or disqualified disposition after review. It does not claim that six causes explain every stalled proposal. The commercial solar proposals guide owns the document itself. The solar sales pipeline guide owns the wider stage model. This page owns the post-proposal diagnosis and next action.

This is desk-research sales-operations guidance, not consumer, financial, tax, lending, contract, legal, privacy, communications-consent, advertising, engineering, safety, equipment, utility, permitting, or investment advice. The company must define its permitted contact practices, stage rules, claim approvals, qualified review paths, and disposition authority. No close-rate benchmark, response cadence, buyer motive, savings result, or guaranteed fix appears here.

What does a stalled solar deal actually mean?

A stalled solar deal is an opportunity whose current buyer decision, active proposal version, unresolved evidence, responsible stakeholder, or next agreed event is not clear enough for a useful action. Define the state from the project record and direct buyer communication. Do not classify a deal as stalled solely from elapsed time, silence, email opens, or a salesperson’s intuition.

Separate event, interpretation, and disposition

Start with what the team can observe. A proposal was sent on a recorded date. A named person asked a question. A meeting was postponed. An expected document did not arrive. A permissioned follow-up received no response. These events belong in the record with their source and date.

Interpretation comes next: the rep believes the buyer may need a financing explanation, another stakeholder, or a revised option. That belief can shape a question, but it should stay labeled as an interpretation until the buyer or another responsible source confirms it.

Disposition is an authorized stage decision. Continue means there is a defined buyer decision and next event. Nurture means interest may remain but timing or readiness does not support active pursuit. Hold means a named dependency blocks progress. Lost records a supported outcome within company rules. Disqualified means the opportunity does not meet the accepted criteria. None of these should be a private synonym for “the rep has not heard back.”

The Department of Energy says there is no universal solar solution and provides questions homeowners may consider when deciding whether solar fits their situation (DOE homeowner solar guide). That is general consumer context, not evidence about this buyer. It supports a narrow reminder: the decision can involve fit questions that a generic follow-up cannot settle.

Define the decision before the next message

Write one sentence: “The named stakeholder is deciding whether to take the stated next step on proposal version X, subject to the listed questions and dependencies.” If the team cannot complete that sentence, more persuasion is premature. Reconstruct the decision first.

Check the original discovery record, stakeholder list, site evidence, usage inputs, active scenario, proposal version, assumption disclosures, financing or ownership discussion, questions, commitments, and contact preferences. Treat a missing record as missing. Do not copy a likely answer from another project.

Why can a solar proposal stop moving?

A proposal can stop moving when one of six decision controls is missing: a defined buyer decision, the necessary stakeholder, traceable proposal assumptions, a single current version, an authorized answer to commercial questions, or a mutually understood next event. These are diagnostic failure modes, not universal causes. Verify the applicable one from direct evidence before choosing a response.

Use six failure modes, each with a bounded fix

These modes can overlap. A missing spouse, co-owner, finance committee, facilities lead, or procurement reviewer may expose a comparison question. A requested revision may create two active versions. A financing question may reveal that the decision and authority were never defined. Diagnose the sequence without pretending one label explains the person.

Fix one: recover the decision

Do not begin with “Are you still interested?” Ask about the work the buyer is trying to complete. Which option are they evaluating? What must they understand before deciding whether to continue? Is the next choice a design review, a financing discussion, a site step, an internal approval, or a decision to stop?

If the buyer says the project is no longer active, respect the answer and apply the authorized disposition. If the buyer is unsure, offer a small set of clearly different next actions without manufacturing urgency. The rep’s job is to make the decision legible, not to force a commitment.

Fix two: bring the right stakeholder into the right question

A name on the record does not prove authority. Identify who owns property, budget, technical review, financing, contracting, operations, or household agreement as the situation requires. Ask the existing contact how each person should participate and what information they need.

Do not bypass the contact, expose confidential information, or add someone to marketing communication without the applicable permission and policy basis. A stakeholder map is a routing tool, not a license to pursue every person associated with the project.

The first solar appointment guide covers earlier discovery. After the proposal, note which stakeholder need was known before release and which emerged later. That distinction helps improve the process without blaming the rep or buyer.

Fix three: expose the assumption behind the question

“The savings look different” is not a complete issue. Identify the proposal version, usage record, tariff or rate input, production model, degradation or escalation input if used, ownership scenario, price basis, equipment, and comparison period that matter to the displayed result. Assign each input a source, date, state, and owner.

The sales rep should not settle engineering, production, financial, tax, lender, utility, incentive, equipment, contract, or legal questions outside their authority. A concise answer can still be useful: name what the proposal assumed, what evidence supports it, what remains conditional, and who must review it.

Fix four: restore one current version

A buyer cannot answer a clean question when the team is discussing different objects. Record one proposal id, scenario, layout, equipment set, price or commercial basis, source cutoff, issue date, and review state. Label any earlier version superseded, retained for comparison, or invalidated with a reason.

NASA requirements-management guidance discusses identifying and controlling requirements, bidirectional traceability, and managing changes to an established baseline (NASA requirements management). NASA does not prescribe solar sales. The useful analogy is limited: a customer request should trace to the proposal elements it changed, and the current output should trace back to its accepted inputs.

The solar sales-to-design handoff guide covers the upstream transfer. When a post-proposal revision enters, record the request, source, affected outputs, decision owners, regenerated artifacts, reviews, customer message, and old-version status. Do not update the layout while leaving price, modeled output, equipment, or narrative attached to another option.

Fix five: route commercial questions without improvising

Financing, tax, incentive, price, deposit, contract, lender, credit, insurance, and ownership questions may control the decision. They also cross authority boundaries quickly. Record the exact question and the document or proposal statement that prompted it. Identify who may answer, what evidence is required, and what the rep may say while review is pending.

The Consumer Financial Protection Bureau’s August 2024 issue spotlight describes risks involving how solar-specific loans are presented and structured and warns against presenting a federal tax credit as universally guaranteed (CFPB solar financing spotlight). This is U.S. consumer-finance background, not advice about a specific loan, tax position, lender, disclosure, or contract. It supports caution around confident financing shorthand.

Do not tell a buyer that an incentive is guaranteed, a payment will stay fixed, savings will cover an obligation, approval is certain, or a financing option is suitable unless qualified evidence and authority support the exact statement. Preserve the dated source and jurisdiction for any time-sensitive term.

Fix six: replace “checking in” with an agreed event

The next event should have a purpose, owner, and condition. Examples include a stakeholder review, an answer to a named question, delivery of a missing record, comparison of two defined options, a qualified financing discussion, a site decision, or an explicit disposition. The event can belong to the customer, the company, or both.

Do not fabricate a deadline to create movement. If the customer does not want an active next step but permits future contact, move the opportunity to the appropriate nurture state with a reason and re-entry condition. If contact is not permitted or the customer asks the company to stop, follow the applicable instruction, policy, and legal review.

How should a sales manager diagnose the stall?

Diagnose the stall in seven steps: freeze the active proposal record, restate the buyer decision, map stakeholders and authority, classify every open question, trace assumptions and revisions, select one permissioned response, and record the resulting next event or disposition. Keep observed events separate from interpretations so the team can review the decision without inventing buyer psychology.

Run the seven-step review

1. Freeze the record cutoff. Identify the active proposal, scenario, source inputs, issue date, revision state, communication history, and records included in the review.

2. Restate the buyer’s next decision. Write what the customer is deciding, for which site and option, and what a yes, no, hold, or request for change would mean.

3. Map stakeholders and authority. Name participants, absent decision-makers, authorized communicators, technical or commercial reviewers, and consent boundaries.

4. Classify the open questions. Separate customer preference, missing evidence, technical review, proposal clarification, financing, price, contract, timing, external dependency, and unknown motive.

5. Trace assumptions and changes. Connect every material question to the proposal version, input, source, model, price basis, equipment, term, or output it can affect.

6. Choose one bounded response. Ask a neutral clarification, supply a reviewed explanation, arrange the right stakeholder event, correct the version, route qualified review, or change the opportunity state.

7. Record the outcome. Capture the buyer statement or continued unknown, action owner, next event, permitted channel, date or trigger, and continue, nurture, hold, lost, or disqualified disposition.

Avoid scoring the rep’s persistence before checking whether the workflow gave the rep a clear decision. The solar lead qualification guide can help when the opportunity may never have met accepted fit and readiness criteria. A clean disqualification is more useful than keeping an unsupported probability alive.

Copy-ready stalled-deal diagnosis record

Use “unknown” rather than a blank when motive or status is not established. Use “pending qualified review” when the team has the record but lacks authority. Use “customer declined to answer” when that is the direct event. Specific states reduce the temptation to translate uncertainty into a convenient loss reason.

What should the follow-up message say?

A useful follow-up should name the proposal or decision, acknowledge the last confirmed context, ask one answerable question, offer a bounded next action, and respect the buyer’s communication preference. It should not assign a motive, repeat unsupported claims, create false urgency, or hide a changed assumption. The message is a request for direction, not proof of buyer intent.

Use a decision-shaped message

A reusable structure is:

I am following up on the named proposal version and your question about the named issue. The current record still shows the stated assumption or open review. Would it be more useful to review that question with the responsible person, compare the two defined options, pause until the named condition changes, or close the active follow-up? I will follow the contact preference you confirm.

Adapt the language to the relationship, channel, consent, company policy, and qualified guidance. Do not present a menu that hides a material option or pressures the buyer to continue. If the customer has already directed the company to stop, do not use a template to override that direction.

Digital.gov says public content should be written for its specific audience and discusses designing and testing content for audience understanding (Digital.gov audience guidance). That does not guarantee comprehension or consent. The sales application is modest: use words this customer can connect to the decision and test confusing explanations through the company’s approved process.

Keep claims consistent with the proposal

The Federal Trade Commission says advertising must be truthful and non-deceptive and that advertisers need evidence for objective claims (FTC advertising guidance). That is U.S. advertising background, not a legal conclusion about a follow-up. Qualified review must address the actual message, proposal, offer, audience, channel, disclosure, and jurisdiction.

Do not make the follow-up stronger than the evidence in the proposal. If production, savings, equipment, schedule, incentive, price, financing, approval, or another material input changed, update the controlled record and explain the change. A short message is not permission to erase a qualification.

How should missing information and exceptions be handled?

Handle missing information by naming the absent record, affected decision, current owner, permitted interim statement, and next review event. Handle conflicting information by preserving both sources until an authorized person resolves them. If consent, authority, safety, finance, tax, contract, legal, engineering, utility, equipment, or approval questions arise, hold only the affected claim or action and route qualified review.

Not every exception requires a full opportunity hold. A missing preference may block only one alternative. A technical question may hold a system claim while a stakeholder discussion proceeds. A consent restriction may stop outreach even while internal record cleanup continues. Match the hold to the authority and decision affected.

Illustrative example, not a customer case

A homeowner receives a proposal showing a base system and a storage alternative. After the presentation, the buyer asks whether a financing-related payment assumption depends on a tax outcome. The rep answers that the question requires the responsible finance and tax boundaries to be clarified and records the exact proposal version and statement.

The buyer then becomes quiet. The rep does not mark “price too high” or send a discount. The manager reviews the record and finds that another household decision-maker did not attend the presentation, the financing question remains open, and no next meeting was agreed. These are record gaps, not a proven motive.

With contact still permitted, the rep sends a brief message that identifies the proposal version, acknowledges the unresolved question, offers a qualified review with the relevant stakeholder, and makes pause or closure an acceptable response. The record remains unknown until the buyer replies or the company’s stage rule supports another disposition.

This hypothetical claims no response, sale, conversion improvement, savings, production, system suitability, financing suitability, tax result, price change, approval, or schedule. It shows how to move from an invented loss reason to a bounded request for direction.

Where can SurgePV support the stalled-deal review?

SurgePV can support the design and proposal record within its documented scope, including roof modeling, layout, shading, energy-yield and financial modeling, electrical-workflow support, material outputs, and proposal generation. It cannot determine why a buyer is silent, establish consent, approve claims, interpret contracts, select financing, make a sales disposition, or guarantee that a deal will restart or close.

Within the solar proposal workflow, a connected project record can help the team identify the active scenario, source inputs, assumptions, layout, equipment, modeled outputs, financial presentation, and current proposal. That makes version and question review more concrete. It does not make the underlying source true or the commercial answer authorized.

SurgePV results depend on source data, assumptions, equipment models, configuration, and review (SurgePV product source). Engineers, utilities, authorities, lenders, tax professionals, legal counsel, customers, and other responsible reviewers retain their decisions. Sales leaders retain ownership of permissioned communication, stage definitions, coaching, and disposition.

The right software question is not “Can it revive the deal?” Ask whether it can preserve the specific proposal object, assumption, revision, or output the buyer is discussing. Then name the human owner who verifies the evidence, approves the answer, and decides what happens next.

Frequently Asked Questions

When should a solar deal be marked as stalled?

Mark the opportunity stalled when the team cannot identify a current buyer decision and a mutually understood next event, not merely because a preferred number of days passed. Confirm the active proposal version, stakeholders, questions, dependencies, consent, and contact history. Keep company stage definitions explicit, and do not invent buyer intent from silence or email activity.

Why do customers stop responding after a solar proposal?

The project record usually cannot prove why a specific customer stopped responding. The decision may be unclear, a stakeholder may be absent, an assumption may need evidence, versions may conflict, commercial questions may remain open, or no next event may exist. Ask a bounded clarification with permission, then record the answer instead of assigning a psychological motive.

How often should a solar sales rep follow up?

There is no universal cadence in this guide. Use the contact permission, customer preference, channel rules, project urgency, promised next event, and company policy that apply to the opportunity. Each message should have a decision-relevant purpose. Stop, change channel, nurture, or close the record when consent, customer direction, policy, or qualified legal review requires it.

Should a sales rep send a discount to restart a solar deal?

Not before identifying the unresolved decision. A discount cannot repair missing stakeholders, unclear scope, inconsistent versions, unsupported assumptions, or financing questions. Any price change needs an approved cost and scope basis, documented authority, consistent proposal treatment, and appropriate contract, advertising, finance, tax, lender, and legal review. Never create false urgency or promise an outcome.

Can proposal software tell why a solar buyer went silent?

No. Software may record project activity and, within SurgePV’s stated scope, support design and proposal workflows. It cannot establish a person’s motive, confirm consent, decide what a customer should buy, resolve financing or contract questions, or guarantee a sale. People must interpret direct buyer evidence, approve communication, verify assumptions, and authorize each project decision.

A proposal-stage deal does not need a more dramatic story. It needs one current object, one decision, the right people, traceable questions, and an honest next event. When the evidence still says unknown, keep it unknown. That discipline improves the record even when the correct result is nurture, hold, loss, or disqualification.