Thirty solar projects between signature and PTO: a small installer's desk.

A small solar installer with a single crew can have thirty projects between signature and permission to operate at the same time. On any given morning most of them are being worked on by nobody at the installer: they wait on a permit reviewer, a utility, an inspector or a meter change. The hardest question for the owner is not how to install faster. It is which milestone each project is stuck on, who holds it, and which homeowner has gone longest without hearing anything.

This article follows one illustrative week in such a business, with three AI assistants keeping that picture current while the owner keeps every signature, login and message. It describes no real installer and reports no measured result.

In this illustrative business the owner sells the systems, holds the license under which the work is permitted, and signs every permit pack. A crew lead runs the one install crew. Plan sets come from an outside designer. The thirty open projects live in a spreadsheet the owner started years ago, one row each, with dates typed in when somebody remembers.

For milestone names the illustration borrows the chain Roseville Electric in California publishes for residential customers, as checked on 15 October 2026: an interconnection application, a reservation confirmation valid for 120 days, a separate city permit, construction once both are in hand, inspection, a multi-register meter, then the utility's permission to operate, after which the customer may turn the system on. The installer's own utilities will differ, and the owner writes each one's steps down from its published material.

The pillar article explains the One-Man Army model; here it takes the form of three Bots the owner creates in Grok Bot, each named for a desk this business already has: the Pipeline Bot keeps the tracker and the morning list, the Permit Pack Bot answers correction notices, and the Updates Bot drafts homeowner messages. They follow Aevrion's pattern; the product supplies no such roles.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

The Pipeline Bot's first task is turning the owner's spreadsheet into a tracker that answers the morning question. The columns are Aevrion's pattern, not a product feature, and the spreadsheet remains the record. The Bot reads it afresh each time, because the documentation warns that what a Bot remembers cannot stand in for the source system. Reading the spreadsheet where it is stored is a custom integration or supervised browser use where the vendor permits it, subject to testing.

