What breaks at 50 people (and how to fix it before it does)

Hitting 50 employees feels like a milestone. And it is, but it's also the point where the things that got you here start working against you.

Here's what to watch for, and what to do about it.

When growth becomes the problem

Reaching 50 people is a milestone for companies, it means something is genuinely working.

It confirms that the original idea has legs, but the leap from small team to mid-size organisation is also where a startling number of companies begin to show signs of strain from the inside.

This is because processes that worked at 12 people don't always scale to 50. The culture that felt obvious when everyone sat in the same room becomes more difficult.

Decisions that used to take minutes now take weeks, and sometimes good people start leaving

These are predictable problems which can be solved before they become crises, if you know where to look.

In this article, we'll cover the five inflection points that consistently break companies at the 50-person mark, and the practical steps you can take to get ahead of each one.

The founder as bottleneck

In the early days, founders tend to know everything. Every customer, every decision, every reason why the returns policy works the way it does. Ask them anything and you'll get a straight answer in thirty seconds. At ten people, that's invaluable. At fifty, it's a structural problem.

The issue is that the organisation starts depending on one brain to make decisions that fifty people need to take every day. Every question routes through the same person and decisions and approvals take too long.

The moment a founder becomes the team's primary decision-making mechanism, that advantage disappears.

When Airbnb lost 80% of its business in eight weeks at the start of the pandemic, CEO Brian Chesky was forced to confront how the company actually made decisions.

In a widely discussed talk at Y Combinator in 2024, he described how delegating control to professional executives, following conventional wisdom about how to scale, had proved damaging.

His response was to move back towards a more hands-on, founder-led model: staying close to the details, maintaining visibility across the organisation, and keeping final authority on decisions that matter.

It's a compelling model, but it only works because Airbnb has built the systems, cultural clarity, and decision-making frameworks that mean the vast majority of the company's daily decisions never need to reach Chesky at all.

That's the real lesson for founders at 50 people. Founders don’t necessarily have to let go of the big decisions, but they do need to build the infrastructure that stops every other decision from routing through you first.

What to do:

• Start a decision log, a shared document recording not just what was decided and why
• Identify the ten decisions that come to you most often and write down the criteria you use to make them
• Delegate one meaningful decision area per quarter, with clear ownership and a review date

At 50 people, the founder can no longer have all the answers, so they need to build the systems that make the answers accessible without them.

Communication starts to break down

At ten people, communication is easy, and everyone hears roughly the same things, and stays on the same page.

At fifty, you have teams with their own meetings, their own channels, and their own priorities.Key details and events get lost amongst these silos.

The research backs this up. A McKinsey study found that improved internal communication and collaboration can increase productivity by 20–25%.

The inverse is equally true: poor communication is one of the most consistently cited causes of operational failure in scaling companies.

The instinctive response is more meetings. More meetings don't fix structural communication problems, they just move them into rooms.

What actually works is deciding, deliberately, what information should travel to whom, how, and at what frequency.

What to do:

• Establish a weekly all-hands rhythm before silos become entrenched
• Create a single source of truth for company priorities, updated fortnightly
• Give new hires a structured context document in their first week, covering not just role but company history and key decisions

Communication problems should be solved with deliberate, structured information flows, not with more meetings.

Role overlap and the ownership vacuum

Early-stage companies are held together by people who do whatever needs doing.

Roles are often fluid, and so someone in marketing runs the CRM, while someone in ops handles customer complaints.

This adaptability is a genuine strength to a point.

At fifty people, the flexibility that made the team agile starts generating ownership vacuums. Important work falls into the gaps between job descriptions. Two teams both believe they own the same decision and resolve the tension by quietly avoiding it. Or nobody thinks they own it, so nothing happens.

This isn't a character problem. It's a design problem.

"The success of a team depends far less on talent than on the clarity of roles and how well people work together." - organisational psychologist Adam Grant

What to do:

