I've scaled three companies past the 100-person mark. Every one of them nearly broke at the same inflection points. Not because the product failed or the market disappeared, but because the organisation itself couldn't keep up with its own growth.
What You Need to Know
- Companies hit predictable breaking points at roughly 15, 50, and 150 people. Each one demands a fundamentally different operating model
- Culture doesn't scale by accident. If you don't codify it early, growth will replace it with something you don't recognise
- The founder's instinct to stay close to every decision is the single biggest bottleneck past 50 people
- Hiring for the company you are today, rather than the company you're becoming, creates a talent mismatch that compounds quarterly
- Operational maturity isn't glamorous. It's the thing that separates companies that survive scaling from companies that implode during it
60%
of high-growth companies experience a significant cultural or operational crisis between 50 and 200 employees
Source: Harvard Business Review, Scaling Up Without Cracking Up, 2019
The Three Breaking Points
Ten to Fifty: When You Lose Line of Sight
At ten people, you know everything. Every customer conversation, every product decision, every hire. Communication is ambient. You overhear things. Problems surface naturally because everyone is in the same room, physically or virtually.
Somewhere around 30 people, that breaks. I remember the moment at Sealcorp when I realised I hadn't spoken to two team members in over a fortnight. Not because I was avoiding them, but because the organisation had grown past the point where informal communication covered everything.
This is where founders make their first mistake: they try to stay involved in everything. I did it myself. I'd attend every meeting, review every proposal, approve every hire. It felt like diligence. It was actually a bottleneck.
The fix is simple to describe and painful to execute. You have to build systems that replace your personal attention. Documented processes. Clear decision rights. Regular reporting cadences. None of it feels as good as just knowing what's happening. But it's the only way through.
Fifty to a Hundred: When Culture Becomes Fragile
At fifty people, you still have most of the original team. They carry the culture implicitly. They know how things are done because they were there when those norms formed.
At a hundred, you've hired fifty people who weren't there. They bring their own assumptions about how work should happen. And unless you've been explicit about your culture, their assumptions will gradually replace yours.
I watched this happen during Sealcorp's growth phase. We'd built a culture of direct communication, of challenging ideas regardless of seniority. But as we hired experienced people from larger, more hierarchical organisations, they brought different instincts. Meetings became more formal. Dissent became quieter. And the speed we'd built the company on started to slow.
You can't hire fifty people in a year and expect them to absorb your culture by osmosis. Culture at scale is a deliberate practice, not a side effect.
Mike Ridgway
Technology Growth Advisory
The solution isn't a values poster in the kitchen. It's structural. How you run meetings, how you make decisions, how you handle disagreement, how you promote. These systems either reinforce your culture or undermine it. There's no neutral.
A Hundred to Two Hundred: When Everything Gets Tested
This is where I've seen the most casualties. The company is big enough to have real complexity but often hasn't built the management layer to handle it.
At Flintfox, scaling past a hundred meant dealing with multiple geographies, multiple product lines, and multiple customer segments simultaneously. The coordination overhead alone could consume your entire leadership team if you let it.
70%
of organisational change efforts fail, primarily due to management behaviour and employee resistance
Source: McKinsey & Company, The Irrational Side of Change Management, 2009
What I learned, painfully, is that this phase requires a different kind of leader than the first two. The scrappy generalists who built the company from nothing often struggle in a world that demands specialisation, process, and delegation. That's not a criticism. It's a recognition that different stages need different skills.
What Actually Matters
Looking back across thirty years of scaling companies, three things stand out.
Hire ahead of the curve. The person you need at 150 people should be hired at 100. If you wait until the pain is acute, you're already six months behind. This means paying for capacity you don't fully utilise yet. It feels wasteful. It's not.
Make culture explicit early. Write down how you work. Not aspirational values, but actual operating norms. How do we make decisions? How do we handle conflict? What does good performance look like? Do this at 20 people, not 100.
Accept that your role changes. The CEO of a 200-person company does a fundamentally different job than the founder of a 10-person startup. Some founders make that transition. Many don't. And there's no shame in recognising that building a thing and running the thing it becomes are different skills.
The companies that scale well aren't the ones with the best product or the most funding. They're the ones that rebuild themselves at each inflection point, keeping what made them special while building the systems that growth demands.
That's harder than it sounds. But it's the job.