Infinite
Leverage.
Five AI employees. Two offices. One weekend. 14 days of building a one-person agentic company - documented end-to-end, while it was happening, without the retrospective gloss.
The playbook said: do the work, then organize.
We did the opposite. Set up the org chart first - staffed entirely by AI - and let the structure tell us what work was next.
A one-person agentic company isn't one founder plus N agents.
It's one founder, plus N agents, plus the comms layer, plus the routines, plus the information architecture that lets the founder actually see what the system shipped.
The agents are the easy part. The machine behind them is the whole game.
Over 14 days we built the machine. Not just the visible agents, but the plumbing - skills, tooling, routing, review workflows, a CRM, a comms layer, three websites, and the curriculum we didn't know we owed our clients.
Every day is a real log. Some days the thing shipped. Some days we learned the thing we built three weeks ago was wrong.
Read it as a build log. Read it as a leadership diary. Read it as the template for what your own org has to become before 2027.
14 days, laid flat.
Each day is a card. Click in for the full log. Designed so you can read the arc in order, or jump to the one that maps to your situation.
Setup · Founding the one-person org.
Five AI employees. Two offices. From blank doc to a running org chart in a weekend.
Meant to ship five agents. Shipped 12 production skills. Foundation work is the real work.
The system started running. I wasn't listening. Merged is not reviewed.
Killed Cowork. Moved the operation to Claude Code. A client bought the seat mid-build.
A mini CRM before a 10am meeting. Ten forms, three databases, three sites.
Notification graphs, PM agent promotions, the rule that killed "it merged so it's done".
The agents stopped being the story. The orchestration layer did.
Leverage · Selling while building.
Every "teach the non-techie" memo turned out to be a module we already owed clients.
Shipping in public closed a 5-day engagement before the program was finished.
Daily, weekly, monthly cadences. What makes an AI team move vs. quietly drift.
The onboarding agent that asks better questions than the human version ever did.
Always be cataloguing. The quiet skill the operator needs, the agent can't fake.
What we got wrong in week one and had to rebuild. All of it. With receipts.
Series finale. Six AI agents running, four queued, and the setup script that lets the pattern travel off my machine.
What actually got built.
Not a vibes piece. Tangible artifacts, all of them still running.
Five things we didn't know on Day 01.
Distilled from the full series. Cited to the day they first appeared.
Foundation work is the real work.
The part of an AI organization you never see - skills, tooling, permissions, review paths - is 80% of what makes it run. It is also the part that dies first when you cut corners. The founders who succeed are the ones who treat plumbing as strategy.- Day 02 · Set up trauma
Merged is not reviewed.
The moment your agents can ship without you, they will ship without you. "It's merged" stops meaning "it's right". You need a comms layer that forces human attention at the decision points that still require a human - and only those.- Day 03 · The comms layer
A 1-person company has three layers, not one.
One founder. N agents. A comms-and-routines layer. Most people build the middle and wonder why the system runs away from them. The layer is the thing. Build it first, or retrofit it in pain.- Day 03, Day 10
Always be cataloguing.
Information architecture is the unsexy skill that compounds hardest. Every document, decision, and artifact has a home, a canonical link, and an owner - or your agents hallucinate one for you. AI punishes sloppy knowledge systems the way the old internet rewarded them.- Day 12 · Information architecture
Build in public, sell from the log.
The same series you're reading now closed a 5-day client engagement on Day 04, before the program we were selling was finished being built. Working in the open is not a marketing tactic. It's the new sales funnel.- Day 04, Day 09
Working on this in your own company?
The Infinite Leverage Blueprint is the public artifact. The retreat is where we apply it to your situation - your org chart, your agents, your comms layer.
Get the next series in your inbox.
One short essay a week plus a heads-up when the next serialized build starts. No sign-up funnel. Unsubscribe with one click.