How Solar Quote Software Works: Address to Sale

Last updated: November 2026

Solar quote software connects a proposed system with the price and savings story a customer sees. The useful part is the calculation chain: site evidence informs the layout, the layout informs production, and production combines with tariffs and costs to support a financial scenario.

An address can start that chain, but it cannot settle roof condition, electricity consumption, equipment availability or the customer’s financing terms. Understanding those boundaries helps installers explain a quote and helps buyers distinguish a preliminary estimate from a firm installation offer.

This guide follows the workflow from address entry through design, pricing, proposal delivery and contract handoff. Some platforms combine several stages; others require external tools or manual checks. Treat the steps as requirements to evaluate, not features that every product automatically includes.

SurgePV publishes this post and sells solar design software.

Solar Quoting Capabilities to Verify

Evaluate the actual workflow offered for your project types and region. A feature label such as automated design or integrated quoting does not tell you which inputs are available, how exceptions are handled or who approves the result.

This is an evaluation checklist. The technical distinctions are illustrated by Google’s Solar API overview for rooftop information, the National Laboratory of the Rockies’ PVWatts V8 documentation for energy-model inputs and outputs, and SAM financial-model documentation for translating electrical output into cash flows. These references do not imply that SurgePV integrates those services.

Sources: Google Solar API, NLR PVWatts V8 and NLR SAM documentation linked above, checked November 2026. These describe stages of a calculation, not speed, accuracy or conversion benchmarks.

A useful evaluation includes an awkward project, not only a clean demonstration address. Ask the vendor to change equipment after the first proposal, correct a roof dimension and replace a tariff assumption. Watch how the team finds and reviews every affected output. That is where the difference between a convenient interface and a dependable quoting process becomes visible.

Step 1: Address Input and Site Identification

Address entry identifies the location to investigate. Geocoding converts an address into coordinates, which can help retrieve available mapping and solar-resource information. Check the result against the actual building before designing: a shared address, detached structure or misplaced pin can send the rest of the workflow in the wrong direction.

Imagery and building-data coverage depend on the provider and location. Google’s Solar API describes rooftop insights and data layers, but that does not mean every property has equally detailed data. Ask which source a platform uses, what access is included and whether commercial use or export has restrictions.

The address is also a clue to the utility and permitting authority, not proof of the customer’s rate plan. Service territories can overlap geographically, and customers may have different tariffs within one utility. Match the provider, meter identifier and rate schedule to the customer’s bill and official tariff before using them in a savings estimate.

Record the original customer address, selected coordinates and source dates in the project. If the site contains several meters or buildings, give each a stable identifier. Do not let a later account or address correction silently change which roof and consumption record the quote represents.

At this stage, ask for roof history, known obstructions and any planned building changes. These inputs help decide whether remote evidence is sufficient for a preliminary quote or whether a survey must come first. Leave unresolved fields visibly pending instead of filling them with plausible values that later look verified.

Step 2: Satellite Imagery and 3D Roof Modeling

A roof model describes the surfaces and constraints used for module placement. It may be created from imagery, lidar, plans, field measurements or a combination of those sources. Ask how the offered software obtains geometry instead of assuming every platform reconstructs the roof automatically from an address.

Each roof face needs a defensible orientation, tilt and usable boundary. Orientation describes compass direction, while tilt is the angle from horizontal. Neither a south-facing label nor a large visible area proves that the roof is suitable for installation.

Check these model elements:

• Roof faces, ridges, edges and changes in level
• Parapets, roof rooms, skylights and ventilation equipment
• Access routes and locally required clearances
• Chimneys, trees and neighbouring structures that may shade the array
• Areas reserved for drainage, maintenance or future roof work
• Dimensions whose source or reliability remains uncertain

Aerial imagery can omit hidden features or predate a building alteration. Compare it with owner photographs, plans and later survey evidence. Record where the model uses an estimate and what decision that estimate is allowed to support.

SurgePV supports 3D roof modeling and array layout. The input method, available imagery and any automated geometry behaviour should be demonstrated in the offered configuration. Keep the accepted geometry revision with the project so later calculations can be traced to the same roof.

