AI in regulated industries: why explainability has to come first

Regulated industries get a reputation for being slow with AI. Look closer and most of them aren't slow, they're careful. In insurance, lending or healthcare, a decision has to make sense to the customer, stand up in front of a regulator and, sometimes years later, be reproduced exactly as it was made.

That doesn't rule AI out. It changes how you build with it. The firms getting results are the ones that design for those demands from day one, not the ones that bolt them on at the end.

Where AI earns its keep

In a regulated business, the gains tend to show up in four places:

  • Time to market. Work that used to take months, such as building a new product or reworking a rate structure, can be drafted and tested in days.
  • Consistency. A well-tested process applies the same rules every time, where manual work varies from person to person.
  • Where experts spend their time. Less keying in and reading through documents, more judgement.
  • The paper trail. Processes built around AI usually log, version and test more than the ones they replace.

That last one surprises people. Done properly, bringing in AI can leave a firm with a clearer record of how its decisions are made than it had before.

What regulators are looking for

The rules differ by market, but the themes are much the same.

  • UK. The FCA's Consumer Duty expects firms to deliver good outcomes and fair value for retail customers, and its general insurance pricing rules, in force since January 2022, stop firms charging renewing home and motor customers more than equivalent new ones. Firms need to be able to show how a price was set. We cover this in more detail in fair value under Consumer Duty.
  • EU. The AI Act treats AI used for risk assessment and pricing of individuals in life and health insurance as high-risk, which brings duties around risk management, data governance, documentation, transparency and human oversight.
  • US. The NAIC has adopted a model bulletin on insurers' use of AI, which a growing number of states have taken up. It expects a written AI governance programme and evidence that AI-supported decisions comply with insurance law, including the rules on unfair discrimination.

The common message: use AI by all means, but be able to show how each decision was reached.

Build it in, don't bolt it on

One approach is to take a model that was never meant to be explained and try to generate explanations for it afterwards. That tends to be fragile. It is far more dependable to make explainability part of how the system works:

  1. Logic people can read. Hold rates and rules as readable configuration, not program code, so the model documents itself.
  2. A trace for every decision. Record the inputs used, the rules checked and the value produced at each step, so any decision can be replayed.
  3. A version for every change, with each decision tied to the version that made it.
  4. Tests as proof. Run a set of known cases with expected results on every change, and keep the results.
  5. A person signs off. AI can draft and propose. A named person approves before anything goes live.

Let AI draft, and people decide

The pattern that works for the business and the regulator is the same. AI does the drafting, extraction and checking at speed. Accountable people review and approve. The AI makes the work faster, and the way the system is designed makes it defensible.

That is how Swallow approaches pricing. Models are plain JSON with labelled inputs, rate tables as rows and formulas written out, so an underwriter can review a change without reading code. Tests live on each version. Any quote can return a full trace of every input, lookup, formula and rule, and is saved with the version that priced it.

AI clients connected through the Swallow MCP server can draft a model, validate it and run its tests, but no MCP tool creates, edits or publishes a project. The agent hands the model to a person, who uploads it to a draft in the dashboard. From there it is approved and published by people your team's roles allow, and each step is logged with who did it and when. Our post on using Claude and ChatGPT to build pricing models shows the workflow end to end.

In short

Regulated firms don't have to pick between using AI and meeting their obligations. Explainability, testing and human sign-off are what let an AI project go live at all, and the firms that plan for them early usually end up moving faster.

Continue reading

From filing to rater: building pricing models from US rate filings

What sits inside a US rate filing, how to rebuild it as a working, tested rating model, where AI speeds things up and which gaps to expect.

Swallow compared: enterprise pricing platforms, core system raters and AI newcomers

Where Swallow sits against established insurance pricing and rating platforms and newer AI-led options, on model format, testing, approvals, AI and distribution.

Building pricing models with Claude and ChatGPT: what works, what doesn't

A practical look at building insurance pricing models with Claude and ChatGPT over MCP: where AI clients help, where they trip up and how to keep people in charge.

AI in insurance pricing: closing the gap between rating guide and live model

Pricing design is rarely the bottleneck. Implementation is. How AI shortens the path from signed-off rating guide to a tested, live pricing model.

Fair value under Consumer Duty: the evidence your pricing should leave behind

What the FCA's Consumer Duty and pricing rules ask of insurance pricing teams, and the records that make fair value something you can show, not just claim.

When the customer is an AI agent: getting your pricing ready

AI assistants are starting to shop for insurance on people's behalf. Here's what your rating engine has to give them to quote your products properly.

How to connect the Swallow MCP server to Claude

Connect Claude to your Swallow pricing infrastructure using MCP to analyse models, inspect rating logic and interact with your tools using natural language

Regression testing insurance pricing: why every rate change needs a test suite

How to build a regression test suite for an insurance pricing model, from worked examples and band edges to declines, refers and real quotes.

A safer rate change: eight steps from analysis to monitoring

A repeatable process for insurance rate changes, from the change statement and draft version to tests, approval, release and monitoring, and where AI helps.

Readable by design: pricing models people can check, even when AI writes them

When AI drafts pricing logic, review becomes the slow step. Why a declarative, readable model format is faster to check and audit than generated code.

Moving off a spreadsheet rater without changing a single price

