Connected Claims USAFind us at booth 502, Signia by Hilton Orlando, Nov 3-4Booth 502 · Orlando, Nov 3-4Booth 502 · Connected ClaimsBook a meeting
Blog›Buyer Playbook
Buyer PlaybookMay 12, 2026·9 min read·Nitish Badu, COO·Updated November 16, 2026

The Claims VP playbook for deploying AI investigation: budget, timeline, change management

A Claims VP buying guide for AI investigation: pilot and 12-month budget ranges, phased rollout, stakeholder map, change management, and board outcomes.

NB
Nitish Badu · COO and Co-founder
May 12, 2026·9 min read·Updated November 16, 2026
The numbers behind this
1,000 - 5,000Cases to scope in a 90-day pilot1-2 LOBs, auto and workers comp
75%Flagged claims closing uninvestigatedthe tier full coverage picks up
25% to 100%Flagged-claim coverage shiftmanual SIU baseline to AI-investigated
14+ days to minutesCycle time per casemanual SIU vs AI investigation

A Claims VP at a Top 50 P&C carrier watches three numbers every quarter: the SIU caseload, the cost per investigated claim, and the loss ratio on lines where fraud is concentrated. AI claims investigation moves all three. The hard part is scoping a buy the CFO will sign, the CIO will integrate, and the SIU director will run.

This playbook is for the Claims VP who has to defend the line item. The wider stack is in our autonomous AI claims investigation pillar.

The pre-RFP diagnostic: why this is a Claims VP decision

The AI investigation buy belongs in the claims-org budget, not the IT capital plan. Three signals say so: SIU capacity is the binding constraint on loss-ratio improvement. Cost per investigated case is the lever the CFO will model. And the antifraud-plan filing under NAIC Model Act #680, adopted in 48 states, is a claims-org responsibility, not an IT one.

At most Top 50 carriers, a manual SIU investigation takes 14+ days per case, an investigator carries 200+ cases, and only about 25% of flagged claims actually get investigated. The other 75% close on adjuster judgment without an investigation file.

SIU staffing growth, per the Insurance Information Institute, slowed to 1.4% in 2021-2022 from 2.5% the prior year. The capacity gap is widening, not closing.

AI investigation is not a detection-vendor swap. FRISS, Shift Technology, and Verisk ISO ClaimSearch keep doing what they do at FNOL. Investigation is the downstream layer, covered in our piece on prevention, detection, and investigation as three distinct layers.

Budget framework: what to ask for and how to model ROI for the CFO

A defensible budget ask has three parts:

  • Scope the 90-day pilot at 1,000 to 5,000 cases on one or two lines and have it quoted against that volume.
  • Plan the 12-month rollout run-rate to scale with flagged-claim count rather than seats or headcount.
  • Carry the ROI in basis points of loss ratio on AI-investigated lines.

Build the CFO model on coverage-corrected unit cost, not headline per-case price. Manual SIU carries a high fully loaded cost per case and reaches about 25% of flagged claims. AI investigation reaches 100% at a unit cost low enough that the marginal cost of one more investigation stops driving the triage decision.

On a carrier flagging 50,000 claims per year, the manual budget covers about 12,500 cases, and covering all 50,000 lands well under that same budget. The fraud caught in the previously uninvestigated 37,500-case tier is the loss-ratio story, not the per-case savings.

Bring two scenarios: a conservative model at a 5% confirmed-fraud rate on the incremental coverage and a base case at 10%, matching the P&C fraud rate cited by the Coalition Against Insurance Fraud.

01CFO model · coverage-corrected

The CFO story is the 37,500 flags that close uninvestigated

A carrier flagging 50,000 claims a year funds manual SIU for about a quarter of them; the loss-ratio upside sits in the rest.

Flagged claims a year50,000The carrier in this example
−
Covered by the manual SIU budgetabout12,500About 25% of flagged claims
=
Close with no investigation file37,500The tier full coverage picks up
Two scenarios to bring the CFO
Conservative: confirmed fraud on incremental coverage5%Base case: the P&C fraud rate (CAIF)10%
Tie payback to loss-ratio basis points on AI-investigated lines, not per-case savings.
Price the fully loaded case. Implementation services, evidence-pack storage and adjuster training land in the SOW, not the software line. Fund the 60 to 90 days of parallel running too.
Worked example from this article: a carrier flagging 50,000 claims a year at about 25% manual coverage (Hesper internal benchmark). Fraud-rate scenarios per the article's CFO guidance; 10% is the P&C fraud rate cited by the Coalition Against Insurance Fraud.

Where flagged claims land today, and under full coverage

Flagged claims investigated today25%
Flagged claims closing with no investigation file75%
Flagged claims investigated under AI coverage100%

Two pitfalls show up in CFO reviews:

  • Services markup on integration. The quoted per-case rate is almost never the loaded cost, because implementation services, evidence-pack storage, and adjuster training all land in the SOW. Ask every vendor to price the fully loaded case.
  • Parallel-run costs. Most carriers underfund the 60 to 90 days when SIU runs the old workflow next to the AI-assisted one for audit confidence.

The full list is in our breakdown of hidden integration costs for legacy claims AI. For ROI scenarios across three carrier sizes, see our ROI case studies for AI claims investigation.

Interactive calculator

Size your pilot and 12-month budget

Pilot budget (90 days)
-
3,000 cases · 1-2 LOBs
12-month rollout run rate
-
50,000 cases · full coverage

Hesper does not publish a rate card, so enter the per-case price from your own quote; what it buys depends on LOB mix and integration scope. Get a quote keyed to your portfolio.

The 12-month timeline: pilot, scale, mature

Commit to phase-gate decisions, not a 12-month lock. Phase 1 is a 90-day pilot on one or two lines, typically auto and workers compensation. Phase 2 scales to more lines once the pilot signal is clean. Phase 3 retires manual triage on the covered lines.

PhaseMonthsScopeCommercial gateOutcomes to measure
Pilot1 - 31,000 - 5,000 cases; 1-2 LOBs (auto, workers comp)Fixed scope, priced against the pilot case countCycle time, false-positive resolution, integration latency
Scale4 - 920,000 - 50,000 cases; add homeowners, commercial, BIFunds only if the pilot exit criteria clearCoverage %, cost per case, SIU role redesign
Mature10 - 1250,000 - 100,000 cases; all flagged claims in scopeRun-rate moves into the claims operating reviewLoss-ratio delta, antifraud-plan refresh under NAIC #680

Write three pilot exit criteria into the SOW before signature:

  • Investigation cycle time measured in minutes on 95% of pilot cases.
  • False-positive resolution rate above 80% on rules-flagged claims (since rules-based detection runs 60-85% false positives in industry studies).
  • Zero unresolved compliance flags from the SIU director on audit-trail completeness.

If any of the three miss, the scale phase does not auto-fund.

02Phase gates

The scale phase funds only if the pilot clears all three exit criteria

Commit to phase-gate decisions, not a 12-month lock: each phase widens the case count only after the last one proves out.

  1. Pilot · months 1-31,000 - 5,000Cases on one or two lines, usually auto and workers comp
  2. Exit gateAll threeWritten into the SOW before signature. Any miss and scale does not auto-fund
  3. Scale · months 4-920,000 - 50,000Adds homeowners, commercial property and bodily injury
  4. Mature · months 10-1250,000 - 100,000All flagged claims in scope; the run-rate joins the claims operating review
Exit criteriaMiss one and the scale phase waits
  • 95%of pilot cases with investigation cycle time measured in minutes
  • above 80%false-positive resolution on rules-flagged claims (rules run 60-85%)
  • zerounresolved SIU compliance flags on audit-trail completeness
Phases, case counts and exit criteria from this article's 12-month rollout plan. The 60-85% false-positive range for rules-based detection is from the industry studies the article cites.

Stakeholder map: the question each one will ask

Run this procurement without a written stakeholder map and you will lose 60 to 90 days of cycle time to ad-hoc objection handling, mostly from CIO security review and legal review of third-party data use. Pre-empt every reviewer with the one question they actually care about.

StakeholderThe question they will ask
SIU DirectorDoes this give me audit-defensible cases on 100% of flagged claims without breaking my case routing?
CIO / CTOWhat is the integration surface to Guidewire ClaimCenter or Duck Creek, and does the vendor have a current SOC 2 report?
ComplianceDoes the audit trail satisfy NAIC Model Act #680 and align with state-level rules like California 10 CCR 2698.36?
LegalWho owns the investigation work product, how is third-party data licensed, and how does EUO evidence flow into the case file?
Operations ManagerWhat does adjuster training look like, and how does day-one workflow change for front-line claims?
CFOWhat is the coverage-corrected cost per case, and where does the loss-ratio impact show up in the next four quarters?

The working documents for these conversations:

Compliance is the reviewer most likely to be skipped and most likely to slow the deal in week 10. Bring them in at week one.

The relevant state rule for California carriers is California 10 CCR 2698.36, which requires the SIU to investigate each credible referral of suspected fraud and to document any decision not to investigate. AI investigation makes that easier: every flagged claim gets a documented decision in the audit log, the exact artifact the state DOI asks for in market conduct exams.

Change management: deploying AI without burning out SIU adjusters

The failure mode at carrier rollouts is anxiety, not pushback. SIU adjusters who handled roughly 10 investigations per month manually do not know what a review queue no longer capped by headcount means for their job. The Claims VP needs three written commitments before the first case routes, all communicated to SIU staff in the same memo.

03The SIU memo

The investigator stops gathering data and starts deciding on evidence packs

The three written commitments that go to SIU staff before the first case routes, drawn as a decision-rights map.

Input
Flagged claim routed to SIU
Referral_alert.pdfClaim_file.pdfRecorded_statement.mp3
AI layer
Logged, sourced, timestamped
  1. 01Document collection and review
  2. 02Database and index-bureau lookups
  3. 03Statements cross-referenced, timeline rebuilt
  4. 04Evidence pack with sources and recommended next actions
15+ investigation phases in parallel
Evidence pack
Investigator decides
SIU director is the final authority
  • Finding, referral or denial
  • Accept or dispute the AI output
  • Escalate a dispute to the SIU director
Agent recommends. Investigator decides.
When the investigator disputes an output
  1. 1.Investigator marks the AI output as disputed
  2. 2.The SIU director makes the final call
  3. 3.Logged and reviewed monthly for model-quality signal
75%No SIU headcount reduction in year one. The freed capacity works the 75% of flagged claims that used to close uninvestigated.
Illustrative exampleIllustrative decision-rights map built from the three commitments in this article. Agent scope per Hesper product scope; 15+ phases and the 75% uninvestigated share are Hesper internal benchmarks.
  1. No SIU headcount reduction in year one. The freed capacity covers the 75% of flagged claims that were previously uninvestigated, where the incremental fraud recovery sits.
  2. The investigator becomes the decision-maker over AI-produced evidence packs. Judgment stays human; data gathering, document collection, and database lookups move to the AI layer running 15+ phases in parallel.
  3. A named escalation path for any AI output the investigator disputes, with the SIU director as the final authority. Disputed outputs are logged and reviewed monthly.

The director's side of that rollout is mapped week by week in the SIU director's first 90 days with AI investigation. The manager-level version - who tells the team what, and when - is in leading a claims team through AI-augmented investigation.

Named-insurer evidence helps at the SIU town hall. AXA Switzerland's deployment with Shift Technology caught a CHF 120,000 false claim involving intoxicated workers in the first week after deployment, per Samuel Klaus, Head of Fraud at AXA Switzerland, in the published Shift Technology case study.

The 12-month outcomes report: what to bring to the CEO and Board

Four metrics belong on the month-12 board report, and only four:

  • Investigation coverage as a percent of flagged claims.
  • Cost per investigated case.
  • Cycle time per case.
  • Loss-ratio delta on AI-investigated lines, isolated from rate action and other claims-handling changes.
MetricManual baselineMature-state target
Investigation coverage of flagged claims~25%100%
Cost per investigated caseHigh: fully loaded investigator timeA fraction of manual
Cycle time per case14+ daysMinutes
Caseload per investigator200+ open casesNot capped by headcount

The board narrative is a coverage story, not a per-case cost story. The carrier is now investigating four times as many flagged claims at lower total cost, with documented decisions on every claim. The loss-ratio delta lands in months 6 to 12.

The forward question for the Board is whether the carrier's antifraud plan, SIU role definitions, and reinsurance reporting reflect a 100%-coverage operating model. Carriers that lock that operating model in 2026 will price 2027 books on a different loss-cost curve than carriers still triaging at 25% coverage.

Key takeaways

  • AI claims investigation is a claims-org budget item, not an IT line. The loss-ratio lever and the NAIC Model Act #680 filing both sit with the Claims VP.
  • Scope a 90-day pilot at 1,000 - 5,000 cases on 1-2 lines, priced against that case count.
  • The CFO math is coverage-corrected: the fraud caught in the previously-uninvestigated 75% is the loss-ratio story.
  • SIU headcount does not get cut in year one. Investigators move from data gathering to decision-making.

Frequently asked questions

Three integration points need scoping: the claims system of record (Guidewire ClaimCenter, Duck Creek, or in-house), SIU case management, and any detection vendor feeding flagged claims into investigation. Standard CIO checklist: a current SOC 2 report, data residency and PII handling, role-based access control, and audit-log export to your SIEM. Plan on 60 to 90 days from signed SOW to first production case.

Less than most Claims VPs expect, if the audit trail is complete. NAIC Model Act #680, adopted in 48 states, requires an antifraud plan with documented SIU procedures, training programs, and standard operating procedures for investigating suspected fraud; it does not prescribe whether the investigator is human or AI-assisted. Refresh your antifraud-plan filing to reflect the AI-assisted workflow.

Plan for 8 to 16 weeks from RFP issue to signed pilot SOW at a Top 50 carrier. Compress this by running the stakeholder map in parallel, not in sequence. Most slippage happens in legal review of data use and indemnification, and in CIO security review when the vendor cannot produce a current SOC 2 report. Pre-qualify on those two items before issuing the RFP.

On the Hesper platform

Hesper AI runs every stage of a claim, from first notice of loss to subrogation recovery, with investigation-grade evidence behind every decision.

The platformFNOL intakeClaims triageFraud investigationSubrogation & recovery

Keep reading

← More articles on the Hesper AI blog

See Hesper AI on your documents

Request a demo and we'll run an analysis on your real document samples.