The Hidden Denominator of Enterprise Growth

When complexity grows faster than organizational capacity, success can become its own source of risk.

I had the privilege of working with a company that grew from roughly a $1 billion valuation to more than $100 billion. I learned a great deal watching what ha

d to change along the way.

So, imagine this.

Your latest acquisition just pushed the company through a $2 billion valuation. Congratulations. Now for the harder question: Will the organization underneath that $2 billion enterprise support a $10 billion one? What about $100 billion?

Likely not, nor should it.

Entrepreneur and investor Alex Hormozi recently made a deceptively simple observation about scale: 

“The fastest way to build a $10 million business is not necessarily the fastest way to build a $100 million one.”

Take that thought further. The architecture that creates a $100 million enterprise may be incapable of supporting a $2 billion one. The architecture that successfully created $2 billion may eventually become the constraint preventing the next $10 billion.

At some point, growth stops being principally a question of adding more. It requires becoming something different.

Growth Loves the Numerator

Revenue, EBITDA, market capitalization, acquisitions, customers, assets under management and the numerous other visible signs of growth. Boards forecast them. Investors underwrite them. Management teams organize around them.

But enterprise growth has a hidden denominator: the organizational capacity required to produce and sustain that growth.

Consider two companies, each generating $500 million in revenue and $50 million in EBITDA. The first requires layers of approval, recurring executive intervention, duplicated systems, increasing headcount, key-person dependencies and an expanding calendar of meetings simply to keep the machinery moving.

The second produces the same financial outcome with faster decisions, cleaner information flows, greater managerial leverage, intelligent automation and enough organizational capacity to absorb another market, acquisition or disruption.

Same revenue and EBITDA. Very different enterprises.

One is producing earnings. The other is producing earnings and capacity. Their futures are unlikely to be valued equally.

Scale Is an Advantage, Until It Isn't

Few executives confront this paradox at greater scale than Jamie Dimon.

JPMorgan Chase generated $185.6 billion in revenue and $57 billion in net income in 2025. Its scale, capital and capabilities provide competitive advantages that smaller institutions simply cannot replicate.

Yet in his 2025 shareholder letter, Dimon offered an unusually direct warning:

 “Size can often be a tremendous business disadvantage.”

He pointed to complexity, bureaucracy and complacency as forces capable of slowing decisions and distancing an organization from its customers.

A $2 billion enterprise should possess capabilities, controls and specialization that would be overly burdensome inside a $20 million company. Complexity itself is not the problem. Some complexity creates competitive advantage. Some consumes the advantage already created.

That creates an important leadership distinction: Value-Creating Complexity versus Capacity-Consuming Complexity.

The first expands what an enterprise can do. The second increases what the enterprise must do merely to manage itself.

The difference eventually becomes financial.

The Denominator Has a P&L

McKinsey's Organizational Health Index draws on experience with more than 2,600 organizations. Its findings make organizational capability difficult to dismiss as “soft.”

Companies in the top quartile of organizational health…

·         Achieve 2.5 times greater return on invested capital

·         Are 2.2 times more likely to have above-median EBITDA margins

·         Are 1.5 times more likely to produce above-median growth in net income to sales.

·         Are also three times more likely to outperform unhealthy ones.

Those numbers do not prove that better organizational health mechanically produces better financial performance. Correlation deserves to be treated as correlation.

The economic signal is nonetheless difficult to ignore. An enterprise's ability to align, execute, adapt and renew itself appears alongside materially different financial outcomes.

How an organization works eventually appears in what the organization earns.

Heroic Employees Can Distort the Calculation

There is another reason the denominator can be difficult to see: great people compensate for weak systems.

High-growth organizations frequently celebrate resilience, grit, an ability to wear multiple hats, and a willingness to do whatever it takes. Those are valuable attributes in an employee. They can also be yellow flags in an operating model.

A resilient workforce and an organization dependent upon employee resilience are not the same thing.

When ordinary performance routinely requires extraordinary effort, something beneath the numbers deserves examination.

