Dealership CRM Demo Checklist

Take the tour away from the vendor and run your own store's worst afternoon on their screen instead.

Every vendor demo you sit through is a well rehearsed path through clean data. That is not dishonest, it is just what a demo is. The trouble is that the path avoids the same three areas at nearly every vendor, and those three are where your store will live.

Messy data. Demo databases have complete records, valid phone numbers and no duplicates. Yours has a customer entered four times, two disconnected numbers and a name spelled three ways. How the system behaves on that is the actual product.

Volume and interruption. The demo shows one lead handled calmly. Your Saturday is nine leads, three walk-ins and a phone that will not stop. Click count and screen switching stop being aesthetic concerns at that point and start costing you appointments.

The unhappy path. A lead that arrives with no phone number. A text reply from a number nobody recognizes. A salesperson who quits and leaves ninety active customers behind. Nothing rehearsed ever goes there.

The fix is simple and almost nobody does it. Take the agenda away from the vendor before the call and hand them scenarios instead.

Email every vendor on your shortlist the same message, at least a week out, with the same three or four scenarios written in plain language. Tell them explicitly that you would like to skip the company overview and start at scenario one.

Sending it early matters. You are not trying to catch anyone out, you are trying to make the demos comparable, and a vendor who has prepared your scenarios properly will show you a better version of their product than one improvising. How a vendor handles this request is itself information: the ones who insist on running their standard tour anyway are telling you something about how the relationship will go.

Ask for a working environment you can log into afterward, not just a screen share. Ask who will be on the call, and request that it includes somebody technical rather than only sales, because half your questions will be technical by minute twenty.

And decide your criteria and weights before the first demo, not after the last one. The vendor comparison template covers the scoring side, and it only works if the sheet exists before you have been impressed by anything.

These are the ones we would send. Adjust the details so they read like your store, and keep them identical across vendors.

Scenario one: the 9pm Saturday lead. A lead arrives at 9:04pm on a Saturday from a third party source. Show me what happens automatically in the first five minutes with nobody logged in. Show me the auto response, who it gets assigned to and how, what happens if that person does not touch it by 9am Sunday, and what a manager sees when it goes untouched. Then show me the same lead arriving with a phone number that turns out to be invalid.

Scenario two: the text from an unknown number. A customer replies to a text but the number does not match any record. Show me exactly what a salesperson sees, how they identify the customer, and how the conversation joins the right record without retyping anything. Then show me the whole thread including calls, texts and emails on one screen.

Scenario three: the salesperson who quits. Reassign ninety active customers to two people, keep the history, keep the scheduled follow ups running, and show me what happens to appointments already booked in that person's name.

Scenario four: the manager's question. One salesperson closes at half the rate of another. Without exporting anything to a spreadsheet, show me why. Response time, touch count, channel mix, and let me listen to or read a call.

Every one of those is an ordinary Tuesday in a dealership, and the gap between systems shows up faster there than in any feature list.

Ask the presenter to stop sharing their desktop, pick up an actual phone, and run scenario two on it while you watch. Not a video of the mobile app. The phone in their hand, on cellular rather than office wifi if you can manage it.

Your salespeople are not at a desk. They are on the lot, in a customer's car, standing at the service drive. If texting a customer back takes six taps and two loading screens on a phone, your team will use their personal phones instead, and the day that happens your reporting becomes fiction and your customer records stop being yours.

Watch for the specific things: how many taps to reply to a text, whether the full history is visible on a small screen, whether they can call from the record with the store's number showing rather than their own, whether they can scan a VIN with the camera, whether photos attach easily, and what happens when the signal drops mid task.

Score mobile separately from desktop. They are frequently different products wearing one name, and the mobile one is where the majority of your team's actual work will happen.

This is the single highest value part of a demo and vendors rarely offer it, so ask for it in advance and hold them to it.

Take the mouse. Put your best salesperson, or better, your least technical one, in front of the system with no coaching, and give them three tasks: find a customer by partial last name, send them a text, and set a follow up for Thursday. Then watch without helping. Count the clicks and count the pauses.

Ten minutes of that tells you more about adoption than any presentation. Adoption is the whole ballgame in a CRM decision, because a system nobody uses properly is worth less than the one you already have, no matter how it scores on features. Stores that switch and then switch back almost always failed here rather than on capability.

Ask the salesperson afterward, out of earshot of the vendor, whether they would use it or work around it. Believe the answer. The adoption playbook covers what to do with that information once you have chosen.

Ask these in the demo rather than in a follow up email, because you want the answer demonstrated rather than described.

Show me my own data in this. Can I import a sample file now and see what happens to the duplicates? Show me the export. What exactly comes out if I leave, in what format, and does communication history come with it? Show me the opt out. If a customer unsubscribes from a service campaign, prove to me that the sales team cannot then text them. Show me user permissions. Can a salesperson see gross, and can I stop them?

