The solo electrician's office: quotes, permits and invoices from the van.

Running an electrical business by yourself usually means doing the office at night: chasing panel photos for quotes, getting a homeowner ready for tomorrow's inspection, turning the day's notes into invoices. A small set of AI assistants can carry most of that preparation during the day, so the evening is spent approving rather than typing.

The boundary is set by the license, not by the software. The owner performs the load calculation and gives the capacity verdict, owns the script used on any hazard call, and signs every certificate. The assistants gather, draft, track and remind around those three points, and they never speak to a customer: every message is a draft a person sends.

The one-man army is the operating model here: the license holder keeps every decision that commits the business, and a few specialized assistants each take one slice of the paperwork. The pillar article covers the model properly; this one puts it in a one-van electrical shop.

Here the assistants are Bots in Grok Bot. Each has a name, one job and a conversation of its own, and they all work on a cloud computer equipped with a browser and files. A Bot can put a request to another Bot or hand it a task to own, and two to six of them can sit in one group chat where a coordinator hands out work. The owner's desktop and phone show the same Bots and conversations, which is what makes approving from the van possible. Grok Bot describes no telephony, so the shop's phone stays the owner's, no connector is named for field-service software, and the accounting apps the documentation lists appear only in an enterprise network-settings table with no description of what they can do; reaching those takes a custom integration or supervised browser use where the vendor permits it, subject to testing.

Based on the Grok Bot documentation at docs.x.ai as checked on 13 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.

This is an illustration, not an account of a real business. The owner holds the license, an apprentice works alongside, and this is what is waiting at twenty to seven in the morning:

• THREE EV-CHARGER QUOTES

  Three homeowners have asked for a charger quote. None of them has sent the panel photos the owner needs to decide whether a site visit is worthwhile.

• A ROUGH-IN INSPECTION TOMORROW

  The inspector is booked for tomorrow on a kitchen rewire. The homeowner has not yet been told the arrival window or the access the inspector will need.

• A BURNING-SMELL NOTE

  Overnight, the answering service emailed a note: a homeowner reported a burning smell near a bedroom outlet.

• TWO JOBS TO INVOICE

  Yesterday's notes and photos for two finished service calls are in the job folder, not yet turned into invoices.

Only two items on that list need the owner's skill: the burning-smell note now, and the quotes later. All four need the owner's attention unless something else prepares them.

Everything else in an electrical office can be prepared by someone or something other than the license holder. These three cannot, and the reason is the same each time: the owner answers for the outcome personally.

The roster is deliberately small. The Grok Bot documentation says to start with as few Bots as will do the work, and to add one only when a role has its own goal, sources, approval boundary or schedule. In this illustration the shop runs three desks and a coordinator, added one at a time over several months:

• QUOTES DESK

  Requests missing panel photos through a draft email the owner sends, builds pre-qualification cards, and drafts load-management and service-upgrade quote shells after the owner records a verdict.

• PERMITS AND INSPECTIONS DESK

  Keeps the permit-to-certificate board, drafts inspection-day notices, and checks that each job file holds what the owner needs on signing day.

• BILLING DESK

  Turns finished-job notes into invoice drafts from the owner's price book and lists unpaid invoices by age. It never takes a payment; payment steps are handed to a person. Cursor's help pages add that a card saved in the Bot's Vault can be used at checkout without asking each time, so this design saves no card there.

• COORDINATOR

  Reads the morning queue, assigns each item to a desk and posts what is waiting for the owner. This is Aevrion's pattern, built on the documented group coordinator and Bot-to-Bot handoffs; the documentation's own Chief of Staff example is narrower, a digest that briefs a person.

Two documented limits shape the group. Approval requests and email drafts do not appear in group chats, so each desk raises them in its own conversation with the owner. Group handoff messages are text-only, so when the apprentice's panel photo must reach the quotes desk, it is sent to that Bot directly.

Each step below ends with something a person did. The desks shorten the gap between the steps; they do not remove the owner from any of them.

