The June 2024 DMS outages were a watershed moment for automotive retail. When a ransomware incident took tens of thousands of rooftops offline for days, it forced every dealer-group operator to answer a question they had been deferring: what does your store actually need from a DMS, and what can you run independently of it?
I am writing this because the post-mortem on those events is effectively a specification for the next generation of dealer software — and the specification is not about replacing the platforms that exist. It is about building the intelligence layer that makes them more resilient.
The architecture lesson
Modern DMS platforms were designed around a core premise: the general ledger is the center of the universe, and everything else bolts onto it. That was the right design for 1995. The lesson from 2024 is that it creates a concentration risk that no dealer group can afford to ignore now.
First, centralized infrastructure planes. When a single infrastructure layer serves every dealership in a customer base, an outage at the plane level is an outage for every customer simultaneously. The 2024 events made that risk concrete for the whole industry.
Second, broad credential scope. When the same credential that accesses the deal desk also accesses the GL, service pay, parts inventory, and customer records, the blast radius of any single compromised entry point is the entire stack. Narrower credential scopes would contain the exposure.
What resilient architecture looks like
The principle is isolation. If each rooftop has its own deployment boundary, a problem at one store does not propagate to others. The central GL can still exist for group-level reporting — but it should be a reporting aggregation, not the live transactional plane.
The infrastructure automation required to do that at scale — 10,000-plus rooftops — is genuinely available now in a way it was not a decade ago. That is the shift that opens the door for a new class of dealer-software architecture.
The incumbents are not standing still. The industry is actively addressing these issues. But the transition takes time, and dealers need to operate today.
What operators learned about decoupling
Three things became clear to anyone writing deals during the outage week.
- The deal desk does not need the DMS to be online. It needs the structure, the credit data, and the lender program file. If those three things exist in a separate layer, deals can continue.
- Customers do not care which DMS you run. They care about picking up the vehicle on Saturday.
- Floor-plan lenders will give you 72 hours and then start treating the car as aging — because from their balance sheet, it is.
Each of those is an argument for decoupling the intelligence layer from the DMS layer. If Louie is down, your DMS still works. If your DMS is down, Louie still knows what to do with the customer at the desk.
The market opportunity this creates
The most valuable dealer-software position right now is DMS-agnostic. An intelligence layer that sits cleanly on top of CDK, Reynolds, Tekion, Dealertrack, or ProMax — without touching the GL — gives dealers a resilience buffer they cannot get from a single-vendor stack.
For acquirers, it is an even simpler proposition: you are not betting on which DMS wins the next cycle. You are betting that dealerships still need the kind of help a desk manager needs, and that help becomes more valuable, not less, while the underlying infrastructure market continues to evolve.
That is what we built Louie to do.