From showroom to install: a short-shipped cabinet and a template to hold.

In a two-person kitchen company one of you designs and sells while the other installs, and both of you chase suppliers in the evening. When a delivery arrives one box short, the instinct is to treat it as a nuisance and get back to the designs. In a kitchen, that is backwards. The missing box sits under the countertop template, the template sits under fabrication, and everything after it waits on the fabricator's calendar.

Supervised AI assistants can make sure the gap is documented properly, the supplier's claim is drafted inside the window its terms allow, and the fabricator booking drafts are ready for whichever choice the owner makes. They do not phone the supplier, accept damaged goods, buy a replacement or tell the household a date. What follows is one invented week, offered as a design illustration: no real company, and no measured outcome.

In this illustration the owner-designer runs showroom appointments, field measures, designs and orders. The install lead sets cabinets and manages the subcontractors: an outside countertop fabricator, a plumber, an electrician and a backsplash installer. Nobody works in an office, and three kitchens are live at different stages.

The One-Man Army model behind this setup is simple to state: the two owners keep every decision, each strand of desk work goes to its own named AI assistant, and a coordinator passes work between them. The pillar article sets it out; here it meets a single missing box.

The three live kitchens on Monday morning (illustrative):

• THE GALLEY KITCHEN

  In design. Revision three went to the clients on Friday, and their comments are due back this week.

• THE ISLAND KITCHEN

  Layout approved, appliance package not yet chosen. The cabinet order cannot be placed until the appliance widths are fixed.

• THE CORNER-SINK KITCHEN

  Demolition done, rough-ins inspected, cabinets arriving Monday, and the fabricator booked to template on Thursday. The household has been without a kitchen since demolition.

Each assistant is a Bot in Grok Bot, an AI agent product that runs on Cursor-hosted cloud computers, and each has a name and a single job. They all belong to the owner-designer's account, run on its one cloud computer and see the same files and saved logins; the documentation is explicit that separate Bots are no security boundary. One Bot can send another a request or hand it a task outright, which Cursor's help pages say no switch turns off, and a group chat holds between two and six Bots working on one outcome.

In the documentation's sample group, one Bot is a coordinator permitted to hand out work. Here the Coordinator posts a morning queue to the group and routes each item; a Bot that supervises a whole roster is not something the documentation describes, so this coordinator is Aevrion's pattern built from those documented pieces. The other three are Orders, which keeps the purchase-order tracker, delivery checks and claims; Design Records, which keeps drawing versions and chases selections; and Schedule, which drafts every trade booking. They were added in that order, over months, because the documentation advises starting small.

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 corner-sink cabinets arrive at nine. The install lead works through the company's delivery checklist before anything is unwrapped for good, because once a box is installed, showing that it arrived damaged gets much harder. The checklist is an Aevrion pattern the owners wrote; the claim window in it comes from each supplier's own terms, entered by the owner-designer when the order was placed, never assumed by an assistant.

The delivery-inspection checklist, in the order the install lead works it:

• COUNT AGAINST THE ORDER

  Every carton checked against the purchase order and packing list before the driver leaves, where the supplier's process allows.

• OPEN AND INSPECT

  Each box opened enough to see the faces, corners and finished ends that will show.

• PHOTOGRAPH

  Every short or damaged item photographed with its label visible.

• NOTE THE PAPERWORK

  Shortages and damage written on the delivery receipt where the supplier's terms ask for that.

• CLAIM WINDOW

  The deadline for reporting, calculated from the delivery date and the window the owner entered from that supplier's terms.

• PHOTOS TO THE OWNER

  Images sent to the owner-designer, who attaches them in her own conversation with the Orders Bot, not the group, because group handoffs are currently text-only.

The count comes up one carton short: the corner sink base. Everything else is present and undamaged. The install lead sends the packing-list photo and the shortage note to the owner-designer, who attaches them to the Orders Bot's conversation; the Bot logs the gap on the tracker, works out the claim deadline from the owner-entered terms, and drafts the shortage claim to the supplier with the photos attached and the purchase order number in the subject line.

The draft waits in the Orders Bot's own conversation as an editable email, and the owner-designer edits it, chooses Send email, then rings the supplier's rep herself. Email drafts and approval requests do not appear in group chats, so the Coordinator's queue line only points to the draft. If the supplier answers with a written replacement date, the Orders Bot copies it onto the tracker with a link to the email. A remembered date counts for nothing; the documentation says a Bot's memory is no substitute for the authoritative source.

