Solar Sales-to-Design Handoff: How to Turn a Customer Conversation Into Workable Scope

The sales-to-design handoff translates a customer conversation into a brief the designer can assess. The handoff does not ask designers to accept every sales statement as fact. It gives them enough context to test what was requested, preserve what was promised, and ask the right follow-up before a polished proposal creates a false sense of certainty.

For solar installers and EPCs, the issue is not whether sales or design “owns” the project. Both roles hold information the other needs. Sales may understand why the buyer is considering PV, who will decide, and what timing or financing question matters. Design must test whether the requested outcome is feasible against site, energy, equipment, electrical, and regulatory information. The workflow should respect both jobs.

A Handoff Is Not a Meeting Summary

Many teams label a short call note as a handoff. “Customer wants a 10 kW system, send proposal Friday” tells the designer almost nothing about the basis for the request. Was the size a customer preference, an estimate from a bill, a local constraint, or a number mentioned in an earlier concept? Does the customer care about annual energy, a monthly payment, backup capability, roof appearance, a portfolio target, or a procurement deadline? Which details were supported by documents, and which were conversational?

Design needs a decision-oriented summary. It should say what the next deliverable is intended to help the customer decide. A concept for an initial residential conversation is different from a commercial financial scenario for a facilities team. The difference determines what can be modeled provisionally and what must be verified before an output is presented as reliable.

The U.S. Department of Energy Solar Energy Technologies Office provides public material about solar technologies and deployment. It is not project evidence. Project-specific claims must remain connected to current utility information, site records, equipment documentation, authority requirements, and the agreement between the customer and installer.

Split the Packet Into Four Conversations

An effective handoff has four parts. Keeping them separate prevents a customer preference from becoming a technical condition or a preliminary assumption from becoming a commercial commitment.

1. The Buyer Conversation

Record who attended, who will participate in the decision, and what question the buyer wants answered next. A homeowner may want to compare an all-cash option and financed option. A commercial customer may need an internal business case, consumption analysis, construction-impact discussion, or review by facilities and finance. Do not write “interested in solar” when the team knows the actual decision.

Include a decision date only if it came from the customer or their stated process. Internal pipeline dates are useful operationally but should not be passed to design as if they are customer commitments.

2. The Evidence Conversation

Attach the bill, interval data, address confirmation, photographs, drawings, site notes, and other materials that informed the call. Identify the date and source of each item. If a customer verbally described a condition, distinguish that statement from a field observation. This allows the designer to judge whether the evidence is suitable for a concept or whether it needs confirmation.

The National Renewable Energy Laboratory’s solar market research and analysis resources can inform general market understanding. They do not establish a tariff, roof condition, electrical service capacity, or project economics for a live project. Those details require records applicable to the actual site.

3. The Scope Conversation

State what sales asked design to produce: a preliminary layout, a scenario comparison, a customer proposal, a battery option, a roof-screening view, or another defined output. List the choices discussed with the buyer, but label each as requested, assumed, optional, or excluded. This stops the design team from treating a casual preference as a firm system specification.

4. The Commitment Conversation

Sales should record statements that could shape the buyer’s expectation. Examples include a promised review meeting, a request to model a particular use case, a statement that a survey is pending, an equipment preference, or a question that the buyer expects answered. Do not use this section to record unsupported savings, approval, or timeline guarantees. It is a record of communication, not a substitute for verification.

Give the Designer a Way to Push Back Productively

A handoff process fails when the only response option is “done” or “late.” The receiving designer needs three legitimate paths:

This is not resistance to selling. It protects the credibility of the proposal. A designer who asks for the current bill, a better site photograph, or a clarified backup objective is turning an ambiguous request into an answerable one. Sales can then explain the request without suggesting that the customer caused a delay.

Useful language is direct: “To compare the two scenarios accurately, we need the latest electricity data,” or “The proposed layout is an early view until a site assessment confirms roof conditions.” Avoid “we just need more details,” which leaves the customer unable to help.

Preserve the Difference Between an Option and a Promise

Customers commonly ask for a number during an early conversation. The temptation is to provide a precise system size, production estimate, monthly saving, or installation date before the relevant inputs are known. Sales teams can still be helpful without presenting an early scenario as settled.

Use qualification that identifies the dependency. A preliminary option may be based on a supplied bill, available imagery, and the customer’s stated objective. It may require confirmation of roof features, equipment configuration, tariffs, site access, electrical conditions, financing terms, authority requirements, or utility arrangements. Say which dependency applies to the project rather than adding a generic disclaimer at the bottom of a proposal.

