Turn Google's view of each roof on Oahu and Maui into estimate requests and booked visits.
Nine ideas for Independent Energy Hawaii. Ideas 1 to 5 are built on Google's Solar API, which reads a single roof from aerial imagery: its usable area, sun hours and how many panels fit. Ideas 6 to 9 run on theStacc's assistant, content, review and AI search tools, fed by the same roof data. Each idea ends in the numbers IEH asked to be measured on: estimate requests and booked visits. Numbers below are example data, four weeks into a pilot.
How it works
- Instant roof estimate on the current site. A homeowner types an address and sees their roof: 610 sq ft usable, up to 30 panels, 1,985 sun hours. One script tag, no migration.
- Sized to their power bill. A $310 bill becomes 13 panels (5.59 kW) and a 13.5 kWh battery. That covers 92% of use and saves about $255 a month at $0.42 per kWh, with the working shown.
- Contact details only after the result. The homeowner sees a price range ($35,400 to $41,700), then books a free site visit. Example pilot: 41 started, 19 left contact, 6 booked visits.
- A personal roof video for every lead. A 58-second video of their own roof, sun map and panel layout. IEH approves each one before it is sent by text and email. Example: 14 sent, 8 watched to the end, 3 led to a visit.
- A repair check for systems other installers left behind. The owner enters system size, install year and last year's kWh. Example: expected 8,700 kWh, actual 5,900, a 32% gap worth $1,176 a year, so the owner books a diagnostic visit. Google has confirmed the Solar API terms allow it.
- Neighbourhood pages with real numbers. Kailua: 71% of 400 sampled roofs are good for solar. Every number on the page carries its source, sample size and date, and IEH reviews each page before it goes live.
- Room for more panels. Past customers without a battery whose roof fits 6 or more extra panels. Example: 610 emailed, 48% opened, 17 assessments booked.
- An intake assistant, from the HGE bot plan. It replies in about 6 seconds on website chat, texts, Meta lead ads and Yelp, and asks only two questions before giving an answer. Every number comes from the Solar API or IEH's approved price table, never from the assistant's own maths. It then hands to a named person with a due time. Example: 64 conversations in a week, 5 visits booked, 2 overdue.
- Every install becomes content. The crew lead uploads 8 photos and a 42-second voice note from the phone. theStacc drafts 6 pieces: a project page, a Google Business Profile post, social posts and a 30-second video, with no house number or owner name unless the owner agreed.
- A first-90-days report for every owner. Example: made 3,012 kWh against 2,890 expected, 4% above. Everyone gets the same review request. The 5 of 46 below expected also go to the repair team.
- Show up in AI answers. 20 solar questions are checked every Monday on ChatGPT, Perplexity, Gemini and Google AI Overviews. Example: IEH named in 14 of 80 checks, rising to 23 of 80. Answer pages are drafted from IEH's own data where it is missing.
What it is and isn't
What's in it
- Address-level roof data from Google
- Bill-based sizing with the formula shown
- IEH approval before anything is sent
- Results measured in requests and visits
Not in this version
- Final quotes, financing, permits (IEH's own process)
- Ads (IEH's new ads partner)
- Incentives in the savings figures
Release order
| Phase | What ships |
|---|---|
| A | Instant roof estimate and roof videos. Neither needs the website migration or the end of the current contract. |
| B | Room for more panels campaign, once past customer addresses are imported. |
| A+ | Repair check, now that Google has confirmed the terms allow it. It sits on the current site like the estimate. |
| C | Intake assistant on website chat and texts, with the inbox. Then Meta lead ads and Yelp. |
| D | Install stories, 90-day reports and AI answers. These run on the Growth Complete content, review and AI search tools, so they start with onboarding. Neighbourhood pages publish with only the live mini estimate until Google confirms stored numbers. |
Still to decide
- Can sampled area numbers be stored and shown on public pages? Recommended: ask Google. Until then, publish pages with the live mini estimate only.
- Which pilot first? Recommended: estimate plus videos (phase A), measured on estimate requests and visits.
- Show price ranges publicly? Recommended: yes, as a wide range marked "final price after site visit".
- Which channels does the assistant answer first? Recommended: website chat and texts, then Meta lead ads, then Yelp.
- May the assistant reply after hours? Recommended: yes, with the estimate and when a person will reply. It does not book visits after hours.
- Approve every video, or a template? Recommended: every video for the first month, then decide with real numbers.