AI for insurance + custom AI insurance development — claims, underwriting governance, FNOL, and actuarial AI around your PAS/CMS stack.

AI claims processing is the workflow most carriers ask about first. From FNOL submission to claim file assembled and routed to the adjuster takes 2–5 business days on mid-market P&C carriers. Each file is 18–40 documents — police reports, photos, repair estimates, prior policy, customer statements — and claims clerks spend 45–80 min per file assembling before an adjuster ever reads it. Leakage from missed coverage details runs 3–8% of loss-adjustment expense. Most insurance AI vendors sell you an AI claims processing demo and a deck full of LAE-ratio screenshots; what they don't ship is the NAIC governance pack that lets your chief actuary sign off.

An agent reads the inbound FNOL (form submission, call transcript, email, photos, attached PDFs), classifies the claim type, pulls the matching policy plus prior claims plus relevant endorsements from your PAS, drafts a coverage analysis with a flag list of issues for the adjuster, and routes to the right segment queue. The adjuster approves or edits — no auto-decisions on coverage. The agent's job is the document assembly and the coverage read, not the liability call.

Underwriting models drift quarterly but most carriers review them annually. Bias-test artifacts get rebuilt manually by the actuarial team every audit cycle — 3–6 weeks of work per cycle. When the state regulator asks "show us the disparate-impact analysis for ZIP-code-correlated features", the answer is a 200-tab spreadsheet that took two senior actuaries a month to produce. AI underwriting without a continuous governance layer isn't AI underwriting; it's a model that'll get pulled at the next market-conduct exam.

A model-governance layer runs the bias tests, drift tests, and feature-stability tests continuously on every underwriting model in production. It surfaces a quarterly governance pack the chief actuary signs off and surfaces real-time alerts when a model crosses a drift threshold. The actuary stays the decision-maker; the platform produces the artifacts they need to sign off on. The base underwriting model stays classical ML (LightGBM or XGBoost) per ASOP No. 56 — the governance wrap is what's new.

Policyholder service calls average 6–11 minutes; agent service calls average 12–22 minutes. 40–60% of those calls are answered by a policy provision a grounded assistant could have read out loud — but generic conversational AI hallucinates coverage details, and a wrong coverage answer is an E&O exposure with measurable downstream cost. A policy assistant that hallucinates a deductible isn't an assistant, it's a litigation primer.

A grounded policy assistant reads ONLY from your actual policy forms (with endorsements applied), the active claim record, and the agent's authorization scope. It refuses to answer outside that scope. Every answer cites the policy section it came from. It surfaces "I'm not sure — let me get an adjuster" instead of guessing. It handles policyholder FAQs, claim-status, and routine agent endorsement requests; complex coverage interpretation routes to a human. The AI insurance agent variant reads the broker's book and the carrier's appetite simultaneously, surfacing appetite-fit and renewal flags for the ai for insurance agents workflow.

Severity classification at FNOL is mostly heuristic — adjusters segment claims by line of business and dollar threshold. Total-loss vs. repairable on auto runs 12–18% wrong at intake; coverage-litigation flags on liability claims get missed 8–15% of the time and surface later as bad-faith exposure. Mid-tier carriers don't lose money on the big claims they triage right; they lose it on the medium claims that should've been triaged big.

A triage model reads the FNOL inputs — description, photos, location, prior-claims history, policy coverage — and predicts severity tier plus total-loss probability plus an early litigation-risk score. High-severity or high-litigation-risk claims route to senior adjusters immediately instead of waiting 5–14 days for re-triage. The triage call isn't auto-binding; it's a queue-priority signal with a confidence score the adjuster can override.

Commercial underwriters receive loss runs as PDFs, Excels, and emailed text — every submission in a different shape. Manual extraction takes 25–60 min per loss run; data-entry errors run 4–9%. Underwriters spend 35–50% of their day keying loss runs, not doing actual underwriting judgment. That ratio's the real reason MGAs can't scale a UW team without a four-month ramp.

An extraction pipeline reads the inbound loss-run document (any format), normalizes to ACORD or your internal schema, validates against the submission's effective dates and prior-policy history, and pushes the structured record into your underwriting workbench. The underwriter reviews the parse and spot-checks; the underwriter never re-keys. Low-confidence fields surface with the source-document snippet so the spot-check is 30 seconds, not 30 minutes.

Subrogation recovery rate sits at 7–14% across mid-market P&C carriers. Recoverable claims get missed because the subrogation review happens 60–120 days after claim close, and adjusters don't flag liability shifts at FNOL. Industry estimate: 25–40% of recoverable opportunities never get worked. The dollars are sitting on the floor — the carrier just doesn't have an analyst who reads every file in time.

An analyzer reads every claim file in real time, flags the ones with subrogation indicators (third-party fault, contractual recovery rights, comparative-negligence shifts), drafts the demand-letter outline, and surfaces the package to the subrogation team within 7–10 days of claim opening — not 60–120 days after close. The team reviews and pursues; the agent is the eyes on every file, not the negotiator.

Renewal prep on commercial books burns 4–9 hours per account per cycle. Underwriting assistants assemble the renewal package — loss runs, exposure changes, market data, prior endorsements — before the underwriter looks at it. Endorsement processing carries a 5–11 business-day backlog on mid-size MGAs. The agentic ai insurance pattern that works here isn't "replace the underwriter"; it's "stop paying an UW assistant to do data entry".

A renewal agent assembles the prep package autonomously (pulls prior policy, runs the loss-run extraction, summarizes exposure changes, drafts the renewal narrative), then routes to the underwriter for decision — not data entry. An endorsement agent handles routine endorsements start-to-finish with policyholder confirmation; complex endorsements surface for underwriter review. The agent runs against your underwriting guidelines via grounded retrieval, not against generic LLM judgment.