Insurance orchestration: why the future is orchestrated, not built

In a recent episode of The Underwriting Intelligence Podcast, ServiceNow's Global Head of Insurance Nigel Walsh makes the case for orchestration as the most pragmatic path forward for insurance technology architecture. Rather than consolidating into a single platform or building from scratch, Walsh argues that insurers should coordinate specialized tools across multi-cloud environments to maintain flexibility and avoid vendor lock-in. Here are the key insights from the conversation.

Key takeaways:

• Orchestration lets insurers coordinate multiple vendors and cloud environments without locking into a single platform, preserving optionality as requirements evolve.

• Discipline in AI investment, such as Nationwide's narrowing to 18 flagship use cases, requires orchestration for visibility and accountability.

• The workbench model moves insurance teams from passive dashboarding to active decision-making within a single operable surface.

• Workflows designed for adaptability outperform static processes as risk profiles, data velocity, and regulatory requirements shift.

• Insurers should use existing platform plumbing and reserve custom development for genuine differentiation.

What is insurance orchestration?

Speaking on The Underwriting Intelligence Podcast, Walsh explained the core idea: insurers need to coordinate tools from different providers across different lines of business and geographies. The goal is to bring it all together in a way that effectively adapts as the business and the world constantly evolve, rather than forcing everything into one place.

In practice, insurance orchestration acknowledges that different portfolios and regions have different needs rather than fighting that reality. It coordinates the right tools across functions while reducing the risk of being locked into any one vendor.

Why insurance organizations need orchestration now

Three forces are converging to make orchestration a priority: growing discomfort with vendor dependency, the aftermath of unchecked AI experimentation, and the accelerating pace of change in underwriting requirements.

The vendor lock-in problem

Insurers are risk averse by nature, and the industry has never been comfortable depending on a single or small number of vendors. The desire to use any cloud, any data source, and any workflow with full interoperability reflects a fundamental risk posture and an operational requirement.

Orchestration addresses this by reducing dependency on any single provider. Rather than betting the enterprise on one platform, insurers can coordinate tools and retain the optionality to swap components in and out as needs evolve.

Managing AI sprawl and complexity

The insurance industry went through what Walsh calls the "let a thousand flowers bloom" phase of AI experimentation, when every team was spinning up pilots and every vendor was pitching AI-powered everything. That phase built curiosity and baseline understanding, but it also created a mess.

Walsh, who previously led global insurance for Google Cloud, is blunt about where things stand now: the industry has to get focused. Nationwide announced a $1.5 billion investment in AI and technology through 2028, but the notable detail was not the dollar figure. It was that they narrowed their focus to 18 flagship use cases.

That discipline, collapsing from hundreds of experiments to a focused portfolio, is exactly what orchestration enables. It gives organizations visibility into what each AI tool is doing, where it is deployed, and whether it is delivering value.

Evolving business requirements

Risk profiles shift, new asset classes emerge, and regulatory requirements evolve. The velocity of data and insight available to an underwriting workbench far exceeds what existed even a year ago, and Walsh emphasizes the need for workflows that can change and adapt over time. Orchestration provides that adaptability by treating workflows as configurable rather than fixed.

Key benefits of orchestration for insurers

Orchestration addresses several challenges simultaneously. When implemented well, the benefits compound across the organization:

• Reduced vendor dependency. Switching or adding components becomes a manageable decision rather than a multi-year transformation project.

• Personalization at scale. Variability across different roles, geographies, and lines of business turns personalized user journeys into a practical advantage.

• Future-proofing. New tools integrate into the orchestrated ecosystem without replacing entire systems.

• Operational visibility. A coordination layer gives leaders clarity on how each component contributes to outcomes.

• Flexibility without fragmentation. Orchestration coordinates across multiple environments without requiring everything to live in one place.

These benefits are particularly relevant for carriers operating across multiple lines and geographies, where no single platform can serve every need equally well.

How orchestration works in practice

Walsh describes several patterns that illustrate how orchestration operates across real insurance environments, from individual user experiences to enterprise-wide architecture decisions.

The workbench model

Walsh uses the analogy of a physical workbench: everything at your fingertips to do your job, whether that is a claims workbench, an underwriting workbench, or a service workbench. The critical distinction is between a workbench and a dashboard. A dashboard shows information, while a workbench lets you act on it.

This reflects a broader industry shift that Amrit Santhirasenan from hyperexponential describes as moving from the era of dashboarding toward the era of action and insight. Orchestration powers that shift by connecting data, tools, and decision points into a single operable surface.

Orchestrating across systems and geographies

A specialty portfolio in London does not have the same needs as a personal lines operation in the Midwest. Orchestration routes workflows according to region and line of business, coordinating different tools and data sources so that each geography operates with the right configuration. The result is consistency in governance without rigidity in execution.

Platform versus point solution thinking

ServiceNow evolved from IT Service Management (ITSM) into an enterprise workflow engine spanning industries. Walsh notes that those origins underscore a core principle: a workflow is a workflow is a workflow, whether it serves IT service management, claims operations, or underwriting.

There is a persistent tension in insurance technology between out-of-the-box configuration and platform flexibility. Orchestration resolves this by letting insurers use platform capabilities for common workflows while preserving the ability to customize where genuine differentiation exists. As Walsh notes: "If you are building the plumbing, you probably have no business building it. Put your secret sauce on top."

