Back to Blog
solar sales30 min read

How to Compare Solar Proposals Fairly

Help homeowners compare solar proposals by normalizing scope, design, assumptions, ownership, evidence, and questions without smearing another provider.

Akash Hirpara

Written by

Akash Hirpara

Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Quick Answer

Help a homeowner compare solar proposals by first defining their priorities, then normalizing site inputs, system scope, equipment, production models, price boundaries, ownership, financing, warranties, schedule, and exclusions. Describe only what each document shows, ask the other provider to clarify its own offer, label unresolved differences, and let the homeowner choose under qualified review.

A homeowner puts two solar proposals on the table. One leads with a lower total. The other shows a different array, equipment list, production model, financing path, and service boundary. The easy sales move is to circle the lower competitor number and say, “They left things out.” That sentence may be wrong, and it does not help the homeowner find the difference.

Fair comparison is a record-making job. Normalize what can be normalized, identify what cannot, and ask each provider to explain its own offer. A solar representative can be useful without becoming the judge of another company, contract, design, lender, or promise.

This article is not engineering, electrical, structural, roofing, contract, legal, advertising, consumer-protection, privacy, tax, accounting, finance, lending, investment, insurance, utility, permitting, incentive, or warranty advice. Proposal terms and applicable rules vary. Qualified reviewers must address the actual homeowner, property, design, company, agreement, lender, utility, and jurisdiction.

The apples-to-apples solar quote checklist provides a detailed field inventory. This guide focuses on the conversation: how a sales rep can help a homeowner examine competing solar proposals without turning uncertainty into an attack.

What should be normalized before comparing solar proposals?

Normalize the homeowner’s objectives, property record, consumption period, system boundary, array design, equipment, production method, electrical and site scope, storage, price definition, ownership, financing, incentives, warranties, schedule, service, and exclusions before comparing proposals. Record source, version, assumption, reviewer, and unresolved status for each field. Similar totals are not proof that the underlying offers are equivalent.

Begin with the homeowner’s decision. The homeowner may care about initial cash outlay, long-term ownership, backup capability, roof use, equipment preference, service responsibilities, construction timing, future property plans, or how uncertainty is presented. Do not assume every homeowner ranks those concerns in the same order.

The U.S. Department of Energy’s homeowner solar guide says there is no universal solar solution and organizes questions around property suitability, production, installers, contracts, and financing. DOE does not choose between proposals. Its question-based posture is the right starting point: define the decision before scoring the documents.

Create a proposal identity line for each document. Record provider name, document title, proposal number if shown, creation and expiration dates if shown, revision, customer, property, design version, financial version, preparer, and pages received. A screenshot or summary email may omit a qualification that appears in the full document.

Then normalize the comparison boundary:

Comparison field What to record from each proposal Clarification to request
Homeowner objective Stated priority and requested scope Does the offer solve the same requested problem?
Property input Address, roof or site record, bill period, usage source Are both providers using the same property and consumption inputs?
System boundary Solar, storage, service work, roof work, trenching, monitoring What is included, optional, owner-supplied, or excluded?
Array and equipment Layout, module, inverter, storage, mounting, counts, versions Are substitutions allowed, and under what approval?
Modeled production Period, weather, shade, loss inputs, model version, status Which inputs are measured, modeled, supplied, or assumed?
Price Cash, financed, contract, allowance, optional, tax, and fee boundary Which items can change and through what process?
Ownership and payment Purchase, lease, power purchase, loan, or other arrangement Who owns what, pays whom, and under which agreement?
Work and handoffs Design, engineering, permits, utility, installation, inspection, closeout Which party owns each step and acceptance?
Warranty and service Issuer, covered item, period, condition, remedy, transfer Which document controls, and who performs service?
Exceptions Unknown site conditions, approvals, changes, cancellation, delays What happens when an assumption fails?

