Battery Attach Rate: A Deliberate Solar Sales Playbook

“Double the battery attach rate” sounds like a sales target. It is not yet a plan. A team can raise the displayed rate by changing the denominator, quoting storage on unsuitable projects, or pushing customers toward an option they do not understand. None of those behaviors creates a sound storage business.

A deliberate playbook starts with a stable baseline and a defined eligible population. It then improves the path from customer objective to site evidence, reviewed option, customer decision, and installed scope. The useful question is where qualified storage opportunities disappear and why.

This guide is for solar sales and operations leaders building that path. Battery design, safety, code, utility, warranty, finance, and contract questions require the current sources and responsible reviewers that apply to the project. The article does not promise a specific attach-rate outcome.

Define the rate before setting the target

Write the numerator and denominator in plain language. The numerator might be signed solar projects that include an approved storage scope. The denominator might be signed solar projects eligible for storage under the company’s market and product rules. Use the same stage and time period for both.

Do not mix proposals with installations or leads with contracts. A sales team can appear to improve when pending storage options move into the numerator while cancelled solar projects leave the denominator. Keep stage-level rates separate: qualified, modeled, proposed, selected, signed, installed, and commissioned where relevant.

Define eligibility before seeing the result. Exclusions may include unsupported jurisdictions, site or electrical conditions outside company scope, incompatible existing equipment, customer goals the offered solution cannot meet, or incomplete evidence beyond the decision deadline. Record the reason. Excluding every difficult project after the fact makes the metric useless.

Illustrative denominator check: If 24 of 80 signed eligible solar projects include storage, the eligible-project attach rate is 24 ÷ 80 × 100 = 30%. If the same cohort contains 100 signed solar projects in total, its all-signed-project rate is 24 ÷ 100 × 100 = 24%. Report both the counts and the denominator. Reclassifying eligibility can move the first rate without adding a single storage sale. These figures are examples, not SurgePV or industry results.

Build the baseline from your own retained data. Market reports can show broader adoption patterns, but they do not establish what this company’s customers should choose or what its process can achieve. Use several consistent periods when seasonality or program changes matter. Label missing records rather than estimating a flattering history.

Set an internal improvement hypothesis tied to a mechanism: better early qualification, fewer missing load files, clearer option comparison, or faster routing of technical exceptions. A target without a mechanism encourages pressure. A mechanism can be tested and corrected.

Ask about the use case before mentioning equipment

Start with what the customer wants storage to do. Common categories include backup for named loads, shifting energy across tariff periods, increasing on-site use, responding to export constraints, supporting a facility operating plan, or combining several objectives. Do not assume every person who mentions outages wants whole-building backup.

Ask the customer to rank the objectives. Backup, bill management, and export behavior can require different data and operating choices. A proposal that says “energy independence” may conceal tradeoffs between reserve energy and daily cycling. Replace the slogan with a defined scenario.

The U.S. Department of Energy’s solar and storage basics explain that storage can retain solar energy for later use and interact with the grid and customer loads. Use that general mechanism, then investigate the project’s tariff, equipment, and operating conditions. The federal overview is not a customer-specific savings or backup calculation.

Record a no-fit answer without trying to overturn it. Some customers value the PV option and do not have a storage objective that justifies further work. Others need a different resilience or power-quality solution. Qualification protects design capacity and keeps battery conversations relevant.

Use customer language in the handoff. “Keep refrigeration and the communications rack operating during a typical outage” is more useful than “interested in backup.” It tells the technical team which loads and duration assumptions need evidence.

Create a minimum storage evidence packet

The evidence request should match the stage. An early screen may use current bills, a customer-described use case, existing or proposed PV information, and a preliminary site record. A customer-facing design needs the load, tariff, equipment, site, electrical, and operating evidence appropriate to the claims shown.

For backup, define critical loads by equipment or circuit, expected power, energy use across time, motor or startup behavior where relevant, desired operating period, and loads the customer agrees can remain off. Do not convert a whole-building monthly bill into a precise outage-duration promise.

For tariff use cases, collect interval data when timing and demand matter, the current tariff and export treatment, operating schedule, seasonal changes, and any planned electrification. A utility bill total may be enough to begin a conversation while being insufficient for detailed dispatch economics.

