.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Procurement Guide How Are Automotive Dealer Management Systems DMS Priced for Enterprises
For a large dealer group, the hardest part of buying a dealer management system is rarely obtaining a DMS quote. The harder task is determining what that quote will become once CRM, fixed operations, data connections, transaction services, implementation, new rooftops and annual increases reach the invoice. CDK’s last public-company filings make the problem unusually visible: in fiscal 2021, its measure of monthly revenue per DMS customer site included the DMS fee, layered applications and data-integration fees, while transaction revenue sat in a separate category. In other words, the licence was only one part of what a dealership paid.
Competitive conditions have also changed. In March 2018, the Federal Trade Commission described CDK and Reynolds & Reynolds as the two largest suppliers to franchised new-car dealers and challenged CDK’s proposed $190 million purchase of lower-priced challenger Auto/Mate; the transaction was abandoned. By 31 December 2025, Asbury Automotive Group said in its Form 10-K that it had already moved 38 stores from CDK to Tekion as part of a broader DMS transition. Large groups therefore have credible alternatives, but greater vendor choice does not automatically create comparable pricing.
Monetizely’s position is that enterprise DMS software should be bought with a per-rooftop monthly subscription as the primary meter. Core departmental software, ordinary data access and a defined integration allowance should sit inside that rate; transaction charges should remain outside only where a real pass-through cost exists. Per-user recurring pricing and uncapped interface fees should be rejected because they make the bill grow faster than the operating value of the DMS.
The real DMS price sits outside the headline licence
DMS procurement becomes clearer when pricing is treated as a system rather than a number. Monetizely’s 5-Step Pricing Framework starts by separating customers whose needs and willingness to pay differ, then decides what each customer receives before choosing the unit that makes the bill grow. Only after those choices does the supplier set rates and build the quoting, billing, renewal and control processes required to run them. The same discipline runs through Monetizing Agentic AI: a price works only when the offer, the meter and the way it is administered reinforce one another.
For a dealer group, the five steps translate directly into procurement questions:
Three of those steps deserve disproportionate attention in a DMS negotiation: Packaging, Pricing Metric and Operationalisation. A per-rooftop rate can be sound and still produce a poor contract if half the required applications are excluded or if ordinary data connections acquire separate monthly charges.
Enterprise rate cards are remarkably opaque. As of 13 August 2026, the public buying pages we reviewed for the six major franchise or enterprise-oriented alternatives below did not present a simple recurring enterprise list price. Auto/Mate discloses relative monthly-cost positioning, Tekion publishes implementation rules, and historical SEC filings disclose useful metrics for CDK and Dealertrack, but procurement still requires a negotiated order form.
The comparison below therefore focuses on the documented pricing meter, not an invented estimate of a confidential quote.
| Vendor | Documented dominant pricing metric | Primary-source evidence and date | Where spend can expand | Monetizely procurement read |
|---|---|---|---|---|
| CDK Global | DMS customer site per month | FY2021 10-K says its site metric included DMS monthly fees, layered applications and data-integration fees; transactions were separately reported. 30 Jun 2021. | Added applications, transactions, implementation and services | The rooftop/site is the right primary meter. Buyers should stop separate recurring layers from recreating a second meter. |
| Reynolds & Reynolds | Monthly dealership maintenance/support, with separately documented per-dealer integrations | A 2005 Reynolds agreement in federal litigation carried $6,088.26 monthly maintenance/support; separate 2017 federal-court evidence documented per-dealer RCI charges. Current RMS pricing is not posted publicly. | Integration, additional products, training and contractual changes | Preserve the dealership-level subscription, but force every recurring data and module charge onto one schedule. |
| Tekion | Negotiated order-form pricing; implementation explicitly varies with DMS users, CRM users, payroll users and rooftops | Current implementation terms, accessed 13 Aug 2026, say changes in those counts may create extra implementation charges. Its Feb 2020 launch advertised zero monthly integration fees. | Implementation scope, user counts during deployment, added products | Do not let an implementation input quietly become the long-term recurring meter. Fix the subscription to rooftops. |
| Dealertrack / Cox Automotive | Historically monthly subscription per subscribing dealership; current core DMS price is quote-based | Dealertrack’s 2014 Form 10-K tracked average monthly subscription revenue per subscribing dealership. Cox’s Jan 2025 integration terms define monthly integration fees per mutual dealer client. | Cox applications, transactions and third-party integration economics | The dealership metric is sound. Procurement must model the connected Cox stack, not only Dealertrack DMS. |
| DealerBuilt | Custom enterprise quote; recurring unit is not publicly disclosed | Current buying page, accessed 13 Aug 2026, describes an enterprise-class DMS tailored to each dealer and directs buyers to a custom demo; professional services include data migration and onboarding training. | Tailoring, professional services and integrations | Price opacity is the weakness. Require a unitised rooftop rate before comparing DealerBuilt with site-priced alternatives. |
| Auto/Mate, part of DealerSocket | Quote-based monthly support | Current pricing page, accessed 13 Aug 2026, says each dealership is quoted after a needs discussion and says customers often report monthly support bills 65-75% below Reynolds or CDK; Auto/Mate also states that it operates without long-term contracts. | Scope selected for each store and third-party applications | Its monthly model creates useful competitive pressure, but large groups still need a common bill of materials before comparing quotes. |
The table points to a surprisingly consistent answer: the dealership or rooftop is already much closer to the industry’s natural unit than the user seat. Where enterprise pricing becomes difficult is everything layered around that unit.
A seat is particularly weak for DMS because adding technicians, service advisers, accountants or sales staff does not create another dealership. Charging every employee can even discourage adoption of software whose value rises when the whole store uses the same system.
Transactions deserve a narrower role. Credit reports, electronic registrations, payment processing and similar services can carry genuine third-party unit costs. Core accounting entries, repair orders, customer records or routine API traffic should not become unlimited transaction meters merely because the vendor can count them.
Integration history shows why a cheap base licence can become an expensive ecosystem
The most important DMS pricing disputes have repeatedly centred on costs adjacent to the core system. Historical cases should not be read as evidence that a vendor’s 2026 quote contains the same charges. They are useful because they expose the contract points where buyers have previously lost control.
Ken Behlmann Automotive Services v. Reynolds & Reynolds provides the clearest example of recurring-cost drift. A federal court order dated 2 July 2012 records that Behlmann entered a Reynolds agreement in September 2005 with monthly ERA maintenance and support fees of $6,088.26. The dealer alleged that by 2010 its monthly maintenance bill averaged $8,913.90, and that it had been billed for increases or services it had not authorised. Those were allegations in litigation rather than findings that Reynolds had improperly charged every customer, but the 46% gap between the two figures shows why signed scope and invoice governance matter.
Authenticom v. CDK Global and Reynolds shows how data connections can become economically significant products of their own. In a 14 July 2017 federal opinion, evidence before the court showed Reynolds integration charges for the full AutoLoop suite of about $700 per dealer per month in 2015, rising to $835 plus writeback fees by 2017. The same opinion recorded CDK 3PA access costs of about $160 in 2014, $694 in 2016 and $735 in July 2017. Another example in the record showed a Reynolds RCI package used by Dominion rising from $247 per dealer per month in 2011 to $893 by September 2017.
The financial significance was not confined to courtroom testimony. CDK later disclosed that it recorded a $90 million litigation provision in fiscal 2019 related to antitrust lawsuits. A provision is not an admission of liability, but the figure demonstrates how material disputes around DMS integration economics had become.
The FTC’s 2018 CDK/Auto-Mate challenge shows the same issue from a competition perspective. In its administrative complaint, the FTC cited Auto/Mate’s market claim that its monthly support bills were often 65-75% lower than Reynolds and CDK and described Auto/Mate as an increasingly effective price competitor. The Commission challenged CDK’s proposed $190 million purchase of Auto/Mate, and the parties subsequently abandoned the deal. The FTC cited the 65-75% figure as evidence of competition; it did not independently certify it as an industry-wide saving.
Billion Auto Group’s 2019 testimony to Montana legislators adds an operator’s view of switching costs. In a 27 March 2019 exhibit submitted to the Montana Senate Business and Labor Committee, dealer Joe Billion alleged that Reynolds pursued $129,000 after his group selected another DMS provider. He also told legislators that outside vendors had faced Reynolds certification charges of $10,000 to $100,000 annually, including a proposed $100,000 data-access charge connected with a desired website-provider change. These were the dealer’s allegations to a legislative committee, not judicial findings.
The market has evolved since those disputes. CDK’s current Dealer Data Exchange page says CDK Drive DMS clients can control data sharing at no additional cost, while Tekion launched its cloud system in February 2020 promising open APIs and zero monthly integration fees. Buyers should reward those moves, but still write the promise into the order form.
Cox’s more recent terms illustrate why diligence remains necessary. Its DMS Integration Terms dated 21 January 2025 define provider charges that can include a one-time enrolment fee, monthly integration fees and annual module fees. After the initial term, Cox can increase those provider fees once per calendar year with at least 45 days’ notice; the document also permits a provider’s monthly integration-related surcharge to a mutual dealer client to reach as much as two times Cox’s monthly integration fee to that provider.
Our view is therefore firm: an integration is not a harmless technical footnote to DMS pricing. Where ordinary dealer data must flow to CRM, digital retail, service, inventory or reporting systems, integration economics belong in the original commercial comparison.
Three-year TCO exposes the false economy of negotiating the DMS line item alone
A procurement team can negotiate a good-looking base rate and still approve an expensive contract. The easiest way to see the problem is to model the entire recurring stack before comparing discounts.
Consider a 20-rooftop group. The first column below represents the figure a team might see if it compares only the core licence. The second architecture adds the kinds of modules, integrations and services that often arrive around it. The third puts those items into a controlled rooftop bundle.
The table means that a controlled bundle can appear about 6% more expensive than a bare core quote while costing roughly $3.5 million less over three years than an add-on-heavy contract.
That distinction changes negotiation strategy. Procurement teams often spend weeks attempting to remove another 5% from the headline subscription while leaving the much larger questions of module scope, data connections and annual increases open.
Rate setting should instead follow the primary meter. A 50-rooftop group deserves a lower per-rooftop rate than a five-store group because sales, implementation and support do not scale perfectly one-for-one. The discount should reward group scale without changing the meter itself.
Acquisitions also become easier to price. When a dealer group buys three stores, both parties know what should happen: three agreed rooftop units are added, subject to the group’s contracted volume band. A seat-based contract can create a far messier true-up involving every technician, accounting employee, manager and salesperson absorbed in the transaction.
Every major vendor leaves at least one commercial problem for the buyer to close
No supplier should be judged by whether its model has “pros and cons”. The more useful question is whether its offer survives the Packaging, Pricing Metric and Operationalisation tests inside Monetizely’s 5-Step Pricing Framework.
Our scorecard below measures each vendor against the committed architecture: one understandable rooftop meter, broad enough packaging to prevent recurring charge proliferation, and operating rules that allow the buyer to predict the invoice.
The synthesis is straightforward: none of these suppliers removes the need for commercial design by the buyer, even when the underlying product architecture is strong.
Tekion illustrates the distinction particularly well. A unified platform and zero-integration-fee positioning can solve part of the packaging problem, but its public implementation terms still count users and rooftops for deployment charges. Procurement should accept those variables for genuine implementation effort without allowing them to become permanent recurring expansion triggers.
CDK presents the reverse lesson. Its historical filings give unusually strong evidence that the DMS site is a workable commercial unit, yet the same filings show how revenue per site could expand through additional applications, integrations and pricing. CDK explicitly said in fiscal 2015 that growth in revenue per DMS site came partly from added solutions and pricing, which is exactly why a buyer must define what the rooftop rate contains.
Contract design matters more than another five points of discount
Once suppliers reach the final round, procurement should stop asking only, “What is the monthly DMS price?” The better question is, “Under exactly what operating events can this invoice increase?”
A negotiation checklist should turn that question into contract language:
The checklist means the commercial model is largely finished before the parties begin arguing about the last few points of discount.
A strong contract should consequently produce a boring monthly invoice. Twenty operating rooftops should create roughly twenty contracted rooftop charges, plus clearly identifiable pass-through activity and pre-approved changes. A bill that requires a specialist to explain dozens of data, interface, module and user lines has failed the Operationalisation step regardless of its headline discount.
In 2026, procurement should standardise the buying model before choosing the supplier
Monetizely’s position for 2026 is not a call for the lowest-cost DMS. Buyers should choose the best operating platform that will accept a clean commercial architecture: per-rooftop subscription as the primary meter, broad core packaging, transparent pass-through transactions, controlled implementation and predictable growth.
The practical actions now sit above individual contract clauses.
Decide the dealership technology architecture before launching the RFP. Determine whether the group intends to consolidate CRM, fixed operations, F&I and related workflows into the DMS platform or preserve a best-of-breed stack. A supplier cannot price comparable scope until the buyer has made that strategic choice.
Build the baseline from the entire current technology estate. Finance should reconstruct twelve months of spend across the DMS, bolt-ons, third-party data connections, transaction services and support before comparing a replacement. A $200,000 DMS saving is meaningless if the selected architecture adds $400,000 elsewhere.
Keep two credible suppliers alive through final executive approval. The FTC’s 2018 Auto/Mate case showed the role challenger competition can play in DMS pricing, while Asbury’s large-scale Tekion transition shows that enterprise switching is no longer merely theoretical. Commercial leverage declines sharply once the incumbent or challenger knows the board has made its choice.
Run the finalist through live dealership workflows before awarding the group. Put sales, service, parts and accounting teams at representative stores through the proposed operating model. The cheapest subscription creates no value if poor adoption leaves the group paying for both the new platform and replacement point tools.
Give DMS economics joint executive ownership after go-live. Finance, technology and dealership operations should review adoption, total software spend and application rationalisation together. The goal is not simply to hold the vendor to its starting price; it is to prevent the technology estate from rebuilding the same bolt-on cost structure the procurement exercise was meant to remove.
For a large automotive retailer, the best DMS agreement should become more economical as the group scales, not more complicated. Price the rooftop, bundle what every rooftop must use, meter only genuine pass-through activity separately, and make all other recurring spend earn its way onto the invoice. That is the commercial standard we believe enterprise buyers should take into the 2026 DMS market.
Assumptions
The three-year TCO model uses a 20-rooftop US franchised dealer group. The core-only case starts at $7,500 per rooftop per month plus $25,000 implementation per rooftop and a 2% annual increase; the add-on-heavy case starts at $12,000 per rooftop per month, including $4,500 of added software/integration/service spend, plus $40,000 implementation and a 5% increase; the controlled bundle starts at $8,000 per rooftop per month plus $25,000 implementation and a 2% increase. These figures are modelling inputs, not vendor quotes. Taxes, financing costs, internal labour, hardware and business interruption during migration are excluded.
Footnotes
Monetizing Agentic AI: https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
CDK Global, Form 10-K for fiscal year ended 30 June 2021: https://www.sec.gov/Archives/edgar/data/1609702/000160970221000058/cdk-20210630.htm
Federal Trade Commission, Administrative Complaint, In the Matter of CDK Global, Inc. and Auto/Mate, Inc., March 2018: https://www.ftc.gov/system/files/documents/cases/docketno9382cdkautomatepart3complaintredactedpublicversion_0.pdf
U.S. District Court, Authenticom, Inc. v. CDK Global, LLC and The Reynolds and Reynolds Company, Opinion and Order, 14 July 2017: https://www.govinfo.gov/content/pkg/USCOURTS-ilnd-118-cv-00868/pdf/USCOURTS-ilnd-118-cv-00868-2.pdf
U.S. District Court, Ken Behlmann Automotive Services, Inc. v. The Reynolds and Reynolds Company, 2 July 2012: https://www.govinfo.gov/content/pkg/USCOURTS-moed-412-cv-00317/pdf/USCOURTS-moed-412-cv-00317-0.pdf
Montana Legislature, Senate Business and Labor Committee Exhibit, Billion Auto Group, 27 March 2019: https://archive.legmt.gov/bills/2019/Minutes/Senate/Exhibits/bus63a09.pdf
Tekion, Automotive Retail Cloud launch and pricing/integration positioning, 11 February 2020: https://tekion.com/blog/blog-post-automotive-retail-cloud
Tekion, Implementation Terms, accessed 13 August 2026: https://tekion.com/implementation
Asbury Automotive Group, Form 10-K for year ended 31 December 2025: https://www.sec.gov/Archives/edgar/data/1144980/000114498026000051/abg-20251231.htm
Dealertrack Technologies, Form 10-K for year ended 31 December 2014: https://www.sec.gov/Archives/edgar/data/1333513/000114420415011777/v402458_10k.htm
Cox Automotive, Dealer Management System Integration Terms and Conditions, version 1, 21 January 2025: https://www.coxautoinc.com/terms/wp-content/uploads/sites/3/Cox-Automotive-DMS-Integration-Terms-and-Conditions.pdf
DealerBuilt, Enterprise DMS Platform, accessed 13 August 2026: https://dealerbuilt.com/home/
DealerBuilt, DMS Installation and Professional Services, accessed 13 August 2026: https://dealerbuilt.com/professional-services/
Auto/Mate, DMS Pricing, accessed 13 August 2026: https://automate.com/dms/pricing/
Auto/Mate, official company/product statement describing monthly customer relationship and no long-term contracts: https://automate.com/auto-mate-launches-recommended-services-to-drive-fixed-ops-revenue/
Reynolds & Reynolds, Retail Management System / ERA-IGNITE, accessed 13 August 2026: https://www.reyrey.com/solutions/retail-management-system
Dealertrack, Dealer Management System, accessed 13 August 2026: https://us.dealertrack.com/content/dealertrack/en/dealer-management-solutions.html
CDK Global, Dealer Data Exchange, accessed 13 August 2026: https://www.cdkglobal.com/dealership-operations/data-management/cdk-dealer-data-exchange
CDK Global, Form 10-K for year ended 30 June 2020, including fiscal-2019 antitrust litigation provision: https://www.sec.gov/Archives/edgar/data/1609702/000160970220000015/cdk-20200630.htm