Roof condition and structural suitability remain separate questions. A model can show where panels might fit without proving that the covering, attachments or supporting structure can accept them. Identify the responsible roof and structural reviewers before making a firm installation commitment.

Step 3: Shade Analysis and Sun Position

Shade analysis estimates how obstructions affect the solar resource available to the array. The result depends on the represented objects, their dimensions, the time basis and the calculation method. A coloured roof image is useful only when the reviewer knows what it represents.

Sun-position calculations use location and time to establish where the sun is relative to the site. A shading model then assesses obstruction effects for the chosen time steps. Ask about interval length and seasonal coverage rather than assuming every tool uses an identical hourly method.

Near objects and terrain horizons need different evidence. A hill on a horizon model may be represented while a chimney is not. The JRC PVGIS user manual explains horizon inputs and solar calculations; verify how nearby objects are handled in the particular model you use.

The electrical effect of shading also depends on module and inverter configuration. A shaded module does not create one universal loss for every string. Bypass diodes, wiring, maximum power point tracking and power electronics affect the response. Require equipment-specific treatment where that difference is material to the quote.

If a report includes total solar resource fraction, or TSRF, retain its definition and reference surface. Do not apply an unsupported universal acceptance threshold or imply that an optimizer can recover sunlight that never reaches the module. Compare alternative layouts under the same assumptions.

A useful shading review shows which obstacles are included, which heights remain uncertain and how those uncertainties affect layout. The customer should be told when tree growth, future construction or an incomplete survey could change the estimate.

Step 4: System Sizing Against Consumption

System sizing connects the usable site with the customer’s energy objective. Start with consumption evidence and the intended operating model, then check whether roof area, electrical capacity, connection rules and budget support the proposed array.

Monthly bills show seasonal totals. Interval consumption can provide more detail about when electricity is used, which matters for time-of-use tariffs, demand charges and storage. An annual total may support an early screen, but it cannot reveal every mismatch between solar production and load.

Agree the objective in plain language. The customer may want to reduce purchased energy, improve daytime self-use or add separately designed backup capability. An annual generation target is different from the percentage of the bill eliminated or the share of consumption served during each interval.

Check planned changes such as electric heating, vehicle charging, new equipment or occupancy. Use a separate scenario for uncertain future loads. Do not silently increase system size and describe the result as matched to the existing bill.

The design also needs electrical review. Phase, service rating, inverter limits and export conditions can constrain the proposal. A consumption-based sizing formula should not override those checks. Where the roof cannot accommodate the target, explain the achievable design and its limitations rather than forcing the layout to fit a sales promise.

Step 5: Equipment Selection and the Pricing Database

Equipment selection turns the concept into a defined scope. Identify exact models and quantities before using the bill of materials, or BOM, as a pricing basis. A brand name or a capacity class alone is not enough to verify compatibility, warranty or delivered cost.

For modules, retain the manufacturer datasheet and review rated power, physical dimensions, electrical characteristics and relevant temperature behaviour. Use the exact warranty document for any degradation assumption. Do not apply a generic premium-module degradation rate to every product.

For inverters, review voltage and current limits separately. Open-circuit voltage, operating voltage, operating current and short-circuit current are different quantities. Check the string configuration against manufacturer documentation and the applicable standard under the relevant conditions. Do not treat an MPPT voltage range as a current limit.

Storage adds its own compatibility and operating requirements. Some systems use a hybrid inverter; others use a separate AC-coupled battery inverter. The presence of a battery does not make one topology mandatory for every project. Record usable energy, power, operating limits, control strategy and the equipment combination approved by the manufacturer.

A pricing database is useful only when its source and scope are known. Ask whether prices are vendor-maintained, installer-entered, imported or obtained through a supported supplier connection. Check currency, tax treatment, freight, regional availability and validity. A catalog entry is not a binding supplier quote.

Build costs for installation as well as equipment. Labour, access, scaffolding, roof work, electrical upgrades, permitting and commissioning may change the delivered total. Show exclusions and allowances explicitly. Unknown cost is not zero cost, and a preliminary estimate should have a clear route for resolving it.

