From a Friday sewer backup to a Monday repair proposal with three options.

In a small sewer repair business the backup is the easy part to schedule: the truck goes, the line is cleared, the camera goes in. What follows is slower. A finding of root intrusion and a belly needs a report the homeowner can follow, three honest options, an answer on permits and locates, and a conversation in which someone explains the choice. Supervised AI assistants can prepare everything except that conversation over a weekend, so the owner starts Monday with a proposal to check rather than one to write.

This article follows one illustrative job through one weekend and the days after it. Nothing here describes a real company, and no result is claimed.

This illustration's owner runs the jetter truck and the push camera himself and holds NASSCO's BSDI certification for building sewers and drains, which NASSCO requires holders to renew every three years (as checked on 15 October 2026). Excavation and lining are done by a two-person crew he books job by job. There is no office. Calls come to the owner's phone, and quotes, permits and follow-up happen in the evenings, when they happen at all.

Four Bots, each created by the owner under Aevrion's pattern, carry the desk work while he remains the only decision-maker, the model the One-Man Army pillar sets out in full: Docs, which drafts inspection reports; Estimates, which drafts option sheets; Permits, which researches requirements and tracks permits and locate tickets; and Follow-up, which drafts messages on open proposals and also posts the morning queue.

All four are Bots in Grok Bot. They share one persistent cloud computer, and one Bot can message another or hand it a task outright, with the handoff visible in the conversation. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it.

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 homeowner rings the owner's phone at five: the basement floor drain is backing up and the downstairs toilet will not flush. The owner takes the call himself, because the Grok Bot documentation describes no telephony and nothing in this setup answers a phone. On site he opens the cleanout, cuts roots with the cable and runs the camera. The recording shows root intrusion at a joint a short way past the foundation and, further out, a belly where water stands in the pipe.

Back in the truck he codes the footage to BSDI, the NASSCO standard for an inspection run from inside or close to the building, because coding is his judgment and not a task to hand on. Then he sends the coded observation list, six stills and a short voice memo to Docs himself, from his own account. Docs is the Bot that will work on them, and when work moves from one Bot to another inside a group the handoff message carries text only, so Docs passes any still another Bot needs in a direct message. Before he drives home he tells the homeowner the line is running and that he will call on Monday with options. That promise is his to make, and no Bot repeats it.

Over the weekend each Bot works on its own part of the job. Docs drafts the inspection report from the coded observations, the stills and the voice memo, in the order the camera traveled, and marks one gap: the memo mentions a second cleanout near the street that appears in none of the stills. It then messages Estimates with the finished observation list, and when Estimates asks for the still of the belly, Docs sends the image to it directly.

Estimates drafts the option sheet from the owner's method notes and price book, read from the source on every draft and never from what the Bot remembers. Permits reads the city's sewer permit pages and the sewer agency's site to see whether a lateral program applies at this address, and records what each page said and when it was read. If a page asks for a login, a code or a payment, the Bot stops and asks the owner to take over the computer rather than looking for a way round. Cursor's help pages add a Vault, where saved logins and cards let a Bot sign in and check out without seeing them, and no setting asks for approval each time a saved card is used, so this design saves no card there.

Nothing is sent. The owner's rule, given to each Bot as a lasting rule to remember, is that nothing reaches the homeowner before his Monday call. The rule also fits a documented limit: if a routine or a message from another Bot raises an approval request with nobody there to answer it, the request lapses after roughly ten minutes (Cursor's help pages say thirty) and the step is skipped.

The sheet Estimates drafts has three columns, set out the way the owner sets out every sewer quote. In this illustration it reads as follows. Every description comes from the owner's method notes, not from the assistant's view of sewer repair.

At seven a routine on Follow-up posts the morning queue to the group chat the four Bots share. The documentation allows between two and six Bots in a group, and a coordinator there may hand out work. The weekend's job sits at the top with three lines: report ready in Docs, option sheet ready in Estimates, permit research ready in Permits with one open question.

The approvals happen elsewhere. Neither approval cards nor email drafts show up inside a group conversation, so the queue only points to each draft, and the owner opens each Bot's own conversation to review it. He corrects one sentence in the report, adds a price the book did not have, and answers Permits' question about the street cleanout. None of this replaces his judgment on the job; it saves him rebuilding the job from memory.

At half past eight the owner rings the homeowner with the report and the option sheet open in front of him. He explains what the camera found, walks through the three options, answers the question about cost, and then the homeowner asks: is part of this the city's pipe? He does not guess. He says he will confirm it with the sewer agency, and he makes that inquiry himself.

After the call he asks Follow-up to draft the email that confirms what was discussed and names the two documents. The draft appears in Follow-up's own conversation with recipients and body; he checks it and chooses Send. The report and the option sheet go out separately, attached by the owner himself from the job file; the documentation describes a draft's recipients and body, not attachments on it. He also asks Follow-up for a reminder draft on the Thursday he agreed with the homeowner, which a routine raises that morning for him to review. No Bot ever answers that ownership question for a customer.

On Tuesday the homeowner chooses the repair. Two clocks now run, and neither belongs to an assistant. The owner applies for the city permit. The crew, or the owner on its behalf, requests a locate through the state 811 center: the national 811 service says anyone digging should make the request a few business days ahead, will receive a ticket stating how long utilities have to respond, and must check that all the utilities have replied before anyone digs (as checked on 15 October 2026).

Permits tracks both clocks. It keeps the permit application status, the ticket number and the response deadline printed on the ticket, and it messages Follow-up whenever one of them changes, so the crew's booking draft always shows real dates. It flags in the morning queue any day on which digging is booked but the ticket has not been recorded as cleared. It never tells the crew it is safe to dig. That comes from the ticket and from the crew's own check on site.

The crew repairs the sections the following week, and the owner runs the camera again before the trench is closed, as his own procedure requires. The new footage and his notes go to Docs, which adds a closing section to the report: what was done, where, and a reference to the final recording. If the city inspects the open trench, Permits shows the booking in the queue, and the result is recorded by the person who met the inspector.

Two loose ends remain, and both are the owner's. One is any root growth he saw upstream of the repair: whether to propose a maintenance visit is his decision, and Follow-up drafts that letter only if he asks for it. The other is Monday's question about the city's share of the pipe, which he answered after speaking to the agency. Docs records his answer in the job file in his own words, so nobody later repeats it as the company's general rule for every street.

Take the last backup that ended in a camera finding and no repair. From the technician's notes alone, write the option sheet you would have wanted on Monday morning. Every line you had to look up elsewhere, whether a price, a method note or the street cleanout, is an input the Estimates Bot's lasting rules will need.

With Aevrion Ops, an owner can scope that roster, set the boundaries each Bot is told to remember, and plan custom integrations to the inspection software, price book and job system wherever the vendor's API or terms make that possible, and only after each connection has been tested. The contact page is the way to arrange that conversation.

1. The backup call and the Monday options call stay with the owner; the assistants prepare everything in between.
2. Coding the footage is the owner's judgment; he sends the stills to the documentation Bot himself, and Bots pass images to each other directly because group handoffs carry text only.
3. Nothing reaches the homeowner over the weekend, and no Bot waits on an approval, because one raised by unattended work lapses after roughly ten minutes (Cursor's help pages say thirty).
4. The option sheet sets out clearing, repair and renewal without ranking them, priced from the owner's book.
5. Permits and locate tickets are human steps; a Bot tracks their status and flags digging booked before every utility has responded.
6. Questions about who owns a section of pipe are answered by the owner after checking with the agency, never by a Bot.