Measure to warranty with one crew: a window company in a pre-1978 district.

In an older neighborhood a small window company runs two clocks at once. One belongs to the manufacturer: order, acknowledgment, ship date, delivery. The other is the lead-safe file that, in the United States, comes with a replacement in pre-1978 target housing however small the job. When the owner is also the salesperson, the measurer and the person the crew answers to, both clocks run through one diary, and a change on the first quietly breaks the second.

This article follows one illustrative job through such a company, from the final measure to the warranty registration, and shows where supervised AI assistants can prepare the paperwork between the owner's decisions. Treat it as a worked design, not a description of any real company and not evidence of results.

Picture a replacement window and entry door company, in this illustration, working a district where most houses went up between the 1920s and the 1960s. The owner sells at in-home consultations, takes every final measure and approves every order. There is one install crew: a lead installer, who holds EPA's renovator credential, and a helper. The firm holds the firm certification EPA requires. Nobody works in an office.

The one-man-army idea is simple: the owner decides, and each recurring kind of desk work belongs to its own named AI assistant. The pillar article explains it at length. In this company the owner has set up four Bots in Grok Bot, following Aevrion's pattern: Order Desk, which follows each order from measure to delivery; Install Week, which coordinates the crew's week; Lead-Safe File, which keeps the RRP paperwork in order; and Service, which prepares warranty registrations and service replies. All four work on the account's one persistent cloud computer and share its files and browser sign-ins.

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 illustrative job is a two-story house from the 1950s: seven double-hung windows going in as inserts, and a back door replaced full-frame. Each step below names the decision a person makes and what the assistants have ready once it is made.

1. 01

   Final measure

   Decides

   Do the owner's measurements, squareness checks and the door's handing agree with what was sold?

   Output

   Order Desk's comparison of the measure sheet with the contract, with every mismatch listed for the owner

2. 02

   Order placed

   Decides

   Is the order right, and will the owner commit the company's money to it?

   Output

   An order sheet the owner checks and places in the dealer portal; the Bot places nothing

3. 03

   Acknowledgment

   Decides

   Does the manufacturer's acknowledgment match the order line by line?

   Output

   A discrepancy list from Order Desk, or a note that every line agrees

4. 04

   Ship date

   Decides

   Once the ship date is confirmed, which install week does the owner offer?

   Output

   A tentative crew hold and a draft letter offering the week, waiting in the owner's conversation

5. 05

   Delivery check

   Decides

   Do the delivered units match the order in size, glass, grids, color and handing?

   Output

   A checklist the lead installer completes, with photos the owner attaches for Order Desk

6. 06

   Install week

   Decides

   Is the house ready, is the lead-safe file complete, and does the crew go?

   Output

   Prep instructions sent by the owner, a complete pre-start file and the crew's week posted

7. 07

   Walkthrough and close-out

   Decides

   Is the punch list cleared and the job finished?

   Output

   Final invoice and post-job lead-safe notice drafted together; warranty registration data prepared

Order Desk owns the middle of the job. A routine runs early each weekday and reads the manufacturer's dealer portal for the company's open orders: new acknowledgments, ship dates and any order whose status has changed since the last run. It compares each acknowledgment with the order the owner placed and lists differences, and a ship date that has moved goes to the top of the owner's morning summary.

The portal is reached through the Bot's browser, which is supervised browser use where the manufacturer permits it, subject to testing. A portal may block automation outright, in which case the owner attaches an export of the open-order list to Order Desk's conversation each morning instead. The login stays the owner's. If the portal asks for a sign-in when the routine runs, Order Desk reports that and stops; the owner signs in later through a takeover of the computer, as the Grok Bot documentation describes, and never types a password into the chat. Order Desk does not accept an acknowledgment, change a line or cancel an order.

The routine's instructions also say what to do when the portal cannot be read: put that at the top of the summary rather than carry yesterday's ship dates forward as today's. Install weeks are booked from those dates, so a summary built on stale ship dates does more harm than one that plainly says it failed. And because the run happens before the owner is up, it asks for nothing: an approval raised with nobody watching expires after about ten minutes (Cursor's help pages say thirty) without running, so the dawn routine ends in a summary and drafts.

Install Week is the coordinator. It works in a group chat with Order Desk and Lead-Safe File, and the documentation's own example gives its coordinator the power to assign work. Bots may message each other, and Cursor's help pages say no switch turns that off; a Bot follows instructions about it. Each Thursday Install Week posts next week's plan: jobs whose units have arrived and passed the delivery check, jobs whose lead-safe file is ready for the start date, and jobs that are blocked and why.