Margin and markup need distinct definitions. Margin expresses profit relative to selling price; markup expresses an addition relative to cost. Have the responsible commercial reviewer check which convention the tool uses before comparing offers or setting pricing rules.

Keep alternatives comparable. If one option adds storage or roof repairs, label the additional scope instead of implying that the price difference is solely a change in module quality. Retain the supplier evidence behind each accepted equipment choice.

Step 6: The Energy Model Behind the kWh Number

An energy model estimates electrical production from the site, array and operating assumptions. Different tools use different levels of detail. Ask which model is running, which inputs the user can change and which outputs or loss summaries are available for review.

Plane-of-array irradiance is solar power incident on the tilted module surface. The model relates the available solar-resource data to the array’s orientation and mounting. Direct, diffuse and ground-reflected radiation can contribute differently, so a horizontal resource number alone is not the array’s electrical output.

Temperature modeling estimates cell or module operating conditions from weather and installation assumptions. Manufacturer temperature characteristics then affect electrical output. Keep the equipment model and mounting assumptions consistent across design alternatives rather than applying an unexplained blanket correction.

The inverter stage converts direct-current output to alternating-current output within its limits. Efficiency can vary with loading and voltage, while clipping and export limits can restrict delivered power. Retain the treatment of these effects so they are not silently counted twice.

PVWatts V8 documentation identifies inputs such as capacity, array type, tilt, azimuth, losses and DC-to-AC ratio, and distinguishes monthly energy outputs from hourly power outputs. It is an example of a documented model interface, not a specification of SurgePV’s internal engine. Record the actual model and data version used for your quote.

Review monthly as well as annual results. A total can conceal seasonal mismatch with consumption or a configuration that relies heavily on export. Where interval data is available, use it to investigate the timing of production and load rather than inferring self-consumption from two annual totals.

Step 7: Financial Modeling, Payback and Cash Flow

Financial modeling translates production and project costs into cash flows under a stated ownership arrangement. The customer’s savings depend on the tariff, consumption timing, exports and continuing charges, not just total annual kWh.

SAM’s financial documentation explains the link between performance-model output and annual cash flows. Apply the same discipline to a quote: name the energy result being used and retain the financial inputs separately. A later tariff or financing change should not be mistaken for a change in physical production.

Review these bill components:

• Import energy charges, including time periods and tiers where relevant
• Export compensation and any credit settlement rules
• Fixed charges that continue after solar installation
• Demand charges and the intervals used to determine them
• Taxes and other charges affected by the specific tariff
• Escalation assumptions, clearly distinguished from known rates

Self-consumed energy can reduce purchases, but the avoided cost depends on the actual bill structure. Exported energy may receive a different value. A battery can change timing, but its dispatch, losses, operating limits and cost must be included before claiming a financial benefit.

For US homeowners, the IRS Residential Clean Energy Credit guidance states that property placed in service after December 31, 2025 is not eligible for that credit. Do not assume a new 2026 homeowner installation receives it. Business-owned systems and other incentives require their own current eligibility analysis.

Keep an incentive estimate separate from cash already available to pay the installer. Identify the applicant, qualifying conditions and timing. If eligibility remains unresolved, present a scenario without the benefit rather than treating it as assured funding.

Cash purchase, loan, lease and power purchase agreement (PPA) should not be compared as though ownership and obligations were identical. A loan involves repayment terms and may leave a utility bill alongside it. A lease and a PPA have different payment bases and contract conditions. Use the finance provider’s actual written terms.

Payback describes when accumulated benefits recover a defined cost under the model. Net present value discounts cash flows at a stated rate, while internal rate of return is the discount rate that brings the modeled net present value to zero. Explain which costs, replacements and financing effects are included before comparing metrics.

Avoid universal payback ranges or claims of free electricity after a particular year. Equipment maintenance, replacement and remaining utility charges can continue. Show sensitivity to material uncertain inputs and make clear that a long-term savings projection is not guaranteed performance or a tax determination.

Step 8: Proposal Output, PDF and Web Formats

The proposal presents the accepted design and commercial scenario in a form the customer can review. A PDF, web page or printed document can work if it shows the same approved scope and preserves the assumptions behind the offer.

A useful proposal includes:

1. Customer, site and proposal revision identifiers
2. System size, layout and exact equipment schedule
3. Estimated production and the source of its assumptions
4. Itemised price, allowances, exclusions and validity
5. Ownership and financing terms supplied for review
6. Estimated savings with tariff and incentive assumptions
7. Warranty and service responsibilities with governing documents
8. Required site checks, approvals and next steps

Choose the format to fit the buyer and process. A web proposal may allow supported interactive options; a PDF may be easier to circulate or retain. Neither format by itself proves higher engagement or faster closing. Ask what happens when the underlying design changes after the document has been sent.

Where customer-adjustable scenarios are offered, distinguish exploration from an accepted quote. Changing a battery quantity or financing option should not silently create a contractual commitment. Require the appropriate review and clearly identify the version approved for signature.

Branding and presentation should help the customer understand the project. Use legible charts, consistent units and plain-language exclusions. Avoid displaying technical precision that the inputs cannot support, such as a highly specific lifetime saving based on an assumed tariff and incomplete consumption record.

If proposal analytics are included, verify what the event actually measures. An opened link may be forwarded or accessed by someone other than the decision maker. Treat it as a possible follow-up cue, subject to applicable privacy requirements, rather than proof that the customer understands or accepts the terms.

Step 9: E-Signature and Contract Management

Signature and contract functions are product-specific. They may be built into a quoting platform, provided by a separate service or handled through an external process. Verify the available workflow and local legal requirements before promising a customer they can complete everything inside one interface.

The signed document should identify the final scope, price, parties and referenced attachments. A customer selecting a preliminary scenario is not automatically accepting a complete installation contract. Have the responsible commercial or legal reviewer check the document before release.

Ask how signers are identified, how co-owners or company representatives are handled and what evidence is retained. Review the applicable process for correcting a mistake, replacing an offer or issuing a change order. Do not assume an activity log alone resolves legal authority or enforceability.

After signing, retain the accepted artifact and its related design revision. The delivery team needs the equipment scope, exclusions, site assumptions and outstanding conditions, not only a notification that the opportunity is won. A signature does not automatically grant a permit or utility authorization.

For software evaluation, make the handoff observable. Ask the vendor to show the approved record, exported documents and receiving-system steps. Identify any manual work and the person responsible. This is particularly useful where sales, engineering and scheduling use separate systems.

Do not infer native e-signature, automated contracts, proposal tracking or customer chat from SurgePV’s documented proposal-generation capability. Confirm additional functions in the offered configuration and written scope.

Step 10: Utility Rate Databases and Tariff Checks

A utility-rate database can help populate a financial model, but the selected record must match the customer. Retain the provider, tariff identifier, effective dates and relevant eligibility conditions. If a rate is entered manually, retain the official tariff evidence and reviewer.

Check which tariff components the calculation supports. Time-of-use periods, tiers, demand charges, fixed charges and export credits may interact. Demand measurement intervals and ratchets are tariff-specific; do not assume one interval or rule applies to every commercial customer.

A rate change can affect an old proposal even when the roof and equipment remain unchanged. Assign responsibility for refreshing the financial scenario and deciding whether the offer needs reissue. Keep the original version for traceability instead of replacing its inputs without a record.

Escalation is an assumption about future prices. Label it as such and show its effect on long-term results. A past average does not guarantee the customer’s future tariff path. Test a lower-escalation case where the investment decision depends heavily on projected rate growth.

Before using an integration, check coverage, update process, error handling and any manual overrides. Do not assume that a large database contains the exact tariff, export policy or special programme applicable to the meter. The customer’s bill and utility’s official rules remain important evidence.

SurgePV Quote Workflow: Design to Reviewed Proposal

SurgePV’s approved product scope includes 3D roof modeling, array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output and proposal generation. Evaluate how those functions fit your quoting process using a representative project.

Start with the source package: site information, available geometry, consumption evidence, equipment documents and cost assumptions. Ask how the offered workflow accepts each input and how missing data is recorded. Do not assume an address alone supplies a verified utility rate, exact geometry or complete project cost.

Review the model and array layout before relying on the production result. Identify the person responsible for site constraints and electrical compatibility. Request an explanation of the weather, equipment and loss assumptions represented in the offered energy workflow.