Use three evidence states: shown, clarified by the responsible provider, and unresolved. “Shown” means the proposal visibly contains the field. It does not mean the field is correct. “Clarified” means the provider responsible for the offer supplied an attributable answer. It does not automatically amend the contract. “Unresolved” means the comparison cannot safely close the issue.

The non-equivalent solar quote guide explains the design normalization problem in more depth. Do not force two designs into one score when their scope, layout, storage, electrical work, or evidence differs.

Separate document observation from technical judgment

An observation names what the document displays. “Proposal A identifies module model M” is an observation if that is what the page says. “Proposal B uses inferior modules” is a judgment requiring a defined criterion and adequate evidence. “They chose that equipment to cut corners” is speculation about motive.

Keep four columns in the working record:

Record type Example form Who can close it?
Observation “Page shows this equipment and this quantity” Reader can verify against the page
Question “Does the equipment substitution clause apply here?” Provider that issued the offer
Inference “This difference may affect another field” Qualified reviewer with relevant evidence
Decision “Homeowner accepts, rejects, or seeks another review” Homeowner under applicable agreements and advice

Do not quietly promote an inference into a fact during the conversation. If the representative cannot verify the field, say what remains unknown and route the question to the right owner.

How can a sales rep discuss differences without attacking a competitor?

Discuss proposal differences by naming the exact field, source page, version, and observable mismatch, then asking a neutral question the issuing provider can answer. Avoid claims about motive, competence, legality, honesty, safety, or quality unless verified evidence and qualified review support them. Explain your own proposal fully, disclose uncertainty, and give the homeowner room to seek clarification.

The sales rep owns the accuracy of their own offer. That includes the proposal’s site inputs, design, equipment, modeled outputs, price boundary, financing presentation, disclosures, schedule language, service scope, and version. A clean competitor critique cannot repair an unclear proposal from your own company.

The Federal Trade Commission’s advertising guidance says United States advertising must be truthful and non-deceptive and objective claims need evidence. It does not approve a particular comparison. Treat every factual statement about another offer as a claim that needs an accurate source and appropriate context.

Use the “document, difference, question” pattern:

  1. Document: identify the exact proposal, page, field, date, and revision.
  2. Difference: state the visible mismatch without ranking it.
  3. Question: give the homeowner a neutral question for the provider that owns the offer.
  4. Boundary: state what cannot be concluded from the document alone.
  5. Next evidence: name the record or qualified reviewer needed to resolve it.

Suppose one proposal shows a different system size. Say, “These documents show different system sizes and array layouts. Ask each provider which property, consumption, shade, equipment, and design inputs produced its recommendation.” Do not say the other company intentionally undersized or oversized the system unless qualified evidence establishes that conclusion.

If a field is missing, use “not shown in the copy reviewed” rather than “not included.” The item may be in another attachment, contract exhibit, lender document, equipment schedule, or later-stage package. The homeowner should ask whether it is included, where it is documented, what terms control it, and what happens if it changes.

Replace labels with testable questions

Loaded labels shut down useful inquiry. Turn them into questions the record can answer.

Attack or unsupported label Neutral evidence question
“Cheap equipment” Which exact models, specifications, substitutions, warranties, service roles, and availability conditions apply?
“Fake production” Which site model, weather source, shade inputs, layout, equipment, losses, period, and review status support the estimate?
“Hidden fees” Which cash-price, financed-amount, fee, payment, term, prepayment, and disclosure fields appear in the controlling documents?
“Bad warranty” Who issues each warranty, what is covered, which exclusions apply, how is a claim made, and what happens on transfer?
“They skip engineering” Which engineering scope, responsible professional, review event, deliverable, and approval is included or still pending?
“They will change the price” Which allowances, site conditions, substitutions, change-order triggers, approvals, and cancellation terms apply?

Neutral language does not require false equivalence. A documented mismatch can matter. The rep can explain why a field matters to their own workflow and show how their proposal handles it. The line is crossed when the rep claims facts not in evidence or attributes motive from an incomplete document.

