top of page

Scaling from 40 to 130 People: What Breaks First

  • Mar 4
  • 3 min read

Updated: Mar 4

Why decision infrastructure - not technology or headcount - is the silent constraint on platform growth.


Over the years, headcount grew from 40 to 130, across three continents, multiple geographies, and two ownership structures.


And I nearly missed what was actually breaking underneath it.


Not the technology. Not the budget. The accountability design.


Proximity Masks the Gaps

At 40 people under one roof, you can get away with informal governance. Proximity does the work. Alignment happens in hallways, accountability is visible and the CEO is the connective tissue holding decisions together.


The problem is that model scales invisibly. You add people, layers, geographies and it still feels like it's working. Teams are executing. Revenue is growing. The dashboard looks fine.


Until one day you realize that three teams all think they own the same process. A critical decision has been sitting unresolved for six weeks. Every meaningful escalation is landing on your desk, not because people are incapable, but because ownership was never clearly assigned at the new scale.


By the time that's visible in the numbers, it's already expensive.


What Actually Broke

In my experience taking a B2B platform business from a single-office team to a 130-person internationally distributed organization across multiple geographies, the breaking point was never the thing that looked most complex on paper.


It was always ownership.


As the organization grew, processes that had worked informally began falling into the gaps between newly formed teams. New management layers created ambiguity about who could decide what. Near- and offshore structures added time zones, communication friction and distance from the informal alignment mechanisms that had held everything together.


The operating logic had not been redesigned to match the organization we had become. It was still running on the wiring of the organization we used to be.


Three Things I Now Apply in Every Mandate:

Ownership does not scale automatically.

It has to be redesigned deliberately at each growth threshold. What worked at 40 people will quietly break at 80. What worked at 80 will break again at 130. Each stage requires a conscious reset of who owns what, who can decide what and how escalation paths are structured. Most leadership teams treat this as something that will sort itself out. It doesn't.


Proximity is not governance.

When a business runs on informal alignment, it feels efficient, until it doesn't. Real governance means decisions are made at the right level, with the right mandate, without the CEO as the bottleneck. Building that structure deliberately, through clear role mandates, defined decision rights and a management cadence that surfaces issues early, is not bureaucracy. It is the infrastructure that makes scale possible.


The operating model is not a one-time design.

Most leadership teams treat it as something you build once during a restructuring and leave in place. The best ones treat it as something you pressure-test continuously against where the business is actually heading. A model designed for a 40-person single-geography business will not support a 130-person internationally distributed platform, regardless of how strong the product or commercial model is.


Why This Matters Beyond the Deal

The financial model of a PE deal prices in scale. The decision infrastructure rarely does.


In most processes I have been part of, operating judgment enters too late, after structures are locked, after leadership is confirmed, after the first 100 days are already being spent firefighting what should have been designed upfront.


The question I would put to any fund evaluating a platform business: who in your process is stress-testing whether the organization can actually execute the thesis, not just whether the numbers support it?


That is a different kind of diligence. And in my view, it is the one that determines whether value creation actually starts at close, or six months after it.


Scale does not fail because of ambition. It fails because the operating model was never redesigned for the next threshold.

bottom of page