Before-You-Discount Solar Deal Checklist

The fastest way to lose control of a solar discount is to discuss the percentage before anyone has named the problem. A buyer says the proposal is expensive. The representative asks for room. A manager approves something in a message thread. The quote changes, but the scope, production model, financing scenario, delivery promise, and customer explanation do not receive the same review.

A before-you-discount solar deal checklist slows down only that dangerous part. It does not require a committee for every negotiation. It gives the commercial owner enough evidence to distinguish a useful concession from a cheaper version of the same unresolved deal.

This guide is an operating framework, not legal, advertising, accounting, tax, finance, lending, contract, procurement, engineering, safety, utility, permitting, insurance, employment, or commission advice. Discount authority, price representations, customer wording, commercial effects, and live agreements require review by the qualified owners for the company and jurisdiction.

The post-site-visit deal-risk checklist governs project evidence after field work. This article begins later and narrower: the team has an active offer, a buyer has asked for price movement, and an authorized person must decide what, if anything, should change.

What should happen before a solar deal is discounted?

A solar discount decision should begin with a documented reason, not a percentage. Confirm the current scope, price basis, buyer’s stated barrier, comparison set, decision authority, delivery effect, approval owner, exchange requested, and customer wording. If a lower price does not remove the verified barrier or would hide a scope mismatch, do not release it.

Start by freezing the offer under discussion. Name the quote identifier, proposal version, equipment basis, system boundary, modeled outputs, included work, exclusions, payment structure, assumptions, contract state, and validity condition. Without that baseline, “take something off” has no stable meaning. One person may think the request affects seller margin only while another quietly removes work, changes equipment, changes a financing input, or narrows support.

Write the buyer’s objection in the buyer’s words, then separate the statement from the team’s interpretation. “Your number is higher” is a statement. “The buyer needs this specific reduction” is an interpretation and may be wrong. The comparison might include different equipment, roof work, storage scope, electrical work, warranty terms, financing assumptions, production boundaries, service commitments, or exclusions.

The unequal quote comparison guide provides the deeper normalization workflow. The discount record should link to that comparison rather than copying a vague conclusion such as “competitor is cheaper.”

Treat a discount as one possible commercial action among several. The action might be to explain evidence, correct an error, offer a different valid scope, change the payment structure through an authorized route, clarify an exclusion, replace an unsupported option, or stop the pursuit. A lower price is appropriate only when it belongs to the diagnosed problem and the company can still deliver the resulting promise.

In the United States, the eCFR API copy of 16 CFR Part 233 distinguishes genuine former-price comparisons from fictitious reference prices created to make a later bargain appear real. That guidance does not decide a private solar quote, and other jurisdictions have their own requirements. It does establish an important review question: can the company substantiate any “was,” “now,” “saving,” or comparative price language it intends to show?

Do not create a reference price merely to make the concession look larger. Do not call a corrected error a special discount. Do not claim the buyer is receiving a limited bargain when the limitation is not genuine. A qualified advertising and legal reviewer should approve the actual language and evidence.

Is the buyer really objecting to price?

Treat a price objection as a question to diagnose. Ask what the buyer is comparing, which outcome feels unsupported, whether the concern is total price or payment structure, what changed since the quote, who can decide, and what evidence would resolve the concern. Do not assume that every request for movement is solely about price.

A price statement can point to several different decision barriers. The buyer may not understand why two scopes differ. The modeled outcome may feel uncertain. A payment arrangement may not fit an approved budget process. A decision-maker may be missing. A roof, electrical, tariff, load, equipment, contract, or schedule question may still be open. The sponsor may need a comparison record for someone else.

DOE’s homeowner solar guide says there is no universal solar solution and discusses property suitability, production estimates, installer selection, contracts, and financing questions. The source is United States consumer guidance, not a commercial discount policy. Its narrow value here is that one apparent price conversation can contain several distinct solar decisions.

Use questions that reveal the mechanism:

• “Which figure or term are you comparing, and which proposal versions are involved?”
• “What appears equivalent between the offers, and what remains unclear?”
• “Is the decision blocked by total price, cash timing, approved budget, financing structure, or confidence in the outcome?”
• “Which assumption, scope item, or customer claim would need evidence before the current price makes sense?”
• “Who else must accept the technical, financial, procurement, legal, or ownership basis?”
• “If the price changed but everything else stayed the same, what decision could you make that you cannot make now?”

The final question is especially useful. If the buyer cannot name the decision unlocked by a lower price, the team does not yet have a discount case. That does not mean the objection is insincere. It means the next useful action is diagnosis.

The value-before-price framework helps a team explain the evidence and operating work behind an offer. Use it to make the current scope understandable, not to perform superiority or create an unsupported return claim.

If the team made an error, correct it plainly. A mistaken quantity, duplicated item, obsolete price input, or incompatible scope needs a controlled correction, not a story about a special concession. The customer communication should distinguish correction, scope revision, and discretionary discount because each has a different reason and approval trail.

