The One-Man Army: running several AI departments with Grok Bot.

The One-Man Army is an operating model, not a product feature. One owner or operations manager oversees a small roster of named AI assistants, each responsible for one kind of work — answering and qualifying inquiries, preparing estimates, drafting follow-ups, keeping job records tidy, assembling the weekly numbers. The assistants prepare, draft, check and report. The owner decides, approves, sends and signs.

Grok Bot provides several of the building blocks this needs: persistent named Bots with their own job and context, reusable skills, scheduled routines, a shared cloud computer they work on, and the ability for Bots to message each other, hand work over and work together in group chats. It does not provide a department-in-a-box. The coordination layer described here — a coordinator that routes work between the others — is Aevrion's way of combining those documented pieces, and it is labeled that way throughout.

The model does not remove licensed technicians, it does not replace a dispatcher's judgment, and it does not run without supervision. Reliability comes from the same things it comes from with people: one owner per task, written procedures, a single source of truth, approval gates on anything consequential, and someone who looks at the exceptions every day.

Most home-service businesses do not lose jobs because nobody can do the work. They lose them in the gaps between the work: the inquiry that arrived during a job and was not answered until evening, the estimate that went out without the photos the homeowner asked about, the follow-up that never happened because the quote lived in someone's notebook, the review request nobody sent, the invoice that is thirty days old and has not been chased.

Every one of those gaps is preparation and coordination — reading, sorting, drafting, checking, reminding. In a small company all of it lands on the owner, usually at night. Hiring an office team is the traditional answer, and for many businesses it is still the right one. The One-Man Army asks a narrower question: which parts of that preparation can a set of supervised AI assistants carry, so the owner's hours go to the decisions only the owner can make?

A single general-purpose chat assistant is useful, but it starts every conversation without the business's context, it has no standing job, and it does nothing until asked. Grok Bot is organized differently. Its documentation describes a Bot as a durable teammate with a name, a job, its own conversation and working context that develops over time; a named Bot keeps its memory, files, browser sessions and preferences between sessions rather than resetting on every task.

The documentation is also explicit about when to create a separate Bot: when the work has a distinct goal, distinct tools and sources, its own working style, its own approval boundary or its own recurring schedule. It discourages a broad "General Helper". That rule is the whole foundation of the One-Man Army — a department exists when a job is genuinely distinct, not because more assistants sound more capable.

Just as importantly, the documentation recommends starting with the smallest useful roster: one Bot that owns an end-to-end outcome, with specialists added only for stable, distinct roles. An army is built over months, one department at a time, not switched on in an afternoon.

The ten departments below, with the coordinator described in the next section, make eleven, and that is a ceiling, not a starting configuration. Most businesses should begin with one or two of these and add the next only when the first is stable. For each department the left side is the preparation an assistant can carry; the decision on the right never moves.

Typical AI departments in a home-service business (an Aevrion operating pattern; the roles are illustrative):

• MARKETING AND SEO

  Drafts service-page updates, review replies and seasonal campaign copy from approved material. The owner approves anything that is published under the company's name.

• LEAD RESEARCH

  Compiles public information on new commercial prospects, builders or property managers into a short brief. The owner decides who is contacted, and how.

• INTAKE AND QUALIFICATION

  Reads new inquiries from the channels it has been given access to, sorts them by service and urgency, and drafts a reply and a job summary. A person confirms anything that commits the company to a time, a price or a visit.

• ESTIMATE PREPARATION

  Assembles the photos, measurements, notes and previous similar jobs into an estimate draft. The estimator — not the assistant — sets scope and price.

• SCHEDULING AND DISPATCH PREPARATION

  Proposes a slot from the calendar and the job's requirements, and drafts the confirmation. The dispatcher or owner confirms the booking and decides on any emergency reshuffle.

• CUSTOMER SUPPORT

  Drafts answers to routine questions from approved policy and the job record. Complaints, refunds, warranty decisions and anything emotional go to a person.

• JOB COORDINATION AND DOCUMENTATION

  Turns technician notes and photos into a tidy job record and flags what is missing. It does not sign off work or certify compliance.

• BILLING FOLLOW-UP

  Lists unpaid invoices by age and drafts reminders in the approved tone. A person sends them, agrees payment plans and handles disputes; payments themselves are never taken by an assistant.

• QUALITY ASSURANCE

  Checks other departments' drafts against the written procedure — required fields present, the right template, nothing promised that policy does not allow — and returns what fails.

• REPORTING

  Assembles a weekly summary from the systems of record: inquiries, quotes outstanding, jobs completed, invoices overdue, exceptions raised. The owner reads it and decides what changes.

Once there are several departments, something has to route work between them, or the owner becomes the router. Grok Bot's documentation supplies the parts. Departments can work at the same time and ask each other for things without waiting, and the exchange stays on record in the conversation. A department can hand a task over outright, so it moves between desks without the owner carrying it. A group of two to six Bots can share one outcome, and one of them can hand out the work.

