Custom Claims Management Platform

What existed before

A public adjusting firm handles claims that run for months. Each one carries inspections, photographs, correspondence, payment records and deadlines, and each of those was living somewhere different — spreadsheets, email threads, a shared drive, someone's memory.

Nothing was wrong with any individual file. The problem was that answering a simple question — where is this claim, what happens next, who touched it last — meant opening four things and trusting that all four were current.

How it was solved

We started with the workflow rather than the interface: what actually happens to a claim from first contact to settlement, and which of those steps people were doing by hand because no tool supported them.

That produced a data model before it produced a screen. Sixteen tables, with permissions built in from the start rather than added later — a firm handling other people's property and payment records can't treat access as an afterthought.

The delivered work

A secure, role-based application covering the full claim lifecycle: intake, inspection scheduling, document management, payment tracking, communications and reporting.

It's a Progressive Web App, so it installs on a phone and works in the field the same way it works at a desk — which matters when half the work happens standing in someone's damaged kitchen.

Under the hood

• Row Level Security enforces permissions in PostgreSQL itself, so a mistake in the front end cannot leak another user's records.
• Fifty-plus distinct business workflows are modelled explicitly rather than left implicit in the UI, which is what makes the system safe to extend.
• Installable as a PWA with offline-tolerant behaviour for field use.