3 December 2025
Lean Teams Beat Incumbents: Stop Hiring Ahead of Growth
Headcount used to be a proxy for momentum. I think it’s now closer to a proxy for inefficiency, and boards need to stop rewarding it.
Key takeaways
- Small AI-leveraged teams are genuinely outcompeting larger incumbents
- Headcount growth is no longer a reliable signal of company momentum
- Founders shouldn’t have to justify staying lean, they should justify hiring
- AI leverage changes the default operating posture for early teams
- Boards should ask what a new hire replaces, not just what they add
I’ve built and exited two companies, Obby and Baluu, in eras with very different hiring norms, and I now run FirstMotion deliberately lean while advising other founders through VAQA on exactly this question. I’ve watched the “hire ahead of growth” playbook get treated as gospel for years, even when it quietly destroyed margin and slowed decision-making. This piece explains why I think that playbook is now actively dangerous advice for most early-stage founders, and what should replace it.
Why “hire ahead of growth” made sense once
The old logic wasn’t stupid. If you believed demand was coming, you staffed up early so you weren’t scrambling when it arrived, and a growing headcount chart was a legible signal to a board or investor that the company was scaling.
That logic depended on one assumption holding true: that output scaled roughly linearly with people. For a lot of functions, for a long time, it did.
Why that assumption has broken down
I don’t think that assumption holds anymore, at least not for the functions where AI tools have matured fastest: content, customer support, coding, research, and a growing slice of operations.
Small teams using AI tools well can now produce output that used to require several times the headcount. That’s not a marginal efficiency gain, it’s a structural shift in what a lean team is capable of. And it’s not theoretical. There are startups running with five or six people that are shipping product, generating revenue, and taking market share from incumbents carrying ten times the headcount.
I see this directly through FirstMotion, where a small team running AI-augmented workflows produces output that would have needed a much larger agency structure even three years ago. That’s not a boast, it’s just the operating reality now, and I think founders who haven’t updated their hiring assumptions accordingly are leaving margin and speed on the table.
What headcount actually signals now
I think a growing headcount used to say “this company is gaining momentum.” Increasingly, I think it says “this company hasn’t rebuilt its processes around what AI tools can now do.”
That’s a harsh way to put it, but I’d rather be direct about it than let founders keep hiring on autopilot because that’s what “scaling” has always looked like.
Here’s how I’d reframe the signal for a board:
| Old signal | What it actually indicated | Better question to ask |
|---|---|---|
| Headcount growth | Momentum and scaling | Has output per person grown faster than headcount |
| Large team for a function | Serious investment in that area | Could half the team, with better tooling, do the same job |
| Fast hiring pace | Confidence in demand | Is hiring solving a real bottleneck or a comfort instinct |
| Org chart depth | Maturity | Does depth add speed, or add approval layers |
None of this means never hire. It means hiring should be the exception a founder consciously justifies, not the default posture a board expects to see.
The new default: lean until proven otherwise
I think the operating posture for most early-stage companies right now should flip. Instead of hiring ahead of growth and justifying restraint, founders should default to lean and justify each hire against a specific, AI-tooling-adjusted bottleneck.
That means asking, before every hire: what specifically can this person do that current tooling and existing team capacity genuinely cannot? If the honest answer is “speed up something we could eventually do slower with better process,” that’s not always a good enough reason anymore.
This is uncomfortable for a lot of founders, because headcount has been such a visible, easy-to-communicate signal of progress for so long. A lean team requires a different kind of story for investors and boards, one built on output and margin rather than org chart size.
What this means for boards evaluating startups
If you’re on a board or advising founders, I think the questions worth asking have changed.
- What’s the output per employee trend, not just the headcount trend?
- Which functions have been rebuilt around AI tooling, and which haven’t?
- When a hire is proposed, what specifically can’t current tooling solve?
- Is the team lean because of discipline, or because of underinvestment?
That last question matters. There’s a real difference between deliberate leanness backed by strong tooling, and leanness that’s actually just under-resourcing dressed up as efficiency. A good board should be able to tell the difference by asking about process, not just headcount.
Where incumbents are exposed
Larger, incumbent competitors are often the most exposed here, not because they lack resources, but because organisational inertia makes it hard to rebuild processes around new tooling quickly. A team of six with no legacy process to unwind can adopt AI-native workflows from day one. A team of 60 has approval chains, legacy tooling, and internal politics to work through first.
That’s the real competitive threat lean startups pose right now. It’s not that they’re smarter or working harder. It’s that they have less to unlearn.
Why lean should be the default posture, not the exception
I think the founders who win the next few years won’t be the ones who hired fastest. They’ll be the ones who stayed lean longest while output kept climbing, and who could clearly explain to a board exactly why each hire, when it came, was necessary.
That’s a genuinely different operating philosophy from the one most of us were trained on, myself included, in earlier company-building eras. But the evidence, from six-person startups genuinely beating well-resourced incumbents, is hard to ignore.
Hiring ahead of growth was a reasonable bet when output scaled with people. It’s a much riskier bet now that it often doesn’t.
Where this fits into operational efficiency and growth advisory
This shift in hiring posture is a recurring theme in the Operational Efficiency and Growth advisory work I do through VAQA, particularly with founders under pressure from investors to “scale the team.” If you want a second opinion on whether your next hire is solving a real bottleneck or just following an old playbook, get in touch. You can also read more on what I advise on.
Frequently Asked Questions
Does this mean startups should never hire?
No, it means hiring should be justified against a specific bottleneck that current tooling and existing capacity genuinely can’t solve, rather than treated as the default response to growth.
How can a six-person team really outcompete a much larger incumbent?
Small teams using AI tools well can produce output that used to require significantly more headcount, particularly in content, support, coding, and operations, while incumbents are often slowed by legacy process they have to unwind first.
How should a board evaluate whether a startup’s lean headcount is a strength or a risk?
Ask about output per person trends and which functions have been rebuilt around AI tooling, rather than judging leanness by headcount alone; genuine discipline looks different from simple under-resourcing once you ask about process.
Is this relevant outside of tech and SaaS companies?
The pattern is clearest in tech and SaaS right now because AI tooling has matured fastest there, but the underlying principle, that output no longer scales linearly with headcount, is starting to apply more broadly.
How does VAQA help founders think through hiring decisions?
Through the Operational Efficiency and Growth advisory pillars, I work directly with founders on stress-testing hiring plans against actual bottlenecks, which often surfaces hires that aren’t as necessary as they first appeared.
Tom Batting is a Forbes 30 Under 30 entrepreneur, founder of Obby and Baluu, and founder of FirstMotion. He advises founders and leadership teams through VAQA.