What the documentation does not describe is a single Bot that supervises a whole roster. (Its own "Chief of Staff" example is something narrower: a Bot that prepares a source-linked digest of what changed across messages, calendar and documents for a person to read, and is told not to send messages or move meetings.) The One-Man Army's coordinator is Aevrion's pattern: a Bot whose job is to receive each new piece of work, decide which department owns it under a written routing rule, hand it over, and report back to the owner what is waiting for a decision.

Two documented limits shape how the coordinator is set up. Approval requests and email or Slack drafts do not appear in group chats, so anything that needs the owner's yes is raised in that Bot's own conversation, not the shared group. And handoff messages to a group are text-only, so a department that must inspect a photo receives it directly rather than through the group.

The coordinator decides who prepares the work. It never decides what the business commits to. That line — preparation can be delegated, commitment cannot — is the single most important rule in the model.

A handoff between two people works because they can ask each other questions. A handoff between assistants needs the questions answered in advance. The tool for that is a work packet: a short, fixed-format note that travels with each piece of work. Grok Bot's skills — reusable instructions capturing steps, decision rules, expected output and safety boundaries, shared across all of a user's Bots — are the natural place to define the packet format once so every department writes and reads it the same way.

1. 01

   Trigger

   Decides

   What happened that created this work?

   Output

   A one-line description and a link to where it came from

2. 02

   Source of truth

   Decides

   Where is the authoritative record?

   Output

   A link to the job, customer or invoice record — never a copy of it held in memory

3. 03

   Requested output

   Decides

   What, exactly, should the receiving department produce?

   Output

   A named deliverable: a draft reply, an estimate draft, a list

4. 04

   Owner

   Decides

   Which department owns the next step, and which person approves it?

   Output

   One Bot and one named human

5. 05

   Approval gate

   Decides

   Does anything here commit the business?

   Output

   Either 'prepare only' or the specific action that needs a person's approval

6. 06

   Deadline

   Decides

   When does this stop being useful?

   Output

   A time, and what happens if it is missed

7. 07

   Exception rule

   Decides

   What does the department do if information is missing or something looks wrong?

   Output

   Stop and return the packet to the coordinator with the question, rather than guess

Grok Bot lets sensitive or consequential actions stop for approval: the conversation shows the proposed operation and its inputs, and the user can allow it once, always allow it, or deny it. Which actions stop depends on the tool, the risk and the user's rules, and the documentation recommends explicit boundaries for exactly the actions a service business cares about — sending messages, publishing, purchases and financial transfers, deleting or overwriting data, changing permissions, and accepting legal terms. Its automatic review is model-based and is meant to complement explicit boundaries, not replace them.

Two caveats matter for anyone running this from a van between jobs. First, an approval controls the action proposed; it does not reverse work already completed, and neither does telling a Bot to stop. Second, an approval request raised by unattended work — a routine, a trigger or another Bot's message — expires if nobody answers, and the action does not run: after about ten minutes according to docs.x.ai, or thirty according to Cursor's help pages. An owner who is on a roof will miss those. The practical answer is to design for it: routines prepare drafts rather than act, and the owner reviews the queue at set times in the day instead of being interrupted.

Some decisions should never sit behind an approval button at all, because they need a person's full attention: anything involving licensed work or safety, prices and estimates, refunds and warranty decisions, legal or insurance commitments, and payments. Grok Bot's own documentation routes passwords, two-factor codes, CAPTCHAs and payment confirmations to a human takeover; the One-Man Army extends that principle to every commitment the business makes. 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.

An illustrative example — a homeowner asks a plumbing and heating company to look at a water heater that is leaking. It shows where each department works, where the work waits for a person, and who owns each state. It is a design sketch, not a description of an existing customer deployment.

1. 01

   Inquiry received

   Owner

   Intake department

   Advances when

   The inquiry is read, matched to the service and given an urgency; a reply and a job summary are drafted

   Ends when

   Spam or out-of-area inquiries are flagged for the owner, not silently discarded

2. 02

   Awaiting owner review

   Owner

   The owner

   Advances when

   The owner reads the summary, edits or approves the reply, and decides whether it is an emergency

3. 03

   Qualified, needs a visit

   Owner

   Scheduling department

   Advances when

   A slot is proposed from the calendar and the technician's skills; a confirmation is drafted

4. 04

   Booking awaiting confirmation

   Owner

   The owner or dispatcher

   Advances when

   A person confirms the booking and sends the confirmation

   Ends when

   The customer declines or does not reply — the packet returns to intake with a follow-up date

5. 05

   Job preparation

   Owner

   Job coordination department

   Advances when

   A job packet is assembled: address, access notes, photos the customer sent, previous visits

6. 06

   On site

   Owner

   The technician

   Advances when

   The licensed technician diagnoses, decides and does the work; notes and photos are captured

