Growing Pains at 50 Employees: What Breaks Between 20 and 60 People, and What to Put in Place
The growing pains of scaling a business to around 50 employees come from one change that founders rarely notice until it has already happened, which is that the business has outgrown the founder's ability to hold it in their head. Communication, management, delivery and finance all wobble at once, because each was quietly running on the founder knowing everyone and approving everything, and the fix is to replace that informal glue with deliberate structure before the cracks become client-visible.
What follows walks through each of those four areas in turn, describes what typically breaks and why, and sets out what to put in place, framed against the two stages most firms of this size sit between: Build, where the founder holds the business together, and Scale, where the business starts to hold itself together.
Why 50 employees is where scaling pains concentrate
At 15 or 20 people a founder-led firm runs on proximity, because everyone hears the important conversations, the founder sees most client work before it goes out, and problems surface at someone's desk long before they reach a spreadsheet. Somewhere between 30 and 60 people that proximity disappears, and it does so gradually enough that nothing announces it, so the founder keeps operating as if it still exists.
The symptoms then arrive in an order that is easy to misread, since a missed deadline looks like a delivery problem, a disappointing month looks like a sales problem and a resignation looks like a people problem, when all three are frequently the same structural gap showing up in different places.
Rule of thumb: if a process only works because the founder is watching it, that process has not scaled, and the larger the team becomes the more expensive that hidden dependency gets.
Build or Scale: recognising your stage
In the Build stage the founder is the operating model, which is entirely appropriate for a small firm, because decisions are fast, quality is personally assured and the overhead of formal structure would cost more than it saved. The trouble starts when a business that has grown to Scale-stage headcount is still run with Build-stage habits, which is the most common source of the wobble founders describe.
A firm has genuinely reached the Scale stage when a few things are true at once: there are managers who make real decisions without checking upwards, delivery follows a recognisable method rather than the habits of whichever senior person is leading, and the leadership team can see the numbers that matter without asking finance to pull them together by hand. If most of those are not yet true, you are still in Build, whatever the headcount says, and the next move is to close that gap deliberately.
Communication: when the founder stops being the network
What breaks
In a small firm the founder acts as the routing layer for information, so priorities, client news and changes of direction travel through one person who knows who needs to hear them. As the team grows that routing layer becomes a bottleneck, so people learn about decisions late or second-hand, teams start making contradictory assumptions, and the founder spends more and more of each week repeating the same context in different rooms.
What to put in place
The answer is not more meetings but a deliberate cadence in which each forum has a clear purpose, a fixed membership and an output that travels onwards, typically a weekly leadership meeting that makes decisions, a short team-level rhythm that turns those decisions into work, and a monthly or quarterly review that looks at direction rather than tasks. A format such as this weekly leadership meeting agenda is a reasonable place to start, provided you hold to it long enough for the habit to become embedded.
Management layers: the first-time manager problem
What breaks
Most firms of this size promote their best practitioners into management, which is sensible, but those new managers are rarely given clear authority, so they carry the title while the founder continues to approve hires, settle client disputes and decide who works on what. The result is a layer of people who are accountable for outcomes they cannot control, and a founder who is busier than before rather than less busy.
What to put in place
The fix is to write down decision rights explicitly, setting out which decisions sit with managers, which need a second opinion and which stay with the founder, and then to honour that list even when it is tempting to step back in. Pair it with a small amount of genuine management development, because people who were promoted for their technical skill need help with resourcing conversations, performance issues and the difficult conversation they have been avoiding.
A manager without decision rights is not a management layer, only a longer route to the founder.
Delivery: from heroics to a repeatable method
What breaks
Delivery in the Build stage tends to depend on a handful of senior people who know how to rescue a project, and that works until there are more live projects than heroes. Quality becomes inconsistent across teams, estimates drift, scope creeps without being recorded, and clients begin to notice that the experience depends heavily on who they happen to get.
What to put in place
A Scale-stage firm needs a defined delivery method covering how work is scoped, kicked off, tracked, changed and closed, with change control that is used rather than admired, and a simple view of capacity that links people to pipeline before a lumpy quarter creates either a bench or an overload. The aim is not a thick process manual but three or four standards that, once they hold, make delivery predictable regardless of which team is running the work, and the guide to capacity planning for professional services covers that side in more depth.
Finance: when the numbers arrive too late to act on
What breaks
Small firms often run finance as a compliance function, so the accounts are accurate but backward-looking, and the founder steers by bank balance and instinct. At 50 people that is no longer enough, because margin can erode project by project for months before it shows in the monthly figures, and by then the work that caused it has finished.
What to put in place
Put in place a short set of forward-looking measures that the leadership team reviews every month, typically utilisation, project margin against estimate, pipeline coverage for the coming quarter and cash forecast, and make sure each one has an owner who can explain movement in it. Measure profitability at project level rather than only across the whole firm, because that is where the margin is actually won or lost.
A quick self-test: if you could not tell, today, which of your current projects is losing money, your finance function is still built for the Build stage.
The order to tackle the growing pains
Trying to fix all four areas at once usually fixes none of them, so the sensible sequence for most firms is to settle decision rights and leadership cadence first, because every other change depends on there being somewhere for decisions to be made, then to standardise delivery, and then to build the financial visibility that tells you whether the changes are holding. Each step should be finished, in the sense that it runs without the founder pushing it, before the next becomes the main focus.
Where Vitori fits
Some founders work through this transition themselves, and some do it with a good operations hire or a strong non-executive director, so the steps above are worth taking whether with Vitori or anyone else. Vitori works inside the leadership team of firms of roughly 20 to 60 people, using its Operational Scale Framework to assess Growth, Delivery and Operations across the Build, Scale, Operate and Enterprise stages, then implementing the changes itself and staying accountable until they hold, sometimes as fractional COO support. Engagements start by agreeing the outcomes and then the timescale, rather than an open-ended retainer, and if that sounds like the right shape you can get in touch with Vitori to talk it through. The goal is a business that runs, and scales, without the founder in every decision.
Common questions about growing pains at 50 employees
Should I hire an operations director when the business reaches 50 people?
Hiring an operations director at 50 people can help, but only once decision rights are clear enough for that person to hold real authority. A senior operations hire brought into a business where the founder still approves everything tends to become an expensive coordinator, so clarify which decisions move to the role before recruiting, and the hire is far more likely to succeed.
Is it normal for profit to fall as a services firm grows past 40 people?
Falling margin as a services firm grows past 40 people is a common pattern, because management overhead rises before the structures that make that overhead productive are in place. It is not inevitable, though, and project-level profitability tracking, consistent change control and capacity planning linked to pipeline usually show where the margin is going and allow the firm to recover it.
How long does it take to move from the Build stage to the Scale stage?
Moving from the Build stage to the Scale stage depends on the starting point, the founder's willingness to hand over decisions and how many areas need work at once. It is better measured in quarters than weeks, because each change has to be embedded and running without the founder pushing it before the firm can reasonably claim to have moved stage.
Related: Scaling Consultant vs Business Coach: Which Does a Founder-Led Firm of 20 to 60 People Need?
