About
Built for PDR, not adapted to it.
Collision estimating software assumes parts, paint and body labour. Hail work is none of those things. A hail estimate is panels, dent sizes and severity — and every tool that treats it as a collision job makes an estimator fight the software to write a normal day's work.
The problem
Per-dent pricing is the wrong shape.
Ask any estimator what a hood costs and they will not multiply a dent count by a rate. They will tell you what that hood, with that dent size, in that severity, costs to fix.
What generic tools do
- Count every dent and multiply by a rate, so two identical hoods price differently.
- Treat a windshield as something you could tap out, because they don't know what PDR is.
- Bury the supplement flow, so the second version doesn't line up with the first.
- Keep pay in a spreadsheet, so the estimate and the paycheck are two different truths.
What this does instead
- Prices from a severity matrix you own — panel × dent size × band.
- Knows glass, trim and lamps can only ever be R&I or R&R, never a PDR panel.
- Locks the sent version and marks every supplement line New or Changed.
- Pays the crew from the same numbers that priced the job.
How it's built
Decisions we made on purpose.
One calculation, everywhere
All money math lives in one place. The builder, the PDF, payroll and the invoice call the same function, so they cannot drift apart.
Advisory, not automatic
Where the software has an opinion — an aluminum panel, an unusual band, a missing photo — it says so and lets the estimator decide. It never quietly changes a price.
Honest state
If a save failed, the screen says it failed. A green tick over a lost estimate is worse than no tick at all.
Your numbers, not ours
No default matrix is imposed. Your bands, your prices, your rate, your upcharges.
Immutable once sent
The version that priced the job is the version that stays, because payroll and audit both depend on it.
Say what isn't built
The roadmap is not a feature list. If something is coming rather than here, we say so before you buy.
What's next
Being built now.
Stated plainly, because a shop choosing software deserves to know what is here and what is coming.
Offline field capture
Write lines and shoot photos with no signal, syncing when you reconnect. Today the builder needs a connection.
Batch intake
Scan a run of VINs onto a dealer or fleet account in one pass instead of one RO at a time.
Carrier interchange
Export estimates in the industry interchange format and import a carrier's file to compare line for line.
Tell us how your shop actually works.
The best features here came from estimators describing what the software was making them fight. If something doesn't fit how you write, we want to hear it.