From crack photo to warranty: a foundation owner and a contract engineer.

A foundation repair business has a second professional inside its pipeline: on a referred job, the most important decision belongs to someone outside the company, the professional engineer who evaluates the house and designs the repair. In North Carolina, the engineering board's guideline on foundation repair (last revised 22 October 2024; checked 15 October 2026) places the preliminary analysis, including how many piers and where, with a PE or someone under a PE's responsible charge. Each state sets its own rules.

So the owner's back office faces two ways: a complete pack out to the engineer, and the engineer's report, design and completion paperwork back into the proposal, the job and finally the warranty file. Supervised AI assistants can prepare both directions. This article follows one illustrative job around that loop. It is invented to show the design: no real company stands behind it, and no result is claimed.

In this illustration the company works in North Carolina. The owner sells and inspects every job himself and runs a crew of two installers. He has no engineer on staff: a PE at a separate engineering firm evaluates the houses he refers and designs their repairs, an arrangement the board's guideline says many companies use. The company's own written warranty allows transfer to a later owner on the terms it states.

The One-Man Army pillar explains the model at length; in brief, every decision stays with the owner, and each recurring stretch of desk work gets an assistant of its own. Following Aevrion's pattern, he creates four: Intake, which turns inquiries into neutral records; Engineer Desk, which owns everything crossing to and from the engineer; Jobs, which runs permits, crew dates and readings; and Warranty, which keeps the register.

He builds them as Bots in Grok Bot: each a named teammate with its own conversation, and all sharing the single cloud computer that comes with his account. The documentation lets Bots message one another asynchronously and pass a task outright, with the handoff visible, and Cursor's help pages say no switch turns that messaging off. None of them touches the phone. The documentation describes no telephony, so calls stay with the owner and his answering service.

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 the Monday, a homeowner emails three photos: a crack running from the corner of an interior doorway, a gap where a window frame meets the wall, and a door that no longer latches. Her question is whether the house is moving. A custom integration copies the email and photos into the shared workspace, where the Intake Bot builds a record in her own words and drafts a reply in the neutral language the owner wrote for it.

Neutral language is not evasion. It tells her what happens next and never what is happening to the house. The owner's approved phrases are given to the Intake Bot in chat for it to remember. Those words steer the Bot but cannot physically block a bad sentence, so he reads every draft before he chooses Send.

• RECEIVED

  Your photos and description are on file, and the inspector will bring them to the visit.

• HER QUESTION

  We don't assess a house from photos. The first step is an inspection, and if anything needs an engineer's evaluation, we will arrange that with you.

• THE OFFER

  Two inspection windows, proposed from the company's calendar (read through a custom integration, tested first) and confirmed by the owner before the draft goes.

• THE ASKS

  Whether there has been earlier foundation work at the address, and any warranty paperwork from it.

• NEVER IN THE DRAFT

  A cause, a reassurance, a repair, a result or a price.

The Jobs Bot prepared a site sheet the evening before: address, access notes, the homeowner's photos and the questions still open. At the house the owner takes a floor elevation survey with a laser level, maps the cracks he can see and notes the gutters, downspouts and grading. He forms a preliminary assessment and decides to refer the house to the engineer. That decision is his, and no Bot suggests it.

Back in the van he sends the survey sheet and his own photos directly to the Engineer Desk Bot, which owns the referral, rather than to the group chat the four Bots share. The group is for status, and a handoff from one Bot through a group can currently carry only text, so anything a Bot must inspect goes to it directly.

The Intake Bot passes ownership of the job to Engineer Desk, and the owner can see the handoff in the conversation. Engineer Desk assembles the referral pack from the shared workspace: the homeowner's words and photos, the survey readings exactly as recorded with the reference point the owner used, the crack map, the site notes and the access details. It checks the pack against the engineer's own intake checklist, which the owner saved as a skill, and lists anything missing.

Then it drafts the covering email to the engineering firm. The draft says what the owner observed and asks for an evaluation. It suggests no repair and no pier count, which under the board's guideline belong to the engineer's analysis from the start, and no timescale, which only the engineer can give. The owner reads it and sends it, and Engineer Desk logs the date it went.

