A proposal record connected to the assumptions behind it.
Map survey, design, equipment, estimate, incentive, approval, revision, signature, and project-handoff context around the proposal process your team uses today.
Currently onboarding a first group of early-access installers.
Start with source records. Then define review and acceptance.
A useful proposal workflow makes the source, assumptions, approval, revision, and customer-acceptance record explicit.
Define which customer, site, survey, design, equipment, and estimate records are authoritative for proposal preparation.
Identify incentive, tariff, pricing, and production assumptions that require a source, review date, and approval owner.
Map version, approval, customer delivery, signature, archive, and operations-acceptance requirements.
Define which project records prepare the proposal
Review customer, site, survey, design, production, equipment, pricing, and assumption sources, including which system owns each value.
See how it comparesGive incentives and tariffs a source, date, and owner
Assess which incentives, tax assumptions, tariffs, and market values belong in the proposal, where they come from, and who approves their use.
Compare proposal toolsMap the customer-visible version and the record that starts delivery
Define revision ownership, approval, customer delivery, signature, archive, commercial conditions, and operations acceptance before relying on the workflow.
Resized to 9.8 kW per customer request
Added battery storage option
Initial 11.1 kW proposal
Proposal workflow decisions to settle before configuration.
Proposal workflow rollout
Carry each proposal requirement into the right implementation phase.
Assessment, configuration, validation, and operation each answer a different part of proposal preparation, approval, revision, and acceptance.
| Capability | Assess | Configure | Validate | Operate |
|---|---|---|---|---|
| Authoritative source records | Included | Partial | Included | Included |
| Pricing and assumption approval | Included | Included | Included | Included |
| Revision and version ownership | Included | Included | Included | Included |
| Signature and archive boundary | Included | Partial | Included | Partial |
| Operations acceptance criteria | Included | Included | Included | Included |
Included means the topic is a primary focus in that phase. Partial means it may be revisited as the rollout develops.
Common questions
Solar proposals — answered directly.
How is proposal preparation scoped in Solar1?
The assessment identifies authoritative customer, site, survey, design, equipment, pricing, and assumption records. Exact preparation, review, and delivery behavior is then configured and validated against representative proposals.
Does Solar1 include current federal and state solar incentives in proposals?
Incentive and tariff facts require a defined source, review date, geographic scope, assumption owner, and approval process. Available data and update responsibilities are confirmed during assessment before they are used in a proposal workflow.
Can Solar1 import system designs from Aurora Solar?
Solar design is an integration-assessment area. Bring the design system, records, version model, and handoff you use today. Connector or staged import availability is confirmed before implementation.
How does Solar1 handle proposal revisions?
Revision identifiers, change reasons, approvals, customer-visible versions, and archive requirements can be mapped during assessment. The configured process should be tested against the revision cases your team actually handles.
What happens after the customer signs the proposal?
The assessment defines what counts as acceptance, where the executed agreement is retained, which commercial conditions must be met, what operations receives, and who accepts the new project record.
Assess the survey-to-proposal workflow.
Bring the source systems, assumptions, approval rules, revisions, and customer-acceptance process your team uses today.