a builder's codex
codex · operators · Boris Cherny · ins_underfund-deliberately

Underfund teams deliberately so AI substrate, not headcount, absorbs the work

By Boris Cherny · Head of Claude Code, Anthropic · 2026-04-27 · podcast · What happens after coding is solved

Tier A · TL;DR
Underfund teams deliberately so AI substrate, not headcount, absorbs the work

Claim

When a team has access to a strong AI substrate, deliberately under-staff each project — one person plus the substrate beats a fully-staffed team — because constraint forces clarity and lets the substrate absorb the rest.

Mechanism

Adding humans to a workstream the substrate can do creates coordination overhead, slower decisions, and weaker individual ownership. A single under-resourced operator with strong tooling has to clarify scope to ship at all; that forced clarification is where the productivity comes from. The substrate eats the throughput gap.

Conditions

Holds when:

Fails when:

Evidence

"There's this interesting thing that happens when you underfund everything a little bit — people are forced to clarify, and the way they ship really quickly is just intrinsic motivation."

"Productivity per engineer increased 200% while we 4x'd the team."

Anthropic measured both more people and more output per person. Boris ships 10–30 PRs/day with ~5 Claude Code agents in parallel and is still one of the most prolific committers on his team.

— Boris Cherny on Lenny's Podcast, 2026-04-27

Signals

Counter-evidence

Operators with no substrate access, or in regulated domains where every artifact must be co-reviewed, will hit a quality wall fast. Underfunding without compensating substrate is just the old "do more with less" trap. Boris is explicit that the win comes from substrate + token budget, not constraint alone.

Cross-references

Open the interactive view → View original source → Markdown source →