One report across every system your claims touch.
Claims system, customer messaging, legal e-billing, vendor invoicing, accounts payable — one registry of numbers, one page per person, and a plain-language Ask that builds the report you need and drills to the invoice line.
The claim journey
- 01First noticeClaims system (Snapsheet, Guidewire, IAS)
- 02Customer contactTwo-way messaging
- 03Counsel assignedClaims Command
- 04Legal invoices reviewedClaims Command (LEDES 1998B/2000, firm portal)
- 05Vendor invoicesConnect
- 06PaymentCarrier AP
- 07ClosedClaims system
Every step is recorded with the system that sent it. Total cost per case = indemnity + legal + vendor. Where a step never happened, the page says so.
Ask
A question becomes a definition from the metric registry — the chips under the answer show exactly what ran — and the same builders that produce the executive pack answer it, so the number matches the PDF. Click any row to drill: firm → timekeeper → invoices → lines; state → claims. Save it, schedule it, export it; every run is logged with a hash of its rows.
What needs attention
Deterministic rules over your own facts. Thresholds you set. Every row is an identifier you can open. Predictions you can audit.
One registry, many lenses
Same numbers, different pages. An adjuster's Ask answers only over their claims; a firm sees only its own line. Lens titles are yours; the definitions are shared.
Honest by construction
- Nothing here approves, pays, blocks or edits.
- Identifiers only — the model never sees a name, an amount or a row.
- Every run and every question is logged with the hash of its result.
- Synthetic data until your systems are connected.
See it on a synthetic carrier
See it on a synthetic carrierRuns on a flagged synthetic sample until your systems are connected. © 2026 VIP Software.