Fixed quote after a free call

Solar lead qualification and site survey booking without phone tag

Quote forms bring in renters, shaded roofs, roofs due for replacement and people who only wanted a rough number. We build a workflow that replies within minutes, asks the questions your designers need, pulls rooftop data from the Google Maps Platform Solar API where coverage exists, collects bills and electrical panel photos, scores the lead against your own criteria and books qualified homeowners into a survey slot. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why solar leads waste consultant time

Solar appointment setting is expensive whether you run an in-house setter team or pay a call centre. A large share of the time goes on calls that were never going to become an installation: tenants, flat roofs the business does not do, homes with a tiny bill, or roofs that need replacing first.

Even qualified leads stall at the survey stage. Finding a time that suits the homeowner and the surveyor, then chasing bills, panel photos and meter details by text, can take days, and every day a competitor is quoting the same home.

What we build

What our solar lead qualification includes

Instant guided reply

A text or email within minutes asking ownership, property type, roof material and age, main roof direction, shading, typical bill and goals such as battery backup or an EV charger.

Roof data lookup

Rooftop area, sunshine and panel-fit data from the Google Maps Platform Solar API where Google has coverage, attached for the designer to judge, never shown to the homeowner as a promise.

Document collection

Secure uploads for a recent bill, the electrical panel or consumer unit and the meter, with a re-ask only for what is missing or unreadable.

Scoring on your rules

Leads scored against criteria your sales team sets; borderline cases go to a person rather than being rejected.

Survey booking

Assessment or video-call slots offered from surveyor calendars by territory, with reminders and easy rebooking.

Survey pack

Address, answers, roof data and documents in one record for the designer before the visit.

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

    Quote request

    A form, ad or call creates a lead and triggers the guided questions.

  2. 02 Automated

    Facts collected

    Answers, roof data and uploaded documents attach to the lead.

  3. 03 Automated

    Lead scored

    The lead is scored against your criteria; unclear cases are flagged.

  4. 04 Coordinator review

    Setter or consultant checks

    Borderline leads are reviewed and survey bookings confirmed.

  5. 05 Consultant or designer decides

    Suitability decided

    Whether a roof, panel or home suits an install is judged by a qualified designer, never by the score.

How it behaves

How qualification and survey booking behave

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

What the homeowner sees

  • A reply within minutes with a few clear questions
  • A simple way to upload a bill and panel photos
  • Survey slots that fit their week, with reminders

What the team sees

  • Scored leads with answers, roof data and documents attached
  • Borderline leads flagged for review
  • Survey packs ready before each visit

What the automation does

  • Asks, checks uploads and re-asks only for gaps
  • Scores against your rules and books from real calendars
  • Records consent and opt-outs on every lead

Edge cases and fallbacks

No Solar API coverage for the address
The lead continues without roof data and the designer is told.
Unreadable bill photo
One polite re-ask, then the consultant follows up.
Homeowner books outside the territory
Flagged for the office before the slot is confirmed.
Calendar or API outage
Booking falls back to a call-back request and the office is alerted.

Architecture

Solar lead qualification and survey booking at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Quote request Form, ad, call n8n workflow Questions, rules Solar API Roof potential Uploads Bill, panel photos Lead score Your criteria Survey slot Surveyor calendar Consultant Borderline leads
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 A quote request arrives and the homeowner gets the guided questions within minutes.
  2. 2 Roof potential is looked up where Google has coverage, and the homeowner uploads a bill and panel photos.
  3. 3 The lead is scored against the rules your sales team set.
  4. 4 Qualified homeowners book a survey slot; borderline leads go to a consultant to decide.

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 lead qualification & site survey booking project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, current setter process, qualification rules, survey types and territories.

  2. 02

    Design

    2 to 3 days

    Question flow, scoring rules, upload checks, booking rules and consent wording.

  3. 03

    Build

    1 to 2 weeks

    Guided questions, Solar API lookup, uploads, scoring, calendar booking and the survey pack.

  4. 04

    Shadow run

    About 1 week

    Leads are scored silently while setters work as usual, and we compare decisions.

  5. 05

    Launch

    1 to 2 days

    Switch on for one lead source, then the rest.

  6. 06

    Support

    Ongoing

    Scoring tweaks, new territories and question changes.

What it runs on

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

n8n Google Maps Platform Solar API Twilio SMS Google Calendar or Microsoft 365 calendars Your CRM Secure upload form

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

    Question flow, scoring rules and booking logic.

    $200 – $400

  • Build

    Guided questions, uploads, scoring and booking.

    $500 – $1,300

  • Integrations

    Solar API, calendars, CRM and messaging.

    $150 – $400

  • Testing and shadow run

    Silent scoring compared with setter decisions.

    $100 – $250

  • Launch and training

    Switch-on and team walkthrough.

    $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. Google Maps Platform, Twilio and n8n usage are billed to your accounts directly.

Monthly running costs you pay directly

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

  • Google Maps Platform: Billed by Google per request under your own Maps Platform account.
  • 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, billed annually).

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: automated texts need consent

Marketing texts sent with automated systems need prior express written consent; opt-outs by reasonable means must be honoured.

Source: www.law.cornell.edu

US: A2P 10DLC registration

Application texts to US numbers from a 10-digit long code must be registered for A2P 10DLC, so registration is part of the plan.

Source: www.twilio.com

EU and UK: automated decisions

Nobody is refused purely on an automated score; a person reviews borderline leads, in line with the safeguards on automated decision-making.

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 lead qualification & site survey booking questions, answered.

With a short set of questions your designers actually need (ownership, roof, shading, bill, goals), document uploads and rooftop data where available. The score follows your rules and borderline leads always go to a person.

It can take most of the repetitive first-touch work: instant replies, questions, document chasing and booking. Many installers keep a smaller setter team for the conversations that need a human voice.

Google's Solar API returns rooftop and solar potential data for buildings where it has coverage. We attach it for the designer as a starting point; it never replaces a site assessment or a designer's judgement.

They get a courteous reply with general information, and the lead stays visible in the CRM. Nobody is told they cannot have solar on the strength of an automated score alone.

No. We explain why a bill and panel photo help and let them send them later. Missing documents are flagged to the consultant rather than blocking the booking.

Time to first reply, share of leads answering the questions, share qualified, surveys booked, no-shows and how many surveys turn into proposals.

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