Fixed quote after a free call

Solar CRM automation for a pipeline that runs from lead to switch-on

Solar leads arrive from quote forms, paid ads, referral partners, door-knocking apps and phone calls, and most installers end up with a CRM that only half the team updates. We connect every source to one pipeline in HubSpot, Salesforce or the solar sales platform you use, sync it with your design and proposal software so stages move when designs, proposals and contracts change, automate tasks for consultants and send a weekly report on which sources turn into signed jobs. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why solar sales pipelines leak

A residential solar sale has more hand-offs than most trades: lead, qualification, site assessment, design, proposal, financing, contract, then a long operations tail. When the CRM, the design tool and the proposal platform do not talk to each other, consultants retype the same homeowner into three systems and the pipeline board stops matching reality.

Owners then cannot answer simple questions: how many leads came from each source last month, how many reached a proposal, how long proposals sit before signing, and which lead vendors are worth paying. Follow-up depends on who remembers.

What we build

What our solar CRM automation includes

Every lead source in one pipeline

Website quote forms, Facebook and Google lead forms, referral partner submissions, phone calls and canvassing apps feed one CRM pipeline, de-duplicated by phone, email and address.

Solar-specific stages

New lead, qualified, assessment booked, design in progress, proposal sent, financing, contract signed, permitting, installed and energised, matched to how your team actually works.

Design and proposal sync

Stage changes driven by events from Aurora Solar, OpenSolar or Enerflo, such as a design completed or an agreement signed, through their APIs and webhooks.

Consultant tasks and reminders

Call-back tasks, overdue alerts and a daily list per consultant, so no lead or signed contract sits untouched.

Clean hand-off to operations

When a contract is signed, the job, documents and homeowner details move to the project board without retyping.

Source and stage reporting

A weekly email with leads, assessments, proposals, signed jobs and cancellations by source and consultant.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Lead arrives

    A form, ad lead, referral or call creates or updates the homeowner record in the CRM.

  2. 02 Automated

    Record enriched

    Address, roof notes and uploaded documents are attached and duplicates merged.

  3. 03 Automated

    Stages sync

    Design, proposal and signature events from your solar platforms move the deal automatically.

  4. 04 Coordinator review

    Consultant works the deal

    The consultant calls, books the assessment and records the outcome.

  5. 05 Consultant or designer decides

    Pricing and design decisions

    System size, price, financing and design are decided by the consultant and designer with the homeowner, never by the CRM.

How it behaves

How the solar CRM pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the homeowner sees

  • A fast acknowledgement after they ask for a quote
  • A consultant who already knows their address, roof notes and bill
  • No repeated questions when the job moves to operations

What the team sees

  • One pipeline board that matches reality
  • Daily task lists per consultant
  • Signed jobs appearing on the operations board automatically

What the automation does

  • Captures and de-duplicates leads from every source
  • Moves stages from design, proposal and signature events
  • Flags leads with no consent record and stalled deals

Edge cases and fallbacks

Same homeowner from two lead vendors
Merged by phone, email and address; both sources recorded.
Lead without a consent record
Acknowledged by email only and flagged; no automated texts or calls.
Contract cancelled after signing
Moved to a cancellation stage with a reason field for reporting.
CRM or platform API outage
Events are queued and retried, and the office gets an alert.

Architecture

A solar CRM pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Quote forms Website, ads Referrals Partners, canvass Solar platform Aurora, OpenSolar n8n Capture and sync CRM pipeline HubSpot or SFDC Consultant Tasks and calls Ops hand-off Signed jobs Weekly report By source
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Leads arrive from quote forms, ads, referral partners and canvassing, and your solar platform reports design and signature events.
  2. 2 n8n captures each event, merges duplicates and updates the homeowner and deal in the CRM.
  3. 3 Consultants get tasks and call lists; signed contracts hand over to operations automatically.
  4. 4 A weekly report shows leads, proposals and signed jobs by source and consultant.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Solar CRM & sales pipeline automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, current CRM use, solar platforms, pipeline stages and reporting needs.

  2. 02

    Design

    2 to 3 days

    Stage definitions, field mapping, duplicate rules, webhook events and consent fields.

  3. 03

    Build

    1 to 2 weeks

    Source connections, platform sync, tasks, operations hand-off and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Leads flow into the new pipeline while consultants keep their old process, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and train consultants and the office.

  6. 06

    Support

    Ongoing

    New lead sources, stage changes and reporting tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM API or Salesforce Aurora Solar API and webhooks OpenSolar API Enerflo API and webhooks Facebook and Google lead forms

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, stages, field mapping and reporting.

    $200 – $400

  • Build

    Capture, de-duplication, stage sync and tasks.

    $500 – $1,300

  • Integrations

    CRM, lead forms and solar platform APIs.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with your current tracking.

    $100 – $250

  • Launch and training

    Switch-over and consultant training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, solar platform API plans, messaging and n8n are billed to you directly. Two-way sync with several platforms may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM and solar platform: Each vendor's own plan; OpenSolar and Enphase API access depends on the plan you hold.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: marketing texts and calls need consent

Telemarketing calls and texts using automated systems need prior express written consent; purchased leads do not carry consent for your business automatically.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

EU and UK: homeowner data

Addresses, bills and roof photos are personal data, so processors sign a contract, access is limited and retention is set before go-live.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Solar CRM & sales pipeline automation questions, answered.

It depends on how you sell. Solar sales platforms such as Enerflo bundle proposals and financing, design tools such as Aurora Solar and OpenSolar handle layouts and proposals, and general CRMs such as HubSpot or Salesforce are flexible and well documented. Many installers run a general CRM plus a solar platform, and we connect the two.

Usually. Aurora Solar publishes a REST API with webhooks, OpenSolar offers API access on its plans, and Enerflo documents its REST API and webhook events. We confirm your plan includes API access before quoting.

Rarely needed. We set up and automate the CRM you already pay for, and only build custom software when the off-the-shelf systems cannot handle a real requirement.

We import them into the same pipeline and tag the source, so you can see which vendors produce signed jobs. Consent to text or call comes from the homeowner, not the vendor, so we flag leads without a consent record.

They will if it saves them typing. Stages move from real events, tasks appear on their phone and nobody retypes a homeowner. We shadow-run with the team before switching over.

Leads by source, time to first contact, assessments booked, proposals sent, signed jobs, cancellations after signing and days from contract to energised.

Free 20-minute call

Want this for your solar & home energy installer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call