This case is a pattern composite, not a real client. It is assembled from operator threads, the research summarised in the sources block, and the patterns that recur across consulting work with services firms in the growth band.
I’ll call the founder Paul. In early 2024 he ran a 35-person services firm that had been growing steadily for four years. Demand was strong. The team was respected in its niche. By autumn 2025, eighteen months later, the firm was a little under seventy people. Hiring had been driven by client commitments, signed before the team to deliver them was in place, and Paul had been quietly proud of how fast the firm was scaling. Then, over a single fortnight in October, three things landed on his desk that he hadn’t been expecting.
Delivery cycle times had grown by about thirty percent against the pre-doubling baseline. Quality complaints from clients were running higher than they had at 35 staff, despite the larger team. And two of the three senior leaders he had built the firm with had quietly disengaged, with one already in conversations elsewhere. Paul went into a long weekend believing the firm had a culture problem. It didn’t. It had an infrastructure problem hiding inside a culture conversation, and the conversation had been holding the wrong question open for eight months.
Why does doubling a services firm so often slow it down?
When a services firm doubles in size, the management infrastructure has to be doubled with it, and almost no firm does the second piece deliberately. Hiring decisions look fine in isolation, none of them is obviously wrong on the day, and the slowdown shows up six to twelve months later when the absence of structure starts to compound.
The compounding works in three layers. New first-line managers are promoted from delivery without training or scaffolding, and they fail in predictable, identifiable ways. New senior hires arrive with implicit expectations the firm hasn’t named, and they default to whatever they observed at their last firm. The leadership team grows from a small group with shared history to a larger group that has neither, and peer accountability stops working without anyone deciding to stop.
The reason the load is hard to see is that it arrives slowly. Each new hire generates a small increment of management overhead. None of it is dramatic on its own. By the time the cumulative load is visible in cycle times and quality complaints, the firm has spent six to twelve months in a slowdown that didn’t have to happen.
What did the predictable management failures actually look like at the firm?
The failures fell into three layers. Three new first-line managers were promoted from senior delivery in the first six months of doubling, and two of them introduced fear-driven over-control inside their first ninety days. Daily activity reports. Escalation requirements for routine decisions. Blanket policies in response to a single underperformer. One of the original team members quietly started job-hunting because the new manager had become an obstacle.
None of the senior leaders saw this until month four, by which point it had already cost the firm a strong delivery lead.
The Head of Delivery brought in from a hundred-person firm settled into the role and ran it competently as a senior employee. Paul had been expecting a mini-founder: decisions made under ambiguity, emotional weight absorbed, mission belief in the firm’s bet on its niche. Six months in, Paul was privately disappointed. The hire was privately confused. Both of them blamed the relationship. Neither of them said the unspoken expectation aloud, because Paul hadn’t named it on the way in, and the hire had no scaffolding for asking.
The leadership team expansion from three to six was the third predictable failure. The original three-person team had operated through trust and shared history. The new six-person team had neither yet, and peer accountability had never been explicitly installed. Decisions made in meetings weren’t followed up because nobody felt it was their place to challenge a colleague. Paul became the only enforcer, again, and the leadership team became a status meeting.
Each of these failures was predictable. Each followed a pattern that recurs in firms doubling through fifty staff. The first-line manager fear cluster, documented in operator-led practitioner work. The senior-hire mini-founder mismatch, named explicitly in early-hire research. The leadership-team accountability gap, framed in standard team-effectiveness literature. None of them are individual failures; they are structural failures dressed up as personnel issues. Treating them as personnel issues makes the situation worse, because the next person hired into the same structure produces the same pattern.
Why did Paul read this as a culture problem for so long?
The culture framing felt emotionally accurate to Paul, and that was why it stuck. Newer hires didn’t show the same urgency as the original team. The natural fix in his head was a culture programme: values workshops, an away day, more frequent all-hands, perhaps an external diagnostic. So he commissioned one in October 2025, and the scores came back respectable on safety and transparency.
None of it changed anything material in cycle times or in the senior team’s quiet stepping-back.
The culture framing is sticky because it is emotionally accurate. The firm did feel different at seventy than it had at thirty-five. The newer team members did seem less invested. The senior leaders who were stepping back were less visible than they used to be. Each observation was true. The diagnosis they pointed at, that this was a culture problem, was the wrong one. The infrastructure question, what is the management scaffolding a seventy-person firm needs that a thirty-five-person firm did not, never came up in the diagnostic and never came up in the away day.
The honest read landed in a second conversation. A consultant who had worked with the firm on the early team came in to look at what had changed. After a week of conversations across the layers, his read was that the new managers had no maps, the new senior hires had implicit role descriptions that did not match what Paul wanted, and the leadership team had stopped functioning as a team because nobody had explicitly said how it should function at six. That conversation was uncomfortable because it reframed Paul’s instinct. The fix was the boring structural work of writing down what each role was, where authority sat, and what the leadership team had agreed to hold itself to.
What three structural moves actually unblocked it?
The unblock ran in three moves over six months. One: write down what each role’s authority and version of “good” looked like, jointly with the role-holder. Two: install weekly thirty-minute check-ins with each new first-line manager for ninety days, with the brief to reset early on concerning patterns. Three: run a four-question accountability framework with the leadership team.
The role-clarity work was the foundation. For each new senior hire and each new first-line manager, Paul sat down for a one-hour session with the role-holder. Together they wrote what decisions sat with the role, what came to Paul, what good looked like, and what would tell them the role wasn’t working. The output was a one-page document per role. Several of the new hires had been waiting for that conversation since week two and were visibly relieved when it arrived; one of them said he had been operating on guesswork for six months.
The first-line manager check-ins ran weekly for ninety days. The format was deliberately small: thirty minutes, the manager bringing the situations they were uncertain about, the senior leader giving feedback on patterns. Two of the over-control behaviours were named and reversed inside the first three sessions. The third manager turned out to be a strong fit once the daily reporting reflex was pulled back.
The leadership team accountability work was the most uncomfortable of the three. The team agreed the four questions in one focused half-day session. Paul went first by reporting against his own commitments at the next meeting, with specificity, and absorbing the feedback in front of the team. The other five followed within two meetings. By month six, the leadership meetings produced decisions that consistently got actioned, and Paul was no longer the only person enforcing follow-through.
What does this mean for your firm if you’re inside the doubling arc?
If you are inside the doubling arc and seeing the symptoms, the work is structural rather than cultural and the order of moves matters. At Paul’s firm, by month nine the cycle times had recovered and were running ten percent faster than the pre-doubling baseline. Quality complaints had dropped by more than half. One of the two disengaged senior leaders re-engaged; the other left cleanly.
The lesson Paul named afterwards, when we walked back through the eighteen months, was that doubling headcount doubles the load on the leadership infrastructure, and that nobody had given him that sentence at the start. The load arrives slowly, in small signals that look like personnel issues. By the time it is loud enough to act on, the firm has spent six to twelve months in a state that didn’t have to happen, and the founder has spent the same period attaching the symptoms to the wrong cause.
If your firm has grown significantly in the last eighteen months and you can name some of the symptoms in this case in your own team, the order of moves matters and the work isn’t the kind of thing a culture programme will reach. Book a conversation.
