Why your AI agency runs slower at 12 people than at 6

At six people, everyone knows what everyone is doing. At twelve, nobody does — and you spend three days a week explaining the work instead of doing it. This is the AI-agency cliff, and most founders walk off it the same way.

We've watched seven agencies cross it in the last 18 months. The pattern is identical enough to be useful.

The 6-person state

A six-person agency is a single working memory. The founder knows every project. Every Builder knows every other Builder's current task. Slack is one channel that anyone can read in five minutes a day.

Status is implicit. Coordination is free. Senior ICs spend most of their time on senior IC work.

This is the period founders look back on as "when we were really shipping."

The 12-person state

At twelve people, no one human can hold the whole org in their head anymore. That's not a culture failure — it's an arithmetic one. Twelve people generate sixty-six possible pairwise threads of work in flight at once.

What changes:

1. The founder becomes the bottleneck on everything they used to be the catalyst for. They're the only person with full visibility, so every decision routes through them.
2. Standups grow. The 10-minute round becomes 25 minutes. People stop listening to half of it.
3. Status lives in DMs. Notion was supposed to fix this. It didn't.
4. Senior ICs context-switch more. The most expensive person on payroll is the most distracted.

The output curve looks like this:

Output per person
│
│        ╱╲
│       ╱  ╲
│      ╱    ╲___
│     ╱         ╲___
│  __╱              ╲___
│
└──────────────────────────── Team size
   3      6      9    12   15

Per-person output peaks somewhere between 5 and 8. By 12 it's down 30–40%. By 15 it's flatter than at 5.

The default response makes it worse

When founders feel the slowdown, they reach for the same playbook every time:

1. Hire a project manager.
2. Adopt a heavier PM tool.
3. Schedule a weekly sync-of-syncs.

All three add coordination overhead — and the slowdown was coordination overhead. So now there's more meta-work, and the senior ICs context-switch more, not less.

By month six on this trajectory, half the team is doing project management of one form or another. The senior prompt engineer you hired to ship is doing standups and writing status updates.

A focus-first response

The agencies that get through the cliff without the slowdown do three things instead:

They make focus the default. One task per Builder, visible to the team, timer-bound. Every interrupt is a deliberate choice, not the default state. See Focus Mode for the version we ship.

They put the truth in the board, not in standups. The board is the status; reading it replaces the meeting. The 9am call becomes optional, then disappears.

They give the lead a signal — not a dashboard. When something is about to stall, the lead sees the named cause: blockers, focus drift, task age. They intervene mid-week, not at the post-mortem. This is what AI Pulse is for.

When to hire the thirteenth

The right answer to "we feel slow at 12" isn't always "hire a PM." It's sometimes "hire the missing IC" and sometimes "stop hiring until output recovers."

A useful test: when the team feels slow, ask if your Focus Ratio has dropped (see Focus Ratio: the only productivity metric that matters). If it has, the slowdown is coordination, not capacity. Hiring another person makes it worse.

If Focus Ratio is holding and the work queue is genuinely larger than the team can absorb in two weeks, then hire — but hire an IC, not a PM. The PM hire is the answer to a slowdown that the IC hire would fix.

The summary, for a busy founder

If you're at 12 people and slowing down:

1. Don't hire a PM yet.
2. Measure Focus Ratio for one week. The number will be lower than you guessed.
3. Run the 5-step focus protocol.
4. Re-measure. If Focus Ratio is back over 50% and the slowdown has eased, you didn't have a hiring problem.
5. If Focus Ratio is up and the work queue is still backed up — then hire. And hire an IC.

The cliff is real. It's not your team. It's the arithmetic of coordination at twelve.