Case Study
Case Study: Solar Installer CRM & Job Automation
We built a connected set of automations for a residential solar and battery installer: a CRM pipeline synced with the design platform, lead qualification with survey booking, proposal follow-up, permit and interconnection tracking with homeowner updates, and monitoring alerts turned into service tickets. Consultants now work one pipeline, coordinators work one tracker, and homeowners hear from the installer at every milestone.
- Business type
- Residential solar PV and battery installer
- Team involved
- Owner, sales consultants, designer, permitting coordinator, service lead
- Systems connected
- CRM, solar design platform, e-signature, monitoring APIs, Twilio, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
Leads came from the website, paid ads and referral partners, and consultants copied each homeowner into the CRM and the design platform by hand. The pipeline board rarely matched reality.
Consultants spent much of their week on calls with renters and unsuitable roofs, and surveys waited days while the office chased bills and panel photos.
Proposals went out and follow-up depended on memory. Signed jobs then disappeared into a permitting spreadsheet, and homeowners called the office to ask what was happening.
Monitoring alerts from systems already in service landed in a shared inbox, and some homeowners noticed problems before the installer did.
Goals
What the project had to change
- One pipeline, fed automatically from every lead source and the design platform.
- Consultant time spent on homeowners who can go ahead.
- Every proposal followed up on schedule, with money questions answered by a consultant.
- Every job tracked through permit and interconnection, with homeowners updated at each step.
- Every monitoring alert owned by a person and turned into a ticket when needed.
What we built
What we built, as one connected system.
CRM pipeline with platform sync
We connected quote forms, ad leads and referral submissions to one CRM pipeline, synced stages with design and signature events, and handed signed jobs to operations automatically.
Service detailsLead qualification and survey booking
New leads get guided questions within minutes, roof data where coverage exists and secure uploads for bills and panel photos, then book a survey from the surveyor's calendar.
Service detailsProposal follow-up
Timed check-ins after each proposal, approved answers to process questions, signature chasing and consultant hand-off for anything about price, savings or financing.
Service detailsPermit and interconnection tracker
A checklist per job, stall alerts per authority and utility, signature requests and a plain update to the homeowner at every milestone.
Service detailsMonitoring alerts to service tickets
Alerts from the monitoring APIs are grouped and sorted, open a ticket with system history and come with a drafted homeowner message the service lead approves.
Service detailsArchitecture
How the installer's workflows connect
- Input
- Logic and services
- AI step
- Data
- Output
- People
How it flows
- 1 Lead sources, the solar platform and the monitoring APIs feed one n8n instance.
- 2 Five workflows update the CRM and tracker, send texts and emails, and use AI to sort replies and alerts.
- 3 Coordinators and the service lead work one set of lists; consultants take every money question.
- 4 Every step is logged, with a weekly summary of the agreed measures.
How it behaves
How the system behaves day to day
What homeowners see
- A reply within minutes after asking for a quote
- Easy survey booking and uploads
- Proposal check-ins that stop when they decide
- An update at every permit and utility milestone
- A message from the installer when monitoring spots a problem
What the team sees
- One pipeline, one tracker and one service queue
- Money and technical questions handed to the right person
- Stall alerts and a weekly backlog view
What the automation does
- Captures, qualifies, follows up and tracks on schedule
- Applies consent, opt-outs and stop rules across every workflow
- Logs every step and alerts the office if anything fails
Edge cases and fallbacks
- A homeowner asks about tax credits
- The question goes to a consultant; no automated message mentions incentives.
- An authority asks for a correction
- The job moves back a step and the designer gets a task.
- A homeowner opts out in one workflow
- One shared opt-out list stops texts from every workflow.
- A monitoring API is unavailable
- No tickets are created from missing data and the service lead is alerted.
- Twilio or n8n has an outage
- Leads are stored and emailed to the office, and the owner gets an alert.
Integrations
What we connected
Aurora Solar
Solar design and proposalsProjects, designs and proposal events for pipeline sync and follow-up.
Aurora Solar's REST API (OpenAPI reference) and webhooks, with API keys from your Aurora account.
Enphase
MonitoringSystem status and telemetry for alert-to-ticket workflows.
Enphase Monitoring API v4; installer access through Enphase's Partner plan.
SolarEdge
MonitoringSites, equipment and production data for service workflows.
SolarEdge Monitoring API on its developer platform tiers.
Google Maps Platform Solar API
Roof dataRooftop solar potential attached to leads for designers.
Google Maps Platform Solar API under your own Google Cloud account.
HubSpot
CRMContacts, deals, pipeline stages and tasks.
HubSpot CRM REST API.
DocuSign
E-signatureContracts, utility and financing forms sent and chased.
DocuSign eSignature REST API and Connect webhooks.
Twilio
SMS and voiceLead replies, check-ins, milestone updates and opt-outs.
Twilio Programmable Messaging and Voice APIs.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We sat with consultants, the coordinator and the service lead, mapped every step from lead to service and agreed consent rules and data flows.
-
02
Design and access
Week 2
Pipeline stages, qualification rules, templates approved by the owner, API access for the design and monitoring platforms, Twilio number and A2P 10DLC registration.
-
03
Sprint 1: CRM pipeline
Week 3
Built lead capture and platform sync, shadow-ran against the old board; demo and sign-off.
-
04
Sprint 2: qualification
Week 4
The pipeline went live. Built guided questions, uploads, scoring and survey booking.
-
05
Sprint 3: proposals
Week 5
Qualification went live for web leads. Built proposal check-ins, sorting and signature chasing.
-
06
Sprint 4: permits
Week 6
Follow-up went live. Built the tracker, checklists, stall alerts and homeowner updates.
-
07
Sprint 5: monitoring
Week 7
The tracker went live with open jobs migrated. Built alert collection, sorting and tickets.
-
08
UAT and handover
Week 8
The team ran acceptance tests on every workflow; we switched everything on, handed over the run book and trained the team.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Captures and de-duplicates leads and syncs pipeline stages
- Asks qualification questions and books surveys
- Sends proposal check-ins and chases signatures
- Tracks permits and interconnection and updates homeowners
- Collects and sorts monitoring alerts into tickets
The team does
- Review borderline leads and confirm surveys
- Submit permits and utility applications and chase stalled ones
- Approve homeowner messages about faults
- Book and run service visits
Consultant or designer decides
- Decides system design, size and price with the homeowner
- Answers every savings, financing and incentive question
- Approves plan sets and applications before submission
- Diagnoses faults and decides repairs
Compliance handled
Privacy, consent and safety, built in.
No incentive or savings claims by automation
Templates and AI steps refuse incentive and savings questions; the IRS confirms the Section 25D credit cannot be claimed for property installed after 2025.
Source: www.irs.govTexting rules in the US
Marketing texts only to homeowners with prior express written consent; opt-outs honoured across every workflow.
Source: www.law.cornell.eduA2P 10DLC registration
The sending number was registered before any texts went out.
Source: www.twilio.comPeople submit permits and applications
The tracker prepares and reminds; a qualified person approves and submits every package.
Source: www.nrel.govMonitoring data used for service only
Production data is used for service purposes set out in the contract and privacy notice.
Outcomes
What changed for the practice
- Every lead lands in one pipeline that matches what consultants are actually doing.
- Qualified homeowners book surveys without phone tag, with bills and photos already attached.
- Every proposal gets timely follow-up, and money questions always reach a consultant.
- Homeowners get an update at every permit and utility milestone instead of calling the office.
- Monitoring alerts have an owner, and homeowners hear from the installer first.
What we track
The measures the practice watches.
Speed to lead
Time from quote request to first reply and to first consultant call.
Qualification
Share of leads qualified and surveys booked.
Proposal velocity
Days from proposal sent to signature, and signing rate by source.
Contract to energised
Days from signed contract to permission to operate, by authority and utility.
Service response
Time from monitoring alert to ticket and to resolution.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, data flows, wording and the backlog for all five workflows.
$1,000 – $2,000
-
CRM pipeline module
Lead capture, platform sync, tasks and hand-off.
$700 – $1,600
-
Qualification module
Guided questions, roof data, uploads and survey booking.
$700 – $1,700
-
Proposal follow-up module
Check-ins, sorting and signature chasing.
$500 – $1,300
-
Permit tracker module
Checklists, stall alerts and homeowner updates.
$800 – $2,000
-
Monitoring module
API collection, sorting and service tickets.
$800 – $2,000
-
Integrations
CRM, solar platform, monitoring APIs and Twilio.
$200 – $400
-
Testing, UAT and launch
QA, user acceptance testing, launch and training.
$300 – $1,500
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every installer gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC fees.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Vendor plans: CRM, design platform, e-signature and monitoring API plans as each vendor publishes them.
- AI usage: Pay-per-use model fees, usually small at installer volumes.
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
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
- Website Speed Test FreeLighthouse score, Core Web Vitals and ranked speed fixes
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Search Console Dashboard FreeReal Google & Bing clicks, free rank tracker and weekly email
Free website tools for practices
Services in this case study
Solar CRM & sales pipeline automation
Every quote request, referral and ad lead in one solar CRM pipeline, with stages from new lead to installed, automatic tasks for consultants and a weekly report on which sources sign.
From $1,000 · About 4 weeks Details
Solar lead qualification & site survey booking
Ask every quote request the questions designers need, check roof potential with Google's Solar API, collect bills and panel photos, and book surveys without phone tag.
From $1,000 · About 4 weeks Details
Solar proposal follow-up & e-signature chasing
Follow up every solar proposal on a schedule, answer process questions from approved wording, chase missing signatures and put savings and financing questions in front of the consultant.
From $1,000 · About 3 to 4 weeks Details
Permit, interconnection & homeowner update tracking
One tracker for every job's permit, inspection and utility interconnection or DNO step, with document checklists, quiet-application alerts and automatic progress updates to homeowners.
From $1,000 · About 4 to 5 weeks Details
Solar monitoring alerts & service ticket automation
Pull inverter and battery alerts from Enphase and SolarEdge, sort them by likely urgency, open service tickets, draft homeowner messages and book visits before customers notice a problem.
From $1,000 · About 4 weeks Details
Consultant or designer decides
-
Solar Installer Website: Turning Visitors Into Qualified Quote RequestsGuides · 8 min read
-
Quote Request to Booked Job: A Workflow for Local Service BusinessesAutomation · 11 min read
-
Missed Call Text Back for Contractors: How It Works and How to Set It UpAutomation · 8 min read
-
SEO for Tradesmen: A Practical Local SEO Guide for Plumbers, Electricians and BuildersSEO · 10 min read
-
Client Document Collection Automation for Accounting FirmsAutomation · 8 min read
Free 20-minute call
Want this built 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.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- IRS: FAQs on OBBB modifications to sections 25C, 25D and others
- NREL: SolarAPP+ automated permit processing
- CPUC: CSLB disclosure documents and Solar Consumer Protection Guide
- MCS: Notifying DNOs
- Aurora Solar API reference
- OpenSolar developers
- Enerflo API documentation
- Enphase API: installer plans
- Enphase API quickstart
- SolarEdge developers
- Google Maps Platform Solar API
- 47 CFR 64.1200 (TCPA rules)
- Twilio: A2P 10DLC
- Twilio US SMS pricing
- n8n pricing
- UK PECR regulation 22
- GDPR Articles 5, 6, 22 and 28
- EU AI Act, Article 50
- FTC: Final rule banning fake reviews and testimonials
- HubSpot API overview
- DocuSign eSignature REST API
- Google autocomplete phrasing checked for keywords (solar crm, solar permit, solar interconnection, solar monitoring, ai for solar, solar installer website, solar appointment setting)