Why Scale Is Not the Same Thing as Strength in Healthcare

Hatched by Ben H.

Jul 30, 2026

10 min read

3 views

67%

The surprising thing about a giant insurer

A company can add millions of members, grow revenue by billions, and still become more fragile.

That sounds wrong at first. We tend to treat size as evidence of resilience, especially in healthcare, where scale usually means bargaining power, distribution, and a wider moat. But the numbers tell a more interesting story: a massive healthcare organization can be growing in one part of the business while absorbing shocks in another, and those shocks can expose a deeper truth. Scale is not the same thing as strength. Sometimes scale is just accumulated complexity with better branding.

That is what makes this moment so revealing. On the surface, the business looks formidable. Commercial membership is rising quickly. Revenue is up. Operating profit remains enormous. Yet one segment’s profit can fall sharply, cyber disruption can ripple through the entire system, and integration between payer, provider, pharmacy, and data businesses can become both a source of advantage and a source of stress.

The deeper question is not whether the company is big. It is whether the company has become so interconnected that its strengths now double as vulnerabilities.

The hidden tradeoff inside vertical integration

Vertical integration is often sold as the ultimate strategic answer. Own more of the chain, reduce friction, capture more value, coordinate care better, and improve margins. In theory, that sounds like the business equivalent of replacing a leaky bucket with a closed loop. In practice, it can also mean that every leak is now inside the same bucket.

The intercompany revenue eliminations rising materially is more than an accounting footnote. It is a signal that the organization is increasingly routing value through itself. That can be powerful because it creates internal control and data visibility. It can also mean that more relationships, processes, and dependencies live under one roof. A problem in one segment is no longer a local issue. It becomes a system issue.

Think of it like a city built around one central bridge. The bridge makes trade faster and the city richer. But once everything depends on that crossing, a single closure creates congestion everywhere. The city did not become weaker in absolute terms. It became more tightly coupled. And tight coupling is efficient until it is brittle.

This is why the most interesting signal in the results is not just membership growth or revenue growth. It is the combination of growth, margin pressure, and operational disruption. The organization is not simply expanding. It is becoming more entangled. That entanglement creates economies of scale, but it also creates what systems thinkers call failure propagation: an issue in one part of the system cascades into others faster than management can contain it.

The lesson extends far beyond healthcare. Many companies pursue integration because they want to own the customer relationship and the economics. But ownership changes the nature of risk. Once you internalize enough steps in the chain, you no longer have a portfolio of separate businesses. You have one organism with many organs. If one organ gets sick, the whole body compensates.

The more a business integrates, the more it must learn to think like an immune system, not just a spreadsheet.

Growth can disguise fragility

What makes a business look healthy? Usually the same things that make it easier to miss its weaknesses: rising membership, rising revenue, and stable market leadership. Those are not trivial accomplishments. They are signs of real demand and real execution. But growth can also mask stress, because expanding systems often absorb shocks more gracefully in the short term than they can in the long term.

A useful mental model here is the difference between load-bearing growth and decorative growth. Decorative growth makes the top line look better, but it does not necessarily improve the organization’s ability to handle shocks. Load-bearing growth, by contrast, strengthens the structure itself. It improves the system’s capacity, resilience, and adaptability.

Not all growth is load-bearing. A big increase in commercial membership may improve the revenue base, but if the organization is simultaneously wrestling with higher loss ratios, cyber recovery expenses, and uneven performance across segments, that growth may be doing less structural work than it appears. It may enlarge the machine without strengthening the gears.

This is especially visible when a business has multiple engines with different operating rhythms. Insurance, provider services, pharmacy benefits, and health data operations do not behave the same way. One can be having a very good quarter while another is under pressure. Investors often look at the consolidated result and think in aggregate. Managers, however, have to think in interfaces. The real question is not whether the sum is positive. It is whether the connections between the parts are making the system more adaptive or more dependent.

Here is the uncomfortable truth: the bigger the organization, the more tempting it is to interpret momentum as immunity. But momentum is not immunity. Momentum is just momentum. A large company can keep moving while its internal friction rises. It can even keep growing while the margins inside the machine deteriorate.

That is why loss ratio matters so much. It is a reminder that the economics of care are never abstract. Premium growth can look impressive until medical costs, funding changes, and business mix shift the floor beneath it. The business is large enough to absorb it this quarter. The strategic question is whether the same architecture can absorb it repeatedly without degrading.

The most valuable asset is not size, but coordination

A company that spans payer, provider, pharmacy, and data services does not win simply because it has more assets. It wins if it can coordinate those assets faster and more intelligently than others can coordinate separate ones.

That is a subtle but crucial distinction. Integration is not value by itself. Coordination is value. Integration only matters insofar as it improves decision quality, reduces waste, speeds feedback loops, and makes the customer or patient experience more coherent.

This is where strategy and operations become inseparable. The path from growth story to real enterprise value is not a slide deck. It is a sequence of operational choices: which systems talk to each other, which teams own which metrics, how data is translated into action, and how leadership prevents a local incident from becoming a companywide crisis.