The Energy and financial modeling tool can help teams connect energy and financial scenarios. Its value is highest when its input assumptions are visible and current. It should not be used to turn an incomplete handoff into a guaranteed customer outcome.

Use a Handoff Acknowledgment, Not a Black Hole

The receiving role should return a concise acknowledgment. It need not be a meeting. The acknowledgment should tell sales which inputs were accepted, which need clarification, what output will be prepared, and whether there is an open condition that changes the expected conversation with the customer.

For example, a design acknowledgment might state: “Proceeding with a preliminary PV and storage comparison based on the supplied bill and stated outage objective. Battery duration remains an assumption until critical loads and equipment configuration are reviewed. Please confirm whether the customer wants whole-home discussion or only named loads.” That message is specific enough for sales to continue the conversation without inventing an answer.

This step also protects the designer. If a design request did not include a customer deadline, site record, or key technical choice, the team can identify the gap before a calendar date becomes a surprise. The project record should retain the acknowledgment alongside the handoff, not leave it in a private message thread.

Control Revisions From the Customer Back to Design

After a proposal discussion, customers often request variations: more modules, different equipment, a battery, altered aesthetic preferences, an alternate payment structure, or a different site. Each request needs a clean path back to design. Sales should not modify design-derived figures from memory or resend an old document with an improvised explanation.

Create a variation note with four fields: what the customer asked for, why they asked, which current version they saw, and what response is requested from design. The designer can then determine whether a new layout, simulation, equipment selection, commercial update, or survey question is required. This creates a useful audit trail when the project later changes again.

Solar Proposals is SurgePV’s product area for creating branded, customer-ready proposals from the design workflow. Test whether the offered workflow reduces manual transfer on a representative project, but it does not resolve a contradiction in the underlying project information. The team must still choose the current source and communicate the effect of a revision.

Design the Handoff for Commercial Stakeholders

Commercial projects tend to require more than a technical concept. A sales contact may be gathering information from an energy manager, operations leader, facilities team, finance reviewer, landlord, and procurement function. The handoff should identify the stakeholder role and their expected question. “Finance needs payback” is less useful than “finance needs a scenario with stated tariff, escalation, CAPEX, and financing assumptions, each clearly labeled.”

Likewise, a facilities review may focus on access, construction constraints, shutdown windows, roof plans, and operations. These are not details to append after a financial presentation. They can determine whether a proposed scenario is viable. Make the stakeholder-specific question part of the requested deliverable.

NASA’s interface-management guidance describes responsibility and controlled changes across boundaries. Adapt that record principle rather than treating it as solar approval or measured sales benefit. Use the handoff bottleneck diagnostic to separate missing inputs from queue or reviewer delays; this page owns the packet and receiving response.

Measure Friction Without Inventing a Performance Claim

Teams can improve the process by reviewing returned handoffs. Categorize why design work was paused or revised: missing electricity data, unclear scope, unsuitable imagery, unresolved equipment choice, conflicting customer instruction, missing stakeholder, or a condition requiring specialist review. The categories help managers see where a sales brief needs improvement.

Do not claim that a new handoff form produces a defined conversion rate or turnaround reduction without retained evidence. Project mix, market, staffing, customer behavior, and many other factors affect those measures. Describe the control: it makes the reason for a pause visible and directs the next action to an owner.

A Short Handoff Standard for Teams to Adopt

Before sending work to design, sales should be able to answer:

1. What exact customer decision is this deliverable meant to support?
2. What source material supports the requested scope?
3. Which customer statements are preferences rather than verified conditions?
4. What did sales already say would happen next?
5. Which question could materially change the proposed output?

When those five answers are present, the receiving designer can assess the requested output and remaining assumptions. When they are absent, the correct next step may be an evidence request rather than a rushed layout.

Frequently Asked Questions

What should sales give a solar designer?

Sales should provide the customer objective, current evidence, requested scope, conversation commitments, decision timeline, stakeholders, and every unresolved question that could change the design.

Should sales promise a system size before design review?

Sales can discuss an indicative scenario when it is clearly qualified, but a final system size depends on site evidence, equipment choices, applicable requirements, and technical review.

Who tells the customer when design needs more information?

Sales usually owns the customer conversation, while design should state the exact information required and why it changes the requested output. The handoff record should retain the request and the customer response so the next version has a clear basis.