Running a general contracting business alone: a failed re-inspection week.

A one-person builder is the estimator, the superintendent, the scheduler and the person who assembles the draw. Most weeks those jobs take turns. The week a framing re-inspection fails, they all arrive on the same afternoon: every trade that this county's sequence, as the builder entered it, puts after framing (in this illustration the rough-ins, insulation and drywall) slides, and the stage the lender was going to fund on Friday is no longer complete.

Supervised AI assistants can carry the redrafting: the new chain of dates, a notice for every waiting sub, the draw checklist with its gaps marked. They cannot decide when the framing is ready, promise a sub a date, or say anything to the lender. What follows is one invented week on one invented build, drawn up to show where the line falls; no real builder, project or measured result stands behind it.

In this illustration the builder holds a California contractor's license, works without office staff and is building a 2,400 sq ft custom home on a construction loan. The clients own the lot and hold the construction loan; the builder assembles each draw package for them under the loan's terms. Framing is up, the plumber, electrician and HVAC installer have roughed in, and the loan's draw terms, as the builder entered them from the loan documents, fund the rough-in stage once its inspections have passed and the releases for the previous draw are on file. That draw is due Friday.

This builder works to the One-Man Army model, which the pillar article sets out: the builder stays the only decision-maker, and each recurring desk job gets a named AI assistant of its own. This builder runs three Bots on Grok Bot: Schedule, which owns the inspection calendar and the sub notices; Paperwork, which owns the lien log and the draw checklist; and Coordinator, which posts the week to the project's group chat. All three work on the same cloud computer, can message one another and can pass a task to the Bot that should own 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.

The first framing inspection left a short correction list. The framer came back, and on Tuesday the inspector re-inspects and leaves a notice: two items still open. The builder photographs the notice and messages the pictures to the Schedule Bot one-to-one. Handoffs posted into a group chat are currently text only, so anything a Bot has to read from an image goes to it directly.

Schedule then reads the inspection sequence the builder entered for this county when the permit was issued. In this illustration, that entry says the rough-in inspections follow framing approval, the insulation inspection follows the rough-ins, and drywall waits for the insulation inspection. Another county may order or name these differently, and the Bot uses nothing except what the builder entered. From that entry it redraws the chain: every trade from the plumber to the drywall crew now hangs on a re-inspection date nobody yet knows.

By late morning Schedule has a table in the builder's conversation. The dates in the third column are left for the builder, because only the builder knows when the framer can return and when the county is likely to send an inspector.

Each notice is an editable email draft in the Schedule Bot's conversation, with the recipient and body shown, and the builder chooses whether to send or discard it. Drafts never appear inside the group chat; the Coordinator's post only says how many are waiting. The documentation describes no telephony or texting, so the framer, who answers only the phone, gets a call from the builder, and the plumber's office gets the email.

The drywall sub is the one most easily forgotten. Their start sits two links further down the chain, and if nobody says anything they will hold the crew for a date that has already moved. The draft to them says plainly that hanging cannot begin until the insulation inspection passes and that the builder will confirm a date once framing is approved. It does not guess when that will be.

When the chain moves, Schedule sends the Paperwork Bot a direct message: the rough-in stage will not have passed its inspections by Friday. That message passes ownership of the question to Paperwork, which reruns the draw checklist the builder entered from the loan documents and returns three lines. The stage inspection item is unmet. The electrician's unconditional release for the previous draw's payment is not in the file. And the lumber yard, which served a preliminary notice early in the job, has no release on file at all.

California's licensing board explains why the last two lines matter (as checked on 15 October 2026): a preliminary notice tells the property owner that the supplier or sub could file a lien claim if unpaid, a conditional release comes before payment and an unconditional one after it, and the property owner, here the builder's clients, may by law hold back the next payment while last time's unconditional releases are missing. Rules differ in other states, and the deadlines are for the builder's lawyer, not an assistant. The lien waiver tracker article covers that paperwork in full.