That is also why people who can bridge strategy, analytics, and execution are so valuable in healthcare. A growth narrative is not enough. A sale to a larger platform, for example, does not happen because the story sounds good. It happens because someone can translate scattered operational facts into a coherent picture that investors and acquirers trust. The craft is not just telling the story. It is making the story operationally true.

In a complex healthcare platform, that means several things:

The data layer must be trusted. If claims, reserves, patient flows, and provider economics do not reconcile, the system cannot learn.
The incentive layer must be aligned. A payer wants lower cost, a provider wants capacity and margin, a pharmacy unit wants throughput, and a data business wants adoption. Coordination only works when incentives are explicit.
The response layer must be fast. When a cyberattack or operational disruption hits, the organization needs prebuilt playbooks, not improvisation.
The communication layer must be credible. Investors, regulators, providers, and employees all need different versions of the truth, but they must all be consistent.

The best operators understand that growth does not merely add more work. It increases the number of handoffs. And in large systems, handoffs are where value leaks out.

In healthcare, the winner is often not the company with the most assets, but the one with the fewest broken handoffs.

What the cyberattack really revealed

A cyber incident is often discussed as a technology problem. That is too narrow. A major disruption exposes the company’s true operating design.

A resilient organization can isolate damage, maintain continuity, fund critical partners quickly, and preserve trust while repairs are underway. A less resilient one discovers that its systems are so interdependent that a breach does not remain a breach. It becomes a cash flow issue, a provider relations issue, a reserve estimation issue, and a reputational issue at once.

This is the real test of a platform business. Not whether it can grow in calm weather, but whether it can keep the system legible under stress.

Imagine a hospital with excellent departments but no clear transfer protocol between them. In normal conditions, each unit looks competent. Under pressure, patients get stuck in the seams. Corporate strategy works the same way. The interface between units matters as much as the units themselves. When the operating environment changes suddenly, the seams are where fragility appears.

That is why the drop in one segment’s profit should not be read only as a segment story. It is a sign that strategic adjacency has costs. Data and consulting businesses often look attractive because they sit close to the center of the system. But proximity to the core also means exposure to the core’s shocks. If the network is disrupted, the business closest to the nervous system may feel the pain first.

So the question becomes: what kind of integration creates compounding advantages, and what kind simply concentrates risk? The answer depends on whether the company is building modular interdependence or monolithic dependence.

Modular interdependence means the units are connected, but each can absorb a local shock without bringing down the whole system. Monolithic dependence means the units are fused so tightly that one disruption becomes a shared failure. The former is a platform. The latter is a pileup.

A better framework: the three tests of durable scale

If scale is not the same as strength, then how do you tell the difference? A useful test is to evaluate large, integrated businesses on three dimensions.

1. Can the system learn faster than it breaks?

A durable company turns every disruption into better process, better data, and better decision making. If an incident only creates cleanup costs and no structural improvement, the organization is paying tuition without earning the degree.

2. Can the company localize failure?

The best systems can compartmentalize. They do not pretend failures will never happen. They ask whether a failure in one zone stays in one zone. This is especially important in healthcare, where operational, financial, and regulatory risks are deeply intertwined.

3. Can growth improve the quality of coordination?

This is the most important test. Growth should not merely increase the number of customers or transactions. It should improve feedback loops, sharpen pricing, make care more efficient, and reduce confusion across the system. If growth only raises complexity, it may be impressive but not durable.

These three tests are simple, but they cut through a lot of corporate theater. They help distinguish businesses that are merely large from businesses that are actually strong.

Key Takeaways

Do not confuse size with resilience. A business can grow quickly and still become more fragile if complexity rises faster than coordination.
Treat integration as a design problem, not a slogan. Vertical integration creates value only when it improves decision speed, data quality, and handoffs.
Look for failure propagation. The key question is not whether a business can absorb one shock, but whether that shock stays contained.
Measure whether growth is load-bearing. Ask if revenue and membership gains actually strengthen the system, or simply enlarge it.
Build for modularity. In complex organizations, the best defense against disruption is not isolation, but compartmentalized interdependence.

The real meaning of leadership in complex systems

The temptation in a company this large is to celebrate the scale itself: more members, more revenue, more reach, more categories, more control. But the deeper leadership challenge is harder and less glamorous. It is to keep the whole machine understandable as it expands.

That means knowing when to integrate and when to simplify. It means investing not only in growth, but in the machinery of coordination: data integrity, operational transparency, crisis response, and clear accountability. It means recognizing that the highest form of strength in a complex healthcare system is not dominance. It is adaptability without collapse.

In the end, the most important question is not whether a company can become bigger. It is whether it can become bigger without becoming less governable.

That is the paradox of modern healthcare scale: the more powerful the platform becomes, the more it must prove that it can remain human, legible, and resilient. Size may get attention. Coordination earns trust. And in a system where one shock can ripple across insurance, providers, pharmacy, and data at once, trust is the real competitive advantage.