Fixed quote after a free call

An AI chatbot for solar companies that never overpromises

We build an AI assistant for your website, text line or WhatsApp that answers homeowner questions from your own approved library, starts lead qualification, books surveys and tells existing customers where their job stands. It discloses that it is automated, never quotes savings, incentives or system sizes and hands money and technical questions to a consultant or designer. Projects typically cost $2,500 to $7,500 and take five to eight weeks.

The problem

What an AI chatbot for solar companies must never do

Homeowners research solar for weeks and ask the same questions: does my roof suit panels, how long does install take, what happens with the utility, do you install batteries or heat pumps, how does financing work. They ask at night and at weekends, when nobody is in the office.

A generic chatbot is risky in this market. Overpromised savings and incentive claims are exactly what regulators and homeowners distrust, so the assistant must stay inside approved wording and hand anything about money, roofs or electrical capacity to a person.

What we build

What our solar AI assistant includes

Approved answer library

Products, process, service areas, warranties, financing types offered and policies, written and approved by your team, and the only source the assistant answers from.

Qualification start

The same questions as your quote form, asked conversationally, with answers saved to the CRM.

Survey booking

Assessment slots from surveyor calendars, or a call-back request.

Job status for customers

Existing customers can ask where their job stands, answered from the tracker after a simple identity check.

Hand-off rules

Savings, incentives, pricing, roof condition and electrical questions go to a person with the transcript.

Transcript review

An admin view and a weekly list of questions the assistant could not answer.

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

    Question asked

    A homeowner asks on the website, by text or on WhatsApp.

  2. 02 Automated

    Answer from library

    The assistant answers only from approved wording and links the source page.

  3. 03 Automated

    Lead or booking

    It starts qualification or books a survey slot.

  4. 04 Coordinator review

    Team follows up

    Consultants pick up hand-offs and confirm bookings.

  5. 05 Consultant or designer decides

    Money and technical answers

    Savings, pricing and roof or electrical questions are answered only by a consultant or designer.

How it behaves

How the solar AI assistant behaves

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

What the homeowner sees

  • A clear note that the assistant is automated
  • Straight answers about process and products, with links
  • Survey booking or a consultant call for anything about money

What the team sees

  • New qualified leads with conversation history
  • Hand-offs flagged with the question asked
  • A weekly list of unanswered questions

What the automation does

  • Answers only from the approved library
  • Refuses savings, incentive and technical questions and hands over
  • Logs every conversation on the lead

Edge cases and fallbacks

Question not in the library
It says it does not know, offers a person and adds the question to the review list.
Homeowner pushes for a savings figure
Polite refusal and a consultant hand-off.
Spam or abuse
Conversation closed politely and logged.
AI provider outage
The widget falls back to the quote form.

Architecture

An AI assistant for a solar installer at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Homeowner Web, text, WhatsApp Assistant service n8n or Laravel Language model Claude, Gemini, GPT Approved answers Installer-written Survey booking Or call-back Consultant Money, technical CRM and logs Lead and transcript
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 A homeowner asks a question and is told they are talking to an automated assistant.
  2. 2 The service retrieves approved answers and passes them, with fixed rules, to the language model.
  3. 3 Process questions are answered, qualification starts and surveys are booked.
  4. 4 Money and technical questions go to a consultant; every conversation is logged on the lead.

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.

AI chatbot & homeowner assistant for solar companies project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Real questions from calls, chats and emails; what the assistant may and may not answer.

  2. 02

    Answer library

    About 1 week

    Write and approve answers with your team, including incentive and savings refusals.

  3. 03

    Build

    About 2 weeks

    Widget or text line, retrieval, qualification, booking, job status and hand-offs.

  4. 04

    Test

    1 to 2 weeks

    Real, tricky and adversarial prompts, including savings bait; your team signs off.

  5. 05

    Launch

    2 to 3 days

    Soft launch out of hours, then widen.

  6. 06

    Support

    Ongoing

    Weekly transcript review at first, then monthly library updates.

What it runs on

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

Claude, Gemini or OpenAI models n8n AI Agent node or Laravel Website chat widget Twilio SMS or WhatsApp Business Platform Your CRM and calendars Slack or email for hand-offs

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 answer library

    Real questions collected, answers written and approved.

    $500 – $1,200

  • Build

    Assistant service, widget or text line, retrieval and hand-offs.

    $1,200 – $4,000

  • Integrations

    CRM, calendars, tracker and messaging.

    $300 – $1,000

  • Testing and evaluation set

    Real, tricky and savings-bait prompts tested before launch.

    $300 – $900

  • Launch and training

    Soft launch, transcript review and team walkthrough.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. WhatsApp or voice adds build and running cost. Model usage and messaging 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.

  • AI model usage: Billed by the provider per use; usually a modest monthly amount at installer volumes.
  • Messaging: Twilio or WhatsApp Business Platform at the provider's published rates if you add a text line.
  • Hosting: n8n Cloud from about €20 a month, or your own server.

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.

EU: tell people they are talking to AI

Article 50 of the EU AI Act requires AI systems that interact with people to inform them they are interacting with an AI system, from 2 August 2026. We disclose everywhere.

Source: artificialintelligenceact.eu

US: no incentive claims

The federal residential credit cannot be claimed for property installed after December 31, 2025; the assistant refuses incentive questions and hands them to a consultant.

Source: www.irs.gov

EU and UK: data minimisation

The assistant collects only what qualification needs, and processors are under contract.

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

AI chatbot & homeowner assistant for solar companies questions, answered.

Ours will not. Savings depend on usage, tariffs, export arrangements and system performance, so savings questions go to a consultant who can prepare a proper proposal.

Yes. It says so at the start and offers a person at any time, which the EU AI Act requires from 2 August 2026.

Yes. It asks the same questions as your quote form, saves answers to the CRM and books survey slots from real calendars.

Yes, after a simple identity check, from the permit and interconnection tracker. It reports the current milestone, not predicted dates.

Sorting replies and monitoring alerts, summarising proposals in plain language and drafting follow-ups for review. We keep AI on drafting and sorting and people on decisions.

Transcript logging, a weekly list of unanswered questions and measures such as qualified leads captured, surveys booked and hand-offs per conversation.

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