AI Development for Insurance
AI development for insurance is the practice of building underwriting, pricing and claims AI that regulators and policyholders can be shown to be fair. It covers explainable decisioning, testing for proxy discrimination against protected classes, governance documentation aligned to the NAIC model bulletin and New York DFS Circular Letter 2024-7, and vendor-model oversight.
Part of Appsierra's Insurance & Insurtech engineering practice — see the full vertical overview.
What do insurance regulators actually expect from AI systems?
The NAIC adopted its Model Bulletin on the Use of Artificial Intelligence Systems by Insurers in December 2023, and it has been the template for state adoption since. It applies across underwriting, rating, claims and marketing, and its central requirement is an AI governance framework ensuring systems are accurate, reliable, explainable and free from unfair discrimination.
New York went further in July 2024 with Circular Letter 2024-7, covering AI and external consumer data in underwriting and pricing. It expects insurers to demonstrate that systems do not proxy for protected classes or produce disproportionate adverse effects, to keep explanatory documentation, to allow regulator review of vendor tools, and to maintain internal oversight. These are engineering requirements as much as compliance ones.
How do you test an underwriting model for unfair discrimination?
The work centres on measurement rather than intention. Protected attributes are usually absent from the feature set, so testing focuses on whether outcomes differ across groups and whether permitted features act as proxies. That means estimating group membership carefully for testing purposes, measuring disparity in approval, rating and pricing outcomes, and probing which features drive any gap found.
External consumer data deserves particular scrutiny, because it is where disparity most often enters. A data source assembled for marketing may encode geographic or behavioural patterns that correlate strongly with protected characteristics. Testing it before adoption — and re-testing as it updates — is considerably cheaper than discovering the problem through a market conduct examination.
Who is accountable for a vendor's model?
The insurer is. Both the NAIC bulletin and the New York circular make clear that using a third-party model does not transfer responsibility for its behaviour, and New York expects regulators to be able to review vendor tools. This has a direct engineering consequence: you need contractual rights to documentation and testing access, and an internal capability to evaluate a model you did not build.
In practice that means treating vendor models as components you must independently validate — running your own disparity testing on their outputs against your book, monitoring their performance over time, and maintaining your own record of that oversight rather than relying on the vendor's assurances.
How does Appsierra help insurers build AI responsibly?
We pair AI engineers with evaluation engineers so that disparity testing, explainability and monitoring are built alongside the model, and the documentation regulators ask for exists as a by-product of development rather than a retrospective exercise.
We also perform independent evaluation of models an insurer has bought or built elsewhere, which is often the faster route to the oversight evidence the NAIC framework expects. We are an engineering and evaluation partner, not your compliance function or legal adviser.
Frequently asked questions
Ship higher-quality insurance software, faster
Appsierra's expert-supervised AI & LLM engineering pods are productive in days and de-risked by our own evaluation platform — with senior accountability and a low-risk pilot. Tell us what you're building.