For retrofit projects, identify the existing PV and electrical equipment, ownership, warranty conditions, documentation, available connection points, site constraints, and responsible technical review. The AC-coupled versus DC-coupled battery guide can support the conceptual comparison; actual compatibility comes from current manufacturer and project records.

Give missing fields a status, owner, and due event. “Critical-load panel unknown, electrician to confirm before reviewed backup scenario” keeps the option alive without pretending the answer is settled.

Build a controlled option set

Customers usually understand storage better when PV-only and solar-plus-storage options use the same project baseline. Hold site, PV design, load data, tariff source, project date, and financial method consistent. Then show what storage changes: equipment, operating scenario, price, energy flows, backup scope, maintenance assumptions, and relevant exclusions.

Do not offer an unbounded size slider. Each customer-facing battery option should map to an equipment configuration, electrical concept, operating assumptions, modeled result, price, and review status. A requested variation can return to design rather than generating an instant sales number.

Use option names that describe the job. “Critical loads, reviewed scenario” communicates more than “10 kWh option,” because capacity alone does not define usable energy, output power, load behavior, reserve, or duration. Keep manufacturer terms and ratings exact to the current documentation.

Show constraints beside benefits. A backup option should state its load boundary and starting assumptions. A tariff option should state the tariff and dispatch method. An export-oriented option should identify the current utility rule and any approval dependency. A balanced proposal is easier to compare because the customer can see what each option is built to do.

The DOE homeowner solar guide encourages customers to compare bids, agreements, financing, and installer qualifications. Storage adds another equipment and operating layer; it does not remove the need for a readable base offer.

Explain backup as an operating scenario

Backup duration attracts absolute language because customers want a direct answer. Give a direct model boundary instead. State which loads are included, their power and energy assumptions, battery configuration, usable-energy basis, reserve setting, starting state, PV contribution treatment, equipment limits, and operating mode.

Show load tiers. Tier one might include safety or essential functions defined by the customer. Another tier may add comfort or discretionary equipment. Do not create generic tiers without confirming actual circuits, power, and customer priority.

Weather and outage timing matter. A battery beginning an outage at a lower state of charge behaves differently from one beginning full. Solar contribution differs by time and conditions. The customer may change loads during the event. Present a modeled operating scenario, not a guaranteed countdown.

Explain transition and equipment boundaries using current manufacturer documentation and qualified design review. Avoid implying that every battery can operate every load or that solar continues during an outage in every configuration. Product and system behavior depends on the installed architecture.

Use a written backup-load schedule as the source of truth. If the customer changes the list, rerun the technical and operating review. A verbal promise made beside a glossy battery image should never outrank the retained load schedule.

Treat storage economics as a separate proof chain

Storage value can come from several mechanisms, and each needs its own model basis. Energy shifting depends on load timing, tariff periods, storage efficiency, controls, and usable capacity. Demand management depends on interval peaks and dispatch. Export-related value depends on the current utility treatment. Backup value may not belong in a bill-savings calculation at all.

Avoid adding incompatible benefits. A battery cannot reserve the same energy fully for outages and also cycle all of it for daily tariff value at the same time. The model should state the operating priority and resolve conflicts. A combined scenario needs logic, not a sum of maximum benefits from separate cases.

Keep incentives, tax treatment, and financing current and jurisdiction-specific. Confirm eligibility and effective dates through primary authority. The salesperson should not decide a customer’s tax treatment or hide financing cost inside a monthly-savings claim.

The DOE storage overview explains energy shifting and the distinction between stored energy and output power. It does not establish a customer’s bill result, attach-rate target or preferred battery size. For the price-shifting calculation, use the arbitrage versus self-consumption comparison; keep that economics question separate from the sales funnel metric.

Present customer economics with the same discipline used for projected solar savings: current load and tariff, defined operating case, equipment and cost basis, financing and incentive treatment, operating costs, sensitivity, review, and rerun triggers.

Give sales an escalation map

Sales should know which questions it can answer and which require another role. A simple use-case and document request can stay with sales. Equipment compatibility, electrical architecture, critical-load analysis, interconnection, code, fire or location requirements, and operating controls belong with responsible technical reviewers.

