Tags
Financial services
Banking & capital markets
Insurance
Insights
AI operationalisation is transforming banking and insurance, enabling organisations to run AI reliably, govern decisions, and explain outcomes.
Why AI operationalisation matters
Most banks and insurers now have AI running in real processes such as onboarding, claims, underwriting and financial crime. Few can run it reliably at scale or show what it did and what it returned and even fewer can reconstruct a single AI decision from last month: what information it used, which version of the model was running, what instructions it followed, who approved it and what it cost. The model usually works. What fails is everything around it.
Who needs to think about AI operationalisation
Chief Operating Officers (COOs) and operational leaders moving AI from experimentation into production, alongside the data, technology and AI leaders responsible for building, governing and operating it.
Why AI operationalisation in banking and insurance raises the stakes
A poor AI decision in banking and insurance rarely stays small. Credit, Know Your Customer (KYC), pricing and claims decisions are revisited through complaints, lookbacks and past business reviews, sometimes years later, and a named executive answers for them. The same flaw applied across thousands of cases becomes a remediation programme.
Many of these decisions also rest on data the firm does not control, such as company registries, sanctions lists, credit bureaux and broker submissions, and on AI inside vendor platforms. In insurance, decisions made under delegated authority add another layer the carrier remains accountable for. AI that cannot be run and evidenced in this environment is a liability, however well the model performs.
How AI operationalisation addresses the challenge of Generative AI and agents
With traditional AI, a firm validated a model and it behaved the same way until someone changed it. GenAI and agents behave differently from day to day, because what they are given, what they remember and what they are allowed to do keeps changing. In practice:
The answer depends on the context. The same model gives a different answer depending on the documents and data it is given.
They remember. Information carries across steps and cases, and so do mistakes.
They act. Agents update records and call other systems, so what they are permitted to do needs the same thought as a new employee's access.
A decision cannot simply be re-run to check it. Outputs vary, so the only reliable evidence is a record kept at the time.
Every decision has a running cost. Usage-based charges scale with volume and grow when agents repeat steps.
They change without a release. The provider updates the model, the data is refreshed and someone edits the instructions, often with no change request.
The value and the risk now sit around the model. That is the problem AI operationalisation solves.
What AI operationalisation means
AI operationalisation means turning an AI model into a working business system: one that runs reliably at scale, has a clear owner and can show what it did and what it returned. In practice, it involves:
Data the AI can rely on, with agreed meaning, data contracts and a named owner.
A redesigned workflow, where AI handles routine cases and people handle exceptions.
A business owner for each AI system.
A record of every decision, so it can be reconstructed.
Ongoing checks on quality, drift and cost.
Controls built into daily running, including who can switch it off.
Behind that sits a system with more parts than most firms track. Take an AI agent carrying out KYC checks on a new corporate client. The model is one component. Around it sits everything below.
Component
What is it
What goes wrong
Data and context
The information the AI is given for each case.
Out-of-date sanctions data or the wrong customer file, with a confident answer.
Instructions and tools (the harness)
The rules, instructions and system access the AI works within.
It can change records it should only read; policy sits in instructions nobody reviews.
Memory
What the AI carries from one step or case to the next.
One customer's details turning up in another customer's case.
Model
The AI engine, usually bought from a third party.
The provider updates it and behaviour shifts with no change on your side.
Traces
A record of what the AI saw, did and decided in each case.
No way to show why a case was cleared.
Monitoring and observability
Ongoing checks on quality, drift and cost, and the ability to investigate problems.
Accuracy slips for months unnoticed; incidents investigated by guesswork.
Human control
Who reviews, who escalates and who can switch it off.
Reviewers approve by default; nobody is clearly authorised to stop it.
How can leaders get there
The firms making progress do four things, broadly in this order.
1. Start from one live system
Trace one real decision end to end rather than starting with a strategy document. It shows quickly where the gaps sit, in the data, the workflow or ownership, and gives each gap a named owner.
2. Know what each system costs per decision
Attribute usage costs (tokens) to decisions and outcomes, and include the review time, rework and exceptions around the model. A pilot that looks successful can turn out to cost more than the process it replaced, usually because every output is still checked by hand.
3. Redesign the work and the operating model
Decide, decision by decision, what AI handles alone, what gets spot checks and what always needs a person. Roles shift towards supervising and handling exceptions, and each agent needs a named owner with clear decision rights.
4. Build controls into daily running
Records are captured automatically and quality thresholds trigger review on their own. The evidence an auditor or supervisor needs is produced as the system runs, which makes each new use case easier to approve.
Firms that get this right can answer a challenge on any AI decision with evidence, instead of rebuilding it from memory. They know what each system costs per decision, so money moves from pilots that do not pay back to those that do. Each new use case also becomes easier to approve, because the records and controls already exist.
What is next in your AI operationalisation process?
1. Ask your operations and data leads to run a trace test on one live AI system.
Expect a note showing whether a single decision can be fully reconstructed, including the data used, model version, prompts or instructions followed, approvals obtained, and the total cost of producing the outcome. The report should also highlight how long it took and any gaps uncovered.
2. Ask your Chief Data Officer, Chief Information Officer or AI governance lead for an inventory of production AI systems.
Expect a consolidated list of all live and production-ready AI systems, including those embedded within vendor platforms. For each system, the inventory should identify the business owner, technical owner, key components, critical data dependencies, and associated data contracts.
3. Ask the business owner of each AI system to demonstrate and test the switch-off process.
Expect confirmation of who is authorised to suspend or disable the system, the circumstances under which they would do so, and the date of the most recent test. Any systems without a tested shutdown process should be highlighted as a priority risk.
4. Ask finance and operations to report cost per decision alongside performance metrics.
Expect cost per decision to appear in the monthly performance pack next to accuracy and business outcomes. The calculation should include model costs, infrastructure consumption, third-party services, and manual review or intervention effort where applicable.
5. Ask AI governance, risk and technology teams to identify the highest-risk dependency for each AI system.
Expect a short summary of the most critical dependency for each system, whether data, model, vendor, infrastructure, or human oversight, together with any existing controls and mitigation plans.
How Forvis Mazars can help
Our AI Operationalisation Framework brings these practices together across four areas: operational maturity assessment, intelligence accounting, workflow and operating model transformation, and governance and assurance.
We can help you review a production or production-ready AI system, identify the operational gaps around it and define practical actions to strengthen control, evidence and performance.
Get in touch with us now to understand how AI operationalisation can help your firm.
AI is no longer a future consideration for asset managers. As AI enters its Return-On-Investment (ROI) or return-on-AI era, firms are expected to focus on demonstrating and realising its tangible value.
Financial and actuarial modelling has always evolved in response to increases in scale, regulatory scrutiny and business expectation as well as advances in technology.
Key contacts
James Isherwood
Partner - Head of Insurance Consulting
-
London