Skip to main content
Welcome to Deloitte
If we have selected the wrong experience for you, please change it above.

The AI Orchestrator

A Deloitte Canada Insurance Point of View · 2026

Architecture and intelligence ownership are strategic choices. Acting on them is where most carriers stall. This paper is about what it actually takes to move from intention to execution, and the six questions that shape the next decade.

About this point of view

Architecture and intelligence ownership are strategic choices. Acting on them is where most carriers stall. What does it actually take to move from intention to execution?

This paper, the fifth in the Compounding Intelligence series, is about that gap. The concept we come back to in every engagement is orchestration. Orchestration in the fullest sense, not task-level automation or isolated agent deployments, but a deliberate enterprise-wide design for how capabilities connect, how intelligence accumulates across them, and how human judgment is positioned where it genuinely matters. Each paper in the series stands alone; this one closes it with the decisions worth making now.

01

What this looks like in practice

Most insurers already have AI. Many have dozens of solutions running across claims, underwriting, distribution, and operations. The capability is there. The connection is not. Closing that gap requires a fundamentally different kind of decision than selecting the next use case.

Moving to a connected, owned architecture is genuinely hard. Business units that have built their own AI capabilities have legitimate concerns about what integration means for their autonomy. Talent gaps in AI architecture and governance are real in most organizations. Surfacing these realities early and designing around them is part of the architecture work itself, not a change management problem to solve afterward. The organizations that confront this upfront build better systems and sustain adoption more effectively.

Three things separate the carriers building toward genuine agentic scale from those that are accumulating complexity.

In every engagement we have led, the binding constraint on agentic AI at scale has not been the technology but the willingness of the workforce to move from using AI as a tool to working with it as a partner, and the willingness of leadership to redesign roles, levels, and incentives ahead of deployment rather than after it. Before workflows can be redesigned around AI, organizations need a clear, evidence-based view of what humans are actually doing at task level, and where AI can take on meaningful ownership. Deloitte's structured role disruption methodology evaluates this across the full workforce, producing scored assessments that inform how roles are redesigned, not just how AI is deployed.

Across engagements, this analysis consistently identifies the potential to shift 20 to 50 percent of task volume to AI execution, while surfacing the supervisory and judgment-intensive work that should stay with people. Organizations that do this work upfront build better systems. Those that defer it find themselves retrofitting workforce change onto a platform that was never designed with people in mind. What the redesigned roles look like on the other side of this shift is the subject of The Insurance Company of 2035, the second paper in this series.

The string of pearls cannot be assembled use case by use case. The shared data foundations, common orchestration layer, and reusable governance controls have to be designed into the platform before the capabilities are added. That is the part most organizations skip. The sequencing discipline behind it is set out in The String of Pearls, the fourth paper in this series.

The difference is measurable. In claims processing, a connected string of eligibility verification, document extraction, classification, and dynamic routing agents produces outcomes that isolated tools cannot match. The design logic we apply targets verification times falling by approximately 95 percent, document processing time by 80 to 90 percent, triage time by roughly 90 percent, and routing decisions more than 95 percent automated. These figures come from connection, not from better individual components.

The same design logic applies to actuarial and pricing work. A connected architecture can bring together claims emergence, exposure movement, underwriting appetite, rate change history, expense assumptions, reinsurance cost and external risk signals into a single pricing and reserving intelligence layer. Agents can prepare diagnostics, identify assumption drift, test scenarios and assemble evidence for model governance. The human actuary remains accountable for selections, overrides and communication of uncertainty, but the platform materially reduces the time spent assembling the evidence base.

An agentic platform built without observability, auditability, and human oversight from the outset will fail regulatory scrutiny and lose workforce adoption.

Under OSFI's E-23, explaining how an AI-driven decision was made is a compliance requirement. Governance architecture and change management belong inside the technical build, designed in from the start rather than added once the platform is live.

The insurers building toward agentic scale are not running more experiments. They have changed the question from "what can we automate?" to "how do we build an enterprise that gets smarter over time?"

02
Decisions worth making now

The questions that shape the next decade

