What slow recon really costs your dealership | Rapid Recon

What slow recon really costs your dealership

How Much Does Time Cost? Part 2

How much does a day in recon actually cost? Bobby and Josh run a live scenario worksheet for a 150-car store and show what happens to annual gross when average age of inventory drops from 40 days to 35, 30, and 25. Then they get into why installing a recon tool isn’t enough, how to sell the “why” to your techs and service team, and the controllable steps (approvals, parts, dispatch) where most stores can steal back time right now.

What slow recon really costs your dealership

Every day a used car spends in recon is a day it can’t sell, and the cost compounds. On ATR Episode 22, hosts Bobby Wilcox and Josh ran a scenario worksheet for a typical 150-car store and found that trimming average age of inventory from 40 days to 35 added roughly $358,000 a year in gross. Getting to 30 days pushed that past $1.1 million. Nothing else changed: same sales team, same F&I, same per-car profit. The only variable was how fast cars got frontline-ready.

That’s the case for treating recon time as a number you manage, not a complaint you hear from the used car desk.

The scenario: a 150-car store at 40 days

Bobby and Josh built the example from numbers a used car manager would know off the top of their head:

  • 150 units in inventory
  • 40 days average age of inventory (most stores they talk to land in the high 30s to 40, and often quote a figure 5 or 6 days rosier than reality)
  • $1,200 front-end PVR
  • $1,500 back-end PVR
  • $1,250 average recon cost per car
  • $100 per day holding cost

At 40 days, that store turns its inventory about 9.1 times a year, which works out to just over 1,300 cars sold. The worksheet then holds every input constant and changes only the age of inventory.

What each day off recon is worth

Here’s how the annual gross moved as the worksheet’s age of inventory came down:

  1. 40 to 35 days: about $358,000 more per year, with turns climbing to 10.4.
  2. 35 to 30 days: another $453,000 on top of that, and turns hit 12.
  3. 40 to 33 days: a more conservative seven-day cut still showed $525,000.
  4. 40 to 25 days: over $1 million a year.

Bobby’s point about the curve matters more than any single figure. The jump from 35 to 25 days is worth far more than the jump from 40 to 35. Improvement compounds, so the stores that keep pushing after the first easy win see the biggest numbers.

He also ran the same exercise with a 26-store dealer group using their combined inventory. Shaving a few days across the group showed a swing he put at around $10 million.

Faster recon also holds more gross

The worksheet had one more input worth pulling. Cars that hit the front line sooner tend to hold more gross, because shoppers online gravitate to fresh listings. Bobby’s phrasing: why are customers always on the cars I got three days ago and never the ones that have sat for three months?

So he bumped front-end PVR by $200, from $1,200 to $1,400, and that single change moved the total more than the initial five-day reduction in age did. Adding just $100 of front-end gross on the 40-to-30-day scenario added another $200,000. Speed-to-sale and gross per copy aren’t separate levers. Fixing the first tends to lift the second.

Why 12 days in recon puts you $1,400 behind before you start

Ask a technician how long recon takes and you’ll hear three to five days. Ask the used car director who actually watches the pipeline and the honest answer at most untracked stores is 10 to 14 days. At $100 a day in holding cost, a 14-day recon cycle means the car is $1,400 in the hole before it’s even sellable, on top of the $1,250 you’re about to spend making it mechanically sound.

Josh put it plainly: every day you choose not to invest in the car, you’ll have to invest more later to overcome it.

How to sell the “why” to your whole team

Downstream people in recon (techs, detailers, porters, parts) often see the car business as a parade of impatient managers who want every car yesterday. Both hosts recommended walking the worksheet in front of the whole team, with two cautions.

First, don’t pitch it as money in the owner’s pocket. Frame it in units. In the 40-to-30-day scenario, the store sells an extra 456 cars a year, which means 456 more cars flowing through the shop and a lot more repair hours for service.

Second, position it as a team measure. As Josh described it, recon is one of the clearest indicators of whether sales, service, and parts are actually working together. Bobby’s version: recon rarely suffers because anybody’s bad at their job. It suffers until people sit in the same room and realize they’re on the same team.

Having the tool isn’t the same as using it

This was the episode’s sharpest warning, aimed at existing Rapid Recon Pro customers. The time savings don’t come from the software being installed. They come from every step having an owner who’s held accountable for the time units spend there. Josh’s recommendation is to sit down with your workflow and ask, for every step, whether someone specifically covers it. Ambiguous steps where a car “kind of just gets lost” are the biggest source of hidden downtime.

He also pushed back on the instinct to open the reports and go straight to technician performance. Start with the controllables instead:

  • Parts pricing and estimate finalization between the tech and the advisor
  • Approval time on recommended work
  • Confirming the approval by writing the lines into the RO and moving the car forward
  • Awaiting dispatch, which is where cars sit while someone decides who’ll work on them

Bobby pulled up a well-run 149-car store as an example. Work got approved within an hour on average. But the pass-through step after approval, simply acknowledging it and sending the car to bill out parts, averaged two hours per car. Awaiting dispatch ran close to a day and a half. None of those steps require anyone to turn a wrench. They’re reaction steps, and every hour they sit is holding cost.

Where to start

Bobby’s closing checklist was three items: start the clock on day zero, approve work in a timely fashion, and manage bottlenecks from there. You can’t do the third one without real-time tracking that shows where every unit is and how long it’s been there. That’s what Rapid Recon Pro is built for.