The Two-Person Team Is a Fantasy
AI tooling raised the ceiling on shipping speed. The minimum viable team for production work is still three or four.
A founder I knew last year was proud of his two-person engineering team. They were shipping more than competitors with ten engineers. He had numbers to back it up: features per quarter, deploys per week, response times on customer requests. The whole pitch sounded like the future of software, and I remember thinking, the first time he laid it out, that I might be the dinosaur in the room.
Six months later they were hiring frantically. Not because the team had failed to ship. Shipping was fine. The product worked, customers paid, revenue grew. The problem was that one of the engineers wanted to go to his sister's wedding in another country and be off the grid for two weeks. And nobody could figure out how to let him.
That is the part of the AI-amplified team story that gets edited out of the case studies. The 1-2 person team can ship. It can ship a lot. The question nobody wants to answer is what happens when one of those people gets sick, takes vacation, or quits. Or when something breaks at 3am and the person who knows how it works is asleep with their phone in another room.
I have watched this play out across several organizations now. A team gets very small, leans hard on AI tooling, and looks like a productivity miracle for two or three quarters. Then the cracks show up. Not in shipping speed. In every other dimension that defines actually running production software.
Code review is the first one to break. With two engineers, every review is the same person every time. After a few months they have read each other's patterns so deeply that review becomes a rubber stamp, a chance to confirm shared assumptions rather than catch mistakes. Then someone introduces an LLM-assisted refactor across a critical path, and the review is two people who already trusted each other plus one model that has no skin in the outcome. Things get merged that should not have been merged.
On-call is the second. Two engineers sharing on-call have no real rotation. Both are effectively always on, taking turns at being slightly less on. There is no real off. PTO becomes a negotiation. Both people start arranging their lives around the assumption that something will catch fire and one of them will have to handle it. That is fine for a few months. It is corrosive over a year.
Then audit. In any regulated context, separation of duties is not a style preference. It is a regulatory requirement. You cannot write code, approve your own code, and deploy it to a system that handles money or health data. The auditors will not care how good your AI is. They will not care that the model caught the bug your colleague missed. They will look at the commit history and they will see one human approving another human, and that has to actually be two distinct humans with enough context to push back. Two people who agree on everything do not pass that test, because nothing tests it. Three or four people occasionally disagreeing with each other does.
The hype cycle right now is built around the 1-2 person team as a kind of moral fable. Founders post about it. VCs amplify it. There is a real story underneath: AI tooling has genuinely raised the floor of what a small team can do. A pair of strong engineers with good agent tooling can build something in three months that used to take a quarter of effort from ten people. That is real and worth taking seriously.
The story that gets attached to it is not. The version that says headcount is over, that the team of the future is two founders and a fleet of agents, that the 10x engineer has finally arrived. A 10x individual still creates a 1x bus factor. The math on amplification does not change the math on continuity. If the system depends on one person being awake, the system has one point of failure, regardless of how productive that person is when they are awake.
The interesting number, in my experience, is not 1-2 and it is not 8-10. It is 3 or 4. Small enough for AI tooling to amplify without process choking the team. Large enough that someone can take a real vacation, that code review has at least one outsider, that on-call is a rotation rather than a pact between two friends, that an auditor sees more than one decision-maker.
When agents are doing real work, this sharpens. You need at least one human who verified what the agent did and at least one other human with enough context to catch what the first one missed. That is two people minimum just on the verification side. Add the person who actually owns the change, and you are at three before you have anyone available to be on call, take PTO, or be sick. The minimum viable team for AI-assisted production work is structurally larger than the minimum viable team for shipping a prototype, because production work has more dimensions than shipping.
I know how this lands. People will read it as a defense of the old normal, a quiet plea to keep teams at eight to ten. It is not. The old number was driven by overhead I do not want to bring back: meetings to coordinate meetings, planning artifacts that nobody read, a layer of management that existed because the team was too big for one person to keep in their head. AI tooling did make a lot of that overhead optional. The team can be smaller than it used to be, and the smaller team can do more.
Just not two. Two is a startup-pitch number. It is what you put on a slide for an investor who wants to feel like they bought into the future. Two works for the first six months of a product that has not yet had to be boring and reliable for years.
When the team has to keep something alive on a Tuesday afternoon while one engineer is at a funeral and the other is debugging something unrelated, the answer is not better AI. The answer is a third person. Maybe a fourth. People who have seen the system, written part of it, and can pick up the pager without a week of ramp-up. That is the team that does not collapse the first time real life shows up.
AI made one person ship like ten. It did not change how many people it takes to keep the thing alive at 3am.