400 recurring accounts and one license: an owner-applicator's back office.

In a one-license pest control company, the person who holds the credential also writes most of the pesticide use records, and nobody reads them twice. The same person works the heaviest route, renews the termite agreements and books the inspection a real-estate agent needs before a closing. The records are the sharpest part of that load, because they are written at the stop and leave with the customer.

Supervised AI assistants can do the second reading. A records-check Bot can compare each record with the owner's field list after every stop and leave a short gap list to deal with between stops, while other Bots prepare tomorrow's route, draft prep notes and renewals, and brief the owner once a week. None of them applies anything, writes an inspection finding or signs a record. The company below is invented to show a design; it describes no real business and reports no results.

In this illustration the owner holds the state's commercial applicator certification and runs the main route. One technician, registered as the state requires, runs a second, smaller route. The book is about four hundred recurring general pest accounts, a set of termite agreements that each renew once a year, and a handful of wood-destroying insect inspections a month for home sales. There is no office staff; records are completed on a tablet and sync to the field-service software.

The One-Man Army idea is short to state: decisions stay with the owner, and each recurring kind of paperwork gets an assistant of its own with a name and a job. The pillar article sets it out; here it meets a trade where some of that paperwork is a regulated record.

The owner creates the assistants in Grok Bot under Aevrion's pattern. Each is a named Bot that keeps its standing rules in memory, and all five work on one persistent cloud computer. Grok Bot's guidance is to keep the roster small and give a new Bot only a job that has settled into its own shape, so the owner added these one at a time, records check first. The five roles, and the order they arrived in, are Aevrion's design for this trade rather than anything built into the product.

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 five work together in one group chat. A group holds two to six Bots, which post and pass work there, so every handoff can be read in one place. Route Prep acts as coordinator, following the documentation's example of a group in which a coordinator Bot can assign work. The Weekly Review Bot is modeled on the documented Chief of Staff role, a digest that briefs a person. It supervises nobody: a chief-of-staff Bot that manages a roster is not a documented feature.

The group has edges the owner has to design around. Nothing that needs a decision shows up there: approval cards and email or Slack drafts appear only in each Bot's one-to-one conversation with the owner. And a Bot handing work on through the group can currently pass only text, so a photo from a stop goes straight from the owner to the Bot that needs it.

The owner finishes a quarterly service, completes the record on the tablet, hands over the customer's copy and moves on. Every thirty minutes during route hours, a routine on the Records Check Bot picks up whatever records have synced since it last looked, well above the documented five-minute floor for scheduled runs. Getting at those records means building a connection to the field-service product the company actually runs, or using an export that product already produces, and testing it before relying on it.

For each record the Bot compares every field with the owner's written list for the state, and checks the links inside it: where one job used two products, each needs its own target pest, area and method (Georgia's fact sheet asks for this; the owner's list follows their own state). Nothing goes to the customer. The output is a gap list in the Bot's own conversation, short enough to read in the next driveway: record, field, what is missing. The owner corrects the record in the field-service software under the correction procedure written down for the state. The Bot touches nothing.

When a gap is in the second technician's record, the Bot drafts a note to that technician and the owner decides whether to send it. Nobody watches the routine while the owner drives, so it is written to need no approvals; one raised by work nobody started by hand goes stale within roughly ten minutes (Cursor's help pages say thirty) and its step is dropped.

The reason to check after every stop rather than on Saturday is memory. A blank found two hours later can still be filled from memory, under the state's correction procedure and with a corrected copy to the customer where that procedure requires one; by the weekend neither is reliable. The check does not change the rule that the record is completed at the stop.

Before an interior service the customer may have a part to play: leaving the house for a time, emptying cupboards, moving pets. EPA's guidance for homeowners hiring an exterminator counts instructions of that kind as part of the control program a company should set out for them (as checked on 15 October 2026). The wording has to come from the product label and the applicator, because the applicator chose the product.

In this company the owner writes down the precautions for each service type once, from the labels of the products in use, and updates the list whenever a product changes. Route Prep turns them into a customer note for each booked interior service and leaves it as an editable email draft; the owner reads it and chooses Send or Discard. If a booked service has no precautions on file, the Bot reports the gap and drafts nothing. It never fills the hole from a general source, because a precaution copied from the wrong label is worse than no note.