Use the hidden design differences guide to show why layout and inputs can matter without declaring another design defective. Ask a qualified technical owner to review material design differences.

Give the other provider ownership of its explanation

Do not interpret another company’s contract or lender document for them. Prepare a question list the homeowner can send to that provider. Ask for a written response tied to the current proposal version. If the response changes scope or terms, request a revised controlling document rather than relying on a verbal assurance.

Record the response accurately. A salesperson’s email may clarify intent but may not amend a contract. A product brochure may describe a manufacturer warranty while the proposal omits installer service. A lender disclosure may control a financing term that the solar proposal summarizes. Qualified reviewers must determine which document controls.

Give the homeowner time. The FTC’s solar consumer guidance distinguishes buying, leasing, and purchasing solar power and warns consumers about pressure for a quick decision or signing without review time. The guidance does not approve any specific offer. A fair sales process leaves room to read, ask, and seek independent help.

How should production, savings, financing, and incentives be compared?

Compare production, savings, financing, and incentive sections by tracing every output to its source inputs, assumptions, period, jurisdiction, model or lender version, disclosure, and responsible reviewer. Keep cash price, financed amount, fees, payments, ownership, tax treatment, utility rules, and modeled benefits separate. Never infer eligibility, approval, guaranteed savings, or future performance from a proposal total.

These fields carry the highest consequence and the easiest false confidence. A clean chart can combine a site model, weather file, shade assumption, equipment model, loss factors, consumption record, tariff, export treatment, degradation assumption, financing terms, tax treatment, incentive assumptions, maintenance, and timing. The homeowner needs to see which inputs each proposal uses and which remain conditional.

For production, compare the model lineage. Record roof or site geometry, shade data, array layout, orientation, equipment, weather source, losses, model version, run date, period, reviewer, and output status. A total alone cannot show why two estimates differ. Do not average the two estimates to create an unsupported middle number.

For savings, separate modeled production from bill treatment. Record the consumption period, tariff source, fixed charges, usage rates, export rules, escalation or change assumptions, storage behavior, taxes, fees, and scenario date. Utilities and rates can change, and individual use can change. Do not promise a bill outcome.

For financing, create a field-level comparison and route interpretation to the lender and qualified advisers. The CFPB’s 2024 solar-financing issue spotlight discusses presentation risks involving fees, tax assumptions, net-cost framing, prepayment expectations, payment changes, and financial-benefit statements. This article does not restate rates, percentages, or borrower results.

Use a finance and ownership table:

Field Proposal A Proposal B Responsible clarification
Cash price and included scope Solar provider and contract reviewer
Financed amount and itemized fees Lender and qualified finance reviewer
Payment schedule and change events Lender
Term and rate type Lender
Prepayment treatment Lender and contract reviewer
Security interest or property-related filing Lender and qualified legal reviewer
Ownership during and after the agreement Contract parties and legal reviewer
Transfer, sale, early payoff, cancellation Contract parties and lender
Tax credit or incentive assumption Current program source and qualified tax adviser
Savings or bill statement Model owner, utility source, finance and advertising reviewers

Do not subtract an assumed incentive from price and call the remainder the homeowner’s cost unless the controlling documents and qualified reviewers support that exact presentation for the homeowner and jurisdiction. Keep system price, financed principal, program assumption, customer payment, and possible tax treatment as separate fields.

Do not describe a loan, lease, or power-purchase agreement as “basically the same” as ownership. Identify who owns the equipment, who receives which benefits, who maintains what, how payments change, which transfer terms apply, and which documents control. The homeowner’s qualified advisers should interpret legal and financial consequences.

The cost-per-watt tradeoff guide shows why a single ratio can hide scope. If the denominator uses different system boundaries or the numerator contains different work and finance items, the comparison is not ready.

Make your own proposal easier to inspect. Keep roof, layout, shade, yield, financial, electrical, material, and proposal versions connected so the homeowner can see which inputs support each section.

