Insurance Business Architecture: AI Blueprint | Capstera

The Insurance Business Architecture Reference Model brings the capabilities, value streams and data of an insurer into one package with the AI layer built in. It covers the work insurers share and three segments, Health Insurance, Life Insurance and Annuities, and Property and Casualty Insurance, with 24 value streams, a 112-entity data model, 60 agent specification starters, 91 use cases and 55 controls, and every segment item is tagged so you can filter to your own. Business and enterprise architects load it into the Capstera platform with the import files, and their AI assistants query it through MCP.

What the Insurance Business Architecture Reference Model Is

The Blueprint edition holds the full business architecture of an insurer, with the AI layer built in. It includes everything in the Capability Model edition and builds the rest of the architecture around it. Its 24 value streams follow the work end to end, from a submission to a bound policy, a claim notified to a claim closed, a fraud referral to a closed investigation, and a valuation date to booked reserves. Each of the 120 stages is described as it works today and as it would work AI-native, with the human checkpoint stated at every stage, and 42 standard value streams come with them.

Beneath the value streams is a data model of 18 subject areas, 112 entities, 811 attributes and 379 relationships, with each entity marked for sensitivity and for the data quality AI needs from it. The AI layer then becomes specific. The 60 agent specification starters state what each agent may read and do, its guardrails and when it hands back to a person, and they share one rule: no agent declines an application for insurance, denies or reduces a claim, decides that care is not medically necessary, cancels, rescinds or nonrenews a policy, sets a premium outside an approved rating plan or decides whether suspected fraud is referred to an authority, and an agent pays a claim only where an approved rule releases it in full. The 91 use cases are written as business cases tied to capabilities, value streams, agents and data, and the 55 controls tie each risk tier to the evidence an owner keeps.

All three segments run through every layer of the blueprint. Health Insurance brings streams from a provider application to a contracted provider, an authorization request to a care decision, an enrollment file to a covered member, and a health claim received to a provider paid. Life Insurance and Annuities follows an application to an issued life policy, an annuity contract to a started payout, and a death notification to a paid benefit. Property and Casualty Insurance covers a first notice of loss to a repaired or settled loss, a catastrophe forecast to closed event claims, and a commercial submission to a bound account. Their entities, agents and use cases carry the same segment tag in the workbook.

The Problem It Solves

AI ideas are not scarce at an insurer. What is missing is a way to see how one idea touches the rest of the business: which stage of which value stream it changes, which data it depends on, who approves its output and which control shows it behaved as intended. The question is sharper here than in most industries, because a wrong output can decline a sound applicant, underpay a claim, refuse needed care or end someone's coverage, and a group that writes more than one line faces it several times over: a group health renewal, a death claim and a catastrophe claim run on different data and different decisions.

In this blueprint those pieces are connected before any project starts. A proposal maps to capabilities and stages, the stages name their data, the agents and use cases state their oversight and risk tier, and the controls and the operating model say who owns the result. Leadership can compare proposals from the health plan, the life and annuity business and the property and casualty business on the same terms, and plan the shared work once instead of once per business.

What's Inside

The Blueprint holds everything in the Capability Model edition and the rest of the architecture around it:

• Everything in the AI-Ready Capability Model edition: 9 L1, 49 L2 and 221 L3 insurance capabilities, with definitions to L3 and 196 KPIs at L2, an AI profile for every L2, AI ratings for every L3, prioritization, the AI heatmap and a 40-question readiness assessment
• 24 insurance value streams, 120 stages with their steps, each described today and AI-native, with the human checkpoint at every stage, plus 42 standard value streams
• An AI-ready business data model: 18 subject areas, 112 entities, 811 attributes and 379 relationships, with sensitivity and data-quality requirements
• 60 agent specification starters with tool permissions, guardrails and escalation paths
• 91 use cases as structured business cases
• 55 controls and responsible AI principles, tied to risk tiers
• An operating model: governance bodies, a RACI, an agent lifecycle, role impacts and new roles
• A three-wave roadmap
• A Welcome document, a leadership presentation template to adapt, the capability map deck, standalone documents for the capability definitions, KPIs, data model, agent specifications, use cases and AI governance, a value streams deck, the Excel workbook, the implementation guide, and import files for the Capstera platform
• Bonus files: an insurance glossary, insurance roles and how AI changes them, operating model archetypes for insurance, an insurance transformation overview and framework, A Practical Guide to Business Architecture, a capability modeling overview, an AI-ready capability profile template, capability relationship mapping templates, a framework-to-enablement deck, a capabilities to microservices and AI agents mapping example, and a business architecture leader role guide
• Free corrections, new versions free for 180 days, and MCP access for your AI assistants for the same 180 days

