# Agent Fleet Quickstart for a Business With No Engineers The small version of the fleet. One lead, two workers, a folder of text files, and about thirty minutes of setup. Written for an owner-operator or an office manager, not a developer. Companion to `agent-fleet-playbook.md`. Version 1.0, 2026-08-21. Source article: https://jwatte.com/blog/claude-code-agent-fleet-org-chart/ --- ## Read this first: the honest version You do not need fifty agents. Almost nobody does. What a five-person business actually needs is three things it does not have: a person who never forgets to follow up, a person who reads every document that arrives, and a person who checks the first person's work. That is the whole design at this size. One coordinator, two workers, and a rule that the coordinator never checks its own homework. You should expect this to save hours, not headcount. The businesses that get burned are the ones that fired the follow-up and then discovered that the agent had been marking things complete without doing them. Section 6 is how you avoid being that business. --- ## What you need * A computer you can install software on. * An AI assistant that can read and write files on that computer. Claude Code is what this guide is written against, and it runs in a terminal window; the desktop application works too if a terminal is not your thing. * A paid plan. The free tiers are not built for work that runs unattended. * One folder for the whole operation. Everything lives in text files inside it. If you can open it in Notepad, an agent can read it. That is it. No servers, no code, no subscriptions beyond the assistant itself. --- ## The folder Make one folder. Inside it, this structure: ``` my-business-agents/ RULES.md the things that are true about your business boards/ followups.md the follow-up project board documents.md the document-reading project board charters/ coordinator.md the lead's job description worker-followups.md worker-documents.md checker.md log.md one line per decision, append only digest/ one file per day, written by the checker inbox/ you drop files in here outbox/ finished work appears here ``` The folder is the system. Everything an agent needs to know is a file in it, which means any agent can be restarted at any time without losing anything. This is not a technical nicety. It is the difference between a setup that survives your laptop rebooting and one that does not. --- ## RULES.md, the most important file This is the file every agent reads before it does anything. Write it once, add to it forever. Keep it under two pages. ```markdown # About this business We are , in , serving . We have people. Our busy season is . # How we talk Our customers are . We never say . We always . Our phone number is and our address is . Never invent either. # Prices and promises # What an agent must NEVER do without asking me - Send anything to a customer, supplier, or anyone outside this business. - Post anything publicly. - Spend money, or agree to a price. - Change anything in . - Delete a file. - Sign, agree to, or commit to anything. # What an agent may always do - Read anything in this folder. - Write drafts into outbox/. - Update a board or the log. - Ask me a question. ``` The two lists at the bottom are the entire safety design at this size. Notice that "send anything to a customer" is on the never list. Draft, do not send. The first month is drafts only. You will be surprised how good the drafts get, and you will also catch the two or three places where the agent was confidently wrong about your business. --- ## The three jobs ### 1. The coordinator Reads the boards every morning, decides what the two workers do today, collects what they produced, and writes you one short summary. It does not do the work itself. That restraint is the whole point: a coordinator that starts doing the work stops coordinating, and you are back to one agent with extra steps. ### 2. Worker one: follow-ups The job nobody in a small business has time for. It reads your board of open threads and drafts the next touch for each: the quote that went out eleven days ago, the customer who said "call me in the spring", the supplier who never confirmed. It writes drafts into `outbox/`. You read them over coffee and send the good ones. ### 3. Worker two: documents Every document that arrives gets read, summarised in three lines, and filed with what it obliges you to do and by when. Insurance renewals, supplier terms, a lease amendment, a licence letter, a customer contract. Most small businesses discover something in the first week that they had already agreed to and forgotten. ### And the checker Not a fourth worker. A different seat that reads what the other three produced and looks for one thing: did anything get marked done that was not done. It writes the daily digest. It is the least glamorous role and the one that decides whether you can trust the setup in three months. --- ## Setup, about thirty minutes **Step 1.** Make the folder above. Empty files are fine. **Step 2.** Write `RULES.md`. Twenty minutes. This is where the value is. Everything else is plumbing. **Step 3.** Write the four charters. Use `agent-fleet-role-charters.md` and cut them down. For this size, a charter can be twelve lines. **Step 4.** Put three real things in `inbox/`. Not test data. Real documents, real open threads. Test data teaches you nothing about whether this works for your business. **Step 5.** Run the coordinator once, watch it, and interrupt it whenever it does something you would not have done. Every interruption is a line you add to `RULES.md`. **Step 6.** Do that for five days before you let it run unattended. --- ## The daily routine, ten minutes Morning: 1. Open today's digest. It is one page. 2. Answer the questions in the decisions section. Each one already has a recommendation, so most of the time you are typing "yes". 3. Read the drafts in `outbox/`. Send the good ones yourself. That is the routine. If it takes longer than ten minutes, either the digest is too long or the agents are asking you things they should be deciding. Both are fixed by adding a line to `RULES.md`. Friday, add fifteen minutes: 1. Read one full agent conversation from the week, beginning to end. You will find something. 2. Look at what you have been correcting all week, and write it down as a rule. 3. Check the spend. --- ## What it costs Budget the assistant subscription plus a small amount of usage on top, and check the number in week one rather than month two. Two things drive real cost at this size, and both are within your control: * **Re-reading.** An agent that reads the whole folder for every small task spends most of its money on reading. Keep the boards short and the rules file under two pages. * **Loops.** An agent that retries a failing action forever is the only way a small setup produces a surprising bill. Give every job a stopping rule: if it has not worked in three tries, stop and ask. Set a spending alert on day one. Not because it is likely, but because the cost of finding out late is the entire reason anyone tells this story. --- ## The five failures you will actually hit **1. It marked something done that was not done.** The most common one, by a wide margin. Fix: the checker opens the artifact. "Drafted the follow-up" means there is a file in `outbox/` with words in it. If the file is empty, the task is not done, whatever the summary says. **2. It invented a detail about your business.** A price, a warranty length, a service you do not offer. Fix: put the real ones in `RULES.md`, and add the explicit line "if it is not in RULES.md, ask, do not guess". Then check drafts for a month. **3. It sounds like a robot.** Fix: paste three things you actually wrote into `RULES.md` under a heading "this is how we sound". Examples work far better than adjectives. **4. It asks you about everything.** Fix: your never-list is too broad or your rules are too thin. Move things to the always-allow list one at a time, each with a written rule. **5. You stop reading the digest.** This is the one that ends the experiment, usually around week six. Fix: keep the digest to one page and make the first line the number of things that need you today. If that number is zero most days, the setup is working and reading takes twenty seconds. --- ## When to add a third worker Add one when the coordinator is turning work away, not when you think of another job to do. Good third seats for a small business, in rough order of payback: * **The quote chaser**, if you send quotes. Separate from general follow-up because the timing rules are different and it is usually the highest-value hour in the week. * **The reviewer responder**, drafting replies to public reviews. Drafts only, forever. * **The reconciler**, matching what was invoiced against what was delivered. * **The listings checker**, verifying that your hours, address and phone number match everywhere they appear online. Do not add a second coordinator at this size. The two-lead pattern in the main playbook earns its overhead somewhere around eight parallel projects. Below that it is ceremony. --- ## What not to hand to an agent at this size * Anything that talks to a customer without you reading it first. Not in month one, not in month six. * Payroll, tax filings, anything with a legal deadline and a penalty. * Pricing decisions. * Anything involving someone's health, safety, immigration status or credit. * The only copy of anything. If it is not backed up, an agent should not be allowed to touch it. --- Companion files at https://jwatte.com/downloads/ * `agent-fleet-playbook.md` * `agent-fleet-role-charters.md` * `agent-fleet-operating-contracts.md` * `agent-fleet-safety-and-cost-controls.md` Written by J.A. Watte. https://jwatte.com