One truck, one owner: an estate clean-out and five other jobs in a day.

An owner-operator with a single truck sells capacity twice: once in the diary and again in the truck bed. Six bookings in a day are not six trips. They are a sequence of loads, each of which has to be emptied somewhere before the next can start, and one large job can rearrange everything after it. An estate clean-out adds something the other jobs lack: other people's papers, photographs and valuables, found among things the family asked to have taken away.

This illustration follows that day for an invented owner and three assistants built on Aevrion's pattern. It is a worked design, not an account of any real company, and it reports no results. The assistants plan, draft and file; the owner prices, loads, drives, decides what is donated, and handles anything personal.

The one-man-army idea, set out in Aevrion's pillar on AI departments, is that a sole operator can hand the desk work of several roles to named assistants while every decision stays with the operator. Here the roles are an Estimate Bot that reads inquiry photos, a Dispatch Bot that plans each day's stops, and a Records Bot that files the paper each load produces. All three are Bots the owner creates in Grok Bot under Aevrion's design; none of them is a product feature.

In Grok Bot each Bot has its own name, job and conversation, while all of an account's Bots share one persistent cloud computer with its files and signed-in browser sessions. The documentation lets Bots message each other directly and work together in group chats of two to six. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. Customer emails the Bots prepare land in the owner's own conversations as editable drafts that the owner sends or discards, and no Bot here takes calls or texts.

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 invented owner's Thursday looks like this when the Dispatch Bot builds the plan on Wednesday evening. Each estimate is the Estimate Bot's photo range, confirmed with the customer by the owner; each destination comes from the facility sheet the owner keeps.

On paper that is about three loads. In practice the estate house decides the day, because nobody knows how much of a lived-in house will really go until the family walks through it with the owner.

At six on Wednesday evening a scheduled routine owned by the Dispatch Bot reads the next day's bookings, the estimate ranges and the facility sheet, and leaves a run sheet in the owner's conversation: the order of stops, which load each job joins, where each load is emptied and the opening hours that bound it. The bookings come from the company's own system through a custom integration or supervised browser use where the vendor permits it, subject to testing. The documentation sets routine schedules at least five minutes apart, keeps the last twenty run records for each routine and describes no automatic retry or failure alert, so the owner opens the run history if the sheet is missing.

The same run drafts a short confirmation email for each customer with an arrival window, which the owner edits and sends from that conversation. In this illustration the owner moves the estate house to the start of the day, because the son can only stay until noon, and pushes the second-floor dresser to the last slot.

The sequence below is the morning as the run sheet planned it, with the decision at each stop and what exists afterwards. Times are illustrative.

The chest freezer is the one item that day whose disposal carries a federal record. Under EPA's safe disposal requirements, as checked on 16 October 2026, whoever takes the final step in disposing of a household freezer, a scrap yard or a landfill for instance, is responsible for making sure its refrigerant is recovered first. When the job was booked, the owner chose a yard that takes freezers with the refrigerant still in them; the guide to disposal records covers the signed statement a yard needs when the refrigerant has already been removed.

At the charity dock, the charity decides what it accepts and the owner decides what is offered. Whatever slip the charity issues is photographed for the Records Bot, and the owner can offer the family a copy. Whether that slip means anything for anyone's taxes is a question for the family's own adviser, and no draft answers it.

1. 07:30

   Estate house, first load

   Decides

   Which rooms the son releases, and which items he wants kept back

   Output

   A full truck of furniture and bags, a set-aside box left in the house and a note of what was loaded

2. 09:15

   Charity dock

   Decides

   Which pieces the charity accepts on the day, from those the owner offers

   Output

   A donation slip, photographed by the owner for the Records Bot

3. 10:00

   Transfer station

   Decides

   None new: the rest of the load goes as planned

   Output

   A weigh ticket or receipt for the load

4. 10:45

   Estate house, second load

   Decides

   Whether the house needs a third load, which the owner tells the son on site

   Output

   The truck full again, the chest freezer strapped at the front