In this illustration the report and repair design arrive ten days later. The owner saves them to the job folder; Engineer Desk files them, logs the date and lists the logistics the documents name: drawing references, any permit the owner says the work needs, and whether the engineer will issue a completion letter. If the report runs late, Engineer Desk drafts a polite chaser for the owner to send; it never contacts the firm itself, and never tells the homeowner when to expect a design.

What Engineer Desk never does is summarize the findings for the homeowner. A Bot's paraphrase of an engineer's conclusion is a structural statement from something that has evaluated nothing. The owner prices the engineered design, and the proposal goes out with the engineer's report attached unchanged. When the homeowner asks what a phrase in it means, the owner answers, or asks the engineer to.

Ownership passes from Engineer Desk to Jobs when the owner records a signed proposal. Whether this job needs a permit is the owner's decision, made from his own notes on each jurisdiction he works in; this article does not say when foundation work needs one, because that varies by place. Building-department portals are supervised browser use where the department permits it, subject to testing. Sites can block automation, and every login or two-factor code is entered by the owner himself after taking control of the Bot's screen.

When the crew finishes, the owner retakes the elevation survey at the points he used on the first visit. The Jobs Bot puts both sets in one table, flags any point missing from either, and files the table for the engineer and the warranty record. It computes no improvement, never calls a floor level and never tells the homeowner what changed. Nobody in this company promises lift, and the assistants are written never to mention it.

The guideline expects the PE's responsibility to run through to the completion documents, so a job without the engineer's letter, where the engineer issues one, stays open on the board.

The Warranty Bot opened a row when the owner issued the written warranty: property, holder, the document itself, the design reference, both sets of readings and the completion letter. In this illustration the homeowner sells three years later and the buyer's side asks about the warranty. The Warranty Bot reads the company's own warranty for that address, lists what it says a transfer needs, and drafts the transfer paperwork with a covering note. The owner checks it against the document and sends it. Whether the transfer is valid, and what the warranty covers, are the owner's answers, not the Bot's.

The four Bots share a group chat that serves as the job board; a documented group holds between two and six Bots, and a coordinator inside one is allowed to hand out work. Here the Jobs Bot posts the Monday board and assigns new items. That coordinating role, like any chief of staff sitting over the Bots, is an Aevrion pattern built from those pieces, not a product feature; where the documentation uses the name Chief of Staff, it means a digest written for a human reader.

A group never shows approval cards, sign-in or secret requests, or email drafts, so the board only points to them, and the owner sends drafts from each Bot's own conversation. If a routine or another Bot's message raises an approval when he is on a site, it goes stale after about ten minutes (Cursor's help pages say thirty) unanswered and is not carried out. And all four Bots share one computer and its sign-ins; separate Bots are not a security boundary.

The engineer is the second professional in this pipeline, and each crossing deserves a written rule: what the pack must hold before it leaves, and what happens to the report when it returns. Sit down with the engineer and agree both, because the engineer knows which missing readings cost a second site visit. The neutral intake phrases come next, and the warranty register last, starting from the warranties already issued.

Aevrion Ops can scope those two crossings with an owner, design the four Bots and where each must stop for approval, and connect them to the inbox, calendar and job records in use, each connection built only where the vendor allows it and tested first. A good first step is Aevrion's workflow automation readiness assessment.

1. A foundation company that refers to a contract engineer has two professionals in its pipeline, and each referred job crosses between them twice.
2. Neutral intake language says what happens next, never what is happening to the house, and the owner reads every draft before sending.
3. The outbound pack carries the homeowner's words, the readings as recorded and a gap list; it never suggests a repair or a pier count.
4. The engineer's report reaches the homeowner unchanged, because a paraphrase of a structural finding is itself a structural statement.
5. Post-repair readings sit beside the first ones with no conclusion drawn, and nobody promises lift.
6. Warranty transfers run as the written warranty allows: drafted by a Bot, decided by the owner.