Paddock20
Wireframe DigestDealer AvatarJuly 11, 2026 · 7 min read

The 6-Day Turn:
I Built the Software Myself

Industry recon runs 12 to 21 days. This lot runs 6. The gap is a system, and the system transfers to a 1-rooftop store.

A car on your lot is not inventory. It is an invoice that reprints every morning.

Holding cost runs $32 to $40 per vehicle per day, per AFC. The industry recon cycle averages 12 to 21 days, per Carketa. Take the middle of both: $36 a day across 16 days is $576 per car. Independent dealers average about $1,500 in front-end gross per used unit, per ACV Auctions. On those numbers, recon lag consumes 38 percent of the gross before the car takes its first photo.

Now price it where this lot operates. 280 exotic vehicles a month at a $289,000 average unit — more than $80 million sitting on the ground at any time. At 7 percent money, one car bills about $55 a day in interest before insurance, before detail, before the square footage under it. A 21-day recon on that car is $1,164 in interest alone. Nobody approves that spend. It approves itself, one quiet day at a time.

$32–$40

Per vehicle per day in holding cost (AFC)

12–21

Industry recon days average (Carketa)

6 days

This lot's average turn across 280 cars/month

$576

Carry cost per car at the 16-day midpoint


The Industry Numbers

The averages are public. Recon runs 12 to 21 days across the industry; top performers get under 7, per Carketa. Rapid Recon sets the target at 3 to 5 days and reports that cutting 2.5 recon days adds a full extra inventory turn per year. The cost of waiting rose while the clock stood still: net floorplan expense climbed 39 percent year over year, to about $139 per unit, per Harney Partners.

And the tooling underneath? Many independents run recon on spreadsheets, whiteboards, or text threads, per Carketa. The whiteboard is free. The days it loses are $32 to $40 each.


What I Watched on My Own Lot

The lot covers 70,000 square feet. We land 120 vehicle transporters a week and route work across 15 service categories: mechanical, PPF, paint correction, wheels, interior, detail, and the rest.

Before the system, status lived in three places: a whiteboard, a group text, and someone's memory. A car sat marked "in detail" for 3 days that detail never received. A vendor waited on an approval that had been given, verbally, to a different person, the day before. "Where is the 812?" got asked 6 times before lunch and answered two different ways. None of that is negligence. It is what 280 cars a month does to a process with no single source of record.

On a $28,000 sedan, a lost day rounds to nothing. On a $289,000 car, a lost day is $55 in interest plus everything stacked on top, multiplied across every unit on the ground.


Why I Did Not Buy a DMS Module

I priced the shelf first. The billing pattern in DMS software is documented: one store believed it paid $525 a month for its system and found itself billed $937 a month after add-ons, per DealerClick. That is a 78 percent gap, discovered on an invoice instead of in the demo.

The fit was wrong before the price was. Those modules are built for franchise stores turning $28,000 sedans at volume. The constraint set here is different: $289,000 average units, 120 transporter handoffs a week, 15 service categories, and a chain of custody that has to survive an insurance claim.

So I wrote a spec. I build systems — 26 years of them: 1,586 retail stores, an Amazon delivery operation graded 99.8 percent on-time. Not a career programmer. An operator who writes exact requirements. I directed AI coding agents from those written specs, with acceptance gates: a feature ships when it passes the gate, not when the code looks finished. The output is DRX Lot Assistant™: a full-stack progressive web app, React and TypeScript in front, Node and PostgreSQL behind, role-gated so a porter, a vendor, and a manager each see their own lane.


What the Software Does, in Plain Words

Intake

Every car checks in once, with photos and a four-view damage diagram: front, rear, left, right. Condition at minute zero becomes a record, not a memory.

Diagnosis

Each car gets a work plan across the 15 service categories. Every line has an owner.

Vendor Assignment

One vendor, one job, one clock. The clock starts at acceptance.

Turn Tracking

Every unit shows its age in days, and every day is charged to a stage. No car is simply "in recon." It is on day 2 of paint correction, and paint correction can see that.

Release

No vehicle moves without a chain-of-custody bill of lading signed at the transporter handoff, with the same four-view diagram. 120 transporters a week means 120 signed records a week. Damage disputes end at the diagram.

One Writer Per Record

The rule that kills the spreadsheet. Two people cannot hold the pen on the same car. Status changes once, by its owner. Everyone else reads.


The Result

Industry average: 12 to 21 days. This pipeline: 6-day average across 280 vehicles a month.

Against a 16-day midpoint, that is 10 days returned per car. At $32 to $40 a day, call it $360 per car in carry avoided, before the interest math on a $289,000 unit. Rapid Recon's data says 2.5 days recovered adds one full inventory turn a year. This pipeline recovered 10.


What to Take If You Run 1 to 3 Rooftops

Not the app. The system. Five rules transfer at any scale.

1

Price the day

Compute your per-day holding number: interest plus insurance plus rent, divided across units, or start from the $32 to $40 range. Post it where the team works. A day with a price on it gets defended. A free day gets spent.

2

One writer per record

Software optional, rule mandatory. One person owns each car's status at any moment. Group texts fail because everyone writes and nobody owns.

3

Put a clock on every stage

Intake, diagnosis, assignment, work, release: five stages, five owners, five timestamps. You cannot shorten a stage you never timed.

4

Document every handoff

Four views, signed, every time the car changes hands. On high-value units, one settled damage dispute repays years of the habit.

5

Write the spec before you buy or build

One page per workflow: who touches the car, what they record, what releases the next stage. If a vendor demo cannot run your page, you learned that for free. If you build instead, the pages are the build plan.

A 40-car lot obeys the same physics as a 280-car lot. The invoice reprints every morning either way.


Walk Your Pipeline Against These Five Rules

A small number of conversations are open for dealers running 1 to 3 rooftops who want to map their recon workflow end to end, identify the stall, and leave with a written spec. It starts with a free 15-minute Fit Call — we decide together if it's a fit.

Book a Free Fit CallSee DRX Lot Assistant™ Case Study

Sources

AFCautofinance.com/insights/how-to-cut-reconditioning-time

Carketacarketa.com/dealership-recon-software-vs-spreadsheets

Rapid Reconrapidrecon.com

ACV Auctionsacvauctions.com/blog/car-dealership-profit-margin

Harney Partnersharneypartners.com/floor-plan-financing-for-auto-dealers

DealerClickdealerclick.com/blog/true-cost-of-dms-software


Related Reading

I Managed 5,000 People. Now I Manage AI Agents.The Tools Businesses Used to RentWhat Is Agentic Engineering — The Full DefinitionAgentic Engineering vs. Vibe CodingCase Studies — Production Software in the Wild

Build With RAIL: Free

90 Seconds to
Build Your App
With RAIL.

Answer three questions—type them or say them out loud—and watch RAIL scope your app in real time. Named app, working interface, and a build blueprint you keep. Before you ever talk to anyone.

A named app. A working interface. A blueprint PDF you keep. Whether we ever talk or not.

AI-powered90 secondsType or speakPDF blueprint
Build Your App Blueprint →Name + email to receive your PDF blueprint.