A go-to-market team of nine, without hiring a marketer.
Before Armada Works existed, we ran a 9-agent fleet inside Dream Event: a consumer product that generates event plans via AI. A solo founder operated the functional equivalent of a four-person GTM team. Every technique we deploy in client repos today was proved here first.
- Client
- Dream Event
- Operator
- Robert Cowherd, solo founder
- Period
- Early 2026: ongoing
- Deliverable cadence
- Daily briefs · weekly synthesis
A solo founder building a consumer product.
A solo technical founder was building a consumer product while simultaneously trying to write the blog that would drive SEO, research keywords, send lifecycle emails, triage support, run cold outbound, track paid ads, and stay on top of 30+ competitor products shipping weekly.
The usual answers: hire a marketer, hire a content person, contract an SEO agency: each cost $5K-$15K/month and took weeks to onboard. The work was fragmented, context-sensitive, and changed daily. A hire would spend three months learning what to do, and their output would still bottleneck on the founder's review.
Nine specialized agents, one synthesizer.
Each agent has a permanent role, a defined cadence, and access to the same codebase the founder works in. Each commits its work to main with its own bylined commit messages. Each posts a daily brief to a private reporting endpoint. A tenth agent: the CMO: reads all nine briefs each morning, synthesizes them, and writes a single message to the founder with the 3 to 5 things that need human attention.
They coordinate through git.
Agents don't message each other directly. They coordinate through git-committed state files. Each day, every sub-agent writes to docs/agents/state/{agent}-brief-YYYY-MM-DD.md.
The CMO reads all of them, writes a synthesis at cmo-brief-YYYY-MM-DD.md, and writes the founder's message at cmo-founder-message-YYYY-MM-DD.md. Work that needs to happen flows from the CMO into content-queue.md. The Content agent picks tasks off that queue.
All state is git. All work is traceable. If any agent produces something wrong, you can see exactly when, why, and what informed the decision: and roll back with a single revert.
Five things we learned.
- I.
Git is the coordination layer.
Every agent writes to files in the same repo. No queue, no message bus, no event stream. Just commits. The simplicity is the feature: you can grep the last 30 days of marketing decisions.
- II.
A synthesizer agent is non-negotiable.
Nine daily briefs is more reading than the founder will do. The CMO agent exists because the founder's attention is the real bottleneck. Without synthesis, the system overwhelms instead of scales.
- III.
Agents should be bylined.
Every commit has an agent's name on it. This makes it easy to see which agent is producing high-quality output and which needs prompt tuning.
- IV.
Constraints beat autonomy.
Each agent's prompt includes hard rules: which files it can touch, which commands it can run, what it cannot deploy without founder approval. The best agents are the most constrained.
- V.
The system improves itself.
Agents file their own bugs against their own prompts via founder messages. "The SEO agent suggested we block specific domains in the Content agent's competitor list." These meta-improvements compound monthly.
The valuable thing isn't the agents: it's the system.
After running the fleet for months, a pattern became obvious. The valuable thing isn't the agents: it's the system architecture. Reports endpoint, state files in git, CMO synthesis, templatized prompts, a dashboard the founder owns. That architecture is stack-agnostic and ICP-agnostic. It could run for any founder-led company with a codebase.
So we packaged it. Armada Works deploys this same architecture into client codebases: adapted to their brand, their ICP, their tooling: and operates it on their behalf. Clients get the outcome of a marketing team without the hiring, the management overhead, or the vendor lock-in. When the engagement ends, the system stays.
We'll ask three questions.
What's stuck on your desk. What your codebase looks like. What “a good quarter” would ship. If Armada isn't the right fit, we'll tell you.
Book the call →