A weekday-morning routine on the Pipeline Bot reads the tracker and posts a stuck list: the longest-held projects first, any reservation inside the owner's warning window, and any homeowner past the owner's silence rule. When the spreadsheet will not open, the routine reports that and stops rather than using an old copy. It runs before the first site visit, so it posts a list and stops; an approval request from a routine nobody is watching lapses after about ten minutes (Cursor's help pages say thirty).

Monday's list (illustrative):

• HELD BY THE UTILITY: 7

  Five applications under review; two projects with a passed inspection and a new meter, waiting for permission to operate. One of those two has been held longer than anything else on the list.

• HELD BY THE PERMIT OFFICE: 9

  Six in review and three returned with correction notices. The corrections are Tuesday's work.

• HELD BY THE INSTALLER: 6

  Two ready to build with both approvals in hand, which fills the crew's next two weeks, and four waiting for the designer's revised plan sets.

• HELD BY INSPECTION OR METER: 5

  Three inspections booked and two meter changes pending.

• HELD BY THE HOMEOWNER: 3

  Two unsigned change forms and one missing utility account detail.

• RESERVATION WATCH

  One reservation enters its last two weeks while its permit is still in review.

For each of the three correction notices, the Permit Pack Bot sets the notice beside the plan set and the owner's checklist for that permitting authority, and lists what the reviewer asked for, which document answers each item and what is still missing. Where an answer needs a revised drawing, it drafts a note to the designer for the owner to send. Where it needs a site photo, the crew lead gives it to the owner, who attaches it in the Permit Pack Bot's conversation or saves it to a cloud folder the owner set up, read by a tested custom integration; group handoffs are text-only for now, so a photo never travels through the group. It does not edit a drawing, interpret a code section or decide that a correction has been satisfied.

When the revised set arrives, the Bot assembles the resubmission in the order the owner's checklist gives and saves it in the shared workspace. The owner reviews it, signs as the licensed person and submits it through the permit portal under their own login. A portal login saved on the shared computer is open to all three Bots; to keep a portal apart, the documentation points to a second user account instead, since separate Bots are not a security boundary.

One of the four projects waiting on the designer is in a jurisdiction that uses SolarAPP+, where there may be no correction round at all: the platform checks the design as the licensed contractor enters it and, for a code-compliant system, issues the permit with an inspection checklist. The Permit Pack Bot files that checklist with the project, because UL Solutions' page for code authorities is clear that installation is still verified by the local code official through inspection.

Seven projects sit with utilities. Some utilities show status in an online account; others answer by email, and Roseville's published process runs through a utility email address. Grok Bot names no connector for any utility system, so the Pipeline Bot reads status by supervised browser use where the utility permits it, or from utility emails the owner attaches in its conversation.

The check works best as a booked half hour. When a portal asks for a password or a two-factor code, the Bot hands the computer to the owner, as the documentation describes; the owner completes only that step and hands it back. The Bot then copies each project's status into the tracker, quoting what the page said and marking anything the page did not say as unknown. It does not submit, amend or withdraw anything in a utility account, and it never treats a status line as permission to operate. Permission arrives as the utility's own document, and the owner records it.

The owner's rule for portals is short: Bots read, people act.

The Updates Bot drafts one message for each homeowner whose project moved this week, and one for each homeowner past the owner's silence rule even if nothing moved. Each draft says who holds the project now, what that party is waiting for, and what the homeowner needs to do, if anything. For the two projects waiting on permission to operate, the draft carries the owner's standard paragraph: keep the system switched off until the utility's permission has arrived and the installer has said so in writing.

Every draft appears as an editable email in the owner's own conversation with the Updates Bot, and only the owner sends it. The crew lead may be asked whether a date is realistic, and the designer whether a revision is close, but neither sends an update: they are consulted, and the owner sends.

Two kinds of message are never drafted. No Bot tells a homeowner that a system may be switched on; the owner does that personally. And no Bot answers a homeowner's question about tax credits or savings: that goes to the owner, and any tax question to the homeowner's own tax professional. The proposal claims review article explains why that line matters: as checked on 15 October 2026, the IRS page on the residential clean energy credit says it is 'not available for any property placed in service after December 31, 2025,' and that page must be re-checked on the date this article is published.

Each morning the Pipeline Bot posts the stuck list in the group chat the three Bots share and hands out the day: new correction notices to the Permit Pack Bot, each moved milestone to the Updates Bot. The documentation describes a group coordinator that can assign work; a Pipeline Bot that also supervises the other two is Aevrion's pattern built on it, not a product feature. A Bot can also pass a task straight to another, so the owner is not the router for every step; Cursor's help pages say no switch turns those messages off.

At the end of the week the owner books the crew's next two weeks. In this illustration that used to start from the crew lead's feel for which jobs were nearly ready. Now it starts from the tracker's ready-to-build rows: only projects with an approved permit and a reservation confirmation in hand, both read from the documents, reach the crew calendar. The crew lead checks materials and weather, and the owner confirms the order.

The reservation watch line closes the week. For the project whose reservation is in its last two weeks, the owner decides whether to chase the permit office, ask the utility what its rules allow, or warn the homeowner that dates may move; the Updates Bot drafts the warning only if the owner asks for it. What happens when a reservation lapses is the utility's rule, read from its own material, never something the tracker assumes.

The first job for the desk is a reservation list: every open project whose utility issued a time-limited reservation, with the last valid day copied from each confirmation, set beside its permit status. Any project the current spreadsheet could not have flagged is where the Pipeline Bot starts.

Score the reservation watch in the workflow automation readiness assessment: it is free, rates one workflow on twelve fixed dimensions and returns a result at once, and rule clarity comes out low if each utility's reservation rules are not yet written down. Scoping the desk with Aevrion Ops then covers each utility's and permit office's sequence in the owner's own words, the tracker and the morning list, and linking the spreadsheet, CRM or design software by custom integration once the vendor's API or terms allow it and the connection has been tested.

1. With thirty projects in flight and one crew, most are waiting on someone outside the business, such as plan review, the utility, the inspector or the meter crew.
2. One tracker row per project, with a held-by column and the reservation's last valid day copied from the utility's confirmation, turns a spreadsheet into a morning stuck list.
3. The Permit Pack Bot assembles correction responses and resubmissions; the licensed owner signs and submits through their own portal login.
4. Utility and permit portals are read during a booked half hour, with the owner signing in when the page asks for a person.
5. Homeowner updates are drafted by milestone and sent only by the owner; no Bot says a system may be switched on or answers a tax question.