About
Born in a hail shop, not a boardroom.
DentSheet started on the floor of a working paintless dent repair shop in Regina, Saskatchewan — the middle of one of the busiest hail corridors in North America. When a storm rolls through, hundreds of cars show up at once, every one of them needing a panel-by-panel inspection, a severity matrix, and an estimate an insurer will accept.
The tools for that job were spreadsheets, paper matrices, and memory. Severity picked from a dropdown and argued about later. Totals re-typed between the sheet, the printout, and the email — and drifting a little each time. Software built for collision shops, bent until it sort of fit PDR.
So we built the sheet we wished existed, alongside the estimators who use it — shaped around SGI’s PDR matrix and catastrophe-season reality, refined claim by claim with our development partner shops. It runs on the phone in the bay, because that is where the car is.
What we refuse to compromise on.
01
Severity is counted, not guessed
The original sin of hail estimating is the severity dropdown — two estimators, one car, two answers. In DentSheet you enter a dent count and the band derives itself from the rate table. The judgment call is gone, and so are the arguments.
02
One number, everywhere
The matrix screen, the print sheet, the PDF, and the body-shop portal all read from a single calculation. Nothing re-computes a total on its own, so nothing can disagree.
03
People stay in control
DentSheet removes repetitive work without making estimating decisions for you. Vehicle plaque scans are reviewed before anything is applied, and panel counts remain in the estimator's hands.
04
Rates don't drift
Rate tables are immutable once a claim has used them. Editing rates creates a new version; existing claims keep the version they were priced under. An estimate from March still means what it meant in March.