I Built a Team of Bots

For a year, my whole operation ran on one AI partner. One machine, one assistant, everything routed through the same brain. It worked. But as the ventures piled up, I could feel the seams. The affiliate sites wanted one kind of attention, the apps another, the writing another, and the day job something else entirely. Asking one generalist to hold all of it meant it relearned my rules every single time. So this summer I did something different. I gave it a team.

Here is the idea. Instead of one assistant that knows a little about everything, I built a handful of specialists that each know one thing cold. Each one has a name, a narrow lane, and a runbook. The runbook is the part that matters. It is the written down, hard won, this is exactly how we do it for that corner of the business. Once the right way lives in a document, the bot stops guessing and starts being an expert. The runbook is most of the work. The bot is the smaller part that reads it and acts.

So meet the team. Carson keeps my gift planning follow ups organized and on schedule. Belvedere runs the commerce side, the affiliate sites and the storefronts and the product picks. Higgins handles growth, the search traffic and the writing that pulls people in. Hudson is the engineer, the one who keeps the command center and the machines healthy and ships the code. Bunter watches over the apps and the monthly invoicing. Five specialists, five lanes, and none of them steps on another one.

I built the whole team with Claude Code. Each specialist is a short definition plus its runbook, written and refined right alongside the work it describes. When a job comes in, my main partner reads the situation, picks the right specialist, hands it its runbook, and lets it work. I am the person at the top who decides what matters. My partner is the manager that routes the work. The specialists are the crew that does it. It is an org chart, except the whole company is software I own.

They live where the rest of my operation lives. On a machine in my house that never sleeps, reachable through the command center and through my own private model console. The heavy, repetitive thinking runs on free local models I host myself, so the team can work all day without a meter running. The expensive brain only gets pulled in when something actually needs judgment.

And they all obey the one rule that makes this an asset instead of a liability. They draft, they prepare, they stage, they remind. They do not send the email, move the money, publish the page, or make the call. I do. Specialists actually make that line safer, not riskier. Each one only knows its own lane, so none of them has the reach to do something dumb across the whole operation. The team runs the loops. I keep the judgment.

People hear team of bots and picture something huge and expensive. It cost almost nothing. It is a few text files, a stack of runbooks, some free local models, and a machine I already owned. The leverage is not in fancy tools. It is in writing down how the work should be done, once, and then handing that to something that will do it the same way every time.

If you build, I wrote the whole thing up. The bots, how each one is put together, and what each one is for. It is a free download below, no fluff, just the wiring.

One human, a team of bots, one rule that keeps me in the chair.

MG