No founder sets out to have people problems. They grow into them. And in our experience the same cracks appear at roughly the same sizes, in almost every business we work with.

The numbers below are not exact. Some companies hit the 50-person wall at 35, others at 70. But the pattern is consistent enough that it is worth knowing which stage you are approaching, because the cheapest time to fix a breaking point is before you reach it.

Around 10 people: the founder is the HR department

At this size everything lives in someone's head or inbox. Contracts are adapted from a template found online. Holiday is tracked in a spreadsheet, if at all. It mostly works, because everyone can talk to everyone.

What breaks first is usually the paperwork nobody noticed was missing. Every employee is legally entitled to a written statement of their main terms on their first day, not at the end of probation. And once you have five or more employees, your health and safety policy has to be written down and shared.

The first difficult conversation is the other early test. A performance issue or a sickness absence handled informally can turn into a dispute very quickly when there is no process to point to.

Build before you need it: proper contracts and written statements, a short handbook covering the policies you actually use, one secure place for employee records, and a simple onboarding checklist.

Around 50 people: managers appear

Somewhere between 30 and 60 people, the founder stops being able to see everyone. A layer of managers appears, often people promoted because they were good at their job, not because they had managed before.

This is where inconsistency sets in. Two managers handle the same situation in two different ways. Pay rises are agreed in one-to-one conversations with no framework behind them. The first formal grievance arrives and nobody is sure what the process is.

None of this is anyone's fault. It is simply the point where informal ways of working stop scaling.

Build before you need it: clear processes for absence, performance and disciplinary matters; basic training for new managers; a simple pay framework, even if it is only bands; and an HR system to replace the spreadsheets.

Around 150 people: nobody knows everyone any more

At this size people stop knowing every colleague by name. Culture now runs on systems rather than relationships, and gaps that were invisible at 50 become expensive.

The most common symptom we see is leadership being unable to answer basic questions quickly. How many people do we employ, by team? What is our attrition? What does our workforce actually cost? If the answers take a week and three spreadsheets, decisions are being made without them.

This is also when many businesses face their first restructure. If you propose 20 or more redundancies at one establishment within 90 days, formal collective consultation rules apply, with a minimum of 30 days before the first dismissal. Businesses that have never planned for this tend to discover it late.

Build before you need it: reliable people data and a monthly report leadership trusts, a consistent performance cycle, workforce planning linked to the budget, and a clear way of managing change.

Around 250 to 300 people: the obligations of a large employer arrive

Once you have 250 or more employees on 5 April, you must publish your gender pay gap each year. From April 2027, private sector employers in scope will also need to publish an action plan alongside it. Expectations from investors, clients and candidates rise at the same time.

The risk here is different. HR can turn into an administration factory, with a growing team processing requests rather than shaping how the organisation works.

Build before you need it: a lean operating model with clear ownership of each people process, proper governance of policies, self-service for routine requests, and a regular reporting rhythm with leadership.

Build for the next stage, not the current one

You do not need a 300-person HR function at 30 people. That would be expensive and slow you down. What you need is the foundation for the next breaking point, built before you reach it.

A useful rule of thumb: look at the stage above you and ask which of those problems you can already see starting. That is usually where the work should begin.