The customer signed the proposal. Operations could not reproduce it.
Usage came from one spreadsheet, the roof design from another tool, and the tariff had changed. The installer received a total but not the assumptions, approval, or version behind it.
The CRM has to preserve the decision, not just the deal stage.
A solar opportunity can cross marketing, sales development, site review, system design, finance, legal, permitting, installation, commissioning, billing, and service. Each team may use a specialist system. A useful CRM coordinates their decisions without pretending to replace their expertise.
This page is a MERGE candidate for custom CRM development. Solar has distinct objects and control boundaries, but buyers still choose among CRM configuration, integration, a custom module, and wider replacement. The energy context belongs inside that decision rather than on a thin parallel URL.
Prove one lead-to-handoff path before replacing the stack
- 1
- Market and workflow first
- Named teams, sources, rules, vendors, reviewers, and exceptions
- 14-20
- Indicative delivery weeks
- After sample records, vendor access, and approved rules are ready
- $60K
- Starting investment
- Fixed after calculations, integrations, migration, and controls
These figures describe a bounded build, not a promise of close rate, installation volume, energy output, savings, payback, approval, or revenue. Performance depends on lead quality, market conditions, field operations, installed equipment, professional decisions, data, training, and adoption.
Build when the solar workflow is distinct, repeated, and owned.
Configure and integrate a commercial CRM when it can hold the pipeline and connect specialist tools with less lifecycle burden.
A fit01A defined lead, proposal, contract, or installation handoff breaks across standard CRM objects and supported integrations.
02Sales, design, finance, operations, installation, security, legal, and market owners can supply approved rules and timely review.
03The business can own vendor contracts, data quality, rate and incentive updates, user training, exceptions, support, and maintenance.
Not a fit01The requirement is a standard sales pipeline and the main objection is licence price rather than process or control fit.
02Proposal formulas, source data, professional review, market rules, and exception ownership are undocumented or disputed.
03The buyer expects software to guarantee savings, production, finance approval, permits, incentives, installations, or regulatory compliance.
Focused scope
What one solar CRM workflow may include
01Qualification property and usage
Capture consented leads, addresses, ownership, contact preferences, source,
usage evidence, tariff references, property attributes, qualification
outcomes, duplicate handling, assignments, tasks, and reasons an opportunity
cannot move.
02Design proposal and finance coordination
Exchange approved inputs with specialist design and finance systems, preserve
versions, show assumptions and disclosures, route professional review, compare
approved options, and keep customer acceptance tied to the exact proposal.
03Contract to installation handoff
Coordinate e-signature, documents, deposits, cooling-off or cancellation
states where supplied, surveys, permits, equipment, scheduling, field
readiness, change orders, commissioning evidence, customer communication, and
exceptions.
04Integration reporting and service
Connect approved CRM, design, lender, ERP, field, inventory, support, and
analytics systems using idempotency, retries, reconciliation, audit,
role-based access, dashboards, export, monitoring, and named incident
ownership.
Choose the solar sales-system path
| Option | Use it when |
|---|
| Configured CRM | Model the pipeline with standard objects and automation | The process fits supported configuration and specialist tools own calculations. |
| CRM integrations | Connect design, finance, contract, field, and ERP systems | The systems work but duplicate entry and failed handoffs create risk. |
| Custom solar module | Own one distinct proposal or operational workflow | A bounded gap cannot be configured without fragile workarounds. |
| Custom CRM replacement | Own the wider customer and installation lifecycle | Distinct economics, controls, migration, and long-term ownership justify it. |
Every material input should have a source, effective date, unit, version, and owner. Every calculated output should identify the approved method and assumptions. If a salesperson changes consumption, equipment, price, financing, or incentive inputs, the CRM should create a new version rather than silently rewriting the document a customer accepted.
The customer view needs plain boundaries. Estimated energy, bill effect, savings, payback, environmental impact, eligibility, and finance terms may depend on variables outside the software. Scenario ranges and dated assumptions are often more honest than a confident single number. The client decides the commercial and legal wording with qualified advisers.
Delivery
From solar rulebook to a reconciled handoff pilot
Four phases connect customer evidence, approved calculations, specialist systems, and operating ownership.
- Phase 1
01Map the lead-to-live workflow
Inventory channels, qualification, properties, usage, tariffs, site checks,
designs, proposals, finance, contracts, permits, installations, systems,
reviewers, and owners.
- Phase 2
02Define sources rules and controls
Specify authoritative data, versions, calculations, disclosures, approvals,
permissions, integrations, reconciliation, documents, exceptions, evidence,
and professional responsibility.
- Phase 3
03Build and verify one market flow
Implement the bounded seller, customer, and operator journey, connect
approved vendors, migrate selected records, and test calculations, failures,
access, and handoffs.
- Phase 4
04Pilot reconcile and transfer
Run a controlled sales cohort, reconcile CRM and downstream records, train
users, review proposal and handoff exceptions, document support, and expand
deliberately.
Operating boundaries
What the solar CRM agreement must settle
- Professional decisions
- Name engineering, electrical, structural, financial, tax, legal, permitting, safety, privacy, and commercial owners for methods, approvals, exceptions, claims, and change.
- Proposal inputs
- Define source, date, unit, confidence, version, validation, correction, disclosure, and expiry for usage, tariffs, designs, equipment, incentives, prices, finance, and assumptions.
- Vendor compatibility
- Verify current APIs, permissions, regions, data rights, limits, webhooks, exports, sandbox behaviour, support, commercial terms, degradation paths, and exit before committing scope.
- Lifecycle ownership
- Set record authority, access, reconciliation, documents, cancellation, installation changes, incidents, customer support, maintenance, regulatory updates, and long-term system stewardship.
Engagement model
Price the CRM after one solar handoff is reproducible.
Related energy and CRM work