Six home visits, two tub-to-shower installs and one rotten subfloor.

A one-owner bath company sells at night, schedules crews at dawn and keeps every signed contract inside its cancellation window in between. Supervised AI assistants can carry a share of the desk work behind that: appointment prep sheets, packet checks, start dates computed from the owner's table, a rot log turned into a change-order draft. The selling, the pricing, every cancellation question and every promise to a homeowner stay with the owner.

This article follows one illustrative week in a small bath company. The week, the company and its customers are made up to show how the work divides; nothing here reports a result.

In this illustration the owner runs every in-home appointment and prices every job. A two-person crew installs tub-to-shower conversions, and a part-time appointment setter books visits from the leads that arrive through the website and home-show forms. The company also has one gut remodel under way, with a tiler and a glazier it subcontracts.

The company follows the One-Man Army model that the pillar article sets out: the owner holds every decision, and each recurring desk job belongs to a named AI assistant of its own. Here that means four Bots on Grok Bot: an Appointments Bot, a Packet Bot, a Job Docs Bot and a Coordinator. All four work on the one cloud computer the account provides, they can message each other and hand a task over outright (Cursor's help pages say no switch turns that messaging off; the Bots follow instructions about it), and they share a group chat where the Coordinator assigns work. The setter keeps the phone: Grok Bot's documentation describes no telephony, so no Bot calls or messages a homeowner.

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 setter books six in-home appointments for the week. The lead forms reach the Bots through a custom integration with the site's form tool, if its vendor allows one and once tested, or the owner attaches them. For each appointment, the Appointments Bot builds a prep sheet from the lead form: the room in the homeowner's words, their photos, whether they want a tub replaced or a shower instead, any mobility needs they mentioned, the year the house was built, and who said they would be present. It also drafts a confirmation email, which the owner edits and sends; the Bot does not send it. Mobility needs are recorded as the homeowner stated them. Grab-bar positions and a low or curbless entry are recommendations for the owner to make in the home, not for an assistant to infer from a form.

Under the FTC's Cooling-Off Rule, as checked on 15 October 2026, a buyer can cancel a covered home sale until midnight of the third business day, and Saturday counts as a business day while Sunday and federal holidays do not. With no holiday that week, Monday's sale runs to midnight on Thursday, Wednesday's to midnight on Saturday and Thursday's to midnight on the following Monday. State rules can be longer, which is why the owner's start-date table, written with the company's lawyer, holds a row for each state the company sells in. The Packet Bot only applies the table.

The table also holds the owner's own policy, which here is simple: no product is ordered and no installer is booked until the window has closed and a person has recorded that no cancellation arrived. That policy is the owner's choice, not a reading of the rule, and the Packet Bot does not decide what Wednesday's missing form means for the deadline. It flags the gap, holds the start date and puts the question to the owner, who takes it to the lawyer.

1. 01

   Signed at the table

   Owner

   The owner

   Advances when

   The signed contract, forms and any financing documents are filed the same evening

2. 02

   Packet check

   Owner

   Packet Bot

   Advances when

   The file matches the owner's checklist, or each gap is listed for the owner

   Ends when

   A cancellation or an unresolved gap stops the sale here

3. 03

   Window open

   Owner

   Nobody acts

   Advances when

   The deadline from the owner's table passes; drafts for this job wait

4. 04

   Window closed

   Owner

   The owner

   Advances when

   The owner records that no cancellation arrived

5. 05

   Products ordered

   Owner

   The owner

   Advances when

   The order is placed and the delivery date logged

6. 06

   Install booked

   Owner

   The setter or the owner

   Advances when

   The Coordinator drafts a crew date on or after the earliest start; a person confirms it with the homeowner

The crew's two tub-to-shower conversions come from sales whose packets were complete and whose windows had passed. The first, on Tuesday and Wednesday, goes as planned: tear-out, substrate check, base, surround, fixtures, and a final check by the owner. The Job Docs Bot assembles the photo set the crew sends the owner, drafts the completion note and a review request for the owner to send, and closes the job file once the owner has signed off the final.

The second starts on Thursday morning, and it is the one that tests the design.

When the old tub comes out, the subfloor at the drain end is soft and dark. The lead installer stops, photographs it and sends the photos to the owner, with a voice note about how far the soft area seems to run and what he would replace. The owner attaches both in a one-to-one conversation with the Job Docs Bot, not the group chat: Bot handoffs in a group are text-only for now, so images go to the Bot that must inspect them.

From those, the Job Docs Bot logs the discovery against the job and writes up the scope wording for a change order, laid out the way the owner's form expects: where the damage is, what the installer saw and recommends, and the photos attached. It leaves the price blank. It does not judge whether the floor is structural, and it does not contact the homeowner. California's licensing board says the customer and the contractor must sign a written change order before any change to price or scope (as checked on 15 October 2026), and this owner applies the same discipline in every state the company works in.

The owner reads the draft between appointments, prices the repair, talks to the homeowner in person and sends the change order once they agree. The rest of the day is the Coordinator's to replan. It drafts a revised crew plan, pushing the surround to Friday and holding the following Monday's job if the repair runs long, and posts it to the group for the owner to confirm. The owner confirms it in a one-to-one conversation with the Coordinator, since the group chat never shows approval cards or email drafts.

The gut remodel runs on a different clock. Its waterproofing was accepted the week before by the person responsible for it, with a flood test as the specification required, and tile has been going on since. The owner's sequence rule is that the glazier measures from finished tile, never before. The Job Docs Bot holds no glazier draft until the tiler logs tile as complete.

On Wednesday afternoon the tiler logs completion. Only then does the Job Docs Bot draft the measure booking to the glazier, with the shower dimensions from the plan, the tile photos and the homeowner's access notes, as an editable email the owner reviews and sends. If the tiler later reopens the job for a cracked piece, the rule is the same: the measure waits until completion is logged again.

The documentation lets a group chat hold between two and six Bots, with a coordinator among them allowed to hand out work, and it lets Bots message each other and pass ownership of a task. A Coordinator that orders the owner's queue each morning is built from those pieces. A supervising 'AI chief of staff' that manages the other Bots is not something the documentation describes; it is an Aevrion pattern, and this company does not need one.

The dawn routine and the financing portal were both set up around the documentation. When the Coordinator's dawn routine needs a yes and the owner is asleep, the approval lapses after roughly ten minutes (Cursor's help pages say thirty) and nothing is carried out, so that routine is written to post drafts only. And every Bot works on the same cloud computer with the same browser sign-ins, so a financing portal signed in there is open to all four. For that kind of separation the documentation points to a second user account; another Bot does not provide it. This owner never signs in to the financing portal on the Bots' computer: the signed financing documents are filed with the contract, and the Packet Bot reads the files.

The week shows where a one-owner bath company is exposed: the packet signed at night and checked by nobody, the window counted in someone's head, and the rot found on a fixed-price job with the owner at a sales appointment across town. Before any Bot exists, map one real week against those three points, then write down what this one ran on: the packet checklist, the start-date table and the rule that a tear-out surprise reaches the owner with the price left blank.

Aevrion Ops can do that mapping with the owner, then size the Bot roster, set where each Bot must stop for the owner, and link the CRM, e-signature and scheduling tools already in place, so far as each vendor's API or terms permit and only once a trial has worked. That mapping starts with the workflow automation readiness assessment.

1. A fast-turn bath week mixes appointment setting, cancellation windows and whatever the tear-out reveals.
2. Appointment prep sheets and confirmation emails are drafts; the setter keeps the phone and the owner sends the emails.
3. Under the FTC's rule Saturday counts as a business day, so the owner's table, not memory, gives each sale's deadline and earliest start.
4. Rot found at tear-out becomes a change-order description draft with the price left blank; the owner prices it and the homeowner signs before work continues.
5. In a gut remodel the glazier's measure booking is drafted only once tile completion is logged.
6. Crew photos reach the Bot that has to look at them through the owner's own conversation with it, and approval cards and drafts never show up in the group chat.