Financing, tax, legal, insurance, warranty, and contract interpretation may need specialist review. The customer should receive current documents and a clear boundary rather than improvised advice.

Use a routing table with question, owner, required evidence, service level, and release stage. A salesperson should be able to say, “Our technical reviewer needs the panel record and load list before we show that backup case.” That answer advances the opportunity.

Track why options stall. If critical-load data is frequently missing, improve the request. If compatibility questions arrive late, screen equipment earlier. If customers cannot understand the difference between energy shifting and backup, revise the proposal explanation. Objection data belongs to operations, not only coaching.

Do not pay or reward solely on attach rate. A narrow metric can encourage unsuitable additions or suppression of no-fit reasons. Balance it with evidence completion, review exceptions, cancellations, change orders, support issues, and other quality measures the company can defend.

Follow up with evidence, not “still interested?”

A battery follow-up should resolve one part of the decision. Send the critical-load worksheet, a controlled option comparison, the tariff source, a corrected electrical question, a manufacturer document, or a summary of what changed after review. Do not repeat the same benefit claim in a new format.

Name the unanswered decision. “We still need the service-panel photograph to confirm which retrofit path deserves technical review” is better than a generic nudge. Give the customer a manageable action and explain what it unlocks in the workflow.

If the customer declines, record the stated reason without forcing a category. Price, unclear use case, site fit, financing, timing, trust, missing information, another provider, or no current need call for different responses. A decline can improve the qualification process.

For customers who choose PV-only, preserve the storage evidence and expiry conditions. A future tariff, outage, load, or equipment change may create a new decision. Do not promise that adding storage later will be simple; screen retrofit compatibility when the topic returns.

The broader battery storage service guide can help operations teams plan capabilities beyond the sales conversation. Attach-rate work should not outrun design, installation, commissioning, and service capacity.

Measure the funnel without gaming it

Track counts at each defined stage: eligible solar opportunities, storage use case identified, minimum evidence complete, option requested, option technically reviewed, option shown, customer selected, signed, installed, and completed under the company’s definition. Preserve reasons for no-fit and customer decline.

Measure data quality. How many opportunities have the required load, tariff, site, and equipment information? How many customer-facing options return for correction? How many signed scopes change materially? A higher proposed attach rate alongside more rework may signal premature quoting.

Segment only when the records support it. Market, customer type, tariff, new-build versus retrofit, and use case can change the path. Do not publish a thin segment as an industry finding. Internal operational data remains a company observation until method, permission, and representative limits are addressed.

Test one process change at a time when practical. Introduce a use-case question, improve the evidence packet, or revise the option table, then observe comparable cohorts. Record concurrent policy, equipment, staffing, and market changes. The aim is learning, not credit assignment to a favorite tactic.

“Double” can remain a private aspiration only if leadership accepts that the evidence may reject it. The process should stop adding storage where fit is weak, even when that lowers the headline rate.

What should a solar battery discovery record contain?

A solar battery discovery record should contain the customer’s decision, use case, critical or flexible loads, outage expectations, existing system and site evidence, tariff and program context, operating constraints, equipment and installation questions, ownership scenario, unresolved safety or code review, reviewer, and next evidence step. It should not begin with a battery recommendation. The record keeps product choice behind evidence.

The record turns “interested in backup” into questions the customer and project team can answer. Backup duration, whole-home language, bill management, self-consumption, resilience, and future electrification describe different operating goals. The appropriate design and equipment path depends on verified loads, system architecture, site conditions, product specifications, and qualified review.

Do not force every customer through the full record at the first mention. Ask enough to identify the decision and route the right next step. A customer who wants outage support may need a load and operating conversation before price. A customer asking about a utility program may need a current program source before a system option.

How should a battery option be released to the customer?

A solar battery option should reach the customer only when its use case, load basis, system configuration, equipment scope, operating scenario, limitations, price basis, ownership terms, reviewer, and next approval steps describe the same current project. Backup, savings, incentive, and performance language must remain limited to retained evidence and qualified review. The customer receives an operating scenario, not a promise.