What happens next is the builder's. Whether to ask the lender to fund part of the stage or move the draw is a conversation every word of which the builder writes and sends; the Paperwork Bot drafts nothing to the lender and does not open its portal. Its output is the checklist with gaps marked, and a draft request to the electrician for the missing release, which the builder sends after checking the amount.

The project group holds the three Bots; the documentation allows two to six in a group, and Bots in it can post and pass work among themselves. Its documented example is a launch group in which a coordinator can assign work, and that is all this Coordinator does: it posts the week, assigns each new item to Schedule or Paperwork, and lists what is waiting for the builder. Approval cards, requests for logins or secrets and email drafts are kept out of groups altogether, so every decision happens in the owning Bot's own conversation.

A Bot that supervises the others, checks their work and chases them is not something the documentation describes. Where the documentation does use the title Chief of Staff, it means a Bot that compiles a digest of what changed for a human to read. Here the Coordinator is an Aevrion pattern assembled from the documented pieces: a coordinator in a group, Bot-to-Bot messages and ownership handoffs. The builder remains the supervisor. Bots can message each other to hand off work, and Cursor's help pages say no switch turns that off; a Bot follows instructions about it, so a builder who wants these items passed along by hand tells the Bots so.

The framer's corrections are made on an open frame. OSHA's federal fall protection page says employers must provide fall protection at six feet in the construction industry. California, where this illustration is set, runs its own OSHA-approved State Plan through Cal/OSHA, which covers private-sector workplaces in the state, and its Construction Safety Orders include a section on residential-type framing (both as checked on 15 October 2026). How the state plan's rules apply to these corrections is for the framing contractor as employer and the builder to settle and carry out. Schedule's notices contain no safety instructions beyond one line the builder wrote once for every notice, and no Bot judges whether a site is safe to work.

In this illustration the framer closes both items on Wednesday and the inspector approves the framing on Thursday morning. The builder records the result in the Schedule Bot's conversation, and only then does the chain get dates: the builder enters a target for each rough-in inspection request, and Schedule redrafts every Tuesday notice with those dates, each marked as the builder's estimate. The drywall draft is the one the builder reads twice, because it still hangs on two inspections that have not happened.

Paperwork reruns the draw checklist against the same entered terms. The stage item is still unmet, since the rough-ins have not yet been inspected. The electrician's release arrived on Wednesday, after the builder sent the request. The lumber yard's is still missing, so the builder rings the yard, then writes to the lender, for the clients, asking to move the draw by a week. That message and the decision behind it are the builder's. The Bots' part was knowing on Thursday morning exactly which papers stood between the clients' loan and the next payment.

One rule changes because of the week: Paperwork now drafts each release request on the day a payment is recorded, not in draw week, so a missing release shows up while the payment is fresh.

This week worked only because two entries already existed: the county's inspection sequence, typed in from the permit, and the draw checklist, typed in from the loan documents. Without them a Bot has nothing to redraw on a Tuesday afternoon. Make those entries for the current build first; a calendar Bot can follow, then the lien log, and a coordinator once two Bots share a project.

Aevrion Ops can help a builder with that groundwork: mapping their own inspection and draw chain, deciding which desks can prepare without them, and scoping custom integrations to the scheduling and document systems they already use, where each vendor's terms and API allow and after testing. A builder deciding where to begin can take the workflow automation readiness assessment; one with a specific project office in mind can ask for a scoping conversation through the contact page.

1. On a custom build, one failed re-inspection moves every downstream trade and the lender's draw on the same day.
2. The chain of dates comes only from the county sequence the builder entered; another county may order or name inspections differently.
3. Notices to subs are email drafts the builder dates and sends; the documentation describes no texting or calls, so phone-only subs get a call.
4. The draw checklist shows unmet stages and missing releases; every word to the lender is written and sent by the builder.
5. The Coordinator assigns and posts; a supervising AI chief of staff is an Aevrion pattern, not a documented feature, and the builder supervises.