DMS Vendor Evaluation Scorecard

A structured way to compare dealer management systems, built so the loudest demo does not automatically win.

Dealer management system demos are performances. They are run by people who do this every week, on data that has been prepared, following a path that avoids the parts of the product that are awkward. That is not dishonest, it is sales, and every vendor does it including us on our own side of the business.

The problem is that a good demo produces a feeling, and a feeling is a terrible basis for a six figure, five year decision that touches accounting, parts, service and every person in the building. Two weeks after the last demo, what a management team actually remembers is which presenter was most likeable and which screen looked most modern.

A scorecard fixes that by moving the judgment forward in time. You decide what matters while you are still calm, you weight it, and then each demo becomes evidence gathering against a fixed list rather than an experience you react to. It also produces something you can hand to a dealer principal or a partner group that explains the decision without asking them to trust your instinct.

Build it before the first demo. A scorecard written afterward is a justification, not an evaluation, and everyone in the room will know.

LeadLocate does not sell a dealer management system and never has. No general ledger, no accounts payable or receivable, no payroll, no bank reconciliation, no deal posting to accounting, no parts inventory, no repair orders, no technician time, no warranty claims, no title or registration processing.

We sell exclusive local leads and a CRM that sits alongside whatever DMS a store runs, and neither a DMS integration nor an inventory feed is required for that to work. So we have no candidate in this evaluation. What we do have is a lot of exposure to stores mid conversion, and the pattern is consistent enough to be worth writing down.

Read this the way you would read advice from a manager at another store who has been through it. If you want the cost model that pairs with this scorecard, the DMS ROI calculator page covers the financial side.

Nine categories cover almost every real DMS decision. Add your own, but be suspicious of a list longer than twelve, because at that point everything is weighted so lightly that nothing decides anything.

Weight these against your store, not against a template. A high volume franchise point with a large service department should weight fixed operations heavily. A used car operation running twelve cars a week should weight it lightly and put the weight on deal workflow and commercial terms instead. A group weights integration and reporting higher than a single rooftop does, because consolidation across stores is where the pain shows up.

The honest way to set weights is to do it in a room with the department heads who will live with the outcome, before anyone has a preference, and to force the total to a fixed budget. Give the group one hundred points to distribute across the categories. A fixed pool prevents the failure mode where everything is important and therefore nothing is.

Expect an argument. The controller wants accounting weighted at forty. The service director wants fixed operations weighted at forty. That argument is the actual value of the exercise, because it surfaces the real trade off while it is still cheap to discuss. Resolve it before the demos and write down the resolution.

Two rules keep the weights honest. First, no category gets more than thirty points, because a single category that dominates makes the other eight decorative. Second, any category weighted below five should be removed rather than carried, since it will never change an outcome and its presence just makes the sheet look more thorough than it is.

Once weights are set, lock them. Changing a weight after a demo is the single most common way a scorecard gets bent to fit a decision that was already made emotionally.

Use a one to five scale. Anything wider invites false precision, and anything narrower cannot separate two decent products.

The rule that makes scoring work is that every score requires a note naming the evidence. Not "felt clunky" but "took eleven screens to restructure a deal with a trade payoff, observed in the 14 March demo". Not "good support" but "named implementation contact for ninety days, then queue based, confirmed by the rep in writing". A score with no evidence line is a feeling wearing a number.

Score independently before the group discusses. If everyone scores in the room together, the loudest person's number becomes everyone's number. Collect individual sheets, then compare, and spend the discussion on the items where scores diverge by two or more. Divergence is information: it usually means two people watched the same demo and saw different products, which is worth understanding before you sign.

Be careful with the seduction of the interface. A modern looking screen scores well on first impression and tells you almost nothing about whether month end close works. Weight what the system does, not how it looks doing it.

Take these into every demo. In our experience they move scores more than any feature walkthrough.

Show me an ugly transaction, not a clean one. A deal with a negative equity trade, a manufacturer rebate, a lienholder payoff that changes after funding and a structure change on delivery day. Ask how many screens it takes and who has to be involved.

What exactly can I export if I leave, in what format, at what cost, and how long does it take. Ask for it in writing. Your leverage on that answer is never higher than the moment before signature, and stores discover the true answer years later at the worst possible time. The DMS data ownership page covers what to insist on.

What does an integration cost, who pays for maintaining it, and what happens to it during a version upgrade. Then ask each of your existing vendors the same question from their side, because their answer and the DMS vendor's answer are frequently not the same answer.

What is the term, what is the escalator, and what is the cancellation process. And finally: give me three references at stores my size, in my segment, who converted in the last eighteen months. The last part matters. A reference from a store that converted six years ago is describing a different product and a different implementation team. Our list in questions to ask during a DMS demo goes deeper on the demo itself.

Be honest about the limits, because a weighted total carries an air of objectivity it has not entirely earned.

It cannot tell you how the vendor behaves in year three, once the implementation team has moved on and you are in the support queue like everyone else. References help. Nothing settles it.

It cannot capture the political reality of your store. If your controller has run one system for fifteen years and is retiring in two, that fact will shape the conversion more than a two point difference in a reporting score.

It cannot measure adoption. A system that scores highest on capability and lowest on usability will lose to a simpler one in practice, because a feature nobody uses has a value of zero. Where you can, put a real user in front of the system rather than watching a rep drive it.

Use the total as a tiebreaker and a discussion starter, not as a verdict. If the winner on points is not the one the room believes in, the interesting question is why, and the answer is usually a criterion that was never on the sheet.

One practical note that costs stores money every year. A DMS conversion consumes management attention for months, and during those months the front end of the store tends to get left alone. Response times drift, follow up discipline slips, and lead flow quietly underperforms while everyone is looking at the back office.

Keep the two decisions separate on purpose. The lead and CRM layer does not depend on the DMS at all in our case, because no DMS integration and no inventory feed are required to operate. That means the front end can be improved during a conversion rather than frozen through it, and it means a conversion that runs late does not also hold the sales floor hostage.

If you are building the integration list for the conversion anyway, the integration inventory template will save you a week, and the implementation plan covers the sequencing once you have picked a winner.

How many criteria should a DMS scorecard have?

Nine to twelve. Fewer and you miss something material. More and every category is weighted so lightly that nothing actually decides the outcome. Remove any category weighted below five points rather than carrying it for appearances.

When should the weights be set?

Before the first demo, in a room with the department heads who will live with the result, using a fixed pool of one hundred points. Lock them afterward. Changing a weight after a demo is how a scorecard becomes a justification.

Should the whole group score together?

No. Score independently, then compare. Group scoring lets the loudest voice set everyone's number. Spend the discussion on the items where scores differ by two or more, because that divergence usually means people saw different products.

Does LeadLocate compete in this evaluation?

No. We do not sell a dealer management system and have none of the accounting, parts, service or title functions one provides. We sell exclusive local leads and a CRM that runs alongside whichever DMS you choose, with no integration required.

What is the single most overlooked scoring category?

Data ownership and exit. What you can export, in what format, at what cost and on what notice. Stores learn the real answer years later when their leverage is gone. Get it in writing before you sign.

Should we pause front end projects during a DMS conversion?

You do not have to. Our lead and CRM layer requires no DMS integration and no inventory feed, so the sales floor can keep improving while the back office converts. Freezing the front end for six months is a real and avoidable cost.

See exclusive local leads and the CRM running on your market, independent of whatever DMS you pick. Month to month, no long term contract, no integration required.