How to tell when an Excel rater has outgrown its job, what keeping it really costs, and a migration plan that uses the spreadsheet's own answers as the tests.

Starting an MGA: from rating guide to first live quote

A practical route for a new MGA's first product: agreeing terms with capacity, building and testing the model, picking channels and watching rates after launch.

AI and insurance distribution: one price, every channel

Aggregators, embedded journeys, chat, voice and AI agents all need the same thing from pricing. Why one explainable rating engine should sit behind them all.

Swallow vs Earnix

Swallow and Earnix Price-It compared for insurance pricing and rating: who each is for, how models are built, tested and released, how AI is used, and distribution.

Swallow vs Guidewire PricingCenter

Swallow and Guidewire PricingCenter compared: who each suits, how each relates to PolicyCenter, how models are built, tested and released, AI and distribution.

Swallow vs Duck Creek Rating

Swallow and Duck Creek Rating compared: who each suits, suite and standalone use, how rates are built, tested and released, deployment, AI and distribution.

Swallow vs Oracle Insbridge

Swallow and Oracle Insurance Insbridge Enterprise Rating compared: architecture, how rates are built and changed, testing, integration, AI, and how to migrate.

Swallow vs Akur8 Deploy

Swallow and Akur8 Deploy compared: where each rating engine fits, how rates reach production, testing and sign-off, how AI is used and when to pick which.

Swallow vs hyperexponential (hx Renew)

Swallow and hyperexponential's hx Renew compared: who each suits, Python models versus readable JSON, testing and approvals, AI and the Guidewire deal.

Swallow vs WTW Radar

Swallow and WTW Radar compared for pricing and real-time rating: who each suits, how models are built and changed, testing and approvals, and AI features.

Swallow vs building a rating engine in house

Build or buy? A fair look at writing your own insurance rating engine versus using Swallow: testing, versioning, audit, serving at volume and rate changes.

How to connect the Swallow MCP server to ChatGPT

Connect ChatGPT to your Swallow pricing infrastructure using MCP to analyse models, inspect rating logic and interact with your tools using natural language

Swallow Data: Live insight into your pricing performance

See how Swallow’s Data area gives you real-time visibility over quotes, performance, and customer behaviour across your entire pricing model

Swallow Tests: Validate your pricing with real-world scenarios

See how Swallow’s Tests area lets you simulate quotes, inspect calculations, and perfect your pricing model before publishing

Swallow Build: Bring your pricing model to life

A quick look at how Swallow’s Build area lets you edit, test, and publish pricing models with complete control and instant feedback

Swallow Overview: Core features at a glance

See how the AI actuary inside Swallow turns a simple prompt into a fully tested and deployable insurance pricing model for electric vehicles in just a few clicks

Why Modern Insurers Are Moving to AI-Powered Enterprise Pricing Engines

A look at how AI is transforming insurance pricing, from spreadsheet-based models to enterprise-grade rating engines built for speed, consistency, and control

Swallow / MGT

How MGT use Swallow to power AI-driven pricing, accelerate model updates and support fast, reliable commercial insurance quoting.

AI Agent for Insurance Products

Sam talks through our new AI Agent for Insurance products. Get a new Insurance product built and live within a couple of minutes.

Swallow / Ouch!

How Ouch! used Swallow to launch digital takaful products faster, with transparent pricing, audit readiness and seamless model updates.

Pricing Pain Point #4 - Slow deployment

Whilst the modelling process is where pricing strategy begins, getting changes in front of customers is where the rubber hits the road and new pricing is tested with real customers. Moving quickly to make changes to live pricing offers pricing teams an opportunity to respond to the market, test and iterate, and roll out new products.

Pricing Pain Point #3 - Testing concerns

With pricing critical to growth and profitability, businesses must understand the impact of any price changes, as well as ensure what goes live to customers is identical to that modelled. With pricing driven by complex financial models, this is particularly true - a percentage point error in the code deployed could easily lead to a significant financial impact.

Swallow / Open

How Open used Swallow to launch embedded insurance in the UK faster, with flexible pricing, rapid updates and lower operational cost.

Pricing Pain Point #2 - Lengthy process

In any fast moving business, having a clear record of decisions, changes and their impacts is key to operating efficiently and successfully. For regulated industries, a clear governance process is a requirement and critical to ensuring compliance with local regulations.

Pricing Pain Point #1 - Data issues

Underlying all pricing strategy is data, whether it be on the market and competition or a company’s own quote, sales and cost data. Collecting this data and using it to inform future pricing decisions is one of a pricing team’s key objectives.

Swallow / Rivr

How Rivr uses Swallow to deliver pricing models faster, with better governance, smoother client handovers and one-click deployment.

What we've learned about pricing

Over the past few months, we've talked to over 100 pricing and technology professionals from a range of industries. From our conversations, many pricing pain points have emerged, helping us to better understand the challenges businesses face and inform the direction of our platform.

Why I created Swallow

Financial pricing models (think insurance, credit, mortgages, financing, leasing, memberships) have, and continue to be, designed in spreadsheets and published through in-house custom code or legacy enterprise software. Pricing changes can take weeks instead of hours.

We feel you, pricing is hard...

Dynamic pricing is hard to create and serve to your customers. Because it is hard, it can become a technical concern rather than a business concern. Here be where the dragons lie.