• Run a ‘who owns what’ audit before your next ten hires and map every major outcome to a named team or individual
• Where gaps appear, assign provisional ownership immediately; review after 90 days
• Introduce a lightweight decision framework (RACI or similar) for cross-functional decisions

Role ambiguity becomes worse with every new hire. A simple ownership map can fix these issues early.

Culture drift

Culture at ten people is often easy. It's what founders do, how they treat each other, what they celebrate and what they let slide.

It doesn't need to be written down because everyone is watching it in real time.

At fifty, culture starts to become a story you tell about yourselves, and this can start to drift, as new hires learn culture by watching what gets rewarded, what gets ignored, and what gets punished.

If those signals diverge from the stated values - let’s say the company says it values honesty but people are reluctant to question leadership -then the culture isn't the one anyone signed up for.

What to do:

• Survey new hires at 90 days to see if what they were told is what they're experiencing
• Review whether your internal reward signals (promotions, recognition, performance conversations) match your stated values
• Treat culture maintenance as a leadership deliverable, not an HR initiative

Culture drift is invisible until it's entrenched. The 90-day new hire survey is one of the cheapest and most revealing diagnostic tools available.

When your systems can’t keep up

Most founders are familiar with tech debt, the accumulated cost of shortcuts and quick fixes that will eventually need to be rebuilt properly. The operational equivalent is less talked about but just as damaging.

It's the onboarding process that worked fine for three new hires but buckles at thirty, or the finance approval that lives in someone's inbox.

Collectively, issues such as these can create an organisation where capable people spend significant energy navigating ambiguity rather than doing their actual jobs.

Decisions slow down, errors increase, and new hires take longer to become productive because the knowledge they need exists only in other people's heads.

The trigger to address this is when you reach a certain level, perhaps 30 staff, and realise the systems were never built for that many people.

What to do:

• Audit your highest-friction processes and document those first
• Assign a named owner to each core operational area; documentation without ownership stays unread and quickly goes out of date
• Build a simple new hire context document that captures not just role information but how the company actually works.

The case for setting up a share scheme early

There is one area where the failure to act before 50 people becomes disproportionately costly: equity and shared ownership.

In the early stage, share schemes feel like something to tackle once things settle down.

Things don't always settle down though, and they often become more complicated.

The longer a scheme is deferred, the higher the HMRC valuation, the more crowded the cap table with investor preference, and the longer early employees have been waiting for something that was implied but never delivered.

The evidence is clear. More than nine in ten Vestd customers report that their share scheme has helped their business grow. 95% say it has supported retention.

Companies that posted shared ownership outpaced average UK GDP growth by 2.5 percentage points, according to a Cass/Manchester study.

That culture is significantly easier to build at 20 people than at 80.

At 80, the early hires who helped create the company's value have watched a generation of colleagues join without a stake. The moment to act is before that becomes the norm.

What to do:

• If you have fewer than 500 employees, an Enterprise Management Incentive (EMI) scheme is the most tax-efficient way to share equity with your team.
• Get an HMRC-agreed valuation locked in before your next funding round, when the company's value will be higher
• Use a digital cap table from day one; the administrative cost of cleaning up a spreadsheet-based cap table at Series A is invariably higher than the cost of doing it properly from the start

What to do now, even if you're already past 50

If you recognise your company in any of the above, start small. Pick the one inflection point causing the most damage right now and fix that first.

• Communication breakdown? Start the all-hands this week.
• Role ambiguity? Run the ownership audit before your next team meeting.
• Cap table in a spreadsheet? Fix it before the next funding conversation starts.

Most of these problems are not expensive to fix, but they are expensive to ignore. A company that addresses structural fragility at 50 people buys itself the stability to grow to 150.

One that defers until something breaks will spend its 150-person stage cleaning up the mess instead of building the business.

The inflection point isn't a threat. It's a prompt.

The companies that treat it as one are the ones still standing at the next one.

Vestd makes it straightforward to set up a structured share scheme, maintain a real-time cap table, and give your team genuine ownership, with the tools to manage it as you scale. Book a call to find out more.