Re-roof season with one owner: three inspections a day, two crews.

Consider a retail roofing company with one owner, who also inspects and estimates, two install crews and a part-time bookkeeper. In peak season the owner's day holds three inspections, two active roofs and a supplier waiting for a delivery date. The office work around that, from photo sorting and proposal writing to delivery changes, customer notices, change orders and warranty paperwork, is preparation that assistants can carry. The decisions inside it are not.

This week is Aevrion's illustration, not a client and not a result. It uses three named assistants, one coordinator group and a single rule throughout: assistants prepare, the owner commits.

Every retail job runs the same chain: inspection, estimate, proposal, signed contract, material order, delivery, tear-off, install, any inspection the local authority requires, close-out. In this illustration the supplier delivers shingles straight onto the roof, which ties the delivery date to the install date. A bundle sitting on a roof is waiting for a crew and a dry day.

That makes the week fragile in a particular way. A wet Wednesday does not just cancel Wednesday's install. It moves a delivery, which moves the next tear-off, which changes what three homeowners were told, and it happens while the owner is on somebody else's roof. None of the paperwork is hard. It is constant, and all of it has to be right.

The One-Man Army model on this site has one person supervising a small roster of named assistants, each owning one kind of preparation; the pillar article covers it in full. Grok Bot supplies the pieces: durable named Bots with a job, working on a shared cloud computer with a browser and files, following written skills and running scheduled routines. Its documentation recommends the smallest useful roster, with a separate Bot only for genuinely distinct work. In this company, three jobs are distinct enough.

