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
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.
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? |
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? |
Q3 |
Sovereignty Can the current platform operate in every geography the organization serves, including markets with data residency requirements or cloud provider restrictions? |
Q4 |
Governance Is governance embedded in how agents are built, or is it addressed primarily through post-deployment review processes? |
Q5 |
Workforce Are the human and agentic workforce being designed together, or is workforce evolution expected to follow the technology deployment? |
Q6 |
Optionality If the economics of a key AI vendor relationship changed materially, would the organization have meaningful flexibility to respond? |
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.
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?
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 |
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. |