Solar proposal follow-up that keeps homeowners talking to you
A carefully designed proposal goes out, the homeowner says they will discuss it at home, and follow-up depends on a busy consultant. We build a workflow that watches proposal and signature events from your solar sales software, sends timed check-ins, answers common process questions from approved wording, chases unsigned agreements and hands every question about price, savings, financing or incentives to the consultant. A typical build costs $1,000 to $2,500 and takes about three to four weeks.
The problem
Why solar proposals go quiet
Homeowners compare several solar proposals at once, often with family, and the installer who answers questions quickly and clearly tends to win. Yet proposals regularly sit for a week without a single follow-up because the consultant is out on appointments.
Questions arrive at night by text: what happens after signing, how long until install, what the financing paperwork involves. Some can be answered from a standard library; others, such as savings or incentives, must only come from a consultant. Since the federal residential credit ended for systems installed after 2025, loose talk about incentives is a real risk.
What we build
What our solar proposal follow-up includes
Event-driven check-ins
Follow-ups timed from proposal sent, opened and agreement events reported by Aurora Solar, OpenSolar or Enerflo where the platform exposes them.
Approved process answers
A library of plain-language answers about next steps, site visits, permitting stages and typical sequencing, written and approved by your team.
Consultant hand-off
Any question about price, savings, tax credits, incentives, export rates or contract terms goes to the consultant with the thread attached.
Signature chasing
Gentle reminders for unsigned agreements and missing financing or utility forms through DocuSign or your platform's e-signature.
Stop rules
Sequences stop the moment the homeowner signs, declines or asks to pause.
Proposal ageing report
A weekly list of proposals by age, last contact and open question.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Proposal sent
Your solar platform reports a sent or opened proposal.
-
02
Automated
Timed check-in
The homeowner gets an approved check-in offering a call or answers.
-
03
Automated
Question sorted
Process questions get approved answers; money questions go to the consultant.
-
04
Coordinator review
Consultant replies
The consultant answers pricing, financing and incentive questions personally.
-
05
Consultant or designer decides
Terms decided
Price, system design and contract terms are agreed by the consultant with the homeowner.
How it behaves
How proposal follow-up behaves
What the homeowner sees
- A friendly check-in a few days after the proposal
- Quick, plain answers about next steps
- A consultant call for anything about money or terms
What the team sees
- Money questions handed over with the thread attached
- Unsigned agreements and forms listed
- A weekly proposal ageing report
What the automation does
- Schedules check-ins from proposal events
- Sorts replies and applies stop rules
- Logs every exchange on the deal
Edge cases and fallbacks
- Homeowner asks about incentives
- Handed to the consultant; no automated answer.
- Proposal revised and resent
- The sequence restarts from the new version.
- Homeowner signs with a competitor
- Marked lost with a reason; no further messages.
- Webhook or e-signature outage
- Events are retried and the consultant gets a daily list instead.
Architecture
Solar proposal follow-up at a glance.
- Input
- Logic and services
- AI step
- Output
- People
- Data
How it flows
- 1 Proposal and signature events arrive from your solar platform and e-signature tool.
- 2 n8n schedules approved check-ins and stops them when the homeowner signs, declines or pauses.
- 3 Replies are sorted: process questions get approved answers, money questions go to the consultant.
- 4 Every message and outcome is logged on the CRM deal.
Project planner
How the project runs, phase by phase.
Solar proposal follow-up & e-signature chasing project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Proposal process, platforms, common questions and current follow-up habits.
-
02
Design
2 to 3 days
Sequence timing, answer library, hand-off rules and stop rules.
-
03
Build
About 1 week
Event triggers, check-ins, sorting, signature chasing and the ageing report.
-
04
Shadow run
About 1 week
Drafts go to consultants instead of homeowners so they can check every message.
-
05
Launch
1 to 2 days
Switch on and walk consultants through hand-offs.
-
06
Support
Ongoing
Answer library updates as products, financing partners and rules change.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Sequence, answer library and hand-off rules.
$200 – $400
-
Build
Triggers, check-ins, sorting and signature chasing.
$500 – $1,300
-
Integrations
Solar platform, e-signature, CRM and messaging.
$150 – $400
-
Testing and shadow run
Drafts reviewed by consultants before go-live.
$100 – $250
-
Launch and training
Switch-on and consultant 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. E-signature, messaging, AI usage and n8n are billed to you 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.
- E-signature: DocuSign or your platform's own plan.
- AI model usage: Billed by the provider per use; short sorting steps are usually a small monthly amount.
- 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
Privacy and consent
Rules we design for, with the sources.
US: federal residential credit ended
The IRS says the Section 25D residential clean energy credit cannot be claimed for property installed after December 31, 2025, so no automated message mentions it as available.
Source: www.irs.govCalifornia: consumer protection paperwork
For net billing interconnection in California, the CPUC requires a signed Solar Consumer Protection Guide and the CSLB disclosure document; the workflow chases them but a person checks them.
Source: www.cpuc.ca.govUS: follow-up texts
Follow-ups to homeowners who asked for a proposal still respect TCPA consent and opt-out rules.
Source: www.law.cornell.eduFree tools
Try these first, free.
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.
FAQ
Solar proposal follow-up & e-signature chasing questions, answered.
We agree a short sequence with you, usually a few check-ins over two to three weeks, timed from when the proposal was sent or opened, and stop as soon as the homeowner signs, declines or asks to pause.
Aurora Solar and Enerflo document webhooks for project and deal events, and OpenSolar offers API access on its plans. Which events are available depends on your plan; we confirm before quoting.
No. Savings, incentives, export rates and financing terms are only discussed by the consultant. The federal residential credit ended for systems installed after 2025, which makes this rule even more important.
Yes. Reminders go out for unsigned agreements and forms through DocuSign or your platform's signing tool, and the coordinator sees what is still missing.
Not with a short, polite sequence and clear stop rules. Every message offers a call and an easy way to pause.
Proposals sent, time to first follow-up, questions answered, hand-offs to consultants, days from proposal to signature and signing rate by source.
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.
More for solar & home energy installers
All servicesSolar 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
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