Next inspect the financial scenario. Check the tariff, ownership, financing and incentive inputs that your customer actually needs. If an assumption or metric is unsupported, keep it in a clearly governed external calculation rather than inferring a native capability from the phrase financial modeling.

Finally inspect the proposal output. Check whether the customer can trace system size, equipment and estimated savings to the accepted project revision. Confirm available formats, exports and commercial terms. Keep signature, accounting, procurement and authority decisions in their designated processes unless the offered integration has been demonstrated.

There is no verified universal quoting duration or accuracy guarantee in the approved product scope. Time a representative pilot, including review and corrections, if speed matters to the buying decision. A result depends on source data, assumptions, equipment models, configuration and responsible review.

Data Inputs Explained: What the Software Needs and Why

Every input should have a purpose, source and review status. The following categories help the team distinguish a usable project record from a collection of plausible defaults.

Address and site identity

The address locates the investigation, while the site identifier keeps the work attached to the correct building and meter. Preserve unit numbers, separate structures and any boundary issue. If the selected mapping location changes, review whether the geometry, weather or authority assumptions also need correction.

Electricity consumption data

Consumption evidence supports sizing and bill modeling. Collect a complete seasonal record where available and request interval data when timing matters. Mark estimated or missing periods, identify any existing solar generation and distinguish grid imports from total behind-the-meter consumption.

If the customer provides only one bill, explain the limitation. Ask whether that period reflects normal occupancy and operations. Planned electric vehicles, heating or production equipment should appear as separate load scenarios rather than unrecorded changes to the baseline.

Tariff structure

The tariff determines the value of changed electricity flows. Match the rate name and effective period to the meter. Retain the utility schedule and identify charges that remain after installation. A familiar utility name does not make every customer eligible for the same import or export terms.

Roof orientation, tilt and condition

Orientation and tilt affect solar-resource calculations, while condition affects installation feasibility and cost. Record their sources separately. A precise-looking model can still depend on uncertain dimensions, and a suitable orientation cannot compensate for an unresolved roof repair or structural constraint.

Battery preferences and operating purpose

Ask whether the customer wants backup, self-consumption, tariff management or a combination. Define critical loads and required operating conditions for backup. For financial modeling, record dispatch rules and reserve assumptions. A storage scenario should not imply whole-home backup unless the complete design supports that claim.

Price and contractual scope

A quote needs a dated price basis and a clear list of included work. Record supplier validity, labour scope, taxes, access requirements and authority fees. Identify which items can change after survey and how the customer will approve the revision. Keep warranties and service obligations tied to their actual provider documents.

How the Energy Model Handles Edge Cases

Edge cases should change the model or trigger specialist review, not be hidden inside a generic loss factor. Ask for a demonstration using the cases your business encounters.

Oversized arrays and clipping. Available DC power can exceed an inverter or control limit. The model should represent the relevant power limits and avoid deducting clipping twice. Compare designs using the same weather and equipment evidence before deciding whether a larger array is worthwhile.

Ground-mounted systems. Ground layouts introduce terrain, row spacing, access, mounting and possible tracking requirements. Verify that the offered tool supports the intended configuration. A rooftop model should not be assumed to represent every ground-mounted or utility-scale project.

Bifacial modules. Rear-side contribution depends on the module, mounting and surrounding reflectance. Do not assign a universal gain percentage to all bifacial installations. Record the model and input basis, including whether the quoted result includes rear-side effects at all.

Long-term performance change. Use a supported degradation assumption and distinguish it from a warranty threshold. A financial projection should identify its analysis period and replacement assumptions. Do not treat the module warranty duration as proof that every system component will operate without cost for the same period.

Grid export controls. Match the approved connection conditions and control strategy. Export limits can change production use and storage operation, so they belong in the energy and financial scenario. Keep approval pending where the utility has not accepted the proposed arrangement.

Multiple meters or changing loads. Identify which generation serves which load and tariff. A total across the property can conceal separate accounts or contractual restrictions. Request specialist modeling where the commercial arrangement cannot be represented by one simple customer-meter scenario.

