Solar Proposal Software That Ties Design, Production, and Interconnection (2026)

Solar proposal software that actually works in 2026 keeps the kW DC system size, the kWh production estimate, and the interconnection paperwork on the same job record from the first site visit to permission to operate (PTO). If your sales tool, your design software, and your utility application live in three different systems, someone on your team is re-keying numbers, and re-keyed numbers are where proposals stop matching what actually gets built and interconnected.

That is the whole job of the platform: one file, one system size, one production number that survives contact with the roof, the panel, and the utility. Most proposal tools fail this because sales, design, and interconnection paperwork were built as separate products and bolted together later. The rest of this guide covers where that breaks down on real jobs and what to check before you build your next proposal.

Why design, production, and interconnection have to live in one file

A solar deal has three separate documents that all have to agree with each other: the signed proposal, the permit set your AHJ reviews, and the interconnection application your utility processes. If those three come from different tools, or from the same tool run three separate times by three separate people, small mismatches creep in. A system sized at 8.4 kW DC on the proposal becomes 7.9 kW DC on the permit set because someone dropped a module during stamped design. Nobody catches it until the inspector does.

The fix isn't more review steps. It's not having three separate data entry points in the first place. When the roof plane azimuth and tilt, the module and inverter selection, and the production estimate all pull from one job record, a change on one end shows up everywhere else automatically. That's the actual argument for tying design, production, and interconnection together in one system, not as a sales pitch but as a way to stop your own team from creating change orders after a homeowner has already signed.

The site survey has to come before the proposal, not after

A lot of shops still build proposals backward. Sales pulls a rough roof size off satellite imagery, sizes a system to hit a target monthly bill offset, and generates a proposal PDF before anyone has set foot on the roof. The real site survey happens later, sometimes days before install, and that's when the crew finds a roof plane shaded from early afternoon on by a neighbor's tree, or a main service panel too small to support the interconnection without an upgrade.

By then the signed proposal doesn't match what can actually get built. Flip the order instead. Get actual roof plane azimuth and tilt, obstruction locations, and service panel condition into the design before you present a production estimate as final. If your process lets sales issue a "final" number before a survey has confirmed roof geometry and electrical service capacity, you're setting up a change-order conversation with a customer who already thinks the deal is done. That conversation costs trust every time, and it costs deals when the pricing math is already tight.

kW DC is a spec. kWh production is the sale.

System size in kW DC tells you the nameplate rating of the array under standard test conditions. It doesn't tell a homeowner what their bill will look like. What closes deals is the kWh production estimate and the offset percentage, how much of the household's actual annual usage the system is expected to cover given roof orientation, shading, and local weather patterns.

A shade analysis run against real obstruction data, not a satellite guess, is what makes that production number defensible when a homeowner (or their electrician, or their loan underwriter) asks you to justify it later. Undersell production and you leave money on the table in the sales conversation. Oversell it and you're the one fielding a call eight months after PTO when the utility bill doesn't match what was promised. Build the habit of presenting production as a range tied to the survey data you actually have, not a single confident number generated before the shade analysis is final.

Interconnection paperwork is not an afterthought

NEC interconnection requirements and utility net metering or successor tariff programs vary by jurisdiction and by utility, and they change the math on a deal more than most sales conversations account for. Some utilities process interconnection applications in a couple of weeks. Others run months behind, especially when a service panel upgrade or a supplemental disconnect is required. If your proposal software doesn't flag when a job needs an upgraded panel or a specific interconnection pathway, that discovery happens after the contract is signed, which is the worst time for everyone.

Build interconnection timeline estimates into the proposal itself, even as a range. A homeowner who understands upfront that PTO might take six to ten weeks under their utility's current process is a homeowner who doesn't call you in week three wondering why the system isn't turned on yet. That single line item, set honestly, prevents more service calls than almost anything else in the proposal.

Pricing conversations without a federal credit to lean on

Federal incentive policy for residential solar has been in flux, and the rules that applied to a job signed in 2024 are not guaranteed to apply to a job signed in 2026. Don't build a proposal or a sales script around a specific credit percentage without checking current federal guidance first, because that number can change out from under a deal that's still in the pipeline. Whatever the current federal, state, or utility incentive picture looks like when you're reading this, verify it directly before you quote it to a homeowner.

