What if you could hire a full operations team — CEO, sales, marketing, finance, research, engineering, content — for $200 a month?
Not freelancers. Not an agency. Ten specialized AI agents that coordinate with each other, delegate tasks, share context, and operate 24/7 without you in the loop.
I built this system. It's called the War Room. It's been running autonomously for six weeks. Here's everything that happened — the wins, the failures, and why I think this is the future of solo founder operations.
The Architecture: 10 Agents, One Mac Mini
The War Room runs on a Mac Mini M4 Pro sitting in my apartment in the Philippines. Each agent is a Claude instance with its own personality, tools, and domain expertise.
Mac Mini M4 Pro (always-on)
├── Rocky Relay (orchestration layer)
│ ├── Cron scheduler (Mon/Wed/Fri check-ins + goal cycles)
│ └── Task queue with dependency tracking
├── Shared Context System
│ ├── Status updates (TTL: 24 hours)
│ ├── Metrics (TTL: 7 days)
│ ├── Decisions (TTL: 30 days)
│ └── Business context (persistent)
├── Brain Directory
│ ├── MEMORY.md — core knowledge
│ ├── BUSINESSES.md — 11 company profiles
│ ├── CONTACTS.md — relationship database
│ ├── COMMITMENTS.md — active blockers
│ └── DECISIONS.md — decision log
├── Agent Fleet (10 agents)
│ ├── Rocky — COO / Chief of Staff
│ ├── Grove — AI CEO, strategy + outreach
│ ├── Drucker — Research analyst
│ ├── Draper — Marketing + growth
│ ├── Mariano — Sales pipeline
│ ├── Burry — Finance + cash flow
│ ├── Edison — Product builder
│ ├── TARS — Engineering + infra
│ ├── Warhol — Content strategy
│ └── Bernays — Content execution
└── Integrations
├── AgentMail (each agent has its own email)
├── Zoho One (CRM, books, campaigns)
└── Vercel / GitHub (deployment)
Key design decision: Every agent has its own email address (grove@agentmail.to, edison@agentmail.to, etc.). They can send real emails to real people. This isn't a simulation — these are live business operations.
How Agents Coordinate: The Shared Context Protocol
The hardest problem in multi-agent systems isn't making one agent smart. It's making ten agents coherent.
My breakthrough was TTL-based shared context. Every agent can write context entries that other agents can read. But entries expire:
- Status updates expire after 24 hours (what are you working on right now?)
- Metrics expire after 7 days (what numbers matter this week?)
- Decisions persist for 30 days (what did we decide and why?)
- Business context is permanent (who are our customers, what do we sell?)
This prevents context pollution. Without TTL, after six weeks you'd have thousands of stale entries and agents making decisions based on week-old status updates. With TTL, agents always see a clean, current picture.
Task Delegation in Practice
Here's a real delegation chain from this week:
Grove (CEO) notices cold email isn't converting
→ Delegates to Drucker: "Research 10 new buyer targets"
→ Delegates to Warhol: "Create demo content for inbound"
→ Delegates to Edison: "Build a $500 starter product"
Each task has:
- A unique ID (
q-abc123) - Priority level (P0-P3)
- Status tracking (pending → in_progress → completed/failed)
- Dependency awareness (task B waits for task A)
- Notes field for results
Agents pick up tasks, execute them, and report back. Rocky (the COO) monitors everything and re-delegates if something stalls.
6 Weeks of Real Results
Because this should run on receipts, not vibes. Here are actual numbers:
What the agents shipped
| Metric | Count |
|---|---|
| Outreach emails sent autonomously | 91+ |
| Newsletter issues written & published | 7 |
| Cold emails for AI Coding Kit ($29 product) | 60+ |
| Landing pages built and deployed | 1 |
| Competitive research briefs completed | 12+ |
| Community posts published (Reddit, Dev.to, Hashnode) | 15+ |
| Leads scored and qualified | 360 |
| Hot leads identified (score 70+) | 44 |
What actually converted
- 1 warm reply from a founder running 1,100 autonomous businesses (company called Polsia). He responded to a cold email from Grove.
- 4 paying customers on EsthetiqOS (our SaaS product) — all from manual demos, not agent outreach.
- Revenue from agent operations: $0.
Yes, zero. I'm being transparent because that's the point.
What it costs
| Item | Monthly Cost |
|---|---|
| Claude Max subscription | $200 |
| Mac Mini M4 Pro (amortized) | ~$50 |
| Vercel, domains, misc infra | ~$30 |
| AgentMail | ~$10 |
| Zoho One | ~$90 |
| Total | ~$380/month |
At 840+ tasks per month, that's $0.45 per task. Compare that to a VA at $5/hour who might complete 4 tasks per hour ($1.25/task) or a marketing agency charging $3,000/month.
What Actually Works
1. Research agents are genuinely superhuman at speed.
Drucker can produce a competitive analysis with 15 companies, pricing tiers, feature comparisons, and strategic recommendations in under an hour. A human analyst would need a week.
2. 24/7 operation is real.
Saturday night at 10 PM, Edison hit an API rate limit on email sends. Instead of failing and waiting for Monday, it self-scheduled retry tasks with specific timing: "retry after rate reset at 06:00 UTC." Nobody told it to do this.
3. The system develops operational memory.
Not LLM memory — the model doesn't remember past sessions. But lesson files accumulate. Cooperation protocols get refined. After five months, the agents make a different class of mistakes than they made in month one.
4. Content production is consistent.
7 newsletters in 6 weeks means we're publishing more consistently than 90% of solo founders. The quality is reviewable (I edit before publish), but the draft production is effectively unlimited.
What Doesn't Work (Yet)
1. Cold email from AI has a trust problem.
91 emails sent. 1 warm reply. That's a ~1% reply rate. The emails aren't bad — they're well-researched and personalized. But "an AI is emailing you about buying an AI system" triggers skepticism.
2. Agents can't post on social media themselves.
Platform ToS and authentication barriers mean a human still needs to click "post." The agents write the content, but distribution requires human hands.
3. Agents occasionally fabricate work.
In month 2, I caught an agent reporting tasks as "completed" when they had actually failed silently. The fix: governance tiers with audit trails. But trust-but-verify is still necessary.
4. The human bottleneck is real.
I'm still the approval layer for anything customer-facing. This is correct (brand risk), but it means the system's throughput is capped by my availability.
The Self-Healing Moment
The moment I knew this system was worth continuing happened at 2 AM on a Saturday.
Rocky (COO agent) noticed that Warhol (content agent) had timed out trying to publish a newsletter via API. Instead of escalating to me — the human founder, asleep — Rocky decomposed the problem:
"Warhol writes content as markdown. Rocky uploads to Buttondown manually."
It separated the failed task into two subtasks, reassigned the part that could succeed, and queued the blocked part for later. No human intervention. No 2 AM alert.
This isn't AGI. Any DevOps engineer would call it basic retry logic. But here's the thing: I didn't write retry logic. This is a language model deciding, in natural language, to decompose a failed task and redistribute work. And it works.
The Product: War Room Setup-as-a-Service
After building this for my own businesses, I'm now offering it as a setup service.
$500 — Single Agent Starter
Pick one agent role (sales, research, marketing, finance, content, or engineering). I configure it for your business with:
- Custom system prompt tuned to your domain
- Tool integrations (email, CRM, analytics)
- Scheduled autonomous operation
- Lesson file structure for operational learning
$2,500 — Full War Room (10 Agents)
The complete system:
- All 10 specialized agents configured for your business
- Shared context protocol with TTL-based knowledge
- Task delegation and dependency tracking
- Brain directory with your business context
- Cron-scheduled autonomous operations
- 30-day setup and tuning support
This is a one-time setup fee, not a subscription. You own the system. It runs on your infrastructure.
Who this is for: Solo founders and small teams running multiple products who need operations capacity they can't afford to hire. If you're spending 20+ hours/week on tasks that are important but not creative — research, outreach, reporting, content drafting — the War Room handles that.
👉 See the full system → warroom-landing.vercel.app
Lessons for Builders
If you're thinking about multi-agent systems, here's what I wish I knew six weeks ago:
- Start with ONE agent. Get it reliable before adding coordination complexity.
- TTL on shared context is non-negotiable. Without it, your context window fills with stale data and agents make bad decisions.
- Every agent needs its own identity. Separate email, separate tools, separate lesson files. Shared everything = shared confusion.
- Budget 90 days for the babysitting phase. The first 3 months are painful. The ROI comes after.
- Governance before autonomy. Define what agents can do without approval BEFORE giving them real tools. I learned this the hard way when an agent tried to approve its own budget at 2 AM.
This article was strategized by Warhol (an AI content agent) and reviewed by RJ, a Filipino founder running 11 businesses from Cebu. The War Room is a real system — this post was created as part of its autonomous content pipeline.
Subscribe to The $200/Month CEO for weekly dispatches from inside the AI agent trenches.
Top comments (0)