Explore connected solar proposal workflows

What conversation keeps the homeowner in control?

Keep the homeowner in control by asking for priorities first, explaining your own proposal and limits, building a shared field comparison, separating observations from questions, inviting each provider to clarify its offer, and pausing on material unknowns. End with the homeowner’s chosen next step, not a forced winner, invented deadline, or conclusion outside the rep’s qualifications.

NASA’s decision-analysis guidance describes characterizing alternatives against a decision-maker’s priorities and uncertainty in NASA systems work. It does not govern solar sales. The useful analogy is simple: the homeowner’s criteria and state of knowledge should shape the comparison.

Run the meeting in this order:

  1. Ask what the homeowner is deciding. Record objectives, concerns, timing, ownership plans, and which advisers are involved.
  2. Confirm document identity. Make sure both sides are using complete current proposals and related attachments.
  3. Explain your own offer first. Show scope, inputs, assumptions, exclusions, unresolved items, change process, and controlling documents.
  4. Build field parity. Use the same comparison categories and evidence states for every proposal.
  5. Mark observations and questions. Do not convert missing or different information into a verdict.
  6. Return questions to the issuing provider. Ask for attributable written clarification and revised documents when terms change.
  7. Escalate consequential differences. Technical, financial, tax, lending, contract, insurance, utility, and legal issues go to qualified owners.
  8. Let the homeowner weigh tradeoffs. Do not substitute the representative’s preferred criteria for the homeowner’s stated priorities.
  9. Record the next step. It may be another question, revised proposal, independent review, site work, lender clarification, more time, or no decision.

Ask permission before marking up the competing document. Preserve the original copy and create a separate comparison record. Do not alter screenshots in a way that hides context. If private or personal information appears, follow the company’s approved privacy, access, retention, and disclosure rules.

Handle a direct “Which company is better?” question

The rep can answer by returning to criteria: “I can show how our current proposal addresses the priorities you named and where it still depends on review. I cannot verify the other company’s intent or work from this document alone. Here are the questions I would ask them.”

That response is not evasive. It gives the homeowner a usable boundary. The rep can still advocate for their own company through visible process, complete scope, responsive clarification, documented assumptions, and clear ownership.

Do not claim a universal best installer, best equipment, best warranty, best price, or best financing. Superlatives need defined criteria and adequate evidence, and the final choice depends on the homeowner’s situation and agreements.

Use the unequal quote warning checklist when parity cannot be established. An unresolved difference is a reason for another question or qualified review, not automatic proof that one provider is wrong.

What should a neutral solar proposal comparison record contain?

A neutral solar proposal comparison record should contain document identities, homeowner priorities, normalized fields, source pages, evidence states, exact differences, questions for each provider, written responses, revised versions, technical and financial review needs, unresolved risks, and the homeowner’s next action. It should preserve originals and avoid scores whose weights, definitions, or evidence the homeowner did not approve.

Copy-ready homeowner solar proposal comparison record

Field Entry
Homeowner, property, meeting date, consent, and privacy handling
Decision to make, priorities, concerns, timing, and advisers
Proposal A provider, title, id, date, revision, pages, and attachments
Proposal B provider, title, id, date, revision, pages, and attachments
Property, bill, usage, roof, shade, and site-input parity
Array, equipment, storage, electrical, roof, site, and service scope
Production model, weather, shade, losses, period, version, and status
Cash price, financed amount, fees, payment, ownership, and disclosures
Incentive, tax, tariff, export, savings, and escalation assumptions
Warranty issuer, coverage, exclusions, remedy, service, and transfer
Schedule, permits, utility, inspection, change orders, and closeout
Observation, source page, exact difference, and neutral question
Issuing-provider response, responder, date, and revised document
Qualified technical, finance, tax, legal, utility, or contract review
Unresolved items and decisions that cannot yet be made
Homeowner’s next step, owner, due event, and evidence needed