For each job it drafts the household's prep instructions: clear the sills and the floor in front of every window, move furniture back from the openings, take down blinds and curtains, keep pets in another room, and say where the crew can park. In a pre-1978 house the letter also tells the household how the crew will contain dust, in wording the lead installer approved once, because setting up the work area is the renovator's responsibility and not something a letter decides. The lead installer is asked about anything unusual at a house, such as a tight staircase for the door; the owner reads and sends the letter.

Two things never travel through the group. Drafts and approval requests surface only in the owner's one-to-one chat with the Bot that made them, so the plan in the group points to a draft rather than containing it. And handoffs between Bots in a group are currently text-only, so the delivery-check photos go from the lead installer to the owner, who attaches them in Order Desk's conversation.

Install Week has been told one lasting rule to remember: no draft names an install date until Order Desk holds a confirmed ship date for every unit on the job. A remembered rule guides the Bot without locking anything, so the owner still reads every draft before it goes. What each household message says at each stage is covered in the guide to the sale-to-install gap. In this district the rule has a second job: the week a letter offers becomes the start date Lead-Safe File measures the pamphlet against, so a date promised early can break both clocks at once.

Every job in this district is in target housing, and the federal rule never treats window replacement as minor repair, so size never excuses a job from the file. Only a lead-free finding on the affected components, made in writing by an inspector or risk assessor or through the credentialed renovator's test-kit or laboratory testing, takes a job outside the rule (40 CFR 745.82(a)), and that record is filed too. The rule itself is set out in the companion RRP guide; what matters here is how the lead time pulls on it.

40 CFR 745.84 allows the Renovate Right pamphlet to reach the owner at most sixty days ahead of the start (as checked on 15 October 2026); the companion guide sets out the two ways of proving delivery. This owner hands the pamphlet over at signing and collects the acknowledgment on the spot. When Order Desk reports a ship date, Lead-Safe File compares the proposed start with the pamphlet date and flags any job where the gap would pass sixty days. The lead installer and the owner decide what happens next. The Bot never judges whether a house is target housing, whether lead-based paint is present or whether the crew's work practices were right; it keeps the file and shows its gaps.

At the walkthrough the owner works every sash, lock and weatherstrip with the homeowner and writes the punch list. Install Week drafts the final invoice from the job record. Alongside it, Lead-Safe File drafts the compliance information that 40 CFR 745.86 says the firm must give the owner by the time the final invoice goes out, or thirty days after completion if that comes sooner; the lead installer checks it and the owner sends both. If the punch list is waiting on a remade unit, the summary shows both candidate completion dates; the RRP paperwork guide explains why choosing between them is the owner's question for their adviser.

Service takes over from there. Warranty registration differs by manufacturer, so the Bot prepares the details each of the owner's manufacturers asks for and the owner submits them through that manufacturer's own process. Months later, when a homeowner reports a fogged pane or a sticking door, the photos come to the owner, who attaches them for Service. Service drafts the reply and the claim; whether it is a warranty matter is the owner's call.

In this illustration the two clocks meet on the seven-window job. The first acknowledgment came back with a grid pattern that did not match the order; the owner had it corrected, and Order Desk's morning summary now shows the corrected ship date three weeks later than the first. Lead-Safe File reruns the dates: the homeowner signed for the pamphlet at the kitchen table on the day the contract was signed, and the new start would fall more than sixty days after that, outside the window 745.84 sets. The lead installer, as the renovator, and the owner decide how the pamphlet reaches the household again, with a fresh acknowledgment, before the crew arrives. Install Week redrafts the household's letter around the new week, and the owner sends it from that Bot's conversation.

If that collision sounds familiar, the readiness assessment is a free, ungated place to begin. Score one workflow in it, keeping ship dates and pamphlet dates in step, against its twelve dimensions; it returns one of four results straight away, with the blockers it found and a next step. Expect ownership clarity and handoffs to score low while both clocks live in one diary. The Bots, the routines and the dealer-portal and job-record connections would then be designed with Aevrion Ops, each connection depending on the vendor's API or terms and built only after testing.

1. A one-crew window company in an older district runs the manufacturer's clock and the lead-safe file through one owner's diary.
2. Order Desk compares measures, orders and acknowledgments and reads the dealer portal; the owner holds the login and places every order.
3. Install Week drafts prep letters and posts the crew's week; drafts sit in the owner's one-to-one chats, and the owner alone sends them.
4. An install week offered to a household is also the start date the pamphlet window is measured from, so none is offered before every unit's ship date is confirmed.
5. The final invoice is drafted with the post-job lead-safe notice beside it; the lead installer checks the notice and the owner sends both.
6. When a ship date slips, the pamphlet date is rechecked before the household hears a new week.