Product demos

The claims suite — the full walkthrough

The long version, paced so you can read every caption and watch every field actually get filled in. One claim, start to finish: a roofing professional counts the damage slope by slope in Roofing Expert and seals the inspection; the homeowner answers the LossList hurricane interview question by question, scans a receipt and watches the store, date and amount fill themselves in, and exports a sealed claim file with a code only they can read out; then a licensed public adjuster opens both files in ClaimForge on a Mac, watches the structural scope draft itself from the inspection, and works the contents valuation line by line — every suggested figure showing its source and waiting for approval. It ends on the pages of the carrier package the software actually generated.

Nothing here is a mockup or a re-enactment: the encryption, the receipt reading, the depreciation tables and the final PDF are all the shipping code doing the work on camera. The policy never appears — the adjuster requests it from their client and makes every coverage determination themselves.

Roofing Expert — a full inspection, start to finish

One inspection from the driveway to the finished report. The client can't remember the date of loss, so Storm Checker pulls the qualifying storms near the property from public NWS reports and the insured picks the one that matches their recollection — the app presents, the client selects. Radar hail from NOAA's MRMS MESH grid is decoded on the phone itself to give the hail size at that address. Then the roof gets documented the way it actually happens on a roof: damage counted slope by slope and by cause, material and vents and every penetration, pitch read by laying the phone on the slope, the roof traced on satellite imagery for squares, and a required-shot photo checklist that captions itself from what was already recorded. It ends where the job ends — one branded PDF with every source printed next to the finding it supports.

For roofing professionals — your inspection, all the way to the carrier

Damage counted slope by slope and by cause, a required-shot checklist that captions itself, and Storm Checker pulling the qualifying storms near the property from the public NWS record so the insured can pick the one they remember. Then the whole inspection leaves in one action — sealed, with a security code read separately — and lands on the adjuster's desk as data, where it drafts the structural scope instead of being re-typed.

For licensed public adjusters — two sealed files, one claim file

Your client's inventory and the roofing inspection both arrive sealed and decrypt only in your workspace. The structural scope drafts itself; the contents map in with photos, receipts, serial numbers and sub-limit classes, nothing re-keyed. You set the valuation basis and the app sources the numbers — depreciation from published useful-life tables, with its working shown, and a plain statement when it cannot source a figure rather than a guess. Nothing reaches the report without your approval, and the coverage narrative is yours to write. The policy never enters ClaimForge.

For desk adjusters — what a documented claim actually looks like

Not a pitch — a walk through a file built with these tools. Contents documented by the policyholder themselves, photos carrying their own capture time and location, the guided interview verbatim with timestamps including the answers that found no damage. Every valuation line shows where its number came from, and a licensed public adjuster approved each one individually. It ends on the document itself, sources printed next to the findings they support.