The release should separate what the option is designed to evaluate from what it guarantees. A preliminary comparison can show a defined operating scenario with visible assumptions. It should not promise outage duration, whole-home coverage, bill outcomes, eligibility, interconnection, code acceptance, equipment compatibility, or tax treatment without the appropriate current evidence and authorization.

1. Confirm the customer use case and decision.
2. Identify the load, existing-system, and site evidence used.
3. Reconcile the battery, inverter, controls, and PV scenario.
4. State operating assumptions and customer actions.
5. Route safety, code, utility, equipment, finance, tax, and contract questions.
6. Review the customer language against the evidence.
7. Assign the current scenario and revision identifier.

Use this copy-ready option record:

Customer use case:
Loads or operating boundary:
Existing-system evidence:
Proposed equipment and configuration:
Modeled operating scenario:
Site and installation questions:
Utility or program questions:
Ownership and price basis:
Claims permitted:
Claims prohibited pending review:
Reviewer and release level:
Next evidence or approval step:

If an input changes, update the affected design, operation, economics, proposal, and customer explanation. Storage options have several interacting assumptions. A revised load boundary or existing-system record can change more than one page.

How should attach-rate performance be interpreted?

Interpret battery attach rate by defining the eligible opportunity, offered option, customer use case, evidence completeness, release quality, delivery capacity, and final decision reason. A higher rate does not prove better selling or customer fit, and a lower rate does not prove failure. The business should inspect the mechanism before setting a growth claim. Growth remains subordinate to customer fit.

Illustrative example, not a company result: A sales team reports low storage attachment. Funnel review shows that many opportunities were counted as eligible even though the company lacked the site, existing-system, or load evidence needed for a responsible option. Other customers never received storage discovery because sales expected a long technical detour.

The improvement plan narrows eligibility, gives reps a short use-case intake, creates a qualified handoff, and tests delivery capacity. The team measures offered, returned, qualified, and customer-declined states separately. It does not claim the process will double attachment or force storage into unsuitable projects.

If the rate rises while returns, installation exceptions, complaints, or service capacity worsen, the program has not proved a better outcome. Review downstream evidence and customer-fit reasons beside the sales metric. Compensation should not reward an option that delivery cannot support.

Use the battery option design and review context for architecture questions, but route the live project to qualified reviewers and current manufacturer, code, utility, authority, and program sources. This article owns the sales operating process, not equipment selection.

Use funnel states that preserve customer fit

One attach-rate denominator can hide why storage did or did not enter the project. Use mutually understandable states and keep the evidence behind each transition.

Do not recode every customer decline as a sales objection. Price, use case, site condition, ownership preference, project timing, complexity, trust, or another reason may be involved. Preserve the customer’s words when they provide them and avoid inventing motivation to complete a dashboard.

Use the solar storage financial modeling guide when a qualified option needs an energy and financial scenario. Keep the modeling work separate from the sales funnel state. A customer can be interested before the financial model is ready, and a complete model does not establish that storage fits their priorities.

Review the state definitions with design, delivery, service, and customer support. Sales may count an option as attached at contract, while operations considers it attached only after a buildable configuration is accepted. Publish the event used for reporting and show later returns or removals instead of silently preserving the early win.

Track delivery feedback by issue type: incomplete intake, equipment or system mismatch, site condition, utility or program change, customer scope change, scheduling, or service constraint. Treat these categories as operational evidence, not proof of fault. A stable feedback loop protects customers from a growth target that outruns the company’s ability to review and deliver the option.

Match the sales target to delivery capacity

An attach-rate program can succeed on paper while overwhelming technical review, procurement, commissioning, or service. Map the capacity required at each stage before increasing proposal volume. Count who can review compatibility, size critical-load scenarios, answer authority questions, configure operating modes, commission equipment, train customers, and respond after installation.

Use queue limits. If reviewed storage options wait behind an unbounded sales backlog, customers receive stale prices, equipment assumptions, or tariff inputs. A service-level goal should begin only when the minimum evidence packet is complete. Otherwise the team rewards incomplete requests for entering the technical queue.

Confirm the supported equipment and project types in writing. A salesperson should know which new-build and retrofit architectures the company accepts, which cases require exception review, and which work is outside current capability. Update the matrix when manufacturer documentation, training, staffing, or local requirements change.