The FTC’s advertising guidance says United States advertising must be truthful and non-deceptive and objective claims need evidence. It does not approve any solar statement. Apply the boundary to every reason offered for the new price. “This guarantees the project will pay back sooner,” “this approval ends tonight,” or “this option always produces more” requires evidence and qualified review, not sales confidence.

How should the team test a discount request?

Test a requested concession against the active quote, buyer record, comparable alternatives, approved commercial policy, delivery requirements, and every customer-facing claim. Separate a real price change from a scope change, financing question, timing condition, or unsupported promise. The decision should show what the seller gives, what it receives, who approved it, and when it expires.

Use this nine-step workflow:

1. Freeze the quoted baseline. Preserve the current quote, proposal, design, financial scenario, equipment basis, bill of materials, contract draft, exclusions, and customer communication. Assign one version id.
2. Capture the request without interpretation. Record who requested movement, the exact language, channel, date, stated comparison, requested timing, and person expected to decide.
3. Diagnose the decision barrier. Classify the open question as price, affordability, payment structure, scope, comparison, evidence, trust, timing, authority, or another named condition. Preserve multiple conditions when they coexist.
4. Normalize the alternatives. Compare included work, technical basis, equipment, modeled outputs, warranties, support, commercial terms, exclusions, and unresolved risks. Do not infer equivalence from system size or total price alone.
5. Generate permitted responses. Consider explanation, correction, re-scope, option change, authorized payment route, additional evidence, changed sequencing, concession, deferral, or exit. Remove any response the company cannot substantiate or deliver.
6. Test commercial and delivery effects. Route cost, margin, commission, procurement, labor, engineering, support, schedule, contract, tax, finance, and cash questions to their authorized owners. This article supplies no threshold.
7. Define the exchange and conditions. State what the customer or seller will do, which authority accepts it, what proves completion, when the offer expires, and what happens if the condition does not occur.
8. Approve exact customer wording. Review every price comparison, urgency statement, savings statement, production statement, schedule statement, and reason for the change. Remove anything unsupported.
9. Create and release a successor version. Update all affected records, preserve the original, obtain required approvals, communicate the boundary, and verify that the customer received the intended version.

NASA’s decision-analysis guidance applies to NASA systems engineering. It discusses alternatives, criteria, evaluation methods, evidence, and recommendations. It does not validate a solar concession process. The transferable discipline is to compare permitted actions against declared criteria rather than treating the requested discount as the only alternative.

Set criteria before debating an amount. The criteria might include whether the action resolves the verified barrier, preserves deliverable scope, remains within delegated authority, can be communicated truthfully, keeps customer records consistent, and has a defined validity condition. Company-specific cost, margin, cash, tax, and commission criteria require the actual records and authorized reviewers.

An exchange must be real, permitted, and observable. “Discount for a decision today” is weak when the decision path still depends on another owner, contract review, financing, site evidence, or external approval. A more precise exchange might concern a reviewed scope selection, a defined procurement step, an accepted meeting with the authorized decision owner, or another action the parties can legitimately control. Legal and contract owners must approve the live form.

Avoid manufactured urgency. Expiration can be appropriate when tied to a genuine equipment quote, capacity boundary, commercial policy, or other substantiated condition. Record its source. Do not invent scarcity or imply control over a utility, authority, lender, insurer, manufacturer, or tax outcome.

What should the discount approval record contain?

A discount approval record should preserve the original quote, requested change, diagnosed barrier, alternatives considered, scope and cost effects, approving authority, customer exchange, communication text, validity condition, and affected proposal versions. It should also state which records must be regenerated or re-reviewed so an old layout, financial scenario, or contract term does not remain attached to the new price.

The record should be usable by someone who did not attend the call. “Manager approved the requested movement” does not identify the active scope, price basis, reason, exchange, authority condition, or customer wording. It also hides whether the number represents a correction, a removed item, a financing change, or a discretionary concession.

NASA’s configuration-management guidance discusses baselines, control of changes, version distinction, and consistency between a product and its information. The source governs NASA work, not private proposals. Its useful analogy is strict: preserve the offer baseline and create a controlled successor when price, scope, or a dependent record changes.

Use separate fields for the requested action and approved action. A buyer may request one reduction while the approver authorizes a different scope, condition, or option. The customer must receive the approved version and its honest explanation, not a hybrid assembled from the request and an old proposal.

Copy-ready discount decision record

Store confidential internal economics separately from the customer-visible explanation. A buyer needs clear scope, price, assumptions, conditions, and changes. The buyer does not automatically need internal margin, commission, probability, negotiation notes, or employee approvals. Access, retention, export, and disclosure rules require company-specific review.

NASA’s interface-management guidance addresses responsibilities, information, and changes across interfaces in NASA work. Applied only as a process analogy, it suggests naming who requests, analyzes, approves, communicates, and implements the change. A discount can fail even when each participant performs their own task if the handoff between them is undefined.

Use explicit handoff states:

