One installer, three measures, a late LVP delivery and oak still settling.

Picture a one-person flooring business on a Monday morning. The board holds three measures to take, a vinyl plank install in a kitchen and hallway booked for Tuesday, and a solid oak dining room whose boards were delivered on Friday and are not yet ready to fasten. By eight o'clock the distributor's portal shows the vinyl delivery moved to Thursday. The oak will be ready when the meter says so and not before.

This article follows that week and shows where supervised AI assistants can carry the paperwork between the installer's decisions: reading delivery dates, checking batch numbers on arrival, logging readings, drafting quotes and the messages that keep two households informed. It is a worked design, not a description of a real business and not evidence of results.

Laid out as states, the week shows who is holding each job. Most of the delays are not the installer's to fix; the work is noticing them early and telling the right person.

1. 01

   Waiting on a quote

   Owner

   The installer, with a drafted quote from the measure notes

   Advances when

   The installer prices the job and sends the quote

   Ends when

   The customer declines, or the quote lapses under the installer's own terms

2. 02

   Waiting on the truck

   Owner

   The distributor, watched by a Bot each morning

   Advances when

   The cartons arrive and pass the driveway check against the order

3. 03

   Waiting on the wood

   Owner

   The boards and the room, measured by the installer

   Advances when

   Readings meet the product's instructions and the installer decides to go ahead

4. 04

   Waiting on the household

   Owner

   The customer, with furniture and appliances to clear

   Advances when

   A date is agreed and the room is ready on the morning

   Ends when

   Closed after the walkthrough and the care instructions

The one-man-army model gives a sole operator a handful of named assistants, each with one job, while every decision stays with the person who answers for the work. The pillar guide to one-man-army AI departments sets out the model; here it is four Bots, each created by the installer under Aevrion's pattern rather than supplied by the product.

The Quote Desk Bot turns measure notes into draft quotes and order sheets. The Truck Watch Bot follows every open order's delivery date and checks cartons on arrival. The Readings Bot keeps the moisture log for jobs that must settle. The Week Planner Bot holds the board and proposes changes to it. Grok Bot supports this shape: each Bot has a name, a job and its own conversation, and its guidance is to split work into another Bot only when the aim, the tools, the approval line or the timetable really is different.

All four work on one persistent cloud computer that every Bot on the account shares, files and logins included, so the distributor login the Truck Watch Bot uses is open to the others too; separate Bots are not a security boundary. When a site asks for a password, a two-factor code or a payment, the installer takes over. 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. Reading a distributor's portal is 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 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 Truck Watch Bot runs a scheduled routine at half past six each weekday. It reads the status of every open order, from the distributor's portal or from the confirmation emails the installer files in a shared folder, and writes one line per order: product, promised date, last date seen, and whether it moved. Routines run at least five minutes apart and this one runs once a day, so it reports what the portal said that morning, not what changed at noon. The routine reads and writes a list and nothing more; what to do about a moved date is the installer's call.

On Monday the line for the kitchen job says the date moved from Tuesday to Thursday. The vinyl plank in this illustration is one whose instructions, like those for COREtec Scratchless, ask for no acclimation period, only a climate-controlled room within the stated temperature range (as checked on 16 October 2026). So this job has one clock only, the truck, and the install can follow the delivery once the cartons pass inspection.

Inspection happens on the driveway on Thursday, before a single carton is opened inside. The installer photographs each end label and sends the photos to the Truck Watch Bot, which reads the product code, color and batch or run number on every carton, checks each against the order and against the other cartons, and lists every difference. A short delivery or a second batch is the installer's problem to take up with the distributor. The Bot only makes sure it is seen before the first cut.

The oak is a solid strip product whose instructions tie installation to moisture content rather than to a calendar. Bruce's 5/16-inch solid strip instructions, for example, say to acclimate the flooring on or off the job as necessary to meet their moisture requirements, and to measure and document the moisture content of both the subfloor and the boards (as checked on 16 October 2026). In this illustration the installer reads a spread of boards and several spots on the subfloor on Monday and again on Wednesday, typing each reading into the Readings Bot's conversation with the room, the spot and the meter setting used.

