The right question is not where tasks can be automated, but which parts of the business, fundamentally reimagined, would change the financial picture. Then: sequence the build so every capability inherits the intelligence of everything that came before it.
About this point of view
Most insurers approach AI by asking where in the business they can apply it. The instinct is understandable. It is also the wrong starting point.
This paper, the fourth in the Compounding Intelligence series, sets out the alternative: start from the business outcome, identify the functions where reimagination would generate the most consequential change, and sequence the build so that value compounds rather than fragments. Each paper in the series stands alone; this one is about architecture and sequencing, the decisions that determine whether ten AI solutions produce ten separate outcomes or one enterprise that gets smarter with every transaction.
01
The right question is not where tasks can be automated, but which parts of the business, if fundamentally reimagined, would change the financial picture. Starting from a business outcome, whether that is a targeted improvement in expense ratio, a step change in claims cycle time, or a structural reduction in processing costs, changes everything about what gets built and in what order.
In our work with insurers, we apply a Vision 2 Value approach to do this systematically. It maps the insurer's full value chain and surfaces the functions where agentic AI reimagination would generate the most consequential change. The goal is not incremental automation, but wholesale redesign of how the work is done to unlock outcomes previously out of reach.
The output is a re-imagination of specific business functions: what they could look like if the work were redesigned from first principles around AI and human capability working together, what outcomes that redesign would produce, and what the path from today's state to that future looks like. This is where the architecture decision becomes concrete.
Build use case by use case, each on its own stack and data.
Governance and cost complexity compounds with every addition.
Ten solutions producing ten separate outcomes. Additive at best.
Most insurers are on this path today.
Start from the business outcome. Map the value chain. Identify where reimagination creates the most value.
Sequence use cases so each one inherits the intelligence of everything that came before it.
Every new capability makes the whole more capable. Multiplicative.
The carriers pulling ahead are making this choice now.
What this looks like in practice varies by function. In underwriting, reimagination means agentic systems handling submission intake, data extraction, appetite screening, and initial risk scoring, redirecting the underwriter entirely toward complex placements, emerging risk categories, and the relationship-intensive decisions where their expertise creates genuine value. The workflow is rebuilt from first principles around what humans do best and what agents do best, rather than automating steps within an existing process that was never designed for AI.
In claims, reimagination means moving from a linear, handoff-driven process to a continuous, intelligent one. First notice of loss triggers immediate triage, coverage validation, and routing. The agent manages documentation, status updates, and straightforward settlements end to end. The adjuster steps in only where judgment, empathy, or complexity genuinely warrant it. The customer experience improves because the process was redesigned around the outcome, not the org chart.
In sales and distribution, reimagination means advisors and brokers supported by real-time intelligence: risk-adjusted quotes available instantly, proactive coverage recommendations based on life events and portfolio changes, and routine service interactions handled by agents so that human capacity is reserved for the conversations that define the relationship.
The common thread across all three is that the business and technology design work happens together, not in sequence. Workforce implications are not an afterthought to be managed once the platform is live. They are a design input from day one. What that requires in practice is the subject of The AI Orchestrator, the fifth paper in this series; how these redesigned roles look once the shift is complete is described in The Insurance Company of 2035, the second.
Once the highest-value functions are identified, the question becomes sequencing. How do you build toward that future in a way that compounds rather than fragments? This is where we apply what we call the string of pearls architecture. A pearl has value on its own. String them together and something qualitatively different emerges: each capability inheriting the intelligence of everything that came before it, producing outcomes that no individual solution could deliver alone. (Deloitte Canada, Future of Insurance Point of View, 2025)
Most AI portfolios are collections of capabilities each solving its own problem on its own data, producing, at best, ten solutions with ten separate outcomes. But when claims intelligence feeds underwriting in real time, underwriting feeds pricing at the individual risk level, pricing feeds distribution, and compliance monitors the whole continuously, something fundamentally different happens. The system becomes more capable than any of its parts, producing outcomes categorically beyond what individual tools can deliver.
Eight pearls illustrate how this plays out in practice. Governance runs through all of them. When the entire chain flows through a shared, observable platform, regulatory requirements stop being a friction point and become a built-in property of how the system works.
The sequencing decisions matter as much as the capabilities themselves. You cannot retrofit connection onto a system that was built for isolation. The shared data foundations, common orchestration layer, and governance controls must be in place before the pearls are added, or each new capability becomes another silo.
The insurers we see pulling ahead are not running smarter pilots. They rebuilt the question. Not "where can we deploy AI?" but "which parts of this business, reimagined, would change the outcome?"
What makes this sustainable is the shared foundation underneath it. Authentication, observability, orchestration, and governance controls: built once, available to every capability added afterward. The cost of each new pearl decreases as the platform matures, and the ability to operate that foundation across regulatory regimes and data sovereignty requirements is what makes this viable for carriers operating beyond Canada. Who owns that foundation, and the intelligence it accumulates, is the question we take up in Owned Intelligence, the third paper in this series.
|
|
|
|---|---|
Q1 |
Which parts of the business, if fundamentally reimagined rather than incrementally automated, would change the financial picture? |
Q2 |
Are the shared data foundations, orchestration layer, and governance controls being designed before capabilities are added, or retrofitted after? |
Q3 |
Does each new capability inherit the intelligence of everything that came before it, or does it start fresh on its own stack? |
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 |
Why record AI investment is not compounding, and why the window for foundational choices is narrower than it looks. |
2 |
The destination: how an agentic enterprise runs, and how four core insurance roles change. |
3 |
The strategic case for controlling what your AI learns, across six dimensions, and the tiered architecture that makes it practical. |
4 |
This paper The String of Pearls Reimagining the value chain from business outcomes, and sequencing capabilities so each inherits the intelligence of the last. |
5 |
What enterprise orchestration requires in practice, and six questions that surface the decisions worth making now. |