The choices being made now will determine how difficult the next phase becomes. Carriers that build the foundation deliberately, while it can still be built rather than inherited, will find subsequent scaling significantly more manageable. Those that defer in favour of use case velocity will encounter the cost later, when changing the architecture is substantially more disruptive.

The underlying shift is not technical. It is a change in how AI is understood at the leadership level. For most insurers today, AI is still treated as a capability that the organization deploys: a tool applied to specific problems, measured on its own terms. The insurers pulling ahead have made a fundamentally different choice: they are building AI into the fabric of how work gets done, treating it as a core competency rather than a capability layer, and sequencing their investments so that each one compounds the last. That shift, from isolated use case to connected intelligence platform, is what transforms AI from a source of operational efficiency into a genuine source of differentiation and a direct enabler of business strategy.

The following questions are not diagnostic alone. They surface the decisions that need to be made explicitly. In our work, the insurers that navigate this well move through a consistent sequence: assess where transformation potential is most concentrated and where the architecture gaps are most costly; design the shared foundation before adding capabilities, so that governance, orchestration, and data infrastructure are built once; then build and sequence so that each new capability compounds rather than complicates.

03
Self-assessment

Where does your organization stand?

Six questions that surface the decisions that need to be made explicitly. Honest answers matter more than confident ones.

Q1

Architecture

Is the current AI architecture designed to be reused across capabilities, or does each new initiative rebuild shared foundations from scratch?
Designed for reuse
Partially shared
Each initiative starts fresh

Q2

Economics

Is there visibility into the total cost of AI at current scale, and a realistic model for what that cost trajectory looks like as agentic workloads grow?
Clear visibility, modelled forward
Partial visibility
No, this needs work

Q3

Sovereignty

Can the current platform operate in every geography the organization serves, including markets with data residency requirements or cloud provider restrictions?
Yes, fully portable in some markets
No, this needs work

Q4

Governance

Is governance embedded in how agents are built, or is it addressed primarily through post-deployment review processes?
Embedded in the build
A mix of both
Primarily after deployment

Q5

Workforce

Are the human and agentic workforce being designed together, or is workforce evolution expected to follow the technology deployment?
Designed together from the start
Some coordination
Workforce follows tech

Q6

Optionality

If the economics of a key AI vendor relationship changed materially, would the organization have meaningful flexibility to respond?
Real flexibility
Some, with effort
Effectively locked in

None of these have universal right answers. What matters is whether they are being asked explicitly, and whether the architecture decisions being made today are informed by honest answers.

Reading your answers

If most answers sit in the first column
Strong foundations across most dimensions
Your organization has clarity on most of the architecture decisions that matter. The remaining areas are where deliberate work would consolidate the position. Carriers in this profile tend to be well placed to scale agentic workloads without retrofitting foundations.

If answers are mixed across the columns
Partial visibility, with explicit gaps
You have visibility on some dimensions and partial visibility on others. The areas marked as needing explicit work are where architecture debt tends to compound most expensively. Worth surfacing these as explicit decisions rather than letting them be made by default.

If several answers sit in the third column
Multiple foundational decisions need explicit attention
Several dimensions show that decisions are being made without full visibility on the trade-offs. This is the most common pattern we see across the market, and also the most actionable. The window for making these foundational choices on your own terms is open now. Sequencing matters: architecture and governance before use case velocity.

The carriers that lead in 2035 will not be those that experimented the most. They will be those that connected the earliest. The window to build that foundation on your own terms is still open. The question is: for how long?

The Compounding Intelligence series

Five standalone points of view on scaling agentic AI in insurance. Each paper is written to be read on its own; together they form a single argument.

1

The Orchestration Gap

Why record AI investment is not compounding, and why the window for foundational choices is narrower than it looks.

2

The Insurance Company of 2035

The destination: how an agentic enterprise runs, and how four core insurance roles change.

3

Owned Intelligence

The strategic case for controlling what your AI learns, across six dimensions, and the tiered architecture that makes it practical.

4

The String of Pearls

Reimagining the value chain from business outcomes, and sequencing capabilities so each inherits the intelligence of the last.

5

This paper The AI Orchestrator

What enterprise orchestration requires in practice, and six questions that surface the decisions worth making now.

Did you find this useful?

Thanks for your feedback