Your best people know which spreadsheet contains the real number, who can actually approve the request, and which unofficial process gets the customer what they need. They bridge broken workflows, carry institutional knowledge, and absorb responsibilities that fall between functions.

The work gets done. The customer is served. The quarter closes. Leadership sees performance. What it may not see is concentration risk.

Investors routinely scrutinize customer concentration, supplier concentration, and key-person dependency. Organizational performance concentrated in a relatively small number of heroic employees deserves similar attention.

Sometimes exceptional employees are subsidizing organizational inefficiency with their own capacity.

That subsidy can eventually surface as turnover, excess headcount, succession exposure, inconsistent service, slower execution, or an inability to scale.

Grit isn't the problem. Grit should be a competitive advantage, not an operating requirement.

There is a profound difference between people performing exceptionally because an organization enables them and performing heroically because the organization requires them. The first creates capacity. The second creates dependency.

Headcount Is Not Capacity

Earlier in my career, I became cautious about treating increased workload as automatic justification for increased headcount, not because people are expensive, but because capable people are valuable.

Before adding people, we learned to interrogate the work itself. Why does this work exist? Can the process disappear? Can the customer accomplish it more easily through self-service? Can technology reliably handle the transaction? Are highly capable employees moving information or applying judgment? Are we adding people to expand capability, or to compensate for a process that should be redesigned?

Done intelligently, automation and self-service can increase human service rather than diminish it. Remove repetitive transactions and talented people regain capacity for judgment, relationships, creativity, exceptions, and complex problem-solving.

The objective isn't minimum headcount. It is maximum productive human capacity. Efficiency should create human capacity, not merely remove humans.

Regenerative Systems Expose the Same Problem

My growing work and interest in regenerative platforms and natural capital has given me another vantage point from which to examine enterprise growth.

The regenerative economy contains sophisticated science, ambitious ideas, and deeply committed people. It also exposes a fascinating contradiction.

Some organizations have modeled the ecosystems they intend to regenerate with greater rigor than they have modeled the enterprises responsible for stewarding them.

They may project forest growth decades forward, model water, monitor soil, design for biodiversity, account for climate risk, and plan biological succession. Yet the enterprise behind those assets may remain disproportionately dependent upon a founder, personal relationships, mission-aligned investors and people willing to believe in what could be.

There is nothing inherently wrong with beginning that way. Most important ventures begin with conviction, passion and a vision for what could be before they possess infrastructure.

But conviction is not architecture, and capital does not become patient simply because the mission is admirable.

If natural capital is to compete seriously for institutional investment, the enterprises behind it will increasingly need what sophisticated capital expects from other asset classes: credible economics, governance, controls, verification, transparent data, risk management and demonstrated execution capability.

Regenerative-development leader Ronny Castillo (Forests VC) frames the issue this way:

“If natural capital is going to mature into a serious institutional asset class, we have to apply the same long-term thinking to the enterprises behind these assets that we apply to the assets themselves. You cannot model a forest over decades and build the organization stewarding it quarter to quarter.”

The lesson extends well beyond natural capital. We routinely model financial growth five and ten years into the future without modeling the evolution of the organization expected to produce it with comparable rigor.

Natural systems make the underlying principle obvious: long-term productivity depends upon the productive capacity of the system underneath it.

So does enterprise productivity. People can be depleted. Leadership attention can be exhausted. Overdependence on a handful of performers creates vulnerability. Insufficient diversity of thinking can reduce adaptability.

This is not an argument for importing environmental idealism into the boardroom. It is an argument for recognizing the same economics when they appear in a different system.

Acquisition Can Hide the Denominator

M&A makes the denominator particularly difficult to see because the numerator changes immediately. Revenue, customers, employees, assets, and market share can arrive the moment the transaction closes.

Organizational capability does not necessarily arrive at the same rate.

Systems remain separate for now. Reporting structures overlap for now. Technology integration waits. Different processes survive. Different cultures persist. Customer experiences diverge.

Each compromise may be perfectly rational. Immediate integration can sometimes destroy more value than it creates. Then another acquisition closes, and another.