Every file names your organization and carries your license ID. Ratings describe a typical large enterprise and are a starting point for your own.

Use Cases

Designing agents for claims and underwriting work. Start from an agent specification such as the claim intake and triage agent, the prior authorization review agent or, for a property and casualty insurer, the exposure accumulation monitoring agent, and adapt its permissions, guardrails and escalation paths to your systems. Claims, underwriting, medical management and risk leadership then approve one document before anything is built.

Redesigning a value stream for AI. Take a stream such as a claim notified to a claim closed, compare each stage today with its AI-native version, and decide where the human checkpoint stays. Process owners get a concrete draft to work from instead of a blank page.

Building a use case portfolio. Use the 91 use cases as a starting portfolio, score them with your own value and data readiness ratings, and keep those that fit your segments. Each one already names the capabilities, value streams, agents and data it touches.

Setting up AI governance for insurance decisions. Adapt the responsible AI principles, the 55 controls, and the operating model's governance bodies and RACI to the way the organization already decides underwriting, claim, fraud and care authorization matters. The risk tiers and the decision rights tell the governance group which agents and use cases need its review and who approves each one.

Planning the data foundation. Compare the data model's entities, sensitivity markings and data quality requirements with the policyholder, member, claim and underwriting data you hold. The gaps become the data work that has to come before the use cases that depend on it.

Briefing the executive committee. Adapt the leadership presentation template to show the ranked capabilities, the first wave of use cases and the governance proposal. Leaders see the plan in terms of their own lines of business.

Who Uses It

Enterprise and business architects. Use the blueprint as the reference architecture for the insurance business, link it to the enterprise model, and tailor the segments to the organization's lines of business.

Chief operating officers and heads of insurance operations. Use the value streams and the roadmap to agree on where AI changes operations first and which decisions stay with named people.

Underwriting, claims and special investigations leaders. Review the agents, use cases and controls in their areas, set the human checkpoints, and decide which controls their teams will own.

Actuarial, reinsurance and capital leaders. Check the reserving, reinsurance and supervisory reporting streams against how their teams close a period, and confirm who signs off each estimate and each return.

Health plan network, medical management and pharmacy leaders. Use the health streams and agents to plan AI in enrollment, prior authorization and claims, with the Utilization Review Nurse approving each prior authorization an agent prepares.

AI and transformation program leads. Use the use case portfolio, the operating model and the three-wave roadmap to staff and sequence the program across lines of business and segments.

Build It, Hire It, or Start Here

An insurer that wants a business architecture with an AI layer has three ways to get one, and the difference lies in how much of the effort goes into structure that every insurer shares.

• Building it from a blank slate. The team elicits capabilities, maps value streams with each line of business, models the data, and then designs agents, use cases and controls on top. Each layer depends on the one before it, so the AI work waits until the architecture is settled, and keeping the layers consistent takes repeated review.
• Hiring consultants to build it. A firm runs the elicitation and delivers the layers, often from its own internal starting point. Much of the effort pays for drafting what is common to insurers, and the links between layers are only as consistent as the firm's own checks.
• Starting from this model. The team starts with every layer already linked: capabilities to stages, stages to data, agents and use cases to both, and controls to risk tiers. Workshops go to setting aside segments the organization does not write, adjusting ratings and oversight, and naming the approver for each decision.

Advisers who know your organization still have work to do: tailoring the blueprint to your lines of business and leading the change. Starting here lets that work begin at the first meeting.

How to Get Started