1. 01

   Morning queue

   Decides

   What is waiting, and which desk owns each item?

   Output

   The coordinator's post: the hazard note flagged for the owner, three quotes waiting on photos, tomorrow's inspection, two invoices to draft

2. 02

   Hazard note

   Decides

   Who calls the homeowner back, and with what words?

   Output

   The owner calls before the first job, using the written script; the desk records the time the call was made

3. 03

   Photo requests

   Decides

   Can the three drafted requests go as written?

   Output

   Three draft emails edited where needed and sent by the owner from the phone

4. 04

   Inspection notice

   Decides

   Is the notice right for tomorrow's visit?

   Output

   A notice the owner checks and sends; the board shows the inspection as notified

5. 05

   Photos arrive

   Decides

   Is a site visit worthwhile for each inquiry?

   Output

   Pre-qualification cards marked 'electrician to verify', and site visits booked by the owner

6. 06

   Invoices

   Decides

   Do the two invoices match the job notes?

   Output

   Two invoice drafts corrected where needed and sent by the owner

7. 07

   End of day

   Decides

   What is still open?

   Output

   A short list for tomorrow: photo requests unanswered, the inspection result to record

Because Bots and conversations sync to the phone, the owner can work through drafts while parked on a driveway. Where an action is set to stop for approval, the card shows the proposed operation and its inputs, with Allow once, Always allow and Deny, and the controls are the same on iPhone. Email drafts appear as editable cards that go only when the owner chooses to send them.

Two caveats decide how the desks are built. An approval controls the proposed action; it does not reverse work already done. And an approval raised by unattended work, such as a routine or another Bot's message, expires after about ten minutes (Cursor's help pages say thirty) and the action does not run. An owner halfway through a panel change will miss most of those, so the desks prepare drafts and wait, and nothing customer-facing depends on a quick tap. Which actions stop at all depends on the tool, the risk and the owner's rules, so the boundaries are written down rather than assumed.

The apprentice's most useful contribution is photos and notes: the panel label, the finished work before covers go on, the meter. Bots accept images, PDFs and documents as attachments, so each photo goes into the conversation of the desk that needs it, labeled with the job it belongs to. When a photo arrives without a job reference, the desks are told to ask for the reference rather than guess it.

If the apprentice works in the owner's account, the apprentice reaches everything the Bots reach, and the Bots reach a great deal: one computer, one set of files and one set of saved sign-ins, shared by all of them. Separate Bots are not a security boundary. Where invoices, bank access or a certification portal should stay with the owner, the apprentice needs a separate user account, which is the documented answer, rather than a separate Bot.

The permits and inspections desk is the safest first assistant: its work is frequent, every output is a draft, and its definition of done is plain. Run it on read-and-prepare work for a few weeks, which is the documentation's recommended first step, before adding the billing desk. The quotes desk comes last because it sits closest to the capacity verdict and needs the clearest rules.

The electrical contractors article in this series sets out the full set of desks and sign-offs, and the EV charger and panel upgrade article covers the photo set and the permit-to-certificate tracker in detail. Aevrion Ops can help owner-operators write the procedures, design the desks and build the custom integrations their software needs, subject to each vendor's API or terms and to testing; the workflow automation readiness assessment is the place to begin.

1. An owner-electrician can delegate quote chasing, inspection notices and invoice drafts, but not the load calculation, the hazard script or the certificate signature.
2. Hazard notes go straight to the owner with the written script attached; no assistant drafts advice.
3. A coordinator that routes work to desks is Aevrion's pattern, built on documented group chats and Bot-to-Bot handoffs.
4. Approvals and drafts never appear in group chats, and a photo meant for another Bot is sent to it directly.
5. Approvals work from the phone, but they do not undo completed work, and unattended ones expire after about ten minutes (Cursor's help pages say thirty).
6. An apprentice who should not see everything needs a separate user account, not a separate Bot.