Procurement needs version control. The battery, inverter, control equipment, protection, communications, enclosures, and accessories in the customer option should match the reviewed design and current bill of materials. Substitutions can affect compatibility, ratings, operating behavior, warranty, location, and approvals. Route them back through responsible review instead of treating the battery as a generic box.

Post-installation support belongs in the original economics. If the offered configuration requires monitoring, software, communications, inspections, subscriptions, maintenance, or customer action, show the responsibility and cost basis. A proposal that wins the sale and creates an unsupported service obligation is not a good attach-rate result.

Learn from commissioned systems without inventing a testimonial

After commissioning, compare the retained use case with the configured operating mode and customer training record. Confirm that the customer knows which loads are backed up, how reserve settings affect daily operation, where status appears, and whom to contact. Do not assume the handover succeeded because the equipment turned on.

Classify support questions. Confusion about backup boundaries may require a better sales explanation. Repeated missing documents may require a new intake field. Unexpected tariff results may show that the model or customer training needs review. Equipment faults and installation issues follow their own technical process.

Use operating observations for internal learning only within their evidence boundary. A measured result from one site can help that site’s review. It does not establish expected savings, duration, or reliability for another customer. Public case material needs permission, complete provenance, qualified review, and language limited to the documented conditions.

Feed verified lessons back into qualification. If certain load profiles, site constraints, or customer objectives regularly produce no-fit decisions, screen them earlier. If one question consistently improves the technical handoff, add it to intake. The attach-rate process should become more selective as it learns, not merely more persuasive.

Review cancellations and scope changes after signing. A customer who removes storage because the final electrical scope differs from the proposal may reveal an early evidence gap. A customer who changes objectives may reveal a weak use-case conversation. Treat these events as process evidence rather than individual blame.

Use a release checklist

Before a battery option reaches the customer, confirm:

1. The customer use case and priority are recorded.
2. The load and tariff evidence fit the decision stage.
3. Site, electrical, and existing-equipment status are visible.
4. Each option maps to reviewed equipment and a named design.
5. Backup loads, operating mode, and duration assumptions are explicit.
6. Financial value does not double count incompatible battery uses.
7. Incentive, finance, warranty, and utility claims have current sources.
8. Missing conditions have owners and rerun triggers.
9. The proposal distinguishes modeled results from guarantees.
10. Sales has a responsible escalation path.

Evaluate energy-yield and financial modeling against the actual solar and storage questions your team needs answered. Request current product documentation and a demonstration of any required storage, dispatch or export functions; this sales playbook does not verify native battery optimization capabilities. Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Frequently Asked Questions

What does battery attach rate mean in solar sales?

Battery attach rate is the share of a defined group of solar opportunities or sales that also includes storage. The company must state the denominator, stage, market, and time period. A rate based on signed projects differs from one based on proposals, leads, or completed installations, so internal comparisons need a stable definition.

Should every solar customer receive a battery quote?

Every customer can be asked a short, neutral storage-use-case question, but a detailed quote should follow evidence and fit. Some sites, budgets, tariffs, objectives, electrical conditions, or regulations may not support the option. A documented no-fit decision is more useful than forcing storage into a proposal the team cannot defend.

What information is needed before proposing a solar battery?

Collect the customer’s objective, critical loads, outage experience, consumption timing, applicable tariff, existing or proposed PV design, site and electrical information, equipment compatibility, operating preferences, and future load changes. The level of detail depends on the decision stage, but missing inputs should remain visible rather than becoming favorable assumptions.

Can a salesperson promise backup duration?

No fixed duration should be promised without a reviewed load definition, battery configuration, usable-energy assumptions, operating mode, reserve setting, equipment limits, starting state, and other relevant conditions. Present a modeled scenario tied to those inputs. Actual duration can differ when customer loads, weather, equipment behavior, or operating choices differ.

How should a company measure battery attach-rate improvement?

Define the eligible opportunity group, measure a current baseline, and track qualification, option creation, review, customer selection, signed scope, and completed installation separately. Compare similar periods and markets, record process changes, and inspect no-fit reasons. Do not publish a performance claim until retained evidence supports its exact wording and conditions.