(2026-02-13) Shipper The Two Slice Team

Dan Shipper: The Two-slice Team. For the past two decades, Amazon’s “two-pizza-team rule” has been the gold standard for team size.

(Today we’re launching a new experiment: Proof, an agent-native markdown editor that lets you collaborate on documents with multiple humans and AI agents—and tracks who wrote what)

Twenty-four years later, two-pizza teams are now themselves too big for building software products. When each employee is armed with Opus 4.6 and Codex 5.3, the ideal team size shrinks even further.

I call it the two-slice team. Two slices, to feed one person.

This is how we structure our product teams at Every. We have four software products, each run by a single person.

And these are real products, not just weekend vibe coding demos. For example, Monologue, our smart dictation app run by Naveen Naidu, is used about 30,000 times a day to transcribe 1.5 million words

AI also helps Naveen do customer service and market research, and think through business and product strategy. It allows him to do by himself what would normally take 3–4 people before AI.

we’ve also had to re-invent how the rest of the organization supports these teams.

Rather than putting more full-time employees on existing products, two-slice teams pull in help as needed from both inside and outside of Every.

To enable this, our design, growth, and marketing teams act as internal agencies that move team members in and out of projects as needed. (functional organization)

This kind of flexible structure is only possible because AI lets internal employees and freelancers alike get up to speed on an unfamiliar product in minutes

Sometimes these resources come from outside of Every too. Cora, run by Kieran Klaasen, employs a full-stack senior engineer who helps out a few days a week with hairy problems that current AI models aren’t great at solving in one go. The engineer dips in and out to help build the infrastructure that lets Cora process millions of emails per day.

Proof has started to get traction inside of Every. We use it to collaborate on the plan files generated by coding agents