The Category That Sold Itself the Same Product Twice

The Category That Sold Itself the Same Product Twice

AI Summary

The dealer CRM category has commoditized. A decade of M&A inside the major incumbents collapsed the vendor count while feature parity converged. Pricing power disappeared a decade ago. The dealer principal who bought one CRM in 2018 and a different one in 2023 cannot name what the second purchase changed. The next wave of value moves to a layer the incumbents cannot build because their architecture is wrong for it. We are building toward that layer.

Source: Brevmont Labs, dealer software category analysis, April 2025.

---

A category that consolidated by buying its own competitors

Between 2014 and 2024, the dealer CRM category consolidated. Cox Automotive acquired VinSolutions in 2014 and DealerSocket in 2021, folding both into a single dealer-tech portfolio that now sits inside Cox's broader Manheim and Autotrader infrastructure. ELead, the long-time independent CRM founded in the 1980s, was absorbed into CDK Global in 2018 and consolidated into the CDK platform. CDK Global itself, after spinning out from ADP in 2014, traded on the public markets through the late 2010s and was taken private by Brookfield in 2022 at an enterprise value above seven billion dollars. Reynolds and Reynolds, the long-time DMS-CRM duopoly partner of CDK, remained privately held throughout.

The vendor count visible to a dealer principal shopping CRM in 2014 was meaningfully larger than the count visible in 2024. The names that survived were the names that consolidated under private equity or that absorbed acquisitions into a platform offering. Net-new entrants into the category were rare. Most of the rare ones did not survive a renewal cycle.

This is what category consolidation looks like from inside the dealer principal's seat. The choice set narrowed. The pricing did not respond.

Feature parity converged faster than vendor count fell

Across the same 2014 to 2024 window, every major dealer CRM in the category converged on the same feature set. Lead routing. Activity reports. Inbound capture. Round-robin assignment. Click-to-call. SMS templates. Email templates. Manager dashboards. Source attribution. Mobile applications. Integration directories listing partner logos that were not always wired to anything operational.

This is the pattern in every commoditized SaaS category. Feature parity is a six-month engineering project for any well-funded incumbent. The vendor that ships a new capability in March will see the same capability appear inside a competitor's release notes by October. The differentiation moves to brand, to sales motion, and to contract terms. None of those advantages last more than two renewal cycles.

The category-leading platforms today all ship roughly the same product. The differences are in interface treatments, in the specific roster of partner logos each platform has stitched into its integrations page, and in the relative aggression of each platform's per-rooftop pricing model.

The dealer principal evaluating these platforms cannot tell from the demos which one will materially change his floor. The vendors cannot honestly tell him either. The thing that would change his floor is not in any of the demos.

Pricing did not follow consolidation

Software consolidation, in most categories, produces a pricing decline as the incumbents capture scale economies. The dealer CRM category did not follow that pattern. Per-rooftop CRM pricing remained roughly stable across the consolidation decade. The vendors captured the scale economy on their side of the ledger and did not pass it through.

A dealer principal buying CRM in 2024 was paying something close to what he would have paid in 2018, sometimes more, often on longer required contract terms than were available at the start of the decade. The negotiated number varied, but the headline structure of per-rooftop license plus multi-year minimum plus stacked integration fees did not move materially.

This is not a failure of the dealer principal's negotiating posture. It is a structural feature of a category in which the buyer cannot meaningfully threaten to defect. There is nowhere meaningfully different to defect to. The defection threat that would have produced pricing pressure does not exist when the alternatives are functionally identical.

The buyer who cannot articulate the difference

Ask twelve general managers a single question. Name three concrete things your current CRM does that your previous one did not.

Most respond first with vendor marketing language. Single source of truth. Cleaner data. Improved manager visibility. None of those phrases describe an observable behavior on the floor. They describe what the website said.

Some respond with a specific report. The new system surfaces a Saturday close-rate report the old one did not. The new system shows aged inventory by source. Press on these, and the same reports turn out to have existed in the old system under a different menu path. Nobody had used them in either platform. The reports are present in both. The consumption pattern is absent in both.

