InsuranceIRIS8
A model trained on your own book
For claims, underwriting and operations leaders: a model trained on your claims and policy documents, run inside your VPC or data centre by IRIS8.
How it fitsIRIS8
Where the model sits in your claims operation
It reads the claim where it arrives, prepares the file, and routes it to your adjuster.
Your VPC or data centre
Your people
Your systems
Added by IRIS8
IRIS8 engineerScoped, logged access
Your records
Use casesIRIS8
Where carriers start
Each of these is a place a pilot can begin.
- Claims intake and triage
- Claims file summaries
- Policy document extraction
- Underwriting submission prep
- Subrogation review
- Customer correspondence drafts
- Policy questions for agents
- 01
First notice of loss in
- 02
Claim type and details extracted
- 03
Police report missing, flagged
- 04
Routed to adjuster
For your reviewersIRIS8
What risk and security will ask
These are the questions we are asked first, with the answers we give.
- 01
Does the model decide claims or set prices?
No. It reads, extracts, summarises and drafts. The adjuster or underwriter decides, and the record shows who reviewed each file.
- 02
Where are medical records and accident reports processed?
Inside your VPC or data centre. They are not sent to a public API.
- 03
What is the model trained on?
Your own claims, policies and underwriting files, inside your environment. The model record lists the datasets used.
- 04
Can we produce the model's history ourselves?
Yes. The model inventory, version history, test scores and request log are yours to show, first-hand.
- 05
Who at IRIS8 can reach our environment?
Named engineers with scoped, task-bound access. Every action they take is written to the same record.
Model record · claims-intake v2
- Base model
- Open-weight, licence checked
- Training data
- Closed claim files, personal data masked
- Benchmark
- Passed at the pass mark set by Head of Claims
- Approved by
- Head of Claims
- Deployed
- Your VPC
- Access
- IRIS8 engineer, scoped, logged
- Previous version
- v1, kept for rollback
One record of the data, training, scores and approvals.
Take this with youIRIS8
A scoping sheet for a claims pilot
Fill in these eight lines and you have what we ask for on the first call.
A scoping sheet for a claims pilot
- 1Line of business
- 2The workflow, in one sentence
- 3Who does it today, and who would review the model's output
- 4Documents that go in
- 5What a good output looks like (attach three examples)
- 6The one KPI that would show it works
- 7Where the model would run: VPC or data centre
- 8Security and risk contacts for data access
iris8.ai/insurance.html
Training dataIRIS8
Your book is the training data
Years of claims, policies and underwriting files are data no API vendor has, and the model is tuned on them.
Nothing crosses this line
BudgetsIRIS8
Gateway · live requests
- Summarise claim fileyour model
- Extract policy termsyour model
- Repeat questioncache
- Draft coverage letterfrontier model
Claimant ID masked before sendEvery request logged
Your model takes routine work. A frontier model you choose takes the rest.
Budgets for claims-season volume
Summaries, extraction and triage at carrier volume run under budgets you set per team.
Run your numbersQuestionsIRIS8
Questions
Talk to usQ1Which line of business should we start with?
One with high volume and clear right answers. Motor and property claims intake are common first picks.
Q2How many past claims do you need?
Enough reviewed examples to build a test set and a training set. We size it in the first week of the pilot.
Q3Do we need our own ML team?
No. Your claims experts set the pass mark and review sample outputs. IRIS8 does the rest.
Q4Can the model use a frontier model for hard cases?
Yes, through your gateway and by rules you approve. There is no lock-in to one model vendor.
Q5How is the pilot priced?
Fixed price, one use case, credited to year one.
Next stepIRIS8