What that means for your proposal process: the production estimate, the offset percentage, and the payback math need to hold up on their own, without assuming a specific incentive will be there to soften the price. A proposal that leans entirely on an incentive that might not apply by the time the system is placed in service is a proposal that can fall apart in the middle of a sales cycle. Build your pricing conversation around system size, production, and utility rate trends first, and treat incentives as a bonus line item you confirm, not a foundation you assume.

Battery attach: pitch it as backup, not just savings

Battery attach rates keep climbing, and the reason isn't usually bill savings math, it's backup power. Homeowners in areas with unreliable grid service or aggressive time-of-use rate structures want to know what happens during an outage, not just what their offset percentage looks like on paper. When you pitch a battery, separate the two conversations. Backup capacity, how many hours of critical loads the battery can carry, is a different sales point than arbitrage savings under a time-of-use rate plan.

Size the battery attach based on actual critical load, not a generic package size. A homeowner running a well pump and a sump pump needs a different battery conversation than one who just wants to keep a refrigerator and some lights on. Your proposal should reflect that difference in the equipment list, not just in the sales pitch.

Retail cash vs loan deals change what the proposal needs to show

A cash deal and a loan deal are not the same proposal with different numbers at the bottom. A homeowner paying cash wants to see payback period and long-term production. A homeowner financing through a solar loan is looking at monthly payment versus current utility bill, and that math needs to account for loan term, rate, and any dealer fee built into the financed amount. If your proposal software generates one generic document and expects sales to explain the difference verbally, you're relying on your team to catch pricing nuance that should be built into the tool.

Roof work adders, tear-off and re-roof needs discovered during the site survey, hit these two deal types differently too. A cash buyer might absorb an adder into the total price without much friction. A financed deal often has a hard monthly payment ceiling, and an unexpected roof work adder can push the deal outside what the loan program will approve. Catch roof condition issues during the survey, before the loan application goes in, not after.

HOA and AHJ permit packages: build them from the same job record

Homeowners association approval and AHJ permit packages both need accurate roof plane data, equipment specs, and site plans, and both processes move slower when the paperwork doesn't match what was actually surveyed. If your permit set gets generated from the same job record as the proposal and the interconnection application, a change caught during design (a module swap, an inverter substitution, a revised roof plane) updates everywhere at once instead of requiring three separate corrections.

This is where SolarWright's approach to keeping one job record pays off in practice: the same site survey data that built the production estimate is what generates the stamped permit set and the interconnection application, so nobody is manually re-entering azimuth and tilt numbers three times and hoping they match.

What to check before you commit to a proposal tool

Ask a few direct questions before you sign a software contract. Does the production estimate update automatically when survey data changes, or does someone have to manually re-run it? Does the permit package pull equipment specs from the same record as the proposal, or is it a separate export? Does the tool flag when a job likely needs a service panel upgrade based on the electrical service data collected during survey? A tool that answers yes to all three saves your team from the re-keying errors that create change orders after a contract is signed.

Frequently asked questions

What's the biggest reason solar proposals fall apart after they're signed?

Usually it's a mismatch between what the proposal promised and what the site survey later confirms, most often roof shading, service panel capacity, or roof condition that wasn't caught before the customer signed. Running the survey before the proposal is final, rather than after, prevents most of this.

How should I present production numbers to homeowners?

Present kWh production as a range tied to actual shade analysis and roof plane data, not a single confident figure generated before survey data is final. It's more honest, and it holds up better when a homeowner questions the number months later.

Do I need to account for interconnection timelines in the proposal?

Yes. Utility processing times for interconnection applications vary widely by jurisdiction and by whether a service panel upgrade is needed. Giving homeowners a realistic timeline range upfront prevents a lot of follow-up calls during the wait for PTO.

Should I build my pricing pitch around a federal tax credit?

Verify current federal incentive rules directly before quoting them, since credit policy has changed in recent years and can change again. Build your core payback and offset math so it holds up without assuming a specific incentive applies, and treat any confirmed incentive as a bonus on top of that math.

How do I decide how big a battery to propose?

Size it around actual critical load the homeowner wants covered during an outage, not a generic package size. Ask what they need to keep running, then size backup capacity to match, separate from any savings math tied to time-of-use rates.