I've watched this pattern from the inside, running teams and advising founders through exactly this stage, and I'll say it plainly: the thing that takes down a fast-growing business is almost never the market. In my experience, why scaling companies stall comes down to coordination: growth adds people faster than it adds the structure that lets those people work together, so the cost of every decision rises while revenue still climbs. Hiring adds capacity. Only structure adds throughput, and a company that confuses the two ends up bigger, slower and more expensive than the business it was a year ago.
Complexity arrives disguised as success. New clients, bigger contracts, a team finally large enough to matter. Then the meeting that took twenty minutes takes an hour, because five more people now need to be in the room to make the same decision. A customer request that used to be answered the same day bounces between three departments before anyone owns it. None of this appears on a profit and loss statement until it is already expensive, and none of it reads as crisis. It reads as busy.
Why scaling companies stall as coordination outgrows structure
The research points inwards. Bain & Company's five-year study of 8,000 companies found that 85 percent of the barriers to profitable growth for the average company are internal and manageable, rising to 94 percent for the largest. Bain's conclusion was that failing to overcome those internal factors would cause two out of every three companies to stall, be acquired or disappear within 15 years. The market was rarely the thing that stopped them. The organisation was.
The mechanism is easy to see once you look for it. Every person you add brings their own output and also a new set of communication lines, handoffs and places for work to be dropped. Rob Cross, Reb Rebele and Adam Grant, writing in Harvard Business Review, reported from two decades of their own data that the time managers and employees spend in collaborative activities has ballooned by 50 percent or more. That figure comes from the authors' own data, not a census of every workplace, but it matches what leaders describe: more of the day goes on coordinating the work than doing it.
The people who absorb that load are managers, and managers are where the pressure shows first. Gallup's 2026 State of the Global Workplace report found manager engagement fell from 27% to 22% between 2024 and 2025, which the report describes as the largest year-over-year drop in manager engagement. When the layer that holds the handoffs together is running out of energy, a stalling company has the symptoms before it has the diagnosis.
The complexity tax is invisible until margins move
I call the cost the complexity tax. Nobody budgets for it and nobody names it in the board deck, yet it is the most reliable profitability drain I see in growth-stage companies. It shows up as rework nobody flagged, decisions made twice by two different teams, and good people burning out holding together a structure that was never designed, only accumulated.
It also arrives as a subscription rather than a single bill. In the first quarter it costs a little speed. In the second it costs a good hire who tired of internal politics just to ship something. By the fourth quarter it is costing customers, because the sprawl that slows internal decisions eventually slows the ones that touch the people paying you. Leaders who catch it in the first quarter are fixing a process problem. Leaders who catch it in the fourth are fixing a culture problem, and those take years to unwind.
There is a trust cost too. As teams grow past the size where everyone can see what everyone else is doing, leaders add checkpoints: another approval, another status meeting, another sign-off. Each looks reasonable alone. Stacked together they build a system where nothing moves until someone senior clears it, which makes the senior people the bottleneck for everything. That is the opposite of what the hiring was meant to solve.
How I evaluate a growth-stage business
- Coordination cost, not headcount: I do not ask how many people you have. Count the approvals needed to ship a decision. If that number rises faster than revenue, you are accumulating debt, not capability.
- Who owns the handoff: Most breakdowns happen in the gap between teams, not inside one. I map every handoff before I look at any individual's performance.
- Systems before people: If the answer to every new problem is 'hire someone', the system is the issue, not the headcount. I look for where a process should absorb the next unit of growth.
- Trust as infrastructure: Low-trust teams route everything through a manager, which caps throughput at one person's attention. High-trust teams route decisions to whoever is closest to the information. That is a structural choice, not a personality trait.
- What breaks first under double the load: Imagine doubling revenue with no new hires. Whatever breaks first is the real constraint, and it is rarely the one you are staffing against today.
Run that framework as a one-hour exercise with your leadership team before the next hiring round. Ask each person to count the approvals behind the last three decisions they shipped, name the handoff that cost the most time, and say what they would stop hiring for if the system could absorb it. The answers rarely match, and the mismatch is itself the finding: a leadership team that cannot agree on how a decision gets made cannot scale the way it makes them.
Reading a stall through the five structural pillars
When I diagnose a stall I work from the Five Structural Pillars of my Leadership Capability Architecture, the five systemic patterns the free Leadership Capability Diagnostic scores. Each pillar has a characteristic way of failing under growth, and the failure is usually visible long before revenue turns.
- Alignment System: Three departments pursue three versions of the same priority, and the number of meetings needed to reconcile them keeps rising.
- Leadership Identity System: Managers still behave like the best individual contributor on the team, so work escalates upwards instead of being led.
- Execution Cadence System: Decisions get made twice, rework is routine, and nobody can say when a given type of decision is supposed to be taken.
- Capability Pathways: Every new problem is answered with a hire, because nobody was ever prepared to take it on from inside.
- Cultural Reinforcement System: Workarounds and heroics are rewarded, so the improvised habits of the early days harden into the way things are done.
You do not need all five to fail for a company to stall. One is enough, and it is usually the one the leadership team has stopped being able to see because they built it.
Decouple output from headcount before you hire
The alternative to hiring your way through complexity is not doing more with less. It is decoupling output from headcount: building systems, decision rights and rhythms sturdy enough that adding a customer does not automatically mean adding a person. Some hiring will always be needed. I am not arguing for a freeze. I am arguing that hiring should be the last lever you pull rather than the first, and that you should pull it into a structure that can absorb the new person.
'Systems' is the word that gets hollowed out fastest in leadership conversations, so I try to be specific. It does not mean a new piece of software. It means clear decision rights: who can say yes without asking, and at what threshold a decision moves up a level. It means documented judgement as well as documented process, the reasoning behind a call so the next person does not have to re-argue it. And it means designing for absence. Could this function survive you, or your best operator, being unreachable for two weeks? If the honest answer is no, you do not have a system. You have a dependency dressed as one.
My Work With Me page publishes a telecommunications case that shows the pattern in numbers. The company was founder-dependent at $15M, every operational decision escalated to the CEO, and growth had stalled. The work installed decision rights and a leadership maturity framework. The page reports that operational decisions were fully delegated within 90 days, the founder freed 20 or more hours a week for strategic work, and the company reached $30M within 18 months. I cite it because it is the same stall described above and the lever was structural, not another hire. For founders in that position, the Founder Bottleneck Challenge is a practical place to start.
When this is right, something changes in how leadership spends its time. You stop resolving every escalation and start designing the conditions under which escalations rarely happen. The distinction is harder than it sounds, because it separates a business that scales from one that gets bigger and slower at the same time. Fix the system that will carry the next stage of growth before you are forced to fix it under pressure, because redesigning mid-crisis costs a multiple of doing the same work calmly six months earlier.
Bigger is not the same as stronger
Growth and strength are different metrics, and most leaders measure only the first. Revenue can climb for years while the organisation underneath becomes more fragile, more dependent on heroics, one resignation away from a very bad quarter. The companies I respect most did not avoid this wall. Everyone hits it. They treated hitting it as information, stepped back from the fire-fighting long enough to redesign what was actually broken, and came out leaner in structure even as they grew larger in revenue.
So the question I would put to any leadership team goes further than how to handle more: what would have to be true for this to run without adding headcount at the same rate? Asked early and often, that question separates growth that compounds from growth that eventually compounds against you. Growth does not kill scaling companies. Unmanaged complexity does, and it does so by making every decision a little more expensive each quarter until the business can no longer afford to move.
If you want to see where your own system is thinnest, start with the free Diagnostic. If you want to test a specific growth decision against my methodology, CapabilityAI, my AI leadership coach, is built on it, and when the stall is already costing you, the Scaling Leadership Ecosystem is the 90-day route to installing the structure.