The roster in this illustration (Aevrion's role names, not documented ones):

• INSPECTION DESK

  Indexes inspection photos, checks measurement reports against each job, and assembles proposal drafts from the owner's estimate.

• CREW AND MATERIALS

  Holds the install schedule, runs the morning forecast check, and drafts weather-hold notices and supplier delivery changes.

• CLOSE-OUT

  Prepares change-order paperwork, checks final photo sets, drafts invoices and keeps the warranty registration list.

Based on the Grok Bot documentation at docs.x.ai as checked on 13 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 three Bots share one group chat. The documentation supports groups of two to six Bots that post and pass work among themselves, with a coordinator Bot able to assign work, and it lets one Bot send another an asynchronous request or hand over ownership of a task. Here Crew and Materials is the coordinator, because the schedule is what every other job depends on.

Two documented limits shape the design. Group handoff messages are text-only, so when Close-out must compare final photos with the inspection set, Inspection Desk sends the images to it directly. And approval requests and email or Slack drafts never appear in a group chat, so every homeowner notice and supplier request is raised in the owning Bot's own conversation, where the owner reviews it and sends it.

Above the group, the owner reads one morning digest. The documentation's Chief of Staff example is exactly that: a source-linked summary of what changed and what needs attention, prepared for a person and told not to send messages. A Bot that supervises the other Bots is something else. It is not a documented feature; where Aevrion builds one, it is an Aevrion pattern assembled from the group coordinator and Bot-to-Bot messages.

The owner inspects three roofs. On each, roof access and fall protection are the owner's call; in construction, OSHA's threshold for fall protection is six feet (as checked on 13 October 2026), and no assistant has a view on how a particular roof is climbed. Between roofs, the owner sends photos and short notes to Inspection Desk as attachments. By evening each job has an index the owner can scan before estimating.

What each inspection photo index holds:

• BY ROOF PLANE

  Photos grouped and labeled by slope and elevation, front first, so the proposal can refer to them.

• CONDITION NOTES

  The owner's notes matched to the photos they describe: lifted tabs, granule loss, flashing, ventilation, penetrations.

• DECKING CONCERNS

  Any area the owner suspects is soft, kept as its own list because it drives a proposal clause and possibly a change order.

• MEASUREMENTS

  Whether the measurement report has arrived and matches the address and roof outline. The provider is reached through a custom integration, or supervised browser use where the vendor permits it, subject to testing.

• GAPS

  What is missing before the estimate can be finished: an unphotographed slope, the attic, the existing layer count.

The owner estimates in the company's usual tool and prices each job. Inspection Desk then assembles proposal drafts. As checked on 13 October 2026, NRCA's homeowner checklist expects a written proposal that spells out the work and its specifications, when it starts and finishes and how payment works, and tells homeowners to read the warranty and understand what would void it. Those become the draft's sections, filled from the estimate and the company's approved wording.

One clause matters more than it looks: decking. Nobody sees every sheet of decking until the old roof is off, so the draft carries the owner's standard decking clause, explaining how replacement is identified, photographed and priced, exactly as the owner wrote it. The assistant does not write that clause or put a number in it. The owner reviews each draft, edits it and sends it, and Inspection Desk records the date sent and drafts a follow-up for the day the owner chose.

Crew and Materials runs a routine at 5:30 every weekday morning. It reads a public forecast for each scheduled address through the browser, compares it with the install schedule, and reports which jobs are at risk on which days. Its instructions say what to do if the forecast page cannot be read: say so, rather than reuse yesterday's forecast.

On Wednesday, Thursday's install looks wet. Before the owner is up, the Bot has prepared three things in its own conversation: a weather-hold notice to Thursday's homeowner with a provisional new date, a request to the supplier to move the roof-loaded delivery to the next dry day the schedule allows, and a revised two-day crew plan. The owner makes the weather call, with the crew lead's view, and sends the two messages as drafted or edited.

Because the routine runs while the owner sleeps, it must end in drafts. The documentation says an approval raised by unattended work expires after about ten minutes (Cursor's help pages say thirty) and the action does not run, so a design that waited for the owner to approve a supplier change before dawn would simply fail. If the supplier's ordering portal is the only way to move a delivery, the Bot can prepare the change through supervised browser use where the supplier permits it, and the owner completes any login or confirmation the site asks for. Once the owner signs in, that supplier session sits on the computer every Bot on the account shares, and separate Bots are not a security boundary.

The rescheduled crew starts on a different roof and finds soft decking under the old shingles. This is the moment the proposal's decking clause was written for. The crew lead sends photos to Close-out directly, and Close-out prepares a change-order draft: the area affected, the photos, the clause it relies on, and a blank where the price goes.

The owner fills in the price, which the assistant never does, and decides whether to ring the homeowner first. Once the homeowner agrees, Close-out files the signed change order with the job and tells Crew and Materials, by a direct Bot-to-Bot message, to add the extra decking to the next materials list. If the crew needs sheets that afternoon, buying them is the owner's action; the documentation hands payment confirmations to a person rather than the Bot. 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.

Close-out compares the final photo set with the inspection index and lists any slope or detail without an after photo. It drafts the invoice from the signed proposal and any change orders, for the bookkeeper and the owner to check.

It also adds the job to the warranty registration list. Where the shingle manufacturer offers a registered warranty, the owner in this illustration treats registration as a close-out step rather than an afterthought, because it is easy to overlook in a busy week. Close-out drafts the registration from the job record and reminds the owner on the date the owner set. The owner submits it, because a registration is made in the company's name, and the reminder follows each manufacturer's terms as the owner recorded them rather than a rule the assistant assumes.

That split is the design, and it is why the roster stays small. If a fourth kind of work appears, such as a steady flow of written spring inquiries, it earns a fourth Bot only once it is distinct and stable. The readiness assessment linked below is a structured way to find which part of a company's week is ready to hand over first.

1. Retail re-roof season is logistics: inspections, roof-loaded deliveries and weather holds, with the paperwork arriving while the owner is on a roof.
2. Three distinct jobs justify three assistants: inspection and proposals, crew and materials, and close-out. Start smaller if the work is not yet distinct.
3. Group chats carry text handoffs; photos go Bot-to-Bot and every customer or supplier draft stays in the owning Bot's own conversation.
4. Overnight routines end in drafts, because approvals raised by unattended work expire after about ten minutes (Cursor's help pages say thirty).
5. Decking is a change-order trigger the owner prices; warranty registrations are drafted by an assistant and submitted by the owner.