Solar Sales CRM
Solar operations features
Follow one solar project record from first inquiry through service.
Explore the records, decisions, and handoffs Solar1 can map with your team during a workflow assessment. Start with the operational problem that is costing the most attention today.
Feature map
Start where the workflow breaks.
Each area opens into three focused capability pages with records, roles, implementation checks, and related workflows.Project operations
Coordinate delivery around stage evidence and cross-department ownership, while keeping schedule dates separate from proof that work is ready or complete.
For project manager and operations coordinator.Design and proposals
Keep technical and commercial assumptions traceable from the site visit through the proposal version accepted for delivery.
For site surveyor and solar designer.Permitting and PTO
Organize regulatory work around effective requirements, controlled submissions, deficiency loops, and evidence-backed approvals.
For permit coordinator and interconnection coordinator.Field operations
Give dispatchers and crews a focused daily workflow tied to project readiness, approved scope, field evidence, and accountable follow-up.
For dispatcher and crew lead.Inventory and procurement
Protect the physical inventory ledger while giving project teams a clear view of demand, shortages, substitutions, kits, and installed equipment.
For procurement specialist and warehouse lead.Finance and profitability
Give finance and operations a controlled project baseline and a traceable view of cost, billing, forecast, and margin decisions.
For finance manager and project manager.Customer and service
Extend the project record into clear customer communication and accountable service without exposing internal operational or financial detail.
For customer success representative and service coordinator.A feature matters only when the surrounding handoff works.
Every feature is scoped around the records, owners, and decisions it needs to carry across the operating workflow.
- 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.
Next step