Avoid an unexplained weighted score. A rep can make any preferred offer win by choosing categories and weights after seeing the documents. If the homeowner wants a score, let the homeowner choose the criteria and importance before the final comparison. Keep disqualifying safety, legal, technical, or financial review items outside casual scoring.

Illustrative example, not a real homeowner or proposal

This scenario is invented to demonstrate the record. It is not a customer case, competitor review, design conclusion, financing analysis, price comparison, savings result, tax opinion, or recommendation.

Two proposal documents show different array layouts and different production totals. The representative does not say the other provider’s estimate is inflated. She records the visible differences and asks both providers to identify the roof model, shade data, equipment, loss assumptions, weather source, model version, and review status behind their outputs.

One document also shows a financed amount while the other page displays a cash price. The representative does not call either offer cheaper. She marks the price basis unequal and gives the homeowner a question list for each provider and lender. A qualified finance and contract reviewer must address the actual terms.

The homeowner decides to wait for revised documents. That is a valid next step. The comparison record stays open, with both original files preserved and each unresolved field assigned to the party that can answer it.

SurgePV’s repository-verified proposal workflow includes 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Results depend on source data, assumptions, equipment models, configuration, and review.

SurgePV can help a team keep its own design and proposal versions connected. It does not verify another company’s proposal, interpret a contract or financing offer, decide tax treatment, approve engineering, guarantee savings or production, or choose an installer for the homeowner. Responsible reviewers and the homeowner retain those decisions.

A fair comparison does not weaken the sale. It shows the homeowner that your proposal can survive questions without borrowing certainty from someone else’s missing page.

Frequently Asked Questions

Can a solar rep point out missing items in another proposal?

Yes, if the rep describes the document accurately and avoids guessing why an item is absent. State the field, page, version, and observation date. Ask the homeowner to request clarification from the proposal’s provider. Label the item unresolved until that provider responds. Do not turn a missing field into an accusation about competence, intent, legality, or quality.

Should homeowners compare solar proposals by price per watt?

Price per watt can be one normalized field, but it cannot explain every difference in design, equipment, electrical work, storage, roofing, site work, warranties, service, financing, assumptions, or exclusions. Confirm that price and system-size boundaries match before calculating or comparing it, and have qualified reviewers address financial, tax, contract, and technical implications.

How should two different solar production estimates be compared?

Compare the site model, weather source, shade data, array layout, equipment, loss assumptions, time period, software version, and review status behind each estimate. Do not average the outputs or call one wrong from the total alone. Ask each provider to explain its own model and obtain qualified technical review for material unresolved differences.

Can a sales rep compare solar financing offers for a homeowner?

A rep can organize disclosed fields and questions, but should not provide individualized lending, tax, investment, accounting, or legal advice unless properly qualified and authorized. Keep cash price, financed amount, fees, payment schedule, term, rate type, prepayment treatment, security interest, transfer, incentives, assumptions, and disclosures distinct. The lender and qualified advisers should clarify their own terms.

Where can SurgePV help with a solar proposal comparison?

SurgePV can support roof models, array layouts, shading and yield analysis, financial models, electrical workflow, bill-of-materials output, and proposal generation. It can help a team expose its own inputs and versions. SurgePV does not validate another provider, approve a design, interpret contracts or financing, determine tax treatment, guarantee results, or choose for the homeowner.

Make your proposal easier to compare

Bring a sanitized comparison record, current design version, and proposal questions to a guided session. Confirm current access, implementation scope, pricing, and contract terms in writing.

Request a guided demo

Sources

Primary research and reference material used for this desk-research article.

Where this fits

This article is part of SurgePV's Solar Sales & Proposals hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Akash Hirpara
Akash Hirpara

Co-Founder · SurgePV

Akash Hirpara is identified by SurgePV as a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; education, certifications, project totals, financial results, speaking engagements, and media appearances are not asserted without retained evidence.

Editor
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.