Building what matters: Why payers should lean into open ecosystems

Executive Summary

Adopting open, modular ecosystems allows healthcare payers to prioritize high-value innovation over building all technology internally.

• Engineering teams can innovate more effectively when relieved of heavy infrastructure maintenance.
• Modular architectures facilitate the rapid integration of pre-built components to accelerate development.
• Market differentiation stems from superior user experiences and intelligence rather than backend systems.
• Open ecosystems simplify partnerships and capability integration without requiring constant re-engineering.
• Leading organizations focus on building unique strategic assets while leveraging platforms for standard operations.

Most payer organizations aren’t short on imagination. They have a clear vision for where member experience needs to go: more personalization, smarter recommendations, and smoother navigation. The challenge is everything that stands between an idea and actually getting something meaningful into market.

Engineering teams carry heavy loads already. Too much of their time still disappears into foundational work members never see, which slows down the kind of experimentation payers need. As expectations rise, more organizations are rethinking how they build. Instead of owning every layer, they’re asking how to create space to innovate, move quickly, and focus on the experience rather than the machinery underneath it.

That’s where open, modular ecosystems become powerful.

Innovation without starting from zero

Healthcare has a long history of trying to build everything internally. I understand the instinct. There’s comfort in believing full ownership leads to full control. But in reality, most teams face constraints like legacy systems, regulatory demands, integration requirements, and simple bandwidth limitations. These are the challenges that make this approach unrealistic.

McKinsey’s recent work on payer modernization highlights how much time gets trapped in foundational tasks. Their analysis shows that modular architecture and reusable components can free up a meaningful share of IT capacity, accelerating delivery and giving teams more breathing room. (Source:McKinsey)

The point is to put your focus and effort into building the right things. Most payers don’t differentiate on identity management or workflow plumbing. They differentiate on the clarity of the experience and the intelligence behind it. When teams don’t have to reinvent the basics, they can finally put more energy into those higher-value layers.

Giving technical teams the control they expect

One consistent theme across engineering teams is the need for flexibility. Not in the sense of doing everything manually, but in being able to choose components, integrate them cleanly, and shape them to fit their existing environment.

No team wants a black box. And few want to abandon years of solid engineering just to adopt a new capability.

Teams want components that plug in without forcing them to rework what already functions. They want support for established languages and frameworks. They want the confidence that comes with fine-grained control.

A strong ecosystem acknowledges those needs. It complements what an organization has already built rather than replacing it.

Keeping the heavy lifting off the critical path

Almost every payer needs the same foundational capabilities: secure identity, data integration, orchestration, analytics scaffolding, content systems. Necessary, yes—but rarely the pieces that set one organization apart.

Differentiation happens in the layers members actually experience: how guidance is delivered, how benefits are surfaced, how the system learns over time, how all the touchpoints feel connected rather than scattered.

But this is difficult and costly to accomplish when engineering teams spend the majority of their time maintaining the plumbing.

Huron and Healthcare Dive highlight the need for strong foundational technology and integrated data systems as prerequisites for meaningful innovation—areas that tend to drain resources when left fully to internal teams. (Source:Healthcare Dive / Huron)

When infrastructure becomes something teams can rely on instead of constantly maintain, they’re able to invest more of their energy in the experiences that members actually feel.

That shift—from supporting systems to shaping experiences—is where the real value gets created.

What a collaborative healthcare ecosystem enables

“Ecosystem” may sound abstract, but the concept is simple: create a technical environment where multiple tools and partners can work together without friction.

Other industries have shown how powerful this approach can be. E-commerce, payments, logistics—none evolved because one company built everything. They evolved because platforms created space for partners to contribute value without re-engineering the same foundation over and over.

Healthcare is now moving down that same path.

Rock Health’s 2024 Consumer Adoption Survey shows how deeply digital tools have embedded themselves in people’s lives. A majority of U.S. adults used virtual care in the past year, more than half own a wearable, and most track health metrics digitally.
(Source:Rock Health)

Members don’t think about point solutions or portals or apps. They think about whether their experience feels connected. Whether their information follows them. Whether they understand what to do next.

Open ecosystems make that possible. They allow payers to:

• onboard new partners with far less friction,
• try new capabilities without restructuring the entire stack,
• scale successful innovations quickly,
• and create a more coherent experience across channels.

Reducing fragmentation is one of the hardest challenges in healthcare. Ecosystems provide one of the few practical ways to make progress.

How AI fits into the bigger picture

AI is top of mind for every payer we talk to. It has enormous potential to improve navigation, personalize experiences, and streamline operations. But it also introduces new technical demands around data, governance, and integration.

McKinsey’s guidance on AI for payers offers a grounded way to think about it: focus on high-impact workflows rather than monolithic AI initiatives. That requires flexible data pathways and modular foundations that allow new models and agents to plug in without major reconstruction. (Source:McKinsey)

Their follow-up work on modular AI architecture reinforces the same point: the future of AI relies on clear roles for models, agents, and domain-specific data rather than all-in-one systems. (Source:McKinsey)

Payers don’t need to own every layer of AI to get value from it. The differentiation comes from how AI is applied to real member needs—not from building the entire stack internally.

A practical way forward

When leaders face the perennial “build or partner” decision, the instinct often tilts toward building. It feels safer. It feels like ownership.

But the organizations that are gaining the most ground are taking a more deliberate approach. They still build—but they build the pieces that express their strategy and define the member experience. And they rely on modular platforms and ecosystems for the foundational work that doesn’t need their unique stamp.

That balance gives engineering teams room to innovate rather than maintain. It accelerates iteration. And it creates more opportunities to deliver experiences members can actually feel.

The payers who make this shift won’t just move faster—they’ll deliver clearer, more connected, more intuitive experiences for the people they serve.ers and the organization alike.