The accumulated liability is what I think of as Enterprise Integration Debt: the organizational, operational, cultural and strategic obligations intentionally or unintentionally left unresolved as an enterprise expands.

Enterprise Integration Debt is not inherently bad. It can preserve value when immediate consolidation would be unnecessarily disruptive, just as financial debt can accelerate productive investment and technical debt can accelerate development.

The distinction is between intentional Enterprise Integration Debt with a repayment strategy and accumulated debt that simply becomes the way the enterprise operates.

Because Enterprise Integration Debt carries interest.

That interest is paid through duplicated systems, management overhead, fragmented information, inconsistent customer experiences, cultural friction, slower decisions, and consumed executive attention.

It rarely appears as a line item on the balance sheet. The enterprise pays it anyway.

This creates another important distinction:

Acquisition creates financial scale. Integration creates enterprise scale.

Private Equity Is Repricing Organizational Capability

The current private-equity market provides a useful signal that sophisticated capital is paying greater attention to the denominator. According to McKinsey & Company…

Average PE holding periods now exceed 6.5 years. Only 19% of acquisitions made in 2021 had been sold by 2025, compared with a typical four-year exit rate of roughly 30% during the preceding decade. Buyout distributions fell to 6% of assets under management in 2025, versus an average of 16% between 2015 and 2019.

When exits slow and multiple expansion becomes less dependable, operating performance has to carry more of the value-creation burden.

Capital has responded. Since 2021, PE firms have more than doubled the average size of their operating groups, and more than 80% of executives in a recent McKinsey survey reported at least one portfolio company undergoing transformation.

PE-backed businesses pursuing enterprise-wide transformations have typically achieved 8% to 12% productivity improvements during the first two years after acquisition.

Perhaps more revealing than any individual statistic is the direction of travel. Leading investors are increasingly examining pricing, operations, technology, commercial performance and organizational effectiveness not as isolated interventions, but as components of an integrated enterprise system.

That is capital voting with resources.

Financial engineering can acquire an enterprise. Organizational engineering determines what that enterprise becomes.

Designing for Scale Does Not Mean Building Big

A 30-person company should not build the bureaucracy of a 30,000-person company in anticipation of becoming one. That would sacrifice one of its greatest advantages.

Designing for scale means something more disciplined: identify which decisions made cheaply today become prohibitively expensive to reverse tomorrow.

Data architecture, ownership structure, governance, decision rights, core technology, brand architecture, verification standards, institutional knowledge, leadership development, and capital structure will not all require the same investment at every stage.

Not every capability must be built early. Some, however, should be architected early.

This is a discipline we are applying in ventures I am involved with today: not attempting to carry the infrastructure of tomorrow, but thinking carefully about which foundational decisions can preserve rather than constrain future options.

The goal is not to carry tomorrow's overhead today. It is to prevent today's expedient decisions from becoming tomorrow's structural liabilities.

That principle applies whether designing a regenerative platform from inception, professionalizing a founder-led middle-market company, integrating the fifth acquisition into a roll-up, or contemplating the architecture required for the next zero on enterprise value.

Put a Denominator Under the Growth Plan

We model five-year revenue, EBITDA expansion, market penetration, acquisitions, and enterprise value.

Now model what must happen underneath those numbers.

What breaks if revenue doubles? Where does growth require disproportionate increases in headcount? Which processes depend upon particular people rather than institutional capability? Which systems will not survive another order of magnitude?

How much integration debt has accumulated? Which complexity creates competitive advantage and which merely consumes capacity? How much leadership attention is required simply to coordinate the organization?

And perhaps the most important question:

What must this enterprise become that it does not yet know how to be?

A $1 billion company does not become a $100 billion company simply by becoming 100 times more of itself. At every inflection point, leadership faces a choice: continue scaling the organization that succeeded yesterday, or begin architecting the enterprise tomorrow's success will require.

Because the architecture that created today's enterprise value can eventually become the architecture that constrains it.

Growth loves the numerator. The enduring enterprise learns to manage the denominator.