5. 12:15

   Scrap yard

   Decides

   Whether the yard's rules for a freezer still holding refrigerant are met

   Output

   A receipt naming the freezer, filed against the estate job

6. 13:00

   Back to the bungalow

   Decides

   What goes in the third load, and what the afternoon can still hold

   Output

   A revised afternoon, drafted for the owner to confirm

Clear-outs after a death are the jobs where the paperwork that matters most is not the company's. Bank statements in a drawer, a will in a shoebox, photographs, jewelry, cash in a coat pocket: anything like that found while loading goes to the owner, who stops, sets it aside and hands it to the person who booked the job, in this illustration the son, or to whoever the family names. In Aevrion's design the rule is a lasting rule every Bot is told to remember: personal documents and valuables are never photographed into a Bot conversation, never saved on the shared computer and never listed item by item in a job record.

What the Records Bot does keep is the fact of the handover, in the owner's words: one box of papers and a jewelry case set aside and handed to the son before noon, who signed the job sheet. That line protects the company if a relative later asks what happened to something, and it carries no more detail than it needs. Because every Bot on the account shares one computer and its files, keeping a stranger's papers off that computer altogether is simpler than trying to confine them to one Bot.

The third load costs the afternoon roughly an hour and a half, and something has to give. Parked in the bungalow's driveway, the owner messages the Dispatch Bot with the change. The Dispatch Bot redrafts the afternoon, proposes moving the second-floor dresser to Friday morning, and drafts an email to that customer giving the reason and two new windows. The owner picks one and sends it at the next stop.

The plan can travel between the Bots as well. If the owner keeps the three in a group chat for the day, the Dispatch Bot can post the revised order there so the Records Bot knows which loads to expect paper for. The documentation says handoffs inside a group are currently text-only, so a photo of a weigh ticket goes to the Records Bot as a direct message, and email drafts and approval requests never appear in a group at all. The owner's own messages in the group can carry attachments; the Bots' handoffs cannot.

One thing the group does not change. No Bot decides that the dresser waits, that the son's set-aside box is complete or that the freezer can go; the run sheet is a proposal, and the owner is the only person on the road.

In the evening the Records Bot compares Thursday's run sheet with the paper the owner has passed it: each load should have a weigh ticket, a donation slip or a yard receipt. In this illustration the second transfer-station receipt is missing, because the owner put it in a pocket and never photographed it. The Bot lists that gap and nothing else; it does not rebuild a figure from memory or guess a weight. The owner finds the receipt in the cab and sends a photo.

Two drafts wait in the owner's conversations: a thank-you to the son summarizing the three loads, the charity drop and the box handed over, and a note to the Friday customer confirming the new time. The owner changes a line in the first and sends both. At six the routine drafts Friday's run sheet, with the dresser first.

Look back over the busiest weeks of the last season and mark each day when one job forced others to move. For each, write down who was told, how, and how late. That list shows whether the planning or the telling is the bottleneck, and it decides whether the Dispatch Bot or the confirmation drafts come first.

Rate the day plan next, from bookings to run sheet to customer confirmations, with those moved days beside you. Aevrion's workflow automation readiness assessment is free, asks for no sign-up and rates that one workflow on twelve dimensions, among them handoffs, exception frequency and ownership clarity, returning a score, one of four results, the blockers and a next step at once. A day plan that lives only in the owner's head will score low on rule clarity, which caps the result. The pillar on one-man-army AI departments explains how the roles fit together, and the contact page is where to scope the three Bots against the company's own booking system with Aevrion Ops.

1. One truck sells the same capacity twice, so a large job such as an estate clean-out reshapes every booking after it.
2. A Dispatch Bot can draft the next day's run sheet and customer confirmations on a schedule; the owner reorders, edits and sends.
3. Personal papers and valuables pass from the owner's hands to the family; Bots record only the fact of the handover.
4. Group chats carry text between Bots, so photos of tickets and slips go to the Records Bot in a direct message.
5. The day closes when every load has a ticket, slip or receipt, and the Records Bot lists gaps without inventing figures.
6. Under EPA's rule the yard that takes a chest freezer for final disposal answers for recovering its refrigerant.