7. 07

   Record and quote

   Owner

   Documentation and estimate departments

   Advances when

   Notes become a clean job record; if replacement is needed, an estimate draft is prepared for the estimator

   Ends when

   The estimator, not the assistant, sets the price

8. 08

   Follow-up and billing

   Owner

   Billing department, then the owner

   Advances when

   The invoice reminder and review request are drafted on schedule and sent by a person

9. 09

   Reported

   Owner

   Reporting department

   Advances when

   The job appears in the weekly summary with any exception it raised

Count the states held by people: the owner, the dispatcher, the technician, the estimator. The departments shorten every state in between; they do not remove those four.

Several limits in Grok Bot's documentation decide what this model can and cannot do for a service business today. Building around them honestly is what makes it reliable.

• TELEPHONE CALLS

  The documentation describes no call answering, voicemail, outbound calling or SMS. A phone line still needs a person, an answering service or a separate telephony system; an intake department can only work on inquiries that reach it in writing.

• TRIGGERS

  Routines run on a schedule — no more often than every five minutes — or from an event. docs.x.ai names Slack messages and GitHub notifications; Cursor's help pages add Linear, Sentry and PagerDuty events, email sent to the Bot's own address and webhook calls. A new web-form submission does not start a routine unless the form's system is built to call that webhook, and no trigger is documented for mail arriving in the business's own inbox. "Answers every lead in seconds" is not a claim this setup supports.

• CONNECTIONS TO YOUR SOFTWARE

  The documentation names Gmail, Notion and Slack as examples of connected apps, and a table on its security page lists others, QuickBooks Online and Zoho CRM among them, without saying what they can do. No field-service product is named. Connecting those systems is either supervised use of their websites through the Bot's browser — where the vendor permits it, subject to logins, two-factor checks and sites that block automation — or a custom integration built against the vendor's API or exports where the vendor offers them.

• SHARED COMPUTER

  All of an account's Bots work on one shared cloud computer and share its files, browser sign-ins and credentials. The documentation says plainly that separate Bots are not a security boundary. Anything that must be kept apart belongs in a separate user account.

• MEMORY

  A Bot remembers preferences and summaries, but the documentation says memory is not a substitute for an authoritative source. Prices, schedules and balances must be read from the system of record every time.

• UNATTENDED RUNNING

  Routines can be paused after a long absence, and approvals from unattended work expire. Someone has to look at the queue every working day.

Every department's output should be checked against a written procedure before it reaches a customer. In the One-Man Army that is partly the job of a QA department — a Bot whose only role is to compare drafts with the procedure and return what fails — and partly the owner's daily review. Grok Bot's documentation advises, for consequential work, asking a Bot to separate facts from source systems, assumptions, completed actions, actions awaiting approval and unresolved questions, and to keep the evidence. That separation is exactly what a reviewer needs.

Reporting closes the loop. Each routine keeps a history of recent runs, successes and failures; a weekly report assembled from the systems of record shows what each department handled and, more usefully, what it could not. The number worth watching is not how much the assistants did — it is how many exceptions reached a person, how long they waited, and whether the same exception keeps returning. A recurring exception is a procedure that needs rewriting.

Grok Bot's own guidance is to begin with read-and-prepare work, review the results, and only then add approved actions or a routine. For most service businesses the best first department is intake preparation or billing follow-up: both are frequent, both have a clear definition of done, and both can run in "prepare only" mode while the owner learns what the assistant gets right and wrong.

Before any of that, write the procedure down. An assistant follows the process it is given, including its gaps. If two people in the business answer the same inquiry differently, decide which answer is correct first — the assistant will otherwise pick one and repeat it every time.

Aevrion Ops can help service businesses with exactly this sequence: identifying which administrative work is suitable to hand to assistants, writing the procedures and approval rules, designing the departments and their handoffs, and building the integrations a business's own software needs, where each vendor's API or terms allow it, after testing. Grok Bot access and plans are set out on the official plans page (linked from the capabilities article); Aevrion does not sell or resell them.

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 product changes often; check the linked pages before relying on a specific limit. 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.

1. The One-Man Army is an operating model: one person supervises a small roster of specialized AI assistants that prepare, draft, check and report.
2. Create a separate assistant only for a genuinely distinct job; start with the smallest useful roster and add departments as each becomes stable.
3. A coordinator that routes work between departments is an Aevrion pattern built from Grok Bot's documented messaging, handoff and group-chat features — not a built-in feature.
4. Preparation can be delegated; commitments cannot. Prices, licensed decisions, refunds, legal and insurance matters and payments stay with people.
5. Approvals do not undo completed work, and approvals raised by unattended work expire after about ten minutes (thirty, by Cursor's help pages) — design routines to prepare drafts for scheduled review.
6. No telephony, no documented field-service connection and one shared computer: plan custom integrations and account separation where the business needs them.