Design the list, consent, segmentation, and estimate follow-up that fit a solar sales cycle, measured from first enquiry to a booked and completed job.
Email marketing for solar companies is estimate follow-up across a long sales cycle
Email marketing for solar companies is not a monthly newsletter plus one reminder. It is a consent-based program that carries a homeowner from first enquiry to a financed, permitted, inspected, and commissioned system across weeks to months. Estimate and proposal follow-up is one stage inside that longer arc, not the whole program.
Use this page to design the operating rules around that follow-up, not to pick an email platform or a fixed sending calendar. It separates commercial marketing from relationship and project communication, and it does not give legal advice. Review consent, privacy, deliverability, and state rules with the people responsible for them before putting a workflow into production.
The solar sale is planned and high-consideration. A homeowner compares installers, weighs financing, checks a federal clean-energy credit whose rules the IRS sets and changes, waits on a utility interconnection, and clears a permit and inspection before permission to operate. That cycle is slower than a same-day repair and less predictable than an appointment business, so this page does not import their send cadence. For the generic how-to, use the email marketing best practices guide and the local-business email guide; the contractor email guide shows the same lifecycle discipline for a bid-based trade. This page owns the solar-specific spoke.
No open-rate, click-rate, close-rate, list-size, lead, booking, or revenue number is promised here, and a top-three result for the primary query is a target, never a guarantee. The only thing the program should produce is a clean, consented record the team can verify from enquiry to completed job.
1. Define the solar job the email program serves
Step one is naming the exact solar job the program serves. Write down the offered work, whether each sale is one-time or the start of a monitoring relationship, the service geography, the hours a real person replies, and who owns each reply. A residential PV lead, a battery add-on, and a commercial array move differently.
Start with the work you actually sell. Residential rooftop PV is the common case, but many installers also quote battery and storage, an EV-charger add-on, service and repair on existing systems, and small commercial arrays. Each carries a different buyer, a different decision path, and a different relationship after the sale. A one-time rooftop install is not the same relationship as a system with an ongoing monitoring plan, and the email program should say which one it is writing for.
Then fix the operating boundaries. Name the service geography so out-of-area enquiries are routed out instead of nurtured, set the staffed response hours so an evening enquiry is not promised a same-minute reply, and assign a reply owner so a financing question does not sit in a shared inbox. Do not set prices or quote ticket sizes in this step; the point is the shape of the job, not its dollar figure.
| Solar job type | Typical buyer | Relationship after the sale | What the email program must respect |
|---|---|---|---|
| Residential rooftop PV | Homeowner, often with a partner | One-time install, optional monitoring | Financing, HOA, utility interconnection, permit, inspection |
| Battery and storage add-on | Existing or new PV homeowner | One-time add-on, possible monitoring | Compatibility questions, backup expectations, rebate rules |
| EV-charger add-on | Homeowner adding a vehicle load | One-time add-on | Panel capacity, permit, scope tied to the PV quote |
| Service and repair | Owner of an existing system | Repeat or ongoing service | Warranty status, monitoring alerts, faster response window |
| Small commercial PV | Business owner or facilities lead | One-time project, possible service | Procurement steps, landlord or board sign-off, longer cycle |
2. Build the list only with consent, and record its source
Build the list only from people who gave consent, and record where each came from. Capture the source, the consent or notice basis, the date, the opt-out path, and the owner for every address. Exclude bought, scraped, and cold lists entirely. A solar lead researching a planned purchase is not an emergency caller or an appointment booker.
Consent is the gate, not a setting. A homeowner who filled a quote form, booked a site survey, received a proposal, was referred by a neighbor, or already bought a system has a relationship the program can document. A list bought from a data broker, scraped from a directory, or pulled from a cold database does not, and it should never enter the sending pool. Keep the researching solar lead distinct from a no-power emergency caller and from a salon or dental appointment booker, because the basis to send and the stop rule are not the same.
The FTC's CAN-SPAM guide treats commercial email, including B2B and B2C messages, as carrying accurate sender information, a non-deceptive subject line, required disclosures and a physical postal address, and a working opt-out honored within the rule's timeframe. Apply it as a US federal minimum for review, not as legal advice, and flag state privacy and texting law for separate review before any automated send.
| Source | Consent type | Date | Opt-out mechanism | Suppression owner | Disposition |
|---|---|---|---|---|---|
| Quote or inquiry form | Marketing consent or reviewed notice captured at submit | Submit date | Working unsubscribe link on every send | Intake or marketing owner | Eligible |
| Site-survey sign-up | Relationship plus reviewed marketing basis | Booking date | Working unsubscribe link; suppression checked before send | Survey or intake owner | Eligible |
| Proposal recipient | Existing relationship for the live proposal | Proposal date | Pause or stop path; suppression checked | Proposal owner | Eligible for that proposal |
| Referral from a customer | Referral context plus reviewed basis before marketing | Referral date | Working unsubscribe link | Marketing owner | Eligible after basis review |
| Past genuine customer | Current consent or notice for post-sale contact | Last-confirmed date | Working unsubscribe link; suppression checked | Lifecycle owner | Eligible where current |
| Bought or scraped list | None verified | Unknown | No reliable suppression | None assigned | Excluded |
| Cold prospect database | None verified | Unknown | No reliable suppression | None assigned | Excluded |
3. Segment by cycle stage, not by a generic tag
Segment by where the homeowner sits in the solar cycle, not by a generic tag like 'lead.' A new enquiry, a scheduled site survey, a sent proposal, a pending financing decision, a signed contract, a permit in review, and a commissioned system each need a different message, owner, and goal. Map every segment to one downstream funnel stage.
A generic "lead" tag hides the question the homeowner actually has. Someone who just requested a quote needs scope and next-step clarity. Someone with a proposal in hand is weighing financing and incentives. Someone under contract is waiting on a permit and a utility interconnection. The same message cannot serve all three, so the segment has to follow the cycle, and each segment should map to exactly one owner, one goal, and one downstream funnel stage.
The cycle-stage map below is the control center for the program. It names, for each stage, the message goal, the consent basis, the owner, the call to action, and the stop condition. Read it as the rulebook a send must clear before it goes out.
| Cycle stage | Message goal | Consent basis | Owner | CTA | Stop condition |
|---|---|---|---|---|---|
| New enquiry | Confirm scope fit and the next step | Form consent or reviewed notice | Intake owner | Book a site survey or confirm geography | Disqualified, out of area, or moved to survey |
| Site-survey scheduled | Set expectations for the visit | Relationship plus reviewed basis | Survey owner | Confirm date and access details | Survey done, canceled, or no-show |
| Proposal or estimate sent | Clarify scope and answer real questions | Existing relationship for the proposal | Proposal owner | Ask a question or book the decision call | Accepted, declined, withdrawn, or inactive |
| Financing or incentive pending | Support the decision without numeric claims | Existing relationship | Sales owner | Send the question or share the education link | Decision made or financing declined |
| Contract signed | Move to project communication | Operational notice basis | Project owner | Confirm next milestone | Status change to permit or install |
| Permit or inspection in progress | Report milestone status | Operational notice basis | Operations owner | View status or reply with a question | Permit issued, inspection passed or failed |
| PTO or commissioned | Confirm handoff and monitoring | Operational basis; marketing only if current | Operations or lifecycle owner | Confirm monitoring access | Handoff complete |
| Post-PTO referral or review eligible | Ask for referral or review under the rules | Current consent or notice | Lifecycle owner | Leave a review or refer a neighbor | Unsubscribe, suppression, or dispute |
Turn that map into working segments with explicit entry and exit rules and a message ceiling. The segment table keeps each list bounded so a contact cannot drift into the wrong cadence and so no sequence runs past its stop condition.
| Segment | Entry rule | Exit rule | Message-count ceiling | Owner | Downstream funnel stage |
|---|---|---|---|---|---|
| New enquiry | Form submit with consent and in-area geography | Survey booked, disqualified, or unsubscribed | Low; set by sign-up expectation | Intake owner | Qualified enquiry |
| Site-survey scheduled | Survey booked | Survey completed, canceled, or no-show | Two to three touches around the visit | Survey owner | Qualified enquiry |
| Proposal sent | Proposal issued to the contact | Decision recorded or proposal inactive | Ceiling set in step four, keyed to milestones | Proposal owner | Booked job |
| Financing or incentive pending | Homeowner raised a financing or incentive question | Decision made or financing declined | Bounded to the decision window | Sales owner | Booked job |
| Contract signed to PTO | Signed contract or scheduled install | Commissioned or status change | As operations require | Operations owner | Completed job |
| Post-PTO lifecycle | Commissioned and eligible under current basis | Unsubscribe, suppression, or dispute | Low; seasonal | Lifecycle owner | Completed job |
4. Write the estimate and proposal follow-up
The estimate and proposal follow-up covers the messages between proposal sent and the homeowner's decision. Each message should clarify scope, answer financing and incentive questions without numeric claims, confirm the next step and its owner, and respect a follow-up ceiling with a clear stop rule. Education proof points can route to the social channel, not duplicate it.
This is the stage most generic guides treat as the whole program, and it is only one stage. A solar proposal sits while the homeowner compares installers, reads the financing terms, checks whether an HOA has a say, and waits on a utility interconnection timeline. The follow-up's job is to keep the proposal record current and the homeowner oriented, not to manufacture urgency or imply a decision that has not happened.
Each follow-up message should do four things: restate the scope the homeowner is weighing in plain terms, answer the financing and incentive questions they actually raised while stating no amounts, rates, or savings, name the real next step and the person who owns it, and offer a simple way to pause or stop. Set a follow-up ceiling and a stop rule before the first send, and stop the moment the proposal is accepted, declined, withdrawn, or goes inactive.
Education proof points belong on the social channel, where short posts can explain monitoring, warranties, and the interconnection wait without crowding the follow-up. The social work runs on its own owner and cadence; the theStacc Social Media module covers scheduled posts to Instagram, LinkedIn, X, and Facebook with an approval flow, and it is the adjacent channel for that education, not a sender of email. Link to it, do not rebuild it inside the proposal sequence.
5. Add re-engagement and post-PTO lifecycle touches
Stalled proposals and post-commissioning customers need separate, bounded touches. Re-engage a stalled proposal with a short, consented sequence that stops on reply or disqualification. After permission to operate and commissioning, shift to referral and review asks that follow Google's and the FTC's rules. Never incentivize a review or condition it on positive sentiment.
A stalled proposal is not a lost one; it is a record that went quiet. Re-engagement should be short, consented, and bounded, with a clear stop on any reply, a decline, or disqualification. The goal is to confirm whether the homeowner is still weighing the decision or whether the record should close, and the sequence should end the moment that answer exists.
After permission to operate and commissioning, the relationship changes. The customer has a working system, and the program can shift to referral and review asks, but only under the rules that govern them. Google permits asking genuine customers for reviews while prohibiting incentives and expecting privacy-aware replies, and the FTC's reviews rule bars fake reviews and any condition tied to sentiment. A review ask must never be incentivized and never conditioned on a positive rating.
Do not send a referral or review ask into an open dispute, an unpaid invoice, or an unfinished inspection or punch item. The lifecycle owner decides eligibility and the stop condition, and a commissioned date alone is not a basis to send. Route review and referral requests through the company's documented reputation process rather than rebuilding those rules inside the email program.
6. Instrument the funnel with separate stages
Instrument the funnel so every stage stays separate in its own record. Keep impression, click, call click, form, qualified enquiry, booked job, and completed job as distinct entries, each with a business rule, a source system, an owner, and a timestamp. A click, an open, or a form is never a booked or completed solar job.
The measurement mistake that breaks every report is collapsing stages. An impression is not a click, a click is not a form, a form is not a qualified enquiry, and none of them is a booked or completed job. GA4 documents lead events such as generate_lead, qualify_lead, working_lead, and close_convert_lead, and the business defines when each one fires. A configured event records the action it was set to capture; it does not, by itself, record an offline signed contract or a system that passed inspection.
The dictionary below keeps each stage in its own lane. Booked job means a signed contract or a scheduled install. Completed job means the install passed inspection and the system reached permission to operate and commissioning. Give every stage a source system, an owner, and a timestamp so the record can be audited later.
| Stage | Business rule | Source system | Owner | Timestamp |
|---|---|---|---|---|
| Impression | The message or listing was shown | ESP or ad platform log | Marketing owner | Send or serve time |
| Click | A tracked link was clicked | ESP or analytics | Marketing owner | Event time |
| Call click | A click-to-call action fired | Call tracking or analytics | Intake owner | Event time |
| Form | A quote or inquiry form was submitted | Website or form system | Intake owner | Submit time |
| Qualified enquiry | The written service and coverage rule was met | Intake or CRM log plus source field | Intake owner | Qualification time |
| Booked job | Contract signed or install scheduled | CRM | Sales owner | Signature or schedule time |
| Completed job | Install passed inspection and reached PTO or commissioning | Job-management or CRM | Operations owner | Commissioning time |
7. Review qualified and completed-job evidence, then keep, change, or stop
Judge the program only inside a declared evidence window and only on the company's own stage data. Compare qualified enquiries, booked jobs, and completed jobs against risk signals like complaints, unsubscribes, and bounces, then keep, change, or stop each sequence. Retain a cadence because the evidence supports it, not because a generic benchmark does.
Set the evidence window before reading results, so one strong week or one quiet week does not rewrite the rule. For each sequence, read quality and risk together. A proposal follow-up that coincides with booked jobs but also with complaints needs owner review, not more volume. A re-engagement that produces replies but drives unsubscribes is a different decision from one that does neither.
Only the formulas in the contract below are approved, and each one keeps every field: numerator, denominator, evidence window, source system, owner, and exclusions. Do not publish portable benchmarks or any rate, lead, or revenue promise from them; they exist so the company can read its own stage data honestly.
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Consented-list growth | New unique contacts added with recorded consent and source | Count, not a rate | One declared 30-day window | ESP or CRM subscriber log | List owner | Bought, scraped, cold contacts; duplicates; contacts without consent |
| Qualified-enquiry rate | Unique enquiries marked qualified under the written service and coverage rule | All unique attributable enquiries in the same window | One declared 30-day window | Intake or CRM log plus source field | Intake owner | Duplicates, spam, employment or vendor enquiries, unsupported geography or services |
| Proposal follow-up response | Unique proposal-stage contacts who reply or book the next step | All unique contacts who received the proposal follow-up in the cohort | One declared cohort plus declared response lag | ESP or CRM | Sales owner | Out-of-sequence or manual replies counted once; bounces and unsubscribes |
| Booked-job rate | Booked jobs from the cohort | Qualified enquiries in the same cohort | Cohort window plus sales-cycle lag | CRM | Sales owner | Reschedules counted once; cancellations before install stay booked, not completed |
| Completed-job rate | Completed jobs that passed inspection and reached PTO or commissioning | Booked jobs in the same cohort | Cohort window plus install, inspection, and PTO lag | Job-management or CRM | Operations owner | Canceled, no-show, or uncompleted jobs; unsupported services |
Failure-state checklist
Before celebrating any metric, inspect the failure states that make a number look better than the program is. Resolve these first, then read the stage data.
- No recorded consent or notice basis on the contact.
- Bought, scraped, or cold source inside the sending pool.
- Duplicate contact producing duplicate sends.
- Unsupported geography or service still being nurtured.
- An incentive or financing numeric claim in any message.
- An opt-out not honored within the rule's timeframe.
- An open, click, or form treated as a booked or completed job.
- A review ask conditioned on sentiment or tied to an incentive.
- Declare the evidence window and the stages you will compare.
- Read quality signals beside risk signals for each sequence.
- Inspect the failure-state checklist before reading the rates.
- Decide to keep, change, or stop each sequence and record who made the call.
- Re-validate consent, ownership, and suppression after any change before the next send.
Frequently Asked Questions
These answers keep the solar boundaries clear: consent, cycle stage, financing and permit timing, and measurement each have their own owner and record. They are operating guidance, not legal advice, platform instructions, or proof that an open or a click has become a qualified enquiry, a booked job, a completed install, or revenue.
Email can support a solar company by keeping a consented homeowner oriented through a long, financed, permit- and inspection-gated purchase, but it does not guarantee leads, bookings, or revenue. Treat it as one channel beside search and referrals, judge it on qualified enquiries and booked and completed jobs over a declared window, and keep it within CAN-SPAM consent and opt-out rules.
Collect addresses only where a real relationship exists: quote and inquiry forms, site-survey sign-ups, proposal recipients, referrals, and past genuine customers. For each one record the source, the consent or notice basis, the date, the opt-out path, and the owner. Exclude bought, scraped, and cold lists; they arrive without consent, source, or reliable suppression and fail the register.
A proposal follow-up should clarify the scope the homeowner is weighing, answer the financing and incentive questions they actually raised without stating amounts or savings, name the real next step and who owns it, and give a simple way to pause or stop. It should not manufacture urgency or imply a decision that has not happened.
There is no universal number. A solar decision often runs weeks to months while financing, an HOA, a lender, a utility interconnection, and a permit are reviewed, so fewer messages keyed to real milestones fit better than a daily drip. Set a ceiling and a stop rule, and stop when the proposal is accepted, declined, withdrawn, or inactive.
The FTC's CAN-SPAM guide applies to commercial email, including B2B and B2C messages a solar company sends. It requires accurate sender information, a non-deceptive subject line, required disclosures and a physical postal address, and a working opt-out honored within the rule's timeframe. Treat it as a US federal minimum for review, not legal advice, and check state privacy and texting rules separately.
Ask only after the system is commissioned and the customer is a genuine one, where the relationship and a current consent or notice basis support the message. Follow Google's review guidance and the FTC reviews rule: no incentive and no condition tied to sentiment. Do not send a review ask into an open dispute, an unpaid invoice, or an unfinished inspection or punch item.
Yes. Cycle stage is the most useful split because a new enquiry, a scheduled site survey, a sent proposal, a pending financing decision, a signed contract, a permit in review, and a commissioned system each carry a different question, owner, and goal. Segmenting by stage keeps the message relevant and stops the wrong touch from reaching the wrong moment.
No. An impression, click, call click, form, or proposal view is an activity signal, not a qualified enquiry, a booked job, or a completed install. GA4 can record lead events such as generate_lead, qualify_lead, working_lead, and close_convert_lead, but the business defines when each fires. A booked job is a signed contract or scheduled install; a completed job has passed inspection and commissioning.
Put the solar email program on a 30-day review
Put the program on a fixed thirty-day review instead of chasing more sends. Start by naming the solar job, recording consent, and separating one proposal path from one post-commissioning path, then hold each to its owner and stop rule. The useful result is fewer mismatched messages and a record the team can verify, not more email.
Do not try to repair every workflow in one campaign. Separate one new-enquiry path from one proposal path first, then apply the same discipline to re-engagement and post-commissioning records, keeping financing, HOA, utility interconnection, permit, inspection, and permission-to-operate milestones anchored to their real owners. The goal is a record the installer can audit from enquiry to completed job, not more email for its own sake.
theStacc is not an email service provider or CRM and does not send, sequence, automate, or manage email lists; sending and list management belong to a dedicated ESP and are outside this product. Its Content SEO module can research and draft follow-up and education copy and queue SEO articles to a connected CMS, and its Social Media module covers scheduled posts to Instagram, LinkedIn, X, and Facebook with an approval flow for the education and proof points that sit beside the follow-up. No module sends email, supplies a CRM, or guarantees deliverability, leads, or booked jobs.
Sources & references
- [1] FTC — CAN-SPAM Act: A Compliance Guide for Business
- [2] Google Analytics — Recommended events (generate_lead and lead stages)
- [3] Google Business Profile — Get reviews (ask genuine customers, no incentives)
- [4] FTC — Consumer Reviews and Testimonials Rule: Questions and Answers
- [5] IRS — Residential Clean Energy Credit
Blog SEO, Local SEO, and Social Media — one dashboard, no headaches.