Capture the objective and source trail
Record the customer goal, property authority, energy-use period, address, roof statement, disclosed constraints and source for every supplied fact.
Workflow blueprint
Solar CRM software that separates interest from technical approval
An enquiry-to-site-evidence blueprint where commercial progress never implies that a building, design, permit, finance decision or grid connection is approved.
Coordinate the customer conversation and specialist handoffs while excluding system design, yield, structural suitability, finance, permit, interconnection, installation and permission-to-operate claims.
TL;DR — Coordinate the customer conversation and specialist handoffs while excluding system design, yield, structural suitability, finance, permit, interconnection, installation and permission-to-operate claims.
Schedule observation with permission
Confirm site access, responsible contact and allowed evidence before a visit, then store salesperson observations separately from qualified findings.
Gate proposal review on missing evidence
Keep price ranges and production expectations visibly unapproved until the required technical reviewer confirms the applicable inputs and assumptions.
Reference external decisions without imitating them
Link permit, inspection, utility and finance outcomes to their issuing authority while the CRM controls owner, communication and next action only.
Page-specific decision aid
An interest-to-site-evidence solar qualification packet
The packet follows a rooftop enquiry through customer objectives, energy-use evidence and a consented site visit. Sales observations stay separate from the assessor finding. Proposal review remains blocked while property authority and the measurement period are unresolved, and later permit or utility references point to outside decisions instead of CRM-made approvals.
- ✓A confident salesperson cannot approve the roof or system.
- ✓An estimate stays labelled until its assumptions are reviewed.
- ✓CRM progress never becomes permission to install or operate.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Customer statements and observed site facts remain separate
- ✓Qualified findings identify their reviewer and source evidence
- ✓External approvals retain the issuing authority and decision date
- ✓Design, yield, finance, permit, grid and installation functions excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow