Skip to content
AtheronLABS

You're visiting from the United States. Prices are shown in US dollars. Not right?

labs@atheron:~/industries/insurance/ai$ train agent --grounded

AI for insurers

Claims photo triage and wording answers for brokers.

Insurance AI is two different jobs. Sorting claims photos depends on your own settlement history, so it is a custom model in your cloud. Answering broker questions from public wordings needs no private data, so a frontier model is the fastest start. We choose the route by the job and the data.

// what matters here

What is different in this industry.

01

Your claims history trains the model

A damage model fine-tuned on how your past claims settled routes new files the way your adjusters would, which a general model cannot do.

02

Adjusters and underwriters decide

Models route files and quote clauses. Coverage, reserves and payments are decided by people, and the system records who decided.

03

Fairness checked, not assumed

We test outcomes across regions, vehicle types and other groups your compliance team names, and report the results before launch and on a schedule after.

04

Private data stays private

Claims photos stay in your own cloud account. The broker assistant only sees public wordings, never a policyholder's details.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appAICustom LLM

Vehicle damage photo model

Hypothetical. Not a client, not a result.

// The problem

Every auto claim photo is opened by an adjuster to decide whether the file is a quick repair or a likely total loss, which slows the simple ones down.

// What we would build

A custom vision model fine-tuned on the insurer's own closed claims photos, served in its own AWS account, that sorts new files by likely severity and the parts affected so the adjuster decides faster. A general frontier model does not know your repair outcomes; yours does.

// What is in it

  • A model fine-tuned on your past photos and how each claim was settled
  • Likely severity and affected parts shown to the adjuster, never sent to the customer
  • The adjuster decides; the model routes and suggests
  • Measured against held-out claims before launch and checked for drift after
  • Served in your own cloud account, with photos kept there

// Stack

  • PyTorch
  • Python
  • Amazon S3
  • Next.js
  • AWS GPU instances

// estimate

Build
≈ US$170,000 to US$259,000, delivered within 38 weeksCAD 241,800 to 369,200
Hosting
≈ US$7,020 a monthCAD 10,000 a month
Support
≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route
Custom LLM
Model running cost
≈ US$6,530 a monthCAD 9,300 a month

Timeline by milestone

Discovery
2.9 to 3.4 weeks
Data and evaluation plan
0.4 weeks
Design approved
2.4 to 3.9 weeks
Core features
2.4 to 3.4 weeks
Full build
1.4 to 2.4 weeks
Training
9.9 to 16.9 weeks
Testing and fixes
0.4 weeks
Evaluation and red-teaming
3.9 to 4.4 weeks
Launch
0.9 to 1.4 weeks
Production
0.9 to 1.4 weeks

How it is paid

Deposit 20%
CAD 48,120 to 73,600
Discovery 1.3%
CAD 3,127.80 to 4,784.00
Data and evaluation plan 8.2%
CAD 19,729.20 to 30,176.00
Design approved 1.3%
CAD 3,127.80 to 4,784.00
Core features 4%
CAD 9,624 to 14,720
Full build 2.6%
CAD 6,255.60 to 9,568.00
Training 24.8%
CAD 59,668.80 to 91,264.00
Testing and fixes 1.3%
CAD 3,127.80 to 4,784.00
Evaluation and red-teaming 16.5%
CAD 39,699 to 60,720
Launch 1.3%
CAD 3,127.80 to 4,784.00
Production 8.7%
CAD 20,932.20 to 32,016.00
Holdback, 30 days after launch (10%)
CAD 24,060 to 36,800
GPU time for training and testing, at cost
CAD 1,200. Billed up front, at cost, outside the milestones
Example projectWeb appAIFrontier model

Broker policy wording assistant

Hypothetical. Not a client, not a result.

// The problem

Underwriters spend hours a day answering brokers' coverage questions that are answered somewhere in long, public policy wordings and endorsements.

// What we would build

An assistant for brokers that answers from the published wordings and endorsements and quotes the clause, on a frontier model because the documents are public and the traffic is light, which makes it the quickest and least costly route.

// What is in it

  • Wordings and endorsements indexed by product and edition
  • Answers that quote the clause and name the edition it came from
  • Questions it cannot answer passed to an underwriter, with the context
  • No policyholder data sent to the model
  • An evaluation set of real broker questions, checked by underwriting

// Stack

  • Frontier model API
  • PostgreSQL with pgvector
  • Next.js
  • DigitalOcean

// estimate

Build
≈ US$73,100 to US$112,000, delivered within 18 weeksCAD 104,100 to 159,200
Hosting
≈ US$218 a monthCAD 310 a month
Support
≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route
Frontier model
Model running cost
≈ US$42 a monthCAD 60 a month

Timeline by milestone

Discovery
2.9 to 3.4 weeks
Specification and evaluation plan
0.4 weeks
Design approved
2.4 to 3.4 weeks
Core features
1.4 to 1.9 weeks
Full build
0.9 to 1.4 weeks
Working pilot
2.9 to 3.9 weeks
Testing and fixes
0.9 to 1.4 weeks
Launch
0.9 to 1.4 weeks
Production
0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Test environment access from your vendor
1 to 4 weeks

How it is paid

Deposit 20%
CAD 20,820 to 31,840
Discovery 2.7%
CAD 2,810.70 to 4,298.40
Specification and evaluation plan 9.1%
CAD 9,473.10 to 14,487.20
Design approved 2.7%
CAD 2,810.70 to 4,298.40
Core features 8.1%
CAD 8,432.10 to 12,895.20
Full build 5.4%
CAD 5,621.40 to 8,596.80
Working pilot 27.3%
CAD 28,419.30 to 43,461.60
Testing and fixes 2.7%
CAD 2,810.70 to 4,298.40
Launch 2.7%
CAD 2,810.70 to 4,298.40
Production 9.3%
CAD 9,681.30 to 14,805.60
Holdback, 30 days after launch (10%)
CAD 10,410 to 15,920

// questions

Questions we get about this.

Does the damage model decide a write-off?

No. It suggests a likely severity so the file reaches the right adjuster sooner. The adjuster, with an appraiser where needed, makes the call.

Why a frontier model for the broker assistant?

The wordings are already public and traffic is light, so a frontier model is the cheapest and quickest route. If the assistant later needs policyholder data, we would move it to an open-source model in your cloud.

How many claims photos does a damage model need?

Usually thousands of closed auto claims with photos and outcomes, which most carriers already hold. We check the quality of what you have before committing to a route.

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

AI for insurance: claims photo triage and broker assistants | Atheron Network Labs