The Readings Bot logs each reading and shows whether the gap to the sheet's figures is closing. It never says the floor is ready. On Wednesday the gap is narrower but not closed, and the installer decides the oak waits into next week. The companion guide to moisture and acclimation records sets out what a full log holds; this week only needs the log to exist and to be dated.

With the kitchen install gone from Tuesday, two of the week's three measures move into it. At each one the installer sketches the rooms, notes doorways and stair nosings, checks what the subfloor is made of, asks when the house went up and lifts a corner to see what lies under the current floor, then drops photos and notes into the Quote Desk Bot's conversation. By evening the Bot has drafted each quote from the installer's own waste table and labor rates, with removal, leveling, underlayment and furniture moving as separate lines, and marked any line it had to guess. The installer corrects, prices and sends.

The second measure is an older house where lifting a corner of carpet shows resilient tiles beneath. As checked on 16 October 2026, the US Consumer Product Safety Commission says vinyl, asphalt and rubber floor tiles may contain asbestos that nobody can identify by eye unless the material is labeled; the guide to moisture and old-floor records sets out the full screen. The Quote Desk Bot adds a line to that draft saying the old floor is untested and that the quote assumes it stays undisturbed until tested. Whether to test, cover or remove it is decided with the homeowner and a qualified asbestos professional; the installer prices the options.

Two households are affected by the week's changes. The kitchen customer had planned to have the range and the refrigerator pulled out on Tuesday and to eat elsewhere for two days; the dining room customer has a table, chairs and a glass-fronted cabinet to clear. In this illustration the installer's quotes say what the installer moves, what the household empties first, and what is excluded, such as anything the installer will not lift alone. That is the installer's policy, written once.

From the board and those quote terms, the Week Planner Bot hands the changes to the Quote Desk Bot, which holds each customer's terms and drafts both messages in its own conversation: the kitchen customer hears that the plank arrives on Thursday and that installation starts on Friday if the cartons pass the check, with the appliance move on Friday morning; the dining room customer hears that the oak is settling and that a date follows once the readings allow one. Both arrive as editable email drafts that the installer edits, sends or discards.

A group chat ties the four together; the documentation allows between two and six Bots in one. Inside it Bots post and pass work along, and the documentation's own example has a coordinator that hands out tasks. The Week Planner Bot plays that part here under Aevrion's pattern; a supervising chief-of-staff Bot is not something the product documents. On Wednesday night it posts a revised board: Thursday, third measure and the delivery check; Friday and Saturday, the kitchen; the oak pencilled for the following week, pending readings.

Some things do not travel through the group. Approval requests, login requests and email drafts never appear there, and handoffs posted to the group are currently text-only, so the carton photos go to the Truck Watch Bot directly rather than through the planner. Bots can also message one another outside the group, with every handoff visible in the conversation. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. None of this changes the order of authority: the board is a proposal until the installer says yes.

By the following Monday the kitchen is down, two quotes are out and the oak has two dated sets of readings. What makes the next week easier is not a faster truck or drier wood; it is that every promised date and every reading now lives in the job records rather than in the installer's memory or a Bot's. The documentation says plainly that a Bot's memory is not a substitute for an authoritative source, and the run history keeps only the twenty most recent records of each routine, so the log files are the record.

For a sole installer, the place to begin is the workflow that cost the most this week: delivery tracking. Aevrion's workflow automation readiness assessment takes that one workflow without a fee or a sign-up, rates it on twelve fixed dimensions and immediately gives one of four verdicts, naming what is in the way and a sensible next move. If the distributor's dates sit only behind a portal login, data availability and integration availability are where that will show. If the verdict is encouraging, Aevrion Ops can work through the four Bots and the distributor connection with you in a scoping conversation; each connection goes only as far as the vendor's API or terms permit, and is tested first.

1. A one-person flooring week runs on two clocks that cannot be hurried: the distributor's delivery date and the moisture content of the wood.
2. A morning routine can read every open order's promised date and show which moved, but it reports what the portal said at that hour.
3. Carton labels are checked for product, color and batch on the driveway, before the first cut, and the installer handles any mismatch with the distributor.
4. Solid wood that must reach a moisture requirement waits on dated readings; the log shows the gap, and the installer decides when to go ahead.
5. Bots hand work on in the group as text and send images to each other directly; approvals and email drafts stay in each Bot's own conversation, and the installer sends every message.