The Stack a Franchise Dealer Group Actually Pays For

The Stack a Franchise Dealer Group Actually Pays For

AI Summary

A franchise dealer group running five rooftops carries between eight and fourteen simultaneous software contracts at each rooftop. The category-leading platforms (DMS, CRM, digital retailing, video walkaround, equity mining, BDC, reputation, inventory pricing, F&I menu) ship as separate purchases under separate contracts with separate renewal cycles. None of them compose. The integration story sold by every vendor is theoretical at the depth a real dealer group operates. The cost is paid in compounding subscription fees, in admin labor at the rooftop level, and in lost rep attention. The dealer principal sees one line item per vendor. The aggregate is a six-figure annual spend on a stack that does not behave like a stack. The next layer of dealer software sits above this stack, not beside it.

Source: Brevmont Labs, dealer software stack analysis, May 2025.

---

A category sold one contract at a time

A dealer principal running a five-rooftop franchise group sees software contracts arrive one at a time. The CRM renewal in February. The DMS contract in April. The digital retailing program tied to OEM compliance, contracted separately, renewing on a different cycle. The reputation management vendor contracted under a multi-rooftop master. The equity mining tool contracted by the GM at one of the rooftops without principal-level sign-off. The video walkaround tool contracted by the used-car manager at another rooftop. The BDC outsource partner contracted by the marketing director.

Each contract, in isolation, is a small decision. Each one looks defensible against the next twelve months of expected revenue. Each one was justified by a slide deck that referenced a specific operational improvement. None of the slide decks accounted for the other contracts that were going to be signed inside the same year by the same group.

The aggregate is the largest invisible cost in the franchise dealer group's operating budget. The principal sees one line per vendor on the AP report. The line items do not communicate with each other. The total reads, in the median group we have analyzed, between five hundred thousand and one and a half million dollars per year per five rooftops, depending on bundle structure and OEM enrollment.

This is not a procurement failure. It is a category structure that produces this outcome by design.

The bill of materials at the rooftop

A typical 200-unit-per-month franchise rooftop carries the following software contracts in some configuration. The DMS at the bottom, running between five and fifteen thousand dollars per month depending on store size, brand, and bundled services. The CRM running between one thousand and three thousand. Digital retailing in the three to six hundred range. Video walkaround between two and five hundred. Equity mining between three and four hundred. BDC management software at three hundred. Reputation management at two to four hundred. Inventory pricing and management between one and three hundred. Add a chat tool, a third-party lead aggregator subscription, a call tracking platform, and the OEM-mandated programs that range from no charge on paper to several hundred per rooftop per month in absorbed program fees.

The total per rooftop clears eight to fifteen thousand dollars per month in software, before payroll, before flooring, before any of the human work the software is supposed to support. On a 200-unit store, that is sixty to ninety dollars per vehicle sold in pure software cost, paid every month whether the cars move or not.

Multiply by five rooftops in a single dealer group. The annual category spend lands between four hundred eighty thousand and nine hundred thousand dollars before integration fees, training, and the percentage of group admin headcount that exists to keep the stack running.

The dealer principal sees one number per vendor on the monthly AP report. The number per vendor looks reasonable. The aggregate does not get audited as a single line because the category never produced a vendor that could be held accountable for the aggregate.

The integration tax

Every dealer software vendor's website has an integrations page. The dominant CRM platforms list more than a hundred partner logos in their integration directories. The DMS vendors list fewer but maintain the page. The category-adjacent tools (equity, video, retailing, reputation) all maintain partner directories. A casual reading of any of these pages would suggest the category is well-integrated.

Walk into a real franchise rooftop and ask which of the listed integrations is wired up live and serving operational data. The answer, across every group we have examined, is two to four. Lead injection from the dealer website into the CRM works. Inventory sync from the DMS into the CRM works at a delay. Sometimes the equity tool reads VIN data from the DMS. Sometimes it does not.

Everything else listed on the integrations pages is theoretical. The webhook is documented. Nobody at the rooftop wired it up. The vendor's integration team is happy to scope a custom project. The cost runs into mid-five figures and a calendar quarter of project management. The rooftop's IT capacity is one part-time generalist or no IT at all. The integration project does not start, or starts and dies inside the first sprint review.

This is the integration tax. The dealer principal pays the per-rooftop license for ten platforms that, in marketing copy, communicate with each other. In production, the platforms communicate with each other through manual rekeying done by the rooftop's admin staff and by the floor's reps. The labor cost of this rekeying is not on any vendor's invoice. It is on the dealer's payroll.