The test Walsh applies is whether you would design it the same way with a blank sheet of paper. When Matthew Wilson, James Birch, and the team rebuilt the smart follow syndicate model from scratch rather than digitizing existing workflows. The results challenged assumptions about what was possible in the Lloyd's market, and the approach illustrates what becomes feasible when organizations coordinate existing investments while creating space for genuine innovation.

Getting started with orchestration

Walsh offers three principles for insurers beginning to think about orchestration. Each one reflects a common failure mode he has observed across the industry.

Fall in love with the problem first

Walsh references advice from Sarah Russell at Google: fall in love with the problem. Before selecting tools, platforms, or vendors, define what you are actually trying to solve. Too many orchestration efforts start with technology and work backward.

Be clear on what you are optimizing for

One person's "amazing" might be someone else's table stakes. That range of expectations means clarity is essential. Marcus Ryu, a board member at hyperexponential, reinforces this: without clarity and exclusion in what you do, you will disappoint your customers. Identify whether you need incremental improvement or true reimagination, and design your orchestration strategy accordingly.

Balance flexibility with focus

Walsh has seen both failure modes: organizations that control so tightly that innovation never gets a chance to succeed, and organizations that let anything go in the name of progress, creating a mess to clean up later. The middle ground, structured experimentation with accountability, is where orchestration delivers the most value.

The future of orchestration in insurance

Walsh describes how one of his analysts built a custom AI bot integrated into Teams that sends reminders, follows up on threads, and functions almost as a team member. Tools like Google's Gemini and emerging agentic workflows point toward a future where AI works for you rather than requiring you to work with it.

Insurance orchestration positions organizations to absorb these capabilities as they mature rather than scrambling to retrofit them into rigid architectures. The progression from experiment, through workflow, to partnership defines how these tools will move from novelty to utility, and the goal is not technology for its own sake. It is getting more time to focus on the work that matters and eliminating the busy work that doesn't.

How hyperexponential fits into orchestrated workflows

The future of insurance technology is orchestrated, not built. Orchestration provides the coordination layer that makes multi-vendor, multi-cloud strategies operationally viable across a complex, multi-geography industry. McKinsey's research on insurance technology modernization reinforces the case for modular, composable approaches over monolithic platforms, particularly for carriers operating across multiple lines and regions.

hyperexponential's underwriting decision platform is designed to operate within orchestrated environments. The platform connects submission ingestion, triage, pricing, and portfolio intelligence into a single workflow that integrates with existing workbenches and core systems through API-first architecture. Carriers can deploy hx alongside tools like ServiceNow for workflow coordination, using the platform's Decision Engine and Pricing & Rating capabilities where actuarial and underwriting precision matter most. That modular approach lets organizations maintain flexibility to swap or add components elsewhere in the stack.

Insurance leaders evaluating their current architectures should ask where vendor dependency limits optionality and where coordinated workflows could replace rigid pipelines. Explore hyperexponential to see how an underwriting decision platform fits into an orchestrated approach.

Hear the full conversation on The Underwriting Intelligence Podcast, where Amrit Santhirasenan and Nigel Walsh discuss how insurance teams can orchestrate workflows to create the flexibility modern portfolios demand: Watch the full episode.

Frequently asked questions

How does insurance orchestration differ from a single-platform strategy?

A single-platform strategy consolidates tools and workflows into one vendor's ecosystem, which simplifies architecture but limits flexibility. Orchestration coordinates multiple vendors and systems through a shared layer, letting insurers select the best tool for each function and swap components without enterprise-wide disruption. The trade-off is greater integration complexity in exchange for long-term optionality.

What role does data privacy play in orchestrated insurance workflows?

Orchestration layers must respect data sovereignty across jurisdictions, routing information according to regional privacy requirements rather than pooling everything centrally. This means workflows in different geographies may use different data handling rules, storage locations, and access controls, all coordinated through the orchestration layer rather than enforced by a single platform.

Can legacy systems work within an orchestration approach?

Orchestration can wrap around existing legacy systems and incrementally modernize them rather than requiring full replacement. APIs and integration layers expose legacy functionality to newer tools, allowing carriers to preserve working systems while adding modern capabilities where they deliver the most value.

How should insurers prioritize which workflows to orchestrate first?

Start with workflows where vendor dependency creates the most friction or where multiple tools already need to coordinate. Submission intake and triage are common starting points because they sit at the intersection of multiple data sources, decision rules, and downstream processes. Pricing and portfolio analytics often follow because they benefit from real-time feedback loops across the underwriting workflow.

What is the difference between a workbench and a dashboard in insurance technology?

A dashboard displays information for review. A workbench connects data, tools, and decision points into a single surface where users can take action, such as triaging submissions, pricing risks, or adjusting portfolio strategy. The shift from dashboarding to workbench models reflects a broader industry move toward surfaces that enable decisions rather than simply reporting on them.

How does orchestration help insurers manage AI investments more effectively?

Orchestration gives organizations visibility into which AI tools are deployed, where they operate, and whether they deliver measurable value. This visibility is essential for moving from broad experimentation to focused investment. Carriers can track individual AI use cases across the orchestrated ecosystem and reallocate resources toward the initiatives that produce results.

Does orchestration increase integration complexity for insurance carriers?

Orchestration adds an integration layer, which introduces some complexity. However, it reduces the cumulative complexity of managing disconnected point solutions or maintaining rigid monolithic systems. The coordination layer absorbs much of the integration work that would otherwise fall on individual teams, and API-first platforms are designed to simplify how components connect.