A flatwork crew of three, and a back office that works while they finish.

Take an illustrative company: three people pouring residential flatwork, the owner finishing alongside a second finisher and a laborer. From the first truck to the last pass of the trowel, and then the joint saw, the owner's hands are on the slab. Email gets read in the cab after dark. By then the plant wants tomorrow's order confirmed, two homeowners are waiting on bids, and last week's customer wants to know when she can park on her new driveway.

Aevrion calls this arrangement the one-man army: the owner keeps every decision, and a few named assistants prepare the paperwork around it. Here they are Bots the owner creates in Grok Bot, each with one job. The pillar article sets out that model in full; here it is applied to a single week that Aevrion invented, with no client, job or result behind 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.

On a pour day the crew is committed from the moment the first truck arrives: placing, screeding, floating, edging, finishing, then curing. NRMCA's sheet on joints in slabs on grade, as checked on 16 October 2026, puts conventional saw-cut contraction joints within four to twelve hours after finishing, and warns that sawing too late can let uncontrolled cracks form. On a morning pour, that cut lands in the late afternoon or the evening. Nobody on the crew has clean hands, a spare minute or a desk until it is done.

The phone stays with the owner. The Grok Bot documentation describes no phone calls or text messaging, so the assistants never answer a call; they work from what is already written down: emails, the website form, the owner's site notes, photos, and voice notes the owner attaches as audio files. The aim of this back office is not to reply faster. It is that when the owner climbs into the cab at eight in the evening, the replies are already written and waiting to be read.

The owner set up three Bots. Each has one job, and each has been told the same three standing rules to remember: send nothing, promise no date or price, and name any fact that is missing. Those rules guide a Bot without locking it, so the owner backs them with an Ask first rule before any external email, and each Bot prepares email as an editable draft in its own chat with the owner, who sends or discards it. The three share one persistent cloud computer and file their work in its shared workspace.

• BID DESK

  Turns site notes, measurements and photos into draft bids priced from the owner's book, and keeps a list of bids promised but not yet sent.

• SUPPLY DESK

  Keeps the pour calendar, drafts order confirmations and changes for the ready-mix plant and the pump operator, and drafts orders for form boards, base stone and reinforcement.

• JOB FILE

  Holds each job after the pour: care messages to the homeowner, photos the owner files, and the crew's silica task log.

At six each evening a routine owned by the Supply Desk Bot reads what all three Bots saved in the shared workspace and posts one queue in its conversation, pointing to each draft in the chat of the Bot that wrote it. A routine is a scheduled job the owner sets up by asking the Bot; schedules must be at least five minutes apart, and an evening run never comes near that limit. The queue is ordered so that whatever the plant needs answered tonight comes first.

1. 01

   Tomorrow's pour

   Decides

   Does tomorrow's order still match the job: yards, the mix agreed with the supplier, start time and pump?

   Output

   A confirmation draft to the plant and one to the pump operator, or a line saying nothing has changed

2. 02

   Date changes

   Decides

   Has any homeowner asked to move a date, and does that touch an order already placed?

   Output

   A change draft for each supplier affected, quoting the original order

3. 03

   Care messages

   Decides

   Which recent pours reach a step in the owner's care sheet tomorrow?

   Output

   One care message per job, using the owner's own timings

4. 04

   Bids

   Decides

   Which of this week's site visits have notes complete enough to price?

   Output

   Draft bids with open lines marked, and a list of what is missing from the rest

5. 05

   Today's task log

   Decides

   Did the owner's end-of-day note say who cut, broke out or ground what, with which tool and for how long?

   Output

   Log entries drafted from the note, with blanks where it was silent

Ready-mix is ordered for a time, not just a date, and the order carries details only the owner can confirm: yards, the mix the owner agreed with the supplier, slump, any admixture the supplier recommended, and whether the truck discharges into a pump or down a chute. The Supply Desk Bot ties each confirmation draft to the job, so a change to the start time or the yardage changes every message that mentions it. It never chooses a mix or an admixture; those are settled between the owner and the plant.

Consider Wednesday in this illustration. A homeowner whose patio is set to pour on Friday writes at noon that the fence installer has slipped and the side gate the truck needs will not open until Monday. By evening the Bot has drafted three things in its own conversation: a change request to the plant quoting the original order, a note to the pump operator, and a reply to the homeowner offering the dates the owner has free. The owner reads them, rings the plant first thing because that is how this supplier likes changes made, and sends the two emails. Whatever the supplier's terms say about a change is the supplier's business; the Bot does not guess at it.

