The questions to answer before you sign: what a dealer CRM must do, which lines matter for your type of store, how to run a fair demo and what the first year costs. Every answer comes with the free scored checklist to take into the demo. No call required.
≡Part of the Automotive CRM Guide for Dealers →Read the answer, then click through to the detail. The checklist below puts every line on paper for the demo.
Eight sections, seven of them scored to 130 points, with a demo test for each, real-scenario worksheets and a first-year price sheet. Print it, score every vendor on the same lines, and compare the totals before you compare the quotes.
Print it, take it into every demo, and score up to three vendors side by side.
If the download did not start on its own, the button below has it.
Download the checklist (PDF)Eight things, each scored 0, 1 or 2 for what the vendor showed you, not what the rep described. Sections 1 to 7 total 130 points; section 8, pricing, is one first-year number per vendor, compared on its own.
Every lead arrives complete: source, type, the customer’s own comments, vehicle, stock number, VIN and trade. Duplicates merge without losing history. Routing follows your rules.
In practice. Log every walk-in, including the ones “just looking”, and re-confirm email and mobile at every touchpoint, service visits included. Keep the lead-source list short: two near-identical entries make new reps guess, and the guesses corrupt the ROI report.
How do you test it?Send the vendor a real lead and watch what the rep sees.
The CRM, or the AI beside it, summarizes the request, flags unanswered questions and intent, surfaces objections, and recommends the next step in your own process.
In practice. Read every inquiry the customer has ever submitted, not only the active one; six leads in a week are six histories, and they may span several models. A wish list that matches stated needs to arriving inventory replaces the paper list walked across the lot each morning.
How do you test it?Submit a detailed lead and ask what the system understood.
One dated, attributed record: who did what and when, human or automation, with an audit trail of changes to customer, vehicle and trade data.
In practice. Sort active leads by last activity, not the task list; trainer Sean V. Bradley’s store audits keep finding prospects untouched for a week while the task list looked complete. Every attempt gets a note, including a turnover to a manager and what the manager said.
How do you test it?Open a record with weeks of activity. Can a manager follow it?
Both channels live inside the record, with delivery and read status where supported, in order, on the mobile app as well as the desktop.
In practice. Text consent is an explicit opt-in stored on the record. Automated emails pause the moment a human engages, or the customer gets a template mid-conversation. Each template reports sent, read and replied counts, and the ones below your benchmark get rewritten.
How do you test it?Text and email the same customer from the mobile app.
Website, DMS, inventory, lead providers, phone, texting, digital retailing, desking, finance, trade tools, chat, data mining and AI: documented, with direction, frequency and fees.
In practice. Reconcile the sales log against the DMS daily so every sold customer carries a deal number and stops getting unsold follow-up. Ask what the service lane sends to sales: tomorrow’s appointments with equity, a repair order opening or closing above a dollar amount. Fewer logins means more usage.
How do you test it?For each tool you use today: what syncs, how often, at what cost?
New leads, unanswered leads, customers waiting, today’s and missed appointments, sold and unsold, employee activity and response time, across every rooftop.
In practice. Per salesperson: today’s completed activity, tasks due, overdue tasks with one click to the customers behind them, and the sent emails readable. One page per rep that combines tasks, appointments, service visits and recent leads is the screen for a five-minute daily one-on-one.
How do you test it?Show a sales manager’s first ten minutes of the day.
Reports the store builds itself, with percentages and lead ROI rather than raw activity totals, plus leads without engagement, lost leads and gross where available.
In practice. Two reports experienced managers review every week: activity by salesperson, every figure drillable to the customers behind it, and lead-source ROI with leads, appointments, shown, sold, gross, cost per lead and profit by source. Manage activities, not closing ratio: when managers lean on the ratio, reps stop logging ups.
How do you test it?Recreate three reports you already run, live.
The complete first-year cost: base CRM with ILM and desking, rooftops, users, AI, texting, license scanning, integrations, implementation, migration and training.
In practice. Contracts commonly run three years, and a store whose managers never bought in is held to the term anyway. Price training alongside the subscription, monthly rather than once, and choose on fit and support rather than the lowest number.
How do you test it?Price the exact configuration that was demonstrated.
Two core systems and the tools around them. The DMS is the record of deals, F&I, parts, service and accounting; the CRM holds customers, vehicles, leads and conversations. Website, inventory, desking, digital retailing, phones and texting sit around both, which is why requirement 5 asks how each one connects.
Where do the in-practice lines come from? They are paraphrased from the dealership trainers and CRM specialists credited on the best-practices page, which lays out the daily process behind each line, with diagrams, and names every source.
The one that scores highest on the lines your store weights most. The checklist does not change from store to store; the weights do. Find your type, then weight the matrix.
A new-car store runs on leads it does not fully control: manufacturer programs, marketplaces, its own website and the service drive. Some manufacturer programs keep an approved list of CRMs; check yours first.
The trapBuying the largest bundle because the DMS vendor sells one, then paying for modules nobody opens. Requirements first, discount second.
No manufacturer behind the store, and one person often running the whole internet department from a phone. Leads come from the marketplaces and the website, and the price has to fit one rooftop.
The trapTwo traps, in opposite directions: a spreadsheet or generic small-business CRM that cannot read an automotive lead, or a franchise-grade CRM priced for a store you are not.
Several stores, often several brands, frequently more than one DMS. The question is what the group can see across all of them, and whether a customer from one store is recognized at the next.
The trapLetting each rooftop pick its own CRM, or forcing one onto stores whose DMS it has never met. Either way, the group reporting never arrives.
For your store, the three that score highest on your weighted checklist. General “top CRM” lists mostly rank business software that cannot read an ADF lead or hold a VIN, and dealer rankings weigh someone else’s store. Shortlist three, run the same lead through each, and let the totals rank them.
From what your store already runs. A franchise store starts with the CRMs its manufacturer program accepts and its DMS has a documented integration with. Every store then adds the ones peers of its own type use, and drops any that fail requirement 1 on a real lead.
Decisive should decide the shortlist; weigh it separates finalists; baseline means every serious vendor passes. Score all eight anyway: the weight changes what a low score costs you, not whether to look.
| Requirement | Franchise store | Independent or used-car lot | Multi-rooftop group |
|---|---|---|---|
| 1 · Leads and customer information | ●DecisiveOEM, marketplace and website leads arrive complete, with source, and merge cleanly. | ●DecisiveADF leads with the vehicle attached; duplicates merged when one shopper enquires three times. | ●DecisiveOne record per customer across rooftops, with routing and a lead-ownership rule. |
| 2 · Lead reading and customer intelligence | ●Weigh itVolume makes the summary useful: which leads asked a question nobody answered. | ●Weigh itFewer leads, one reader. The summary is the second pair of eyes. | ●Weigh itA standard: the same reading of intent at every store, so reports agree. |
| 3 · Communication history | ●DecisiveSales, BDC and service touch one customer; the record shows who did what, dated. | ●BaselineEasier to keep honest with two people. Check it is dated and cannot be edited silently. | ●DecisiveBought at store A, serviced at store B: one history, not two. |
| 4 · Email and texting | ●DecisiveBoth channels in the record and the mobile app, with consent under TCPA in the US and CASL in Canada. | ●DecisiveTexting is the channel. If the app cannot text from the record, a personal phone replaces the CRM. | ●DecisiveThe same consent and opt-out handling at every rooftop; a STOP at one store applies to all. |
| 5 · Integration and API access | ●DecisiveDMS, OEM feeds, inventory, phones, digital retailing, desking: direction, frequency and fee documented. | ●Weigh itFewer systems, but the marketplace feeds, website and inventory tool must be on the list, not promised. | ●DecisiveSeveral DMS platforms: every store’s DMS needs its own documented integration before signing. |
| 6 · Manager dashboard | ●Weigh itUnanswered leads, missed appointments and response time by salesperson, for the first ten minutes. | ●BaselineThe manager can see the floor. Weight the mobile view over the wall screen. | ●DecisiveEvery rooftop on one screen, comparable, with role-based views for group, store and salesperson. |
| 7 · Reporting | ●DecisiveReports the store builds itself, in percentages and lead ROI by source, plus what the OEM requires. | ●Weigh itThree reports you already run, recreated live. A vendor ticket means keep looking. | ●DecisiveSame definitions across stores, exportable, no ticket. This is what the group is buying. |
| 8 · Pricing | ●Weigh itPrice the configuration demonstrated: base with ILM and desking, users, texting, integrations, implementation. | ●DecisivePer-user pricing, the texting plan and the contract term decide whether one rooftop can afford it. | ●DecisiveRooftop fees multiply. Price per rooftop, user and integration, plus migration from each store’s CRM. |
Engagement counts and attempts per lead, at every type of store. CRM specialist Sam Maimone asks for them before lead volume, because they show whether leads are being worked at all.
Franchise, independent or group is the first sort. Practitioners who configure CRMs for dealers add four more.
Bring your own scenarios and ask every vendor the same questions in the same order. A prepared demo shows a CRM under ideal conditions. Yours shows the store, and you leave with a number instead of an impression.
One real internet lead with a trade and a question, three reports you already run, and the list of systems the store uses today.
Submit the identical lead, ask the identical questions, in the identical order. A prepared demo shows ideal conditions; yours shows the store.
Every line of the checklist gets a 0, 1 or 2 for what you saw, not what the rep described. Sections 1 to 7 total 130 points.
For each product you use: what data syncs, in which direction, how often, and at what extra cost. A lead-only connection is not a sync.
Base CRM with ILM and desking, rooftops, users, AI, texting, scanning, integrations, implementation, migration, training. One number per vendor.
Write a discovery. Sam Maimone’s first step with any store that wants to buy or switch is to sit with the managers and write down how walk-ins, web leads and phone-ups are handled today, where the gaps are and what each costs. Then map every CRM to that document.
When key managers will not buy in. That is Maimone’s rule, because CRM contracts commonly run three years, and a principal who wants out after six months because nobody adopted the system is held to the term.
Yes. Ask what the account manager does after go-live. Mark Vickery, who leads performance management at a CRM vendor, holds his team to coming into the store and saying what it is doing wrong. If the role on offer is training and tickets, budget for coaching elsewhere.
Mobile and integration depth. Notes, appraisals and contacts get logged on the lot or not at all. And fewer logins means more usage, so the CRM should be the one screen that pulls in website, inventory, desking and service data.
It depends on the configuration, so build one first-year number from its parts. This page gives no dollar figures: it gives the components every quote is built from, the order to price them, and the question each type should ask. Requirement 8 is the same test in one line.
Per rooftop, then per user or seat band; a group pays both, multiplied. Count everyone who touches a record, service advisors included.
Rooftops × usersILM plus desking is usually the base: receiving and routing internet leads, and structuring the deal. Confirm what is a module.
ILM + deskingTexting, per message, user or rooftop. Each integration (DMS, inventory, phones, lead providers), some charged on both sides. AI. License scanning.
MonthlyImplementation, migration of the current CRM’s records and history, and training. Ask what migrates: customers only, or history too.
First yearRooftops times users, plus texting and each integration. Ask for it in those parts, then add the one-time costs for the first year. Two quotes compare only when they price the same configuration.
Free generic CRMs exist, but a generic small-business CRM cannot read the ADF lead a marketplace sends or hold a vehicle record with a stock number. If a free plan is on the table, score it like any other, and still price the first year: texting, integrations and training cost money even when the license does not.
Practitioners who roll these systems out put the term and the training ahead of the monthly price.
Replace it when the record cannot be trusted; keep it when the reply is the gap. Low marks on requirements 1, 3, 4, 5 and 7 are a CRM problem. High marks with leads still waiting until morning for a reply is a different problem, with a different fix.
Before you replace it, be sure the problem is the system and not how it is run; several of these show up in a CRM left on the vendor’s defaults. If the problem is how the CRM is run, start here.
Matador is not a CRM; it is conversational AI that works alongside the one you keep. What Matador adds, and how it connects to the CRM you have.
The short version of the whole decision: what a dealership CRM must do, how to score one, what running it well looks like, and when to add AI instead.
Open the guide →Best practicesThe processes and daily habits the people who train dealerships on their CRM teach, drawn as diagrams you can hold your store against.
Read →Matador IntegrationsWhat conversational AI adds to a dealership CRM, how it connects to fourteen CRM and DMS platforms, and what syncs in which direction.
Read →Buyer’s guideUse cases by department, the questions to ask vendors, what implementation involves, and how to read the ROI.
Read →Industry mapFrom design and the factory floor to the car, the supply chain and the dealership: where AI is at work, and where it is not yet.
Read →The PDF is free and needs no call. When the scores are in, twenty minutes with our team shows what Matador adds to the CRM you keep: we connect to it, replay real leads from your store, and show you the appointments sitting in them.