These steps take a team from the download to a first wave of AI work that leadership has approved:

1. Read the Welcome document and the implementation guide for the order in which the files are meant to be used.
2. Filter the workbook's Segment column to the shared items and the segments your organization writes.
3. Review the value streams with process owners and mark where your stages differ from the reference.
4. Check the data model against the policyholder, member, claim and underwriting data you hold and list the gaps.
5. Score the use cases and agents with your own ratings, and name the approver for each decision before choosing the first wave.
6. Adapt the operating model, the controls and the leadership presentation, and take the plan to leadership.

Read the Public Sample

The sample follows one thread through the package, claim intake and triage, and is 0.63% of the content. From the Claim Intake and Triage (IN-5.1) AI profile:

• Work patterns: Transactional processing, Rules-based decision, Coordination & orchestration
• Target AI mode: Automate
• Human oversight: Human-on-the-loop
• AI fit / Value / Feasibility / Data readiness: 4 / 4 / 4 / 3 (1–5)
• Risk tier: Moderate
• Roadmap wave: Wave 1
• AI opportunity: Take in claims from phone notes, web forms, email and producers, extract who is claiming, what happened and when, and open the claim record
• What stays human: The Chief Claims Officer approves the claims handling rules, including the triage scores, fast-track criteria and authority levels the assignment applies, prepared by the Claims Manager after hearing the Chief Actuary; no triage rule changes inside this capability

The preview above shows more of the profile, the AI heatmap, an agent card and a value stream stage redesigned for AI. Any MCP client can also query the sample at https://platform.capstera.com/api/mcp/blueprints?package=in without a key.

Connect Your AI Assistant

Your license includes access to the package through MCP (Model Context Protocol). Connect an MCP-capable AI assistant or your own agents, and they look up your licensed content as they work: one capability, agent or control at a time, scoped to your edition and stamped with your license ID. The key arrives with your order confirmation, and access runs for the 180 days in which new versions are free. Setup and limits: AI-ready license and MCP access.

Upgrade Credit

Bought the AI-Ready Capability Model edition in the last 90 days? The full price you paid counts toward this Blueprint. Email support@capstera.com with your order number for a one-time checkout code.

Frequently Asked Questions

What is the difference between the two editions?

The AI-Ready Capability Model covers the capability map, an AI profile for every L2 capability, prioritization, the heatmap and the readiness assessment. The AI Transformation Blueprint adds value streams redesigned for AI, the business data model, agent specifications, use cases, responsible AI principles and controls, the operating model and the roadmap, a leadership presentation template, and bonus files on roles, operating model archetypes and transformation.

Can I upgrade from the Capability Model to the Blueprint later?

Yes. The full price you paid for the Capability Model counts toward the Blueprint if you upgrade within 90 days. Email support@capstera.com with your order number for a one-time checkout code.

What happens after 180 days?

Your license to use the files does not end. Corrections are free for as long as you use the files. New versions released within 180 days of purchase are free, and MCP access runs for the same 180 days. There is no renewal after that: you can buy a new version at 25% off its price. Orders placed before October 27, 2026 keep the 12 months they were sold with.

Can I load the content into our own AI tools?

Yes, within the license. The Enterprise license allows internal tools, including your own assistants and agents. Neither license allows training, fine-tuning or prompting AI systems for third parties.

Does the package cover AI laws and regulations?

No, by design. It is business architecture: capabilities, value streams, data and the AI layer describe what an insurer does and how AI fits, and they hold whichever laws apply where you operate. The risk tiers, principles and controls are durable practices your compliance team maps to your own jurisdictions.

Why not just ask ChatGPT or another AI assistant?

An AI assistant can sketch value streams or suggest use cases for an insurer, and that is useful for a first look. A blueprint has to hold together across its layers. Here every link between capabilities, value stream stages, data entities, agents, use cases and controls is checked before release, IDs stay stable, every agent and use case carries a risk tier, and segment items are tagged so they can be filtered instead of guessed. A generated answer changes with each prompt and checks none of those links, which matters once underwriting, claims and actuarial leaders have to approve the plan.