Eight sections. Straight answers. Start anywhere.
An estimator is headcount — salary, training, turnover, and a ceiling set by one person's experience. PDR Logic is a standard applied to every file, running on software built for this work.
You aren't buying hours. You're buying the discipline that decides what a repair order is worth.
Plenty of shops try. Writing the estimate is the easy part — it's the documentation, the supplements, the follow-up, and the endurance to hold a position for six weeks that quietly consumes the week.
In-house, that work competes with production and loses. Here, it's the only thing we do.
Hail isn't collision. Dent count, depth, and position relative to character lines and panel edges each move repairability and cost — and the choice between paintless repair and conventional body work can decide whether the vehicle totals at all.
That's a narrow reference most general estimators were never trained on. The Storm →
You do. The file goes out under your shop's name — the estimate, the documentation, the supplement — and the relationship stays yours.
Where you want us in the conversation, we're there. Where you don't, the file still stands on its own.
A submission from the Portal: the VIN, the odometer, and a walkthrough of the vehicle. A technician aims a phone at the plate and the data comes off the images — nobody keys a vehicle in twice.
If the carrier has already written, send that too. If you've written your own, send both.
Most files come back within 24 hours of submission. Teardown supplements and total-loss packages run closer to 48, because there is more to document and more riding on it.
If a file is going to take longer than that, you hear it when it lands — not when you go looking for it three days later.
Both. Some shops send us the vehicle and we write it from the ground up. Others write their own and want it held to the standard before it goes out.
Either way, what leaves the shop is complete.
Earliest is best. At intake, before the carrier's first number sets the anchor, you have the most room and the fewest assumptions to unwind.
But files reach us at every stage, including after a denial. Later simply means more to reconstruct.
A flat fee per file. Not a percentage of what we recover.
That is deliberate. A fee that moves with the settlement is the fastest way to have someone ask whether we are acting as a public adjuster on your customer's claim. We are not, and we would rather the fee structure say so plainly than have to explain it later.
Current rate is $XXX per file, $XXX for a total-loss package, with volume pricing above XX files a month. No contract and no minimum volume — thirty days' notice ends it.
And the first review is free. Send two estimates and we will return them rebuilt before any money changes hands.
On hail files, shops we have onboarded have typically seen 20–30% more per vehicle.
The honest version of that number: the range is wide because the starting point is. A shop already writing teardown, documentation, and storage into every file gains the least from us. A shop that has been absorbing all three gains the most.
And a file where we find $300 is still $300 you were not going to bill. Ask us to read your closed files — that is a real number instead of somebody's average.
Yes. The fee is for the file, not for the outcome.
We would rather be straight about why. Anyone who bills you only on recovery has a quiet incentive to chase the easy dollars and let the hard ones go — and the hard ones are where your money actually is.
What you get instead is that a denial is not the end of a file. Most of what is refused on the first pass gets paid on the second or third, once the documentation is in front of someone who has to answer it in writing. We keep going at no additional charge.
Yes — and it's the fastest honest look you'll get. Send closed files, repaired or totaled. We'll show you line by line what was earned and never billed.
No live claim, no exposure, nothing to unwind. Just the ledger. The Ledger →
Yes. Nothing goes out under your shop's name without your review. There is no version of this where you find out what was submitted after it was submitted.
Say so, and we'll show you the basis for the line — the OEM procedure, the published standard, or the real cost behind it.
If you still disagree after that, it's your file and your call. We'd rather lose the line than hand you something you can't defend at your own counter.
You do. Access is role-scoped, so your facility sees its own files and nobody else's. Every event is logged. Deleted items purge on a fixed schedule.
You can export your account in full, and you can delete it outright. Privacy →
No. We do not hold a credential to your system, and we would decline one if you offered.
Files move through the Portal — you send, we return. If you would rather hand estimate data across directly, we set that up as a data exchange, with your people and your permissions. That is a different thing from us logging in as you, and the difference matters the day anyone asks who touched a file.
Yes. Storm volume is the case this was built for.
The whole reason intake, documentation, and supplement handling run through software instead of one person's inbox is so that the hundredth file of the week is written to the same standard as the first. Volume is what breaks a headcount solution; it is not what breaks this one.
What we ask for is warning. Tell us a storm has landed and roughly what is coming, and we staff to it. The shop that calls on day one gets a very different week than the shop that calls on day ten.
In a normal week, 24 hours. In a catastrophe surge, 48 to 72.
Everyone's turnaround stretches in a CAT event, ours included, and we would rather tell you that in September than discover it together in June. What does not stretch is what is in the file when it comes back. The volume changes the clock, not the standard.
Shops that enter a storm with documentation already in place spend the next six weeks repairing. Shops that don't spend them catching up. The Storm →
Yes. Hail is seasonal, so the arrangement should be too.
That's most of the argument against solving this with headcount — you aren't carrying a salary through the quiet months to be ready for the loud ones.
Nothing changes on your side. Your labor rates, your PDR matrix, your market's tax treatment, and every file you've ever sent live in the system — not in one person's memory.
That's the difference between a service and a dependency.
— Already Using PDR Logic? —
Here is what comes next.
Loss Logic is the software the practice runs on. It reads the insurer's estimate and yours side by side, finds every line where the two disagree, and builds the documented case for the difference.
PDR Logic is the firm. Loss Logic is the system underneath it — and it doesn't exist anywhere else in this industry.
No double entry. Estimate data moves across as data, not as retyping — you don't key a vehicle or a line item twice to work with us.
Nothing to migrate, and nothing to retrain your front office on.
The bay. A technician aims a phone at the VIN plate and the odometer, walks the vehicle, and submits — the vehicle data and mileage come off the images.
The desk sees the same job a moment later, with every message and file on one thread instead of an email chain nobody can find in six weeks.
No. AI reads. It extracts line items, matches operations across thousands of variants, and flags what's missing or short — at a speed and consistency no person sustains across a storm season.
A human decides what the file says. Nothing reaches a carrier that a person hasn't reviewed.
That's the usual order, and the one we'd recommend. The estimating relationship comes first.
The software tends to become obvious on its own, once you've seen what it has quietly been doing behind your files.
Every file we write already runs through it. Turning it on for your shop doesn't add a process — it opens the window.
You see what we see: the comparisons, the gaps, the history, the file as it moves. Instead of only receiving the result.
Pattern. One estimate is an anecdote. A hundred is evidence.
Which carriers write which operations short, and by how much. Where your own estimates run thin. Which files never got the supplement they had already earned. None of that is visible one repair order at a time.
Usually three things: revenue that was earned and never billed, a carrier behaving differently with you than with anyone else, and hours your team spends fighting instead of repairing.
Money you lose can be re-earned. Time you spend cannot.
Yes. A de-identified example is available on request — ask and we'll send it.
Though we'd rather rebuild one of yours. Your own file is considerably more convincing than someone else's.
Yes. Tell us your market and roughly your size and we will put you in touch with a shop that looks like yours.
With their permission and a heads-up first — nobody gets a cold call from a stranger holding their name.
There isn't one. Two estimates on the same vehicle — the insurer's and yours — come back rebuilt. No cost, no obligation, no follow-up campaign.
We're betting the difference speaks for itself. That bet only works if you actually get to look at it.
Yes. Ask for a walkthrough and we'll run it against a real file rather than a demo dataset — ideally one of yours.
A staged demo proves nothing. Your own vehicle, your own carrier, your own numbers proves the whole thing at once.
Leave your details and we'll reach out. No obligation, no campaign, no drip sequence.
We'll be in touch shortly. If it's urgent, call 844-84-LOGIC.
Ready now? Send us two estimates →
sales@pdrlogic.com · 844-84-LOGIC