
By Will Schulz, Founder & CEOPublished
The benchmark that defined software for twenty years was roughly $200,000 to $300,000 in revenue per employee. Good companies beat it. Great companies doubled it. The number was stable enough that investors used it to sanity-check a plan without opening the model. Even now, High Alpha's 2025 benchmarks put the median public software company at about $283,000 per employee.
That benchmark is now describing a world that no longer exists.
One widely cited 2025 tally of the ten leanest AI-native startups found an average of $3.48 million in revenue per employee, on an average team of 24. That is nearly six times the $611,000 average of the ten best traditional SaaS companies in the same comparison, and more than fifteen times the old rule of thumb. The figures for private companies are estimates, but the named cases are hard to argue with. Gamma says it reached $100 million in ARR, profitably, with about 50 employees. Midjourney was reported in 2023 to be making about $200 million a year with roughly 40 staff and no outside funding. Cursor passed $500 million in annualized revenue in mid-2025, up from $300 million just two months earlier. And the story making the rounds this year, of a company crossing $50 million with six full-time staff, is an extreme version of a pattern that is now well documented.
These are not rounding errors at the tail of a distribution. They are the new ceiling, and the ceiling moved by an order of magnitude in about three years.
What actually changed
It is tempting to attribute this to AI writing the code, and that is part of it. In a survey of more than 500 technical leaders published by Anthropic in December 2025, 86% said they deploy AI coding agents for production code, not just experiments. Grindr says AI now writes about 70% of its code and that engineering output has risen 2.5x since July 2025, according to company disclosures reported by the Financial Times.
But coding throughput is the least interesting part of the story. Engineering was never the majority of headcount at a $50 million software company. Support, sales ops, implementation, QA, content, finance ops, and the coordination layer required to keep those functions aligned: that was the headcount. A traditional org chart is mostly an apparatus for moving information between people.
What collapsed is the coordination cost. When a six-person company can run support, onboarding, and billing operations through agents that a single person supervises, the functions that used to require forty people require four. The org chart was never the work. It was the overhead of distributing the work across humans, and a large fraction of that overhead has become optional.
The line item nobody modeled
Here is the part that is genuinely new, and it is showing up in the operating reviews we see this year: for the leanest companies, the token bill can rival payroll.
That is a structurally different business. Payroll is fixed, predictable, and slow to change in either direction. Inference cost is variable, scales with usage, and can move 10x in a month if a customer changes behavior or someone ships a prompt that loops. You have swapped a stable cost base for a volatile one, and most finance functions at small companies have no instrumentation for it. Midjourney is an early example: even at $200 million a year, much of its revenue was reported to go back into compute.
This connects directly to the pricing problem we wrote about in $285 Billion Vanished From SaaS in 48 Hours. If your costs are variable and your revenue is per-seat and fixed, you have built a business that loses money precisely when it succeeds. Lean headcount does not save you from that; it makes the exposure sharper, because there is less fixed margin absorbing the variance.
Where lean actually breaks
We staff founding teams for a living, so we have watched the failure mode up close, and it is consistent enough to describe.
Small teams do not break on throughput. They break on surface area.
A six-person company can ship like a sixty-person company. It cannot be in as many places as a sixty-person company. Enterprise procurement, a SOC 2 audit, a security questionnaire from a bank, a regulated-industry deployment, a partner integration with a quarterly business review attached: each of those consumes a human who must hold context over months. Agents do not yet absorb that work, because the other side of the table is an institution that requires a named, accountable person.
The second failure mode is key-person concentration. At six people, every person is load-bearing. One departure in a critical seat is an existential event, not a hiring problem. Traditional orgs carried redundancy inefficiently but on purpose.
The third is the judgment bottleneck. Agents multiply execution, not discernment. A small team's output is gated by how fast its people can review, decide, and take responsibility. We have watched teams add agent capacity and get slower, because the humans became a review queue. If one person is approving everything, you have built a system whose throughput is one person.
How we staff a company now
Our actual working practice in the studio, as of this quarter:
- Start at three to five, not one. Solo is romantic and fragile. The minimum viable team is the smallest group that survives someone getting sick.
- Hire for judgment, pay for it, and give it leverage. The highest-leverage hire in 2026 is a senior operator who can supervise a fleet of agents across a function. That person replaces a department and costs less than four of the people they replace.
- Staff the surface area, not the throughput. Add humans where an institution needs a counterparty: enterprise sales, compliance, partnerships. Do not add humans to go faster; add agents.
- Instrument tokens as COGS from week one. Per-customer, per-feature. You cannot price what you cannot see, and this is the line item that will surprise you.
- Keep a written list of what the agents handle well, and revise it monthly. The teams that sustain their gains all do this. The boundary moves constantly, and an unexamined division of labor silently becomes wrong.
The honest version
Revenue per employee is a seductive metric because it makes a company look efficient without saying anything about whether the company is good. A business can post $10 million per head and be one competitor away from irrelevance.
What the lean-team era actually changed is not that small companies are better. It is that headcount is no longer evidence of anything. For twenty years, team size was a usable proxy for scale, seriousness, and capability, the same way seats were a usable proxy for software value, right up until they were not.
Both proxies broke for the same reason, in the same cycle. Measure the work.
Sources
- Stealth Agents, Startup Revenue Per Employee Benchmarks 2026, 2026 (citing High Alpha/OpenView 2025 SaaS benchmarks)
- Jeremiah Owyang, AI Startups are Dominating Traditional Software in one Key Metric, May 13, 2025
- SaaSRise, Gamma Hits $100M ARR With 50 Employees, November 2025
- The Decoder, Midjourney generates $200 million in revenue and adds web support with V6, September 6, 2023 (citing The Information)
- TechCrunch, Cursor's Anysphere nabs $9.9B valuation, soars past $500M ARR, June 2025
- Anthropic, How enterprises are building AI agents in 2026, December 9, 2025
- AI Weekly, Grindr CEO Bets on $350 AI Companion Tier as Premium Push Reaches 1.4M Paying Users, August 30, 2026 (citing the Financial Times)



