Solar1 — Proposals & Quotes
Generate proposals from your project data. Not from last week's template.
The average solar proposal takes 2–4 hours to prepare by hand. Most of that time is re-entering data that already exists somewhere else. Solar1 closes that gap.
2–4 hrs
avg time to prepare a solar proposal manually
What manual proposals actually cost
The problem isn't your team. It's the process.
Proposal rework is structural, not human error
When system design lives in Aurora, customer info in the CRM, and financial assumptions in a spreadsheet, any proposal involves re-entering data from three places. Every time. The first error you catch costs 20 minutes. The one you don't catch until the customer questions it costs the deal.
"Proposal_FINAL_v3_REVISED.pdf" is not version control
Most solar teams maintain proposal versions across email threads and shared drives. When a customer requests a system change, the updated proposal is a new file — and the previous version is still circulating. Closing teams spend real time tracking which version is current.
Incentive calculations change, proposals don't always follow
The federal ITC is 30%. State incentives vary and change. SREC prices fluctuate. When these numbers live in a proposal template that someone built two years ago, customers get financials that don't match current programs — and you find out at signing.
“Most solar companies finish a project before they know whether it was profitable. The cost accounting comes after the final invoice — which is too late to adjust anything.”
Solar1 — Operational truths for growing installation teams
How Solar1 handles proposals
From system design to signed contract in one workflow.
Generate from project data — not from scratch
When your system design, site survey, customer information, and equipment selections live in Solar1, proposals generate from that data. Customer name, address, system specifications, equipment model numbers, production estimates, and utility rate assumptions populate automatically. You review and send — not assemble.
- Auto-populate from system design and customer record
- Equipment spec sheets attached from the product library
- Utility rate and production estimates from your project data
- White-labeled — your logo, your brand, your document
Incentive modeling that reflects what's actually available
Solar1 maintains current federal, state, and utility incentive data — ITC, MACRS, state tax credits, SREC programs, net metering tariffs — and applies them to each proposal based on the project location. Customers see accurate 25-year financial projections, not spreadsheet guesses.
- Federal ITC at current rates applied automatically
- State incentive library by jurisdiction
- SREC program eligibility and pricing by market
- Net metering tariff applied based on utility and rate class
Version control — one record, complete history
Every proposal version is stored in the project record, timestamped, with a note of what changed. When a customer requests a smaller system or different financing, you revise — you don't create a new file. The customer sees one clean proposal. You see the full history behind it.
- Version history with change notes on every revision
- Customer-facing link always shows the current version
- Side-by-side comparison for customer-requested changes
- Revision approval workflow for proposals above threshold value
e-Sign and contract in one flow
When the customer is ready to sign, the proposal converts to a contract without re-formatting. DocuSign and Adobe Sign are natively integrated — the customer signs on the same link where they reviewed the proposal. Countersignature triggers the deposit invoice and moves the project to the operations queue.
- DocuSign and Adobe Sign native integration
- Contract generated from the accepted proposal
- Countersignature triggers deposit invoice automatically
- Signed contract stored in the project record permanently
The full workflow
Site survey complete
Data captured in Solar1
System design finalized
Specs attached to project
Proposal generated
From project data, not templates
Contract signed
Triggers deposit + ops handoff
How Solar1 compares
Proposal tools built for solar vs. tools adapted for it.
| Capability | Solar1 | Aurora Solar | HubSpot | Manual / PDF |
|---|---|---|---|---|
| Auto-populate from project data | ✓ | Design only | ✗ | ✗ — re-enter every field |
| Live incentive calculations (ITC, SREC) | ✓ — updated by location | Partial | ✗ | Manual — stale spreadsheet |
| Version control with history | ✓ | ✗ | ✗ | Filename: FINAL_v3 |
| Native e-sign (DocuSign / Adobe Sign) | ✓ — in same flow | ✗ | Add-on | Separate tool + upload |
| Contract generated from proposal | ✓ — automatic | ✗ | ✗ | Re-format manually |
| Countersign triggers deposit invoice | ✓ — automatic | ✗ | ✗ | Manual invoice creation |
| Connected to ops handoff | ✓ — same system | ✗ | Manual data entry | Email to ops team |
| Prep time per proposal | ~25 min | 1–2 hrs (design only) | 2–3 hrs | 3–4 hrs |
Common questions
Solar proposals — answered directly.
How long does it take to generate a solar proposal in Solar1?
Most Solar1 customers prepare a proposal in 20–30 minutes. That time is spent reviewing — not assembling. Customer name, address, system specifications, production estimates, equipment specs, and incentive calculations populate automatically from the project record. Manual proposal preparation typically takes 2–4 hours per job when data lives in separate systems.
Does Solar1 include current federal and state solar incentives in proposals?
Yes. Solar1 maintains a current incentive library including the federal Investment Tax Credit (ITC) at current rates, MACRS depreciation schedules, state tax credit programs, SREC pricing by market, and net metering tariffs by utility. Incentives apply automatically based on the project location. Solar1 does not rely on proposal templates that become outdated.
Can Solar1 import system designs from Aurora Solar?
Yes. Solar1 connects natively to Aurora Solar. System specifications, shading analysis, and production estimates import directly into the Solar1 project record. Proposals generate from the imported data. There is no copy-paste between Aurora Solar and a proposal template.
How does Solar1 handle proposal revisions?
Every revision is stored in the project record with a timestamp and change note. The customer-facing link always shows the current version — you do not need to resend a PDF. Side-by-side comparison is available for system size or financing changes. Revision approval workflows are configurable for proposals above a set value threshold.
What happens after the customer signs the proposal?
When the proposal is countersigned, Solar1 automatically generates the deposit invoice, creates the project record in the operations queue, and archives the signed contract. The operations team receives the handoff with the full project record — system design, site survey data, customer information, and signed contract — without any manual re-entry.
Stop rebuilding proposals from scratch.
When your project data lives in one system, proposals generate from that data. Your team reviews and sends — instead of assembling.
14-day free trial · No credit card required · Guided setup included