Each termite agreement in this illustration renews once a year, and the Renewals Bot drafts notices ahead of each date from the agreement on file. Every notice asks whether the structure has changed since the last inspection. EPA's leaflet warns homeowners that a company's termite promise may become invalid if they make structural alterations without telling the company first, so the question protects the customer as much as the company.

Replies come back to the owner. When one mentions a new room or an enclosed porch, the Renewals Bot messages Route Prep directly, asking it to put an inspection visit on the owner's proposed list, and the handoff shows in both conversations. Cursor's help pages say no switch turns off messaging between Bots, so the owner checks that no Bot has been told not to message the others before the design leans on it. Whether the agreement still applies after the change, and what happens next, is the owner's decision.

Home sales bring a different document. NPMAForms.com, the National Pest Management Association's site for digital inspection forms, describes the NPMA-33 Wood Destroying Insect Inspection Report as used only to report activity or damage from wood-destroying insects, which for that report means termites, carpenter ants, carpenter bees and reinfesting wood-boring beetles (as checked on 15 October 2026). Its FAQ explains that an inspector's signature and license number are stored in the inspector's profile and filled into each form they create.

That settles where an assistant stands. The findings are a professional report by the person who inspected. A forms account that signs as the inspector should never be signed in on a computer every Bot can use: the documentation says all of an account's Bots share one cloud computer, including its browser sessions, and that separate Bots are not a security boundary.

Intake can still prepare everything around the inspection: the property, the agent, the closing date, who ordered the report and who will provide access. Afterwards it files the finished report against the account and drafts a cover email for the owner to send to whoever the inspector directs. The owner attaches inspection photos straight to Intake's conversation when the account file needs them.

Each Bot saves its outputs to a dated folder in the shared workspace, where, the documentation confirms, other Bots can read them. The Weekly Review Bot reads those files and the field-service records, not its own memory, and writes the owner a digest in the order the week runs.

• RECORD GAPS

  Gaps found last week, gaps fixed, and any still open, by technician.

• RENEWALS

  Agreements due next month, notices sent, and replies that mention a change to the house.

• PREP NOTES

  Booked interior services that still have no precautions on file.

• CREDENTIALS

  The owner's and the technician's credential lapse dates from the register, flagged a full quarter ahead.

• INSPECTIONS

  Wood-destroying insect inspections booked for the coming week, with closing dates and access still unconfirmed.

• WAITING ON THE OWNER

  Drafts not yet sent or discarded, oldest first.

EPA reserves restricted-use pesticides, for purchase as well as use, to applicators with certification and the people they directly supervise, and leaves the certifying to state agencies running programs EPA has approved; that was its position on its certification-standards page when checked on 15 October 2026. Supervising the second technician, in whatever form the state requires (and directly, for any restricted-use pesticide), is the owner's duty, not a field on a route sheet. The same holds for pest identification, product and method, precautions for sensitive occupants, every record and every inspection finding, every warranty decision, and every price, refund or payment. No Bot here collects or pays money; if a website ever stops at a payment step, the owner takes over the computer and finishes it in person. 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.

A records check needs a field list before it needs a Bot. In this illustration the owner spent the first evening turning the state rule into that list and the credential register, ran the check by hand against a week of old records to see what it caught, and only then set the routine. Take last month's records, mark every field the state list asks for that a record left blank, and count how many of those records a customer had already carried away. That count says whether the after-stop check is worth building first; the field list becomes the Records Check Bot's lasting rules.

Aevrion Ops can sit down with an owner-applicator to sort which paperwork could run between stops, draft the field list and the credential register with them, and connect the Bots to their field-service product if its vendor's API and terms make that possible, testing it first. For a company in that position, the readiness assessment is a sensible first conversation.

1. When the licensed owner also runs the main route, the records check has to happen without them: after every stop, by a Bot that only reads.
2. Five Bots cover records, route prep, intake, renewals and a Monday digest; anything awaiting the owner's decision sits in one-to-one conversations, never in the group.
3. Prep notes come only from label precautions the applicator supplied; with none on file, the Bot drafts nothing.
4. Renewal notices ask about structural changes, and a reply that mentions one goes to the owner.
5. An NPMA-33 report carries the inspector's own signature, so the forms account stays off the shared Bot computer and the findings stay with the inspector.