000

All work

Claims Reader

The brief saidBuild us auto-approval for claims the model is sure about.

What we builtNever auto-approve. Route by confidence and always show the source.

Client
A mid-size insurance carrier
Year
2025
Work
Retrieval
Stack
Python, FastAPI, pgvector, Next.js

Claims arrived as scans, photos and forwarded email chains. Adjusters spent most of their time finding policy numbers, not judging claims.

Every extracted value links back to the region of the page it came from. Uncertain files jump the human queue instead of being guessed at.

The details that mattered

  • Source highlighting

    Clicking a value opens the scan at the region it was read from.

  • Confidence routing

    Three queues by confidence, each with its own review screen.

  • Permission-aware search

    Retrieval follows the same access rules as the claims system.

Adjusters review instead of retype. The carrier’s engineers now own the extraction rules, with our eval suite as the safety net.