In this illustration the fabricator's written booking terms ask for every base cabinet to be set and fixed before the templater arrives, which is common practice because the sink's position is taken from the cabinet beneath it. Losing Thursday means waiting for the fabricator's next free visit, and the backsplash installer, the plumber and the electrician all move behind it.

The Schedule Bot does not choose; it prepares drafts for each option, so once the owner-designer decides, only reading and sending remain.

The model below follows the shortage from the driveway to the template. The Bots hold only the states that are preparation or watching.

1. 01

   Gap found

   Owner

   Install lead

   Advances when

   The checklist line is logged and the photos reach the Orders Bot through the owner-designer

2. 02

   Claim drafted

   Owner

   Orders Bot

   Advances when

   The claim email, photos and deadline wait in the Orders Bot's conversation

3. 03

   Claim sent

   Owner

   Owner-designer

   Advances when

   She edits the draft, sends it and calls the supplier's rep herself

4. 04

   Waiting on the supplier

   Owner

   Orders Bot

   Advances when

   A written replacement date arrives, or the owner's chase date passes and a chase email is drafted

5. 05

   Template decision

   Owner

   Owner-designer

   Advances when

   She holds, moves or splits the template, and the choice is recorded on the tracker

6. 06

   Fabricator booked

   Owner

   Owner-designer

   Advances when

   The Schedule Bot's matching draft is sent, and the fabricator confirms in writing

7. 07

   Sink base set

   Owner

   Install lead

   Advances when

   The replacement is inspected with the same checklist and set

   Ends when

   Closes when the template visit is confirmed against a complete base run

The Coordinator's ordering rule, which it has been told to remember, puts threatened install dates first, claims with deadlines second, drafts third and design work after that. A remembered rule is guidance, not a technical control, so the owners still read the queue themselves.

The galley clients send comments on Tuesday. The Design Records Bot files them against revision three, lists each requested change and opens a revision-four entry. It does not redraw anything or judge the layout. The owner-designer works from the National Kitchen & Bath Association's Kitchen Planning Guidelines, which present each point as a recommendation alongside a separate code line, and which remind the designer that local, state and national law still has to be followed (in the version hosted on NKBA's knowledge base, as checked on 15 October 2026). The guidelines inform her judgment; the local code is what an inspector enforces.

The island clients still have not chosen appliances. The Design Records Bot drafts an email listing the open selections and explaining that the cabinet order waits on the appliance widths; the owner-designer softens one line and sends it. Neither job loses anything by waiting a day; the corner-sink household would.

Each stayed with a person by design, and the documentation gives two reasons not to lean on a quick approval instead: an approval cannot take back what has already happened, and one raised by unattended work is canceled after about ten minutes (Cursor's help pages say thirty) if nobody answers.

• CALL THE SUPPLIER

  Grok Bot's documentation describes no telephony, so the owner-designer made the call.

• SEND THE CLAIM

  The claim left as an email the owner edited and sent from the draft.

• ACCEPT OR REFUSE GOODS

  Whether a damaged carton is accepted, refused or claimed is the owner's decision under the supplier's terms.

• BUY A REPLACEMENT

  A replacement order sits behind an explicit approval, and any payment goes through a person taking over the computer. 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.

• REBOOK THE FABRICATOR

  The Schedule Bot drafted; the owner-designer chose and sent.

• PROMISE THE HOUSEHOLD A DATE

  Only a person tells a family how much longer they will be without a kitchen.

Start at the driveway: Monday's claim went out the same day only because the delivery checklist existed and the supplier's claim window was already on the order.

Aevrion Ops can take a small kitchen company through that groundwork: walking through a real week, separating the desk work that can be prepared from the calls only the owners make, and connecting the supplier mailboxes and dealer portals they already rely on, as far as each vendor allows and once tested. The readiness assessment is where a two-person company can begin.

1. In a two-person kitchen company, a short-shipped base cabinet can threaten the countertop template more than any sales problem.
2. A delivery checklist with photos, and claim windows entered from each supplier's terms, turn a shortage into a same-day claim draft.
3. Bots draft the claim and a booking for each template option; the owner decides, sends and makes the phone calls.
4. Crew photos reach a Bot through the owner-designer's own conversation with it, because the group carries text only, and approval cards and email drafts never show up there.
5. A coordinator that routes work is Aevrion's pattern built from documented group chats, messages and handoffs, not a product feature.
6. Design revisions and selection chasing can wait a day; a household without a kitchen cannot.