03
QuickClaims
Case study · shown for the engineeringA four-layer parser that reads carrier PDFs into structured line items at 99%, and an email engine that files correspondence to the right claim.
- Parser
- Four layers. The carrier's scope PDF read into structured line items, with the subfolder hierarchy carriers use. 99% on the client's scopes.
- Mail
- Correspondence filed to the right claim by name and claim number. 95%.
- Billing
- Invoices with void. A client dashboard with live scope, roadmap, tickets and logged hours.
- Ownership
- Licensed to the client. The parser architecture and the training data stay reusable.
Notes
Rise Roofing Supplements · licensed · Next.js · Drizzle · Neon · Vercel · Jan 2026ContextRoofing 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.
RoleDesign, build, run. One builder, one client, a standing rule that no work starts without a written proposal accepted by all four parties.
ApproachA 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.
SolutionScope 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.
ResultParser at 99% on the client's scopes. Email triage at 95%. Licensed to the client; the parser architecture and training data stay reusable.
LearnedThe 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.
Punch list · 3 open- Parser handles multi-page supplements
- Email tool: per-user permission model
- Subfolder tabs replace the group-by-trade view
This piece as markdown