Then the commercial ones, asked with the screen still up because they are less comfortable in writing. What is the total monthly cost with every module I just saw switched on, at my headcount? Which of the things you demonstrated cost extra? What is the contract length and the notice period? What does the price do at renewal? Is anything I saw dependent on an integration with the dealer management system you would need us to have?

Write the answers down during the call. Vendors comfortable being pinned down in a live demo tend to be the ones still worth having in year three. Contract negotiation covers what to do with those answers when the paperwork arrives.

Some of these are minor on their own. Two or more together is a pattern.

Refusing to run your scenarios. If a vendor will not deviate from the standard tour after a week of notice, either the product cannot do it or the organization cannot bend. Both matter.

"That is on the roadmap." Fine as an answer, worth zero in your scoring. Every vendor has a roadmap and none of them are contractual.

Vague export answers. Hesitation about what you can take with you when you leave is the loudest signal in the entire process.

Pricing that requires a conversation with someone else. You should be able to get a total number for your configuration by the end of the second call.

Pressure tied to a deadline. Discounts that expire on Friday exist to stop you from finishing your evaluation.

No live customer you can call. Ask for a store your size in your market that switched in the last year, and pick from a list rather than accepting the one reference they wanted to give you.

Everything answered yes. No product does everything. A vendor who never says "no, we do not do that" is either not listening or not telling you the truth, and both cost you later.

Fair to apply our own checklist to ourselves. If you send us those scenarios, here is what you would see.

Scenario one runs on lead distribution rules with escalation, an automated first response, and the phone validator flagging the bad number before a salesperson wastes twenty minutes on it. Scenario two runs in the SMS inbox, where the thread sits on the customer record next to email, calls and appointments, with call recording and transcription on the voice side so a manager reads a twelve minute call in thirty seconds. Scenario three is user management and reassignment with follow up processes intact. Scenario four is the three reporting layers plus lead attribution, and we would let you read a real transcript rather than describe one.

We would also show you things dealers usually do not expect in a CRM: the email validator and phone validator, RCS with SMS fallback, voicemail drop, lead pages, a free live chat widget, personal salesperson websites, customer facing deal pages with e-signature, and desking covering loan and lease with a fifty state tax matrix.

What we would tell you plainly is where we lose. We are not an OEM certified CRM. Our integration depth into the dealer management system you run is more limited than an enterprise product's, and if certified integration or manufacturer program compliance drives your money, you should stay where you are. If you would rather watch before booking anything, the recorded demo is up now, and pricing is published rather than quoted.

Score it within the hour, while it is fresh. Recall drifts toward whoever presented most recently, which is exactly how a store ends up choosing the last vendor it saw.

Then debrief with everyone who watched, and ask each person for one thing they liked and one thing that worried them. The worries are the useful half and they surface faster in a room than in an email thread. Log the questions the vendor could not answer and send them in writing the same day, because response speed on that email is a preview of support.

When you get to two finalists, stop scoring and start piloting. Run one team, or one store in a group, on the system for three to four weeks with a defined slice of live lead flow, and measure time to first response, follow up touches before a lead goes cold, and appointments set against your current system over the same period. Month to month pricing is what makes that possible; a vendor who needs a multi year commitment before you can evaluate is asking you to carry the risk they will not.

Once you have chosen, the migration checklist covers the cutover in order, including the overlap period and the integrations that have to be repointed.

How long should a CRM demo be?

Ninety minutes for a scenario driven first demo, then a second session for hands on time and commercial questions. Anything under an hour is a tour, and anything over two hours stops being information and starts being persuasion.

Who from the store should attend?

A sales manager, whoever runs the BDC, and at least one salesperson who will actually use it daily. The salesperson matters most, because the ten minutes with their hands on the keyboard predicts adoption better than anything else in the process.

Should we let the vendor use their own demo data?

For the walkthrough, yes. Then ask to import a sample of your own records and watch what happens to duplicates and bad phone numbers. Clean demo data hides the behavior you will live with.

What if a vendor will not run our scenarios?

Treat it as a finding rather than a scheduling problem. After a week of notice, refusing to deviate usually means either the product cannot do it or the organization cannot bend, and both show up again later.

Do we need a dealer management system integration for a demo to be meaningful?

Not with us. No dealer management system integration and no inventory feed is required to operate the platform, so a demo on live lead flow is representative. If a vendor's demo depends on an integration you do not have, ask what the product does without it.

Can we try it after the demo instead of signing?

With us, yes. Everything is month to month with no long term contract, so a three to four week pilot on one team is the normal next step rather than a signature.

We will run your worst Saturday on our screen, hand your salesperson the keyboard, and tell you where we do not fit. Month to month, no long term contract.