37 agents across 8 businesses: books closed from bank statements, a Google Ads agent that can't wreck the account
Published
How does this AI workflow work?
- Replaces: Closing a year's books by trusting a bookkeeping app's numbers, re-asking the accountant the same questions, managing Google Ads by hand, and the founder relaying work between projects himself.
- What to connect:
- Claude Code (Opus for orchestrators, Sonnet for research subagents), with Codex as the reviewer that tries to break things;
- Herdr, an open-source terminal workspace manager for coding agents, with one workspace per business and phone access over SSH;
- Hermes Agent, which reads iMessages and routes each one to the right business;
- each business as a git repo of markdown with a short CLAUDE.md.
- How it works: Every question to the owner carries a code (e.g. "P47"), answered with "P47 yes".
- The finance agent: closed last year's books for several companies.
- It treats bank and card statements as the only truth and keeps categories in rules files.
- It adds a balance assertion at every statement close and sorts questions before they go to the accountant.
- It wrote down 17 mistakes with fixes, and those became a shared books skill.
- The ads agent: writes a Google Ads Script that runs with DRY_RUN on and logs what it would do; the owner reads the script and the log before it goes live.
- Lesson: a scheduled prompt that names the skill and the job loaded it 7 of 7 times, while a passing mention loaded it once in 8.
- Results: on the day described, 72 commits and 23 merged pull requests, with one product question waiting on the owner. No cost stated.
- Who it's for: Sole proprietors and indie founders running several small businesses or projects who want agents to handle bookkeeping prep, ads and code while keeping business data in their own repos.
From the Morning Tokens issue of Oct 19, 2026