Back to Blog
solar business12 min read

Speed-to-Proposal Checklist: Residential Solar

A speed-to-proposal checklist for residential solar sales teams: what to collect, who owns each step and what to check before the proposal is sent.

Nimesh Katariya

Written by

Nimesh Katariya

Solar-industry contributor

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

Speed to proposal comes from preparation, not shortcuts: collect the bill, address and roof photos before the design request, send one complete request, review the design against it, and check every customer-facing figure against the current revision before sending. A shared checklist with owners at each stage removes most of the waiting.

A homeowner who has asked for a solar quote is comparing you with other installers while they wait. Most of the delay is not design time. It is time lost to missing bills, unclear goals, a second round of questions and a proposal that has to be corrected after review.

This checklist covers the stages between a qualified lead and a sent proposal for residential sales teams: prepare, request, design, build, review and send. It focuses on removing waiting time without skipping the checks that protect the customer.

Last updated: November 2026

Direct Answer

Prepare the inputs before the design request, give every stage one owner, and check the proposal against the current design revision before it goes out. A fast proposal is one where nothing has to be redone.

Get Proposals Out Without Redoing Them?

See how design, production and proposal outputs stay linked so one change does not mean rebuilding the whole document.

Book a Demo

Checking cost first? See the SurgePV pricing page · 20 minutes · Live project walkthrough

Why Residential Proposals Run Late

Proposals run late when the team learns something new after the design has started. A bill turns out to cover a different meter, the roof is older than assumed, or the customer wants a battery nobody mentioned. Each surprise sends the project back a stage.

A written checklist moves those questions to the front. It also gives the team a single record, so a designer, a salesperson and a reviewer are all looking at the same revision. Our post on seven ways to cut proposal turnaround time without sacrificing accuracy covers the same problem from the design side.

The Checklist by Stage

The table gives the full flow. Each stage has an owner and a clear finish line.

Stage Checklist item Owner Done when
1. Prepare Address, recent bill, roof photos, roof age Sales All four are on the project record
1. Prepare Customer goal and constraints in one sentence Sales Written, not verbal
2. Request Single intake form submitted Sales Designer accepts, holds or returns
3. Design Numbered revision, assumptions labeled Designer Inputs marked confirmed, estimated or pending
4. Build Proposal built from the current revision Sales Module count and size match the design
5. Review Second-person check against the request Reviewer Mismatches fixed or flagged
6. Send Next step, owner and follow-up date stated Sales Customer knows what happens next

Stage 1: Prepare Before You Ask for Design

Collect the basics before the request exists. DOE’s homeowner guide shows what buyers care about and what affects the numbers: it says panels perform best on roofs sloping between 15 and 40 degrees, that heavy tree shade can make a roof a poor fit, and that roof age matters because replacing a roof later means removing the array (U.S. Department of Energy, checked November 2026).

So ask about roof age and shade on the first call, not after the layout. Our guide to the fields a design request should include lists what to capture.

15 to 40 deg
Roof slope range DOE says suits panels best
7.15 kW
Average residential system size DOE cites, with a 3 to 11 kW range
4
Ownership options DOE says buyers should compare: purchase, loan, lease and PPA

Source: the DOE homeowner’s guide to solar, checked November 2026. The average system size is attributed there to NREL.

Stage 2: Send One Complete Request

A complete request means the designer can begin without a call. If something is missing, label it as an estimate or return the request with a specific question. A “held” status is useful: the designer starts on labeled assumptions while sales chases the missing item.

Stage 3: Design in a Numbered Revision

Number every revision and label each input as confirmed, estimated, pending or changed. For a quick baseline production figure, DOE points homeowners to NREL’s PVWatts calculator. PVWatts states that its predictions include many inherent assumptions and uncertainties, so treat it as a starting point and keep the final model’s assumptions on the project record.

Shading deserves a stated method. A model should name its source data and say whether trees, nearby objects and future construction are represented. The shadow analysis workflow is one way to document that.

Stage 4: Build the Proposal From the Revision

The proposal should be built from the current design, not rebuilt from memory. The project name, system size, module count, expected production, scope, exclusions and next step should all come from the same revision. A polished proposal tied to an older layout is the most common reason a customer loses trust.

For the financial section, record the tariff source and date, the usage period and any incentive. DOE’s guide says projected savings depend on electricity use, system size, roof orientation, utility rates and export compensation, so each of those needs a source on the record. The generation and financial tool can keep those assumptions with the design.