A meaningful share respond honestly that they cannot name a difference. They paid for the migration. They went through the project management. They signed the renewal. The product they bought was the product they had been told they were buying. The product they received was not different from the product they had.

This is what commoditization looks like from the buyer's seat. The product is real. The differences are not.

Why the incumbents cannot build the answer

The thing the dealer principal actually wants from a CRM is execution. He wants the rep to send the right message at the right time to the right customer through the right surface. He wants the manager to see what actually went out, not what got typed afterward. He wants the dashboard's data to match the floor's reality.

None of the incumbents can build this from inside their own architecture. The architecture is the system of record. The system of record is, by design, downstream of the rep's typing. Reorienting that architecture to capture what actually happened at the customer interface, rather than what the rep got around to logging, is not a feature ship. It is a category ship.

A category ship requires the vendor to redefine its own product around a different data model. PE-owned incumbents do not redefine. They optimize for margin retention, for renewal terms, and for the OEM relationships that generate program-revenue stability. The redefinition cost is borne by a vendor outside the category, building toward a product the dealer principal has been waiting for without having a name for it.

This is not an observation the incumbents would dispute. They would dispute the timing. We do not.

The OEM customer who is not the dealer

There is a second structural reason the incumbents cannot build the next layer. The largest dealer software vendors are not, strictly speaking, selling to dealers. They are selling to OEMs.

A meaningful share of the major CRM and DMS revenue lines is OEM program revenue. The factory mandates a tier of software for its certified dealers. The vendor is qualified by the OEM. The dealer is enrolled by the OEM. The pricing is negotiated at the OEM level. The dealer principal pays the bill but does not select the product.

This dynamic produces a vendor incentive structure aimed at the OEM, not the dealer. Product roadmaps optimize for OEM compliance reporting, OEM-mandated lead source integrations, and OEM-branded program features. The dealer principal's actual pain is downstream of all of this. The vendor's investment focus follows the buyer who controls the largest single line of revenue, which is the factory, not the rooftop.

The next layer of value, by contrast, is sold directly to the dealer principal. The execution layer's customer is the buyer the incumbents have been treating as a downstream beneficiary. The pricing power, the product roadmap input, and the renewal leverage all sit with the rooftop.

This is the second architectural reason the incumbents cannot build the layer. It would mean reorienting the customer relationship away from the OEM and toward the dealer. The OEM revenue line is too valuable to put at risk for a layer the OEM has not asked for.

What the next decade actually buys

The dealer CRM category is not going away. The system of record stays necessary. The audit trail belongs there. The compliance copy belongs there. The historical data belongs there. Dealer principals will continue to license CRMs from incumbents who continue to consolidate.

What changes is where net-new value enters. In every commoditized SaaS category we have studied, the new value enters from a different layer. Email service provider commoditization preceded the marketing automation layer. Help desk software commoditization preceded the customer success platform. Project management software commoditization preceded the work-OS layer. The pattern repeats because it is structural. The middle of a category becomes cheap. The layers above and below become expensive. The vendors that own the middle keep their renewal stream and lose the budget growth. The new layer captures the budget growth.

For dealer software, the new layer sits above the CRM. The CRM is the system of record. The new layer is the system of execution. The two are different categories, sold to different buyers inside the same dealership organization, on different pricing models. The CRM continues to charge by rooftop. The execution layer charges on a different basis. The dealer principal who has been paying for the CRM for a decade buys the new layer because the CRM did not solve the problem the CRM was sold to solve.

This is the architectural argument we are making with the work. The category opens for the first time in twenty years. The first lab to ship the layer at scale captures the decade. We have not asked the incumbents for permission. We do not expect to.

---

*Brevmont Labs publishes original research on the execution layer beneath relationship-driven sales. This essay opens our 2025 series on the structural conditions that produced the dealer software category we are positioned against.*