• Captured: the request and active baseline are preserved.
• Diagnosed: the team has named the barrier and comparison evidence.
• Reviewed: authorized owners have evaluated commercial, delivery, claim, and record effects.
• Approved with conditions: the exact action, authority, exchange, wording, and validity boundary are accepted.
• Released: the successor records were generated, checked, and delivered.
• Accepted, expired, withdrawn, or superseded: the decision has a closed outcome and no obsolete offer remains active.

Do not mark a discount approved when only the amount has been discussed. Approval is incomplete until the responsible owners accept the resulting scope, claim, delivery boundary, and customer wording.

The unplanned-discount governance guide examines the wider sales-system issue. Keep this record focused on the live decision so policy learning can later use accurate cases rather than anecdotes.

When should the seller refuse, defer, or redesign?

Refuse or defer a discount when the requested comparison is misleading, the buyer’s barrier remains unknown, the concession would breach approved policy, the scope cannot support delivery, a customer-facing claim lacks evidence, required authority is absent, or the price change would leave dependent records inconsistent. Re-scope only when the buyer understands exactly what leaves the offer.

Refusal is not a performance of confidence. It is a controlled decision that the proposed action cannot be supported under the current evidence and authority. State the reason plainly, name what could reopen review, and avoid blaming the buyer. A clean exit is better than an approved-looking concession attached to an undeliverable promise.

Defer when the issue may become decidable after a specific record or owner arrives. Examples include an unresolved competing scope, missing site evidence, an unconfirmed equipment basis, an unavailable signatory, a financing question awaiting an authorized provider, or a contract term awaiting qualified review. State what work may continue and what output must pause.

Redesign or re-scope only as a real project change. Removing equipment, support, electrical work, storage, monitoring, roof work, warranty coverage, production assumptions, or another deliverable is not a discount if the buyer receives less. The new proposal should show what changed and how modeled and commercial records were re-reviewed.

Illustrative example, not a customer case, price benchmark, savings result, close-rate claim, contract, or outcome. A commercial buyer says another offer is lower and asks the representative to match it before an internal meeting. The representative first captures both proposal versions and discovers that the competing total excludes an electrical item and uses a different equipment and service boundary.

The team does not call the difference a discount opportunity. It prepares a normalized comparison, asks which scope the buyer wants evaluated, and routes the electrical boundary to the responsible technical and commercial owners. The buyer selects a narrower alternative for review. The company issues a successor design basis and proposal rather than placing a “special reduction” on the original scope.

If the buyer instead wanted the original scope at a lower price, the commercial owner could evaluate that request under the company’s actual authority and economics. Nothing in this example supplies the answer. The value is the sequence: compare, diagnose, choose the valid action, govern the change, and communicate it accurately.

Software can help keep affected project records visible. For this workflow, SurgePV’s verified solar design platform covers 3D roof modeling and solar array layout, plus shading, energy-yield, and financial modeling. The repository registry also lists electrical workflow support, bill-of-materials output, and proposal generation. Results still depend on source data, assumptions, equipment models, configuration, and responsible review.

Those functions can help a team inspect whether a scope change affects layouts, modeled outputs, material records, electrical work, financial scenarios, and proposal content. SurgePV does not set a company’s price, cost, margin, discount authority, commission, contract, tax position, customer decision, or permitted claim. It cannot make an unsupported concession responsible.

The final release test is simple: can a reviewer explain what problem the approved action solves, what changed, what stayed constant, who had authority, which evidence supports the customer message, and which version is now current? If any answer is missing, the discount is not ready for the customer.

Frequently Asked Questions

Who should approve a solar deal discount?

Use the authority defined in the company’s current commercial policy. The approver should understand the active scope, price basis, delivery effect, customer claim, requested exchange, and any downstream records that must change. A sales representative should not infer authority from urgency, prior exceptions, or a manager copied on an email.

Should every solar price objection lead to a discount?

No. First identify whether the barrier concerns total price, payment structure, quote comparability, scope uncertainty, trust, timing, decision authority, or missing evidence. A lower price only addresses some of those conditions. If the request would leave the real barrier untouched, choose the evidence, scope, option, or decision step that addresses it directly.

Can a solar company trade a discount for a faster signature?

Only an authorized owner should approve any exchange, and the live contract and applicable law need qualified review. A target signature date is not valuable if required technical, finance, procurement, legal, or customer decisions remain unresolved. Record the exchange precisely, avoid pressure or unsupported urgency, and never imply that an external approval is guaranteed.

What records should change after an approved discount?

Update the controlled quote and every dependent proposal, financing scenario, contract draft, approval record, forecast input, commission basis, procurement assumption, and customer communication that uses the price. Recheck technical scope and delivery commitments. Preserve the prior version and identify the approval, effective condition, expiration, and reason for the successor.

Where can SurgePV support the discount review workflow?

SurgePV can support current roof, layout, shading, energy-yield, financial, electrical, bill-of-materials, and proposal records used to test scope changes. It does not set prices, margins, authority, legal terms, or customer decisions. Commercial owners must approve concessions, and qualified reviewers remain responsible for finance, contracts, claims, engineering, utilities, and jurisdictions.