Pricing
One platform. A quote built around your rollout.
Pricing is scoped after reviewing your operating model, required workflows, migration, integrations, rollout, and commercial requirements.
No public self-serve trial. Exact terms are confirmed during the walkthrough.
Quote inputs
Project model, teams, entities, and workflow priorities.
Migration, integrations, validation, and training.
Support, security review, billing, and offboarding terms.
Illustrative planning model
Model a buyer-provided operating scenario.
Tools you run today
Assumptions: selected tool categories use illustrative monthly ranges. Coordination uses 1.5-4 hours per install at a loaded rate of $35-$55 per hour. Replace these assumptions during assessment.
Illustrative annual operating-cost range
$14,500–$52,000
A scenario combining selected tool assumptions and coordination time. This is not a Solar1 price or customer result.
Illustrative scenario only. It is not a savings guarantee, product outcome, or substitute for a reviewed quote.
Quote scope
What shapes a Solar1 quote.
Pricing follows the operating model and implementation work agreed during assessment. These are the inputs we review before proposing scope or terms.
- 01Company and project model
Establish the operating context the rollout must support.
- Residential, commercial, or mixed work
- Project volume and complexity
- Entities, branches, and teams
- 02Required workflows
Choose the records, roles, approvals, and exceptions to assess first.
- Current handoffs and owners
- Required controls and approvals
- Exceptions that cannot be ignored
- 03Data migration
Define what must move, how it will be validated, and what can remain archived.
- Source systems and spreadsheets
- History and attachment requirements
- Cleanup, mapping, and acceptance
- 04Integration boundaries
Document systems that must exchange data before connector scope is quoted.
- Systems and supported objects
- Sync direction and ownership
- Error handling and reconciliation
- 05Rollout and training
Plan phases, owners, validation, and role-specific enablement.
- Rollout phases and acceptance
- Roles that need training
- Internal owners and decision dates
- 06Support and security terms
Confirm operational expectations and review requirements in the quote.
- Support window and escalation needs
- Access and security review
- Commercial and offboarding terms
The assessment identifies open questions before commercial scope is proposed.
Scope table
How assessment inputs affect a quote.
The table makes each pricing input explicit without implying a package, connector, support term, or capability before it is reviewed.
| Quote driver | What we assess | Quote treatment |
|---|---|---|
| Company and project model | Project mix, volume, entities, and teams | Scope input |
| Required workflows | Records, roles, approvals, and exceptions | Configuration candidate |
| Data migration | Sources, history, quality, and acceptance | Scoped separately |
| Integration boundaries | Systems, objects, direction, and failures | Integration required |
| Rollout and training | Phases, owners, validation, and enablement | Scoped in rollout |
| Support and security terms | Support, access, review, and offboarding needs | Confirmed in quote |
FAQ
Common questions
How do I get started with Solar1?
Book an assessment and choose the workflow you want to review first. The conversation covers your project model, current systems, implementation questions, and the evidence needed before scope is proposed.
How is data migration priced?
Migration scope depends on source systems, record volume, history, attachments, data quality, mapping, and acceptance requirements. Those inputs are reviewed before migration work is quoted.
Is there a per-project fee?
Solar1 is quote-based during early access. Any project, user, workflow, migration, integration, training, support, renewal, and offboarding terms are confirmed in the reviewed quote.
Can residential and commercial teams request an assessment?
Yes. Use the project-type field to identify residential, commercial, or mixed work. Product and implementation scope is then reviewed against the workflow you bring to the call.
How are integrations handled in a quote?
Integration work is scoped only after the systems, data objects, sync direction, ownership, authentication, error handling, and reconciliation requirements are documented.
When are support and billing terms confirmed?
Support, billing, renewal, data export, and offboarding terms are reviewed before rollout and recorded in the commercial agreement. The public site does not promise a default support package.
Scope the workflow before the quote.
Bring your current systems, project model, and implementation questions. The assessment identifies what still needs validation before terms are proposed.
Now onboarding a first group of early-access installers