Skip to main content
It’s 8am. A family’s solar quote came in through the website form yesterday — address, power bill, roof — and nobody has looked at it. Three utility interconnections are stalled, each waiting on a missing document nobody can name. This afternoon’s site visit was never confirmed with the customer. And a customer whose system was installed six weeks ago just messaged “so when does it turn on?” — and the honest answer is that nobody has tracked the protocol with the utility. It isn’t disorganization — it’s too few hands to watch leads, documents, schedules, and protocols across a cycle that takes months. What leaves your plate: qualifying inbound leads and dropping site data into the CRM, collecting the documents each install or connection needs, scheduling site visits and installs with reminders, and keeping customers updated at every stage all start happening on their own — with context, within budget, and with pricing, contracts, payments, and any technical judgment always waiting on a qualified professional.

​
How it works, in one line

In energy and solar the bottleneck is rarely the install — it’s walking each customer through a long cycle of qualification, paperwork, scheduling, and interconnection without a protocol stalling or a customer going dark. The agent doesn’t set pricing, doesn’t sign contracts, and never issues an engineering, safety, or sizing sign-off: it makes sure every lead is qualified, every document collected, every visit confirmed, and every customer kept informed — and it hands you what needs judgment, money, and technical accountability.

​
Concrete flows

​
1. Qualify the inbound lead and capture the site data

Trigger: a lead arrives — website form, WhatsApp, email, or referral — asking for a solar quote, a supply switch, or a new connection point. The agent reads the message, extracts what matters — address and property type, monthly usage (kWh or bill amount), roof or structure type, the utility, the desired timeline — and creates a lead in the CRM with the fields filled and the original attachment (roof photo, power bill) alongside. It checks the Company Brain for what else needs to be known at that usage tier and what tends to stall a proposal, and opens a task to qualify a site visit, routed to the right tech. If essential data is missing, the agent drafts a crisp ask — “to finalize the study, can you send the power bills for the last 3 months?” — that goes out by email or WhatsApp via Marcus, with the option to ask for your approval before each send.
Which usage justifies a visit, which roof needs an inspection, which utility is slowest on interconnection — that lives in the Brain, not in a fixed form. The agent pulls that calibration from the history you already ingested and qualifies every lead by the same standard.

​
2. Collect the install or connection documents and assemble the file

Trigger: a customer moved into the project stage, or a utility interconnection requires a set of documents to proceed. The agent checks the Company Brain for the checklist for that install or connection type — power bill, account holder ID, property proof, the project drawings, the responsible engineer’s sign-off form, the utility’s interconnection form — compares what’s arrived against what’s missing, and chases the customer for the gaps, one at a time, never re-asking for what’s already in. Each file that arrives is filed in that customer’s folder, by stage, and ingested into the Brain. When the file is complete, the agent opens a proactive notification in your bell: “Aurora’s dossier is ready to submit.”
The interconnection that slips was almost always stuck on a single document nobody chased. Turning the utility’s checklist into an automatic, item-by-item chase is what keeps the submission from bouncing and the customer from waiting weeks on one missing form.

​
3. Schedule site visits and installs with reminders

Trigger: a lead was qualified and needs a survey, or a project was approved and the install needs to enter the crew’s schedule. The agent proposes times by matching the field crew’s availability against the customer’s window, creates the event in Google Calendar via Composio, and confirms with the customer over WhatsApp or email. The day before, a routine fires the reminder to the customer and the crew — address, what to bring, what to check on site. If the customer reschedules, the agent reopens the time negotiation and updates the calendar and the card on the board — no one redoing the schedule by hand.
A no-show visit costs a day of an idle crew. A reminder the day before, with active confirmation, turns “I thought it was tomorrow” into “confirmed” before the truck rolls out — and the reschedule becomes a tap, not a hole in the day.

​
4. The routine that keeps customers informed across the long cycle

Trigger: a routine the agent schedules for itself sweeps, every few days, the customers in an open cycle — in design, in interconnection, awaiting a meter swap, awaiting energization. The routine surfaces who hasn’t heard anything in too long and who just had a stage change, and drafts an honest update for each: “your project was submitted to the utility on 06/12; the average survey lead time is X days — I’ll let you know the moment it clears.” The send goes out via Marcus, with optional approval. At the end of the day, Athena — the organization’s chief of staff — gathers into a short digest what moved, what’s stuck, which protocol passed the utility’s deadline, and which customers were updated, in your bell and the channel you use.
The customer who complains about solar usually wasn’t poorly served — they were simply uninformed. A routine that updates at every stage, even when the news is “still in the utility’s queue,” holds the trust through a cycle that can run months and earns the referral that brings the next customer.
For new utilities, equipment, or suppliers, Scout runs the public web research — interconnection timelines, inverter price ranges, references — and returns a summary with sources, no guessing.

​
What stays human

The agent proposes, never decides alone, whenever the subject is:
  • Pricing and commercial proposal — the study’s price, the discount, the formal offer that goes to the customer.
  • Contract and signature — any commitment that creates an obligation with the customer, a supplier, or the utility.
  • Payment — collecting, refunding, paying a supplier or crew, any movement of money.
  • Any engineering, safety, or sizing sign-off — sizing the system, approving the roof structure, releasing the install, signing the engineer’s certification, attesting electrical compliance. That is always a qualified professional’s call, never the agent’s.
  • Heavy regulatory communication with the utility or a regulator, governance decisions, and destructive actions.
In those cases the agent prepares everything — the customer dossier, the usage history, the draft update — and waits for your approval. Every action lands in the auditable trail, with author and justification, LGPD-aligned, and autonomy grows like a ratchet per action class, not in a leap.

​
Where to start

1

Upload checklists, customers, and equipment to the Brain

Ingest your document checklists by install and utility type, your customers in an open cycle, and your equipment catalog into the Company Brain. That’s where the agent pulls the right qualification, the right chase, and the honest update from.
2

Let the agent qualify the first batch of leads

Connect a channel and let the agent capture inbound leads, fill the CRM, and chase the missing data. Start with human approval before each external message and loosen it as it earns trust.
3

Schedule the document sweep and the cycle digest

Create a routine that chases pending documents and another that updates each customer at every stage change. One agent, one cadence, one channel — and autonomy grows slowly.

​
Next steps

Commercial

Qualify leads, run the funnel, and keep customers warm — of which selling solar is a long-cycle case.

Backoffice

The full pattern of the office that sustains the operation — documents, chases, and the digest that connects the dots.

CRM

Leads, pipelines, and activities — where each qualified lead becomes a customer tracked end to end.

Routines

The document chase and the per-stage update — proactive, at the same time, every day.