Pro Tip

Put the source date beside every input that moves the savings figure, such as the bill period and the tariff. A value can be reasonable and still be stale.

Stage 5: Review Against the Request

A second person compares the proposal with the request and the design. The reviewer is not re-designing. They check that module count, system size, production, price and scope match, and that assumptions are labeled. Questions on structure, electrical design, code or interconnection go to the qualified person your company designates.

A short review on every proposal is faster than correcting a mismatch after the customer has seen it. Solar proposal software that builds outputs from the design file reduces re-keying, but it does not remove the need for the check.

Key Takeaway

Speed comes from fewer loops. Preparing inputs, returning incomplete requests and checking the proposal against the revision take minutes, and each one removes a rework cycle that takes days.

Stage 6: Send With a Next Step

State what the customer is being asked to decide, who owns the next contact and when. Sending a proposal does not mean the customer has accepted anything. Permits, inspection and utility connection come later: DOE’s permitting page says local governments generally require a permit before panels are installed, an official inspects the system afterwards, and the utility then connects it to the grid (U.S. Department of Energy, checked November 2026). Tell the customer which of these steps the proposal does and does not cover.

For follow-up, see our 14-day proposal follow-up checklist and the post on why prospects go cold while waiting for a quote.

Model Payback on Your Own Design?

Walk through a live project to see production and financial outputs update when the design revision changes.

Book a Demo

See the SurgePV pricing page for plan details · No commitment required

What to Measure Without Inventing a Benchmark

Measure whether the checklist is used, not whether you hit a generic industry target. Useful internal measures include:

  • The share of proposals tied to the current design revision
  • Requests returned at intake
  • Open items at the time of sending
  • Time between a material change and the customer update

These are team diagnostics. Do not present them as a promise of commercial outcomes. Once a month, pull a few delayed proposals and ask where an assumption became invisible. If the same cause repeats, add a field or an owner. If a step is never used, remove it.

A Field-Ready Version

  1. Record the site and customer data sources, with dates.
  2. Mark each input as confirmed, estimated, pending or changed.
  3. Write the customer goal and constraints in one sentence.
  4. Submit one intake form and wait for accept, hold or return.
  5. Check the design revision and its reviewer before building the proposal.
  6. Tie the BOM and proposal to that revision.
  7. Label production, tariff, incentive and finance assumptions.
  8. Send code, structure, utility and contract questions to the qualified reviewer.
  9. Send with a named next step and a follow-up date.
  10. Review delayed proposals at the next operating meeting.

Conclusion: Make Fast Work Reviewable

  • Prepare the inputs before the design request exists.
  • Review the design, BOM, financial model and proposal as connected outputs.
  • Give every stage one owner, and log changes against the revision.

To see how a connected workflow handles these stages, book a SurgePV demo or explore solar design software.

Frequently Asked Questions

How can a residential solar sales team send proposals faster?

Collect the utility bill, address and roof photos before requesting a design, send one complete request and review the result against it. Most waiting comes from missing inputs and rework, so fixing intake saves more time than rushing the design.

What should be ready before requesting a solar design?

Have the site address, recent usage data, roof photos, roof age, the customer’s goal and any known constraints. Label estimates as estimates so the designer knows what is confirmed.

What should be checked before a solar proposal is sent?

Check that module count, system size, production, price and scope all match the current design revision. Confirm that tariff and incentive assumptions have a source and date, and that open items are stated plainly.

Does a faster solar proposal mean a less accurate one?

Not if the speed comes from better intake and a short review rather than skipped checks. Label assumptions, keep one design revision and send a preliminary proposal only if it is marked as preliminary.

Who should own each step of the proposal process?

Give each stage one named owner: sales for intake data, the designer for the layout, a reviewer for the pre-send check and sales again for follow-up. A step with no owner is where proposals stall.

Sources and Further Reading

Ready to Speed Up Your Solar Workflow?

Explore a connected solar design workflow for installers and EPCs.

Book a DemoExplore Solar Designing

Sources

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

Where this fits

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

About the Contributors

Author
Nimesh Katariya
Nimesh Katariya

Solar-industry contributor

Nimesh Katariya contributes to SurgePV content concerning solar project workflows. This profile intentionally does not assert certifications, project totals, seminar counts, or technical-review authority without retained verification 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.