Industry estimates of the per-rooftop labor cost of stack reconciliation vary widely because no vendor measures it. Conservative estimates put the cost between five and twenty thousand dollars per rooftop per year in admin time alone, before the rep-side cost of context switching across tabs.

The vendor incentive that runs against integration

The reason most listed integrations remain theoretical is structural. A vendor that integrates deeply with the rest of the stack reduces switching cost. A vendor that integrates shallowly preserves switching cost. The longer the dealer's data lives only inside one vendor's database, the harder it is for the dealer to leave for a competitor.

This is not a conspiracy. It is product strategy. Customer success teams will deny it. Sales teams will deny it. Engineering teams will believe their own published roadmap. The behavior across fifteen years of vendor decisions tells the truer story. The integrations that ship are the ones that bring data in. The integrations that do not ship are the ones that let data out.

The dealer principal absorbs this asymmetry. Every shallow integration is a moat protecting the vendor's renewal. Every deep integration is a hole in the vendor's moat the vendor would rather not dig. The dealer is paying full per-rooftop pricing for a product whose integration roadmap is structurally aligned against him.

This is what is meant by "the integration story is theoretical." The story is not false. It is engineered to remain just credible enough to mention at sales-cycle close, and just hollow enough to never produce data exit.

The OEM-mandated overlap

The other structural feature of the stack the dealer principal cannot escape is the OEM-mandated layer. Each manufacturer runs a program that requires the franchise dealer to enroll in specific software tools as a condition of certification, co-op marketing, or factory program participation.

These OEM-mandated tools rarely replace anything the dealer already pays for. They overlap. The dealer principal who has chosen a CRM at the rooftop level then enrolls in an OEM-mandated lead routing program that injects a duplicate workflow into the rep's day. The dealer principal who has chosen a digital retailing platform then enrolls in a factory-mandated retailing program that runs in parallel. The dealer principal who has chosen an inventory pricing tool then absorbs the OEM's recommended pricing system on top.

Each of the OEM-mandated layers carries a pricing structure that is rarely negotiable. Each one duplicates a workflow the dealer principal had already solved with a freely-chosen vendor. Each one produces a parallel dashboard, a parallel report, and a parallel set of compliance obligations.

The dealer principal absorbs the duplication because non-enrollment puts certification at risk. The factory understands this leverage and prices the program accordingly. The category writes a check to the OEM-mandated vendor on top of the check it writes to the freely-chosen one.

The dealer principal's mental model

When the dealer principal evaluates this stack, he does not see the aggregate. He sees a sequence of small contracts, each justifiable against the operational improvement it promised at sale, each integrated with other tools according to a marketing claim that has not been operationally verified inside his group.

He has been told for ten years that the next vendor will solve the integration problem. He has switched CRMs in pursuit of that promise. He has switched DMS partners in pursuit of that promise. He has signed bundle deals across CRM, DMS, and digital retailing in pursuit of the promised composition that bundling was supposed to deliver. None of these decisions changed the underlying integration problem. The bundles produced cleaner pricing on his AP report. They did not produce a stack that composed.

This is the structural condition that opens the next layer.

What the next layer actually looks like

The next vendor that wins meaningful budget in dealer software does not enter the stack as another contract. Another contract would compound the problem. The next vendor sits above the stack and consumes it.

The architecture of an above-stack layer is different from the architecture of a stack participant. The layer reads from every vendor's surface and writes back to every vendor's surface. The dealer principal does not have to negotiate vendor cooperation, because the layer does not require vendor cooperation. The layer rides the rep's authenticated session inside each tool the dealer already pays for. The data flows because the user flows.

The economic implication is straightforward. The dealer principal continues to pay for the CRM, the DMS, the digital retailing program, the equity tool, the OEM-mandated programs. The renewal cycles continue. The vendor relationships continue. The aggregate stack spend does not fall in year one. What does fall is the integration tax, the rekey labor, the rep attention cost, and the dashboard inaccuracy that compounds across coaching, hiring, and pay-plan decisions.

The vendors do not have to cooperate with the next layer. The architecture does not depend on their cooperation. We assume they will not cooperate. We have built around the assumption.

The dealer software stack is not a stack today. It is a collection of tools that share a customer and nothing else. The next layer is the one that disappears into the existing tools, absorbs the integration problem, and stops asking the dealer principal to solve a problem the category has had fifteen years to solve and has not.

---

*Brevmont Labs publishes original research on the execution layer beneath relationship-driven sales. This essay continues our 2025 series on the structural economics of dealer software at the dealer-group level.*