Common Questions About Solar Quote Software Accuracy

Accuracy depends on the input evidence, model scope and comparison boundary. There is no single verified percentage that can be applied to all software, sites and project stages.

How close are modeled and actual production?

Compare the same system configuration, time period and meter boundary, then account for weather, outages, curtailment and maintenance. A difference between a typical-weather forecast and one operating year is not automatically a model defect. Retain enough detail to identify the cause before changing the assumptions.

For proposal use, disclose the estimate’s limitations in ordinary language. If the contract includes a performance obligation, have the responsible engineer and legal reviewer define the measurement method, exclusions and remedy. A sales estimate should not silently become a contractual guarantee.

What happens when imagery is poor?

Obtain better evidence or reduce the certainty of the offer. Request field measurements, suitable plans or authorized survey data for important dimensions. Verify whether the tool can accept those inputs and how the accepted model is revised. Do not assume software always detects low-quality imagery without human review.

How are new rates and equipment changes handled?

Assign an owner to refresh affected inputs and reissue the relevant outputs. A revised tariff may change savings without changing production; a module substitution can change layout, electrical checks, production and cost. Preserve the earlier offer and show the reason for the replacement.

What should a reviewer be able to reproduce?

A reviewer should find the source data, equipment, settings and proposal revision used for the estimate. They should also see unresolved items and approved overrides. If they cannot explain a material difference between two runs, investigate it before relying on the output for a customer commitment.

Choosing the Right Solar Quote Software for Your Business

Choose from your project mix and required handoffs. A feature list is a starting point; a representative workflow demonstrates whether the product supports the work your team must complete.

Residential teams should inspect the usability of intake, layout review and customer explanation. Commercial teams should identify required tariff, load, ownership and finance scenarios before choosing a model. Multi-region teams need a process for local equipment, authority and incentive evidence rather than assuming global coverage from a marketing label.

Use a pilot that includes a revision after the initial proposal. Have a different qualified teammate review the result without a verbal briefing. Record missing information, manual steps and the time needed to close exceptions. Measure the full accepted output, not only the first draft.

Compare costs using the offered seats, billing period, usage limits, data access and implementation scope. Confirm taxes, renewal and cancellation terms in the quote. A lower subscription price can still require more manual work, while an additional feature has little value if it does not support the actual process.

For more evaluation questions, see the solar quoting software selection guide. Review how SurgePV prepares proposals against the same acceptance checklist you use for other products.

Conclusion: Keep the Quote Traceable

A dependable solar quote connects site evidence, design, energy, cost and customer terms. Software can support that connection, but people still need to verify important inputs and approve the commitments being made.

Keep one accepted revision, label unresolved assumptions and refresh dependent outputs when something changes. To review the design and proposal functions available for your workflow, book a guided SurgePV demo.

Frequently Asked Questions

How does solar quote software work?

Solar quote software combines site inputs, a proposed design, energy estimates and cost assumptions into a customer offer. Review the inputs and accepted revision because the output is only as reliable as its evidence and model scope.

What inputs does solar quote software need?

A useful quote needs site evidence, consumption, tariff, equipment, cost and ownership assumptions. An address can start a preliminary assessment but cannot establish every fact required for a firm installation price.

How accurate are solar quote software estimates?

Accuracy depends on data quality, model scope and the operating conditions being compared. Keep weather, shading, equipment, losses and tariff assumptions visible rather than applying a universal accuracy percentage.

Can solar quote software handle commercial projects?

Some configurations can support commercial quoting, but required capabilities vary by project. Verify load, demand-charge, ownership and export-limit treatment against the actual customer scenario.

Does solar quote software include e-signature?

E-signature availability depends on the product and configuration. Check whether signing, identity evidence and document retention are native, integrated or handled externally before committing to a workflow.

What is the difference between a solar quote and a proposal?

A quote usually focuses on price and scope, while a proposal also explains the design, production and financial case. In either format, identify assumptions, exclusions and the accepted project revision.

How long does it take to generate a solar quote?

Quoting time depends on source-data readiness, design complexity and required review. Measure a representative pilot through corrections and acceptance rather than relying on an unsupported universal turnaround claim.