01
Project operationsAssessment area
Assess how project stages, documents, owners, and exceptions should share context.
Projects and stagesTasks and ownersDocuments and field updates
Decision to settleWhich stages are required?
Solar1 platform
One operating record for solar. From first lead to PTO.
Start with the workflow an installer already runs, then map the project records, owners, approvals, and system handoffs a configured rollout would require.
Currently onboarding a first group of early-access installers.
solar1erp.com/app/operations
Dashboard
Projects
Permits
Dispatch
Docs
Active Jobs
+ New
Active Jobs
47
+6 this week
On Track
91%
43 of 47
Pending PTO
8
utility queue
Recent Activity
Hernandez — 12.4 kW Res
InspectionPatel — 48 kW C&I
InstallChen — 7.2 kW Res
PermittedThompson — 22 kW C&I
PTOThe problem is not one missing feature. It is the handoff.
Most solar teams can sell, permit, install, and invoice. The pain starts when each step lives in a different system and the project has to be reconstructed by hand.
One job record
Sales, permitting, install operations, and job-cost context stay attached to the same project instead of being rebuilt at each handoff.
Solar-specific workflow
The platform is organized around surveys, proposals, AHJ work, inspections, interconnection, PTO, and milestone billing.
Early-access implementation
Solar1 is onboarding a first group of installers with guided setup, not a self-serve promise or a generic login flow.
Operating record
Keep the project intact as it moves between teams
The assessment identifies which lead, survey, proposal, permit, install, and billing context needs to move with the project, and where each record remains authoritative.
See Solar Sales CRMSolar1 operating recordLead to PTO
PI
SalesPipelineSite survey scheduled
PE
OpsPermittingAHJ packet in review
IN
FieldInstallCrew assigned
FI
Back officeFinanceMilestone invoice ready
Next handoffPermit approved
Job costing
Put margin context where the job is actually moving
Review how equipment, labor, subcontractor, and milestone-billing context should attach to the project, including which accounting system owns the final ledger.
See install operationsJob margin checkBefore closeout
EquipmentAttached
LaborTracked
SubcontractorsScoped
Milestone billingReady
Module map
Five operating areas to map before Solar1 is configured.
Each module starts with the records your team already trusts, then turns the unknowns into explicit implementation decisions.
02
Project financeAssessment area
Map project cost and billing context without claiming a completed accounting implementation.
Costs and commitmentsBilling milestonesAccounting handoff context
Decision to settleWhich system owns the ledger?
03
Sales and customer contextAssessment area
Define what must move from lead and proposal work into delivery.
Leads and opportunitiesCustomer and site contextProposal and contract handoff
Decision to settleWhere does the lead originate?
04
Workforce coordinationAssessment area
Review assignment, time, certification, and access needs around active projects.
People and rolesAssignments and availabilityTime and certification context
Decision to settleWho can see each record?
05
Reporting and decisionsAssessment area
Start from the decisions each role needs to make and the records those answers require.
Operational statusFinancial contextExceptions and ownership
Decision to settleWhich decisions repeat?
A rollout path that names the decision before the configuration.
Solar1 should not be dropped on top of messy operations. The assessment turns the way your team already works into a controlled rollout plan: what stays authoritative, what gets configured, what must be tested, and who needs to be enabled.
- 01Assess
Start with the system your team already trusts
Map the current tools, project records, owners, approval paths, and exceptions before changing how work moves.
- 02Configure
Shape Solar1 around real handoffs
Define stages, fields, permissions, notifications, and role views around the workflow your team actually runs.
- 03Validate
Test representative projects before rollout
Walk through sample jobs, edge cases, acceptance checks, and reporting needs before broader operational use.
- 04Enable
Train by role, then expand with control
Confirm owners, training notes, operating rituals, and review cadence so the team knows what changed and why.
Rollout responsibility
Know when each implementation question gets answered.
The workflow assessment begins the process; configuration, validation, and enablement each have a distinct job before wider operational use.
| Capability | Assessment | Configuration | Validation | Enablement |
|---|---|---|---|---|
| Current systems and record ownership | Included | Partial | Not available | Not available |
| Stages, fields, roles, and approvals | Included | Included | Partial | Partial |
| Representative project records | Partial | Partial | Included | Partial |
| Acceptance criteria and exception handling | Included | Partial | Included | Partial |
| Role training and operating ownership | Partial | Partial | Partial | Included |
✓ Included— Not availablePartial · limited or paid add-on
Included means the topic is a primary focus in that phase. Partial means it may be revisited as the rollout develops.
Common questions
Solar1 platform — answered directly.
Is Solar1 a finished self-serve platform?
Solar1 is in early access. The current path is to request access, walk through your workflow with us, and decide together whether your team is a good fit for the first installer group.
Which workflows are the focus right now?
The assessment covers project operations, finance context, sales and customer handoffs, workforce coordination, and the reporting decisions each role needs to make.
Why call it a platform instead of a CRM?
A CRM stops around the signed contract. Solar1 is structured for the handoff after the sale: permit work, install milestones, field updates, job costs, billing triggers, and PTO.
Walk through the Solar1 operating record.
Show us how a job moves through your team today, and we will map the same workflow across the Solar1 platform.