#0006 · Case study · Rise Roofing Supplements · licensed
QuickClaims
What's missing from this insurance scope?
Privatelast deploy 7 h agoMarkdown
Context
Roofing supplement teams read insurance scopes by hand and miss line items that pay. Rise Roofing Supplements wanted the reading done by software, with their people checking the result instead of producing it.
Role
Design, build, run. One builder, one client, a standing rule that no work starts without a written proposal accepted by all four parties.
Approach
A four-layer parser that reads the carrier's scope PDF into structured line items, then an email engine that files adjuster correspondence to the right claim by homeowner name and claim number.
Solution
Scope in, line items out, with the subfolder hierarchy carriers use. Invoice billing with void. A client dashboard with live scope, roadmap, tickets and logged hours.
Result
Parser at 99% on the client's scopes. Email triage at 95%. Licensed to the client; the parser architecture and training data stay reusable.
Learned
The spec sheet beat the proposal. When the long-form plan read as fluff, a plain list of what ships and when was what the client could sign.
Ticket 6 of 7. Left and right arrow keys move between tickets.