If the plant runs an ordering portal, the Bot can prepare an order there by supervised browser use where the supplier permits it, subject to testing, or through a custom integration built against that supplier's terms. Supplier orders sit behind an Ask first rule, so submitting stops on an approval card (Allow once, Always allow or Deny), and the owner signs in personally by taking over the computer; once an order has gone through, no approval control reverses it. The evening routine is never asked to submit: the owner keeps that step and does it after dark. Separately, the documentation notes that an approval request raised by work the owner did not start, a routine included, expires after about ten minutes (Cursor's help pages say thirty), and that action does not run.

The days after a pour bring more questions than the pour itself. When can we walk on it? When can the car go on it? Should we water it? When will you seal it? Is that line meant to be there? The owner has answers, and they vary with the job, the season and the mix. The Job File Bot keeps the owner's care sheet as a document and drafts each homeowner's messages from it on the dates it sets: a first note on the evening of the pour, a reminder before the day cars may use a new driveway, and a sealing reminder where sealing is in the contract.

Every timing in those drafts is the owner's. The Bot never works out a curing period, and it answers a question about a crack only by acknowledging it and handing the photo to the owner; the money page in this series covers the expectation letter that goes out before a contract is signed. A homeowner's photo reaches the Bot through the owner, who attaches it to the Job File Bot's conversation, since the Bots sit on the owner's account alone.

One group chat holds the week's handoffs: the owner added all three Bots to it, and the Supply Desk Bot coordinates there. The documentation describes a coordinator in a group that can assign work; a Bot that supervises the others is Aevrion's arrangement, not a product feature. When the Bid Desk Bot finishes a bid for a job that will need a pump, it posts a line to the group, and the Supply Desk Bot adds a pencilled pump booking to its own draft list.

According to the documentation, approval requests, login and secret requests, and email drafts never appear in a group; they stay in the private chat between that Bot and the owner. Handoff messages into a group are currently text-only, so when the Job File Bot needs the Bid Desk Bot's site photo of an apron, it asks for it Bot-to-Bot. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. The second finisher and the laborer can be asked about anything, but they never send a Bot's draft: the drafts sit in the owner's account.

This crew saws joints and breaks out old drives, and OSHA's silica standard for construction sets out a table of specified controls for common tools, as checked on 16 October 2026. For a walk-behind saw cutting joints, the entry calls for a saw fitted with an integrated water delivery system feeding the blade without a break, and lists no respirator when the saw is used outdoors, however long the shift. For a handheld power saw with the same water feed used outdoors, it lists no respirator for four hours or less in a shift and a respirator with an assigned protection factor of ten beyond that. A jackhammer breaking out an old drive with a continuous stream or spray of water at the point of impact has the same outdoor split. So duration belongs in the record.

The Job File Bot drafts the day's entries from the owner's end-of-day note: who used which tool, on which job, indoors or out, whether the water feed ran, and roughly how long. Where the note says nothing, the entry stays blank and the gap is listed. The competent person the employer designates reads the log; the Bot never decides whether a task is within the table or what protection it needs. Federal OSHA puts these duties on the employer, and in a state with an OSHA-approved State Plan the owner confirms the matching rule with that plan. The written plan and the wider records are covered in this series' siding guide on fiber-cement silica records.

By the end of this illustrative week the owner has poured twice, moved a patio, sent four bids and answered the parking question without writing any of it from scratch at night. Every call stayed with the owner: the dates, the words, the prices and the phone call to the plant.

A simple test of whether this is worth building is the pile itself. On the next pour day, count what is still unanswered when the saw stops, and note whether each item is a supplier, a bid or a customer. Then try the readiness assessment: free, ungated, one workflow measured on twelve fixed dimensions, with the score, what is holding it back and a next step on screen as soon as you finish. Score the evening supplier confirmations; if the same yardage is typed into three places, manual re-entry and handoffs are where the score will show it. Where the result shows the workflow is ready, the three Bots and the evening queue are something Aevrion Ops can design with you, starting from where each order, bid and care sheet lives today.

1. A three-person flatwork crew places, finishes, cuts joints and cures until dusk, so supplier confirmations, bids and care messages must be drafted before the owner opens the laptop.
2. Three Bots the owner creates, a bid desk, a supply desk and a job file, each own one job and prepare emails as editable drafts that only the owner sends.
3. Order changes to the plant and pump are drafted with the original order quoted; the owner decides how to tell the supplier.
4. Care messages follow the owner's own care sheet; the Bot never sets a curing time or judges a crack.
5. For employers, OSHA's Table 1 lists respirators for some outdoor concrete tasks only beyond four hours a shift, so the crew's task log records tool, water feed and duration.