Dealership CRM Scorecard for General Managers

Two scorecards. One for choosing a system, one for finding out whether the system you already pay for is doing anything.

A demo is a controlled environment run by someone who does it forty times a month. Every product looks good in one. The questions a general manager actually needs answered do not come up in a demo because nobody wants to raise them: whether your people will use it, how fast it makes them, what happens to the data when you leave, and what the whole thing costs against units sold.

A scorecard fixes that by deciding what matters before you see anything. You write the criteria and the weights first, then you score each vendor against your own list rather than being led through theirs. The discipline is the point. A GM who defines the criteria in advance cannot be talked into weighting a feature heavily just because it demoed well.

The second scorecard on this page is the one most stores skip and need more. It is not about buying. It is about grading the CRM you already own, monthly, on six numbers. Plenty of stores are paying for a good system and getting nothing out of it, and no vendor change will fix that. Find out which situation you are in before you shop.

Weight these to your store. What follows is a starting point that has held up across a lot of different operations, and you should adjust it rather than accept it.

Score each vendor one to five per line, multiply by weight, total it. The exercise usually surprises people, because the feature that dominated the demo conversation turns out to be worth five points.

Six numbers, pulled monthly. If you can produce all six from your current CRM in under thirty minutes, you already have most of what you need. If you cannot produce them at all, that itself is a finding.

1. Active user rate. Percentage of licensed users who logged a meaningful action in the last seven days. Logins do not count. Actions do.
2. Median time to first response, by source and by person. Median, not average, because two overnight leads will make an average look terrible and hide the real pattern.
3. Touches per lead before it goes cold. Count the leads that died and look at how many attempts they got.
4. Appointments set and appointments shown, as separate numbers. A set rate with no show rate next to it is a story with the ending missing.
5. Records with a valid phone and email. Straight data integrity.
6. Cost per sold unit through the system. Total software and lead spend divided by units sold that touched the CRM.

Write down last month's six before you look at this month's. The trend matters more than any single reading.

If your people are not in the system, the other five numbers are fiction. Reports built on partial data are worse than no reports, because they give a manager confidence in a picture that is missing a third of the activity.

The tell is always the same: salespeople texting customers from their personal phones. When that happens, the store loses the record, the manager loses visibility, and the customer relationship walks out the door with the employee when they leave. Nobody does it out of defiance. They do it because the personal phone takes two seconds and the CRM takes eleven clicks.

So score the eleven clicks. Time a real task in each system you evaluate: receive a lead, call it, log the outcome, send a text, set a follow up task. If that sequence takes more than about ninety seconds, adoption will be a fight forever. Mobile matters here more than most GMs assume, because a large share of that work happens on the lot and not at a desk.

If adoption is your problem today, the CRM adoption playbook is a better next step than a vendor search.

Response time is the one metric where the industry consensus is unambiguous, even if the specific figures vary by study. Faster is better and the drop off after the first hour is steep. You do not need to trust a particular statistic to act on that.

What to score in a vendor: does the system make speed easy or does it depend on someone watching a screen. Look for a sound alert on new leads, a visible badge, distribution rules that route by team and time of day, a mobile alert path, and automation that can fire an acknowledgment text within seconds of arrival while a human works toward a real call.

What to score in your own store: median time to first response by person and by source, every month, posted where the team can see it. Publishing the number changes it more reliably than any coaching session, because nobody wants to be last on a list their peers read. Set an internal standard and hold to it. The response time SLA page covers how to define one that people can actually meet.

Pull twenty leads from ninety days ago that never bought and read the history on each one. This audit takes an hour and it is the single most useful hour a GM spends on their CRM.

You will find a pattern. Most dead leads got two or three attempts inside the first forty eight hours and nothing after. Not because anyone decided to stop, but because there was no mechanism to continue and the next day's fresh leads were more interesting. The customer bought somewhere five weeks later from whoever was still in front of them.

Score the system on whether a manager can build a cadence once and have it run without being remembered. Follow up processes, automations, drips with an editor, task automation and reminders. Then score whether the cadence uses more than one channel, because a sequence that is all email is really a sequence of one channel that most people ignore.

Score your own store on touches per dead lead. If the median is three, you do not have a lead problem. You have a fifth touch problem, and it is fixable without spending another dollar on lead sources.

This is the least interesting section on the page and the one that quietly wrecks the other five metrics.

Duplicate records mean two salespeople call the same customer, which is a bad experience and an internal fight. Bad phone numbers mean your dialer productivity is a fraction of what the activity report claims. Undeliverable email addresses damage your sending reputation, which then hurts the messages that would have landed. Missing opt out status across departments is a compliance exposure, not just an annoyance.

Score the system on what it does about this natively. A phone validator and an email validator built in are worth more than they sound, because the alternative is buying a separate service or ignoring the problem. Duplicate management, blacklist handling with import, and opt out status shared across every channel belong on the same line. Ask how each vendor handles a customer who unsubscribes from sales but is still a service customer.

Score your own store on percentage of records with a valid phone and email, and on duplicate rate. Then do something about it. CRM data cleanup covers the sequence.

The invoice is not the cost. Build the real number before you compare anything.

Add the base subscription, per seat charges, every module you actually need turned on, integration fees, texting and telephony charges, implementation, and the renewal price rather than the promotional one. Then divide by units sold that came through the system. That is your cost per sold unit through the CRM, and it is the only figure that lets you compare a cheap system nobody uses against an expensive one that works.

Illustrative only, not a claim: a store paying $2,400 a month all in and selling 90 units a month that touched the CRM is at roughly $27 per sold unit. A store paying $1,200 with half the team working outside the system and 60 units attributable is at $20 on paper and considerably worse in reality, because the units it is not seeing are not in the denominator. Your numbers will differ.

For a structured version of this calculation, use the CRM ROI calculator. For reference, our own pricing starts at $199 a month for CRM Only and $799 for plans that include exclusive local leads, month to month with no long term contract.

A scorecard nobody runs is a document. Put it on a rhythm.

First Monday of the month, thirty minutes, same six numbers, with the sales manager and the BDC lead in the room. Ten minutes pulling the numbers, ten minutes on the one that moved the wrong way, ten minutes assigning exactly one change with a name and a date attached. One change. Stores that try to fix five things fix none.

Twice a year, run the twenty dead lead audit by hand. Reports tell you what happened. Reading actual histories tells you why, and it is the only exercise that reliably surfaces the process gaps nobody reports.

Once a year, run scorecard A against your incumbent as though they were a new vendor pitching you. If they score well, you have saved yourself a switch you did not need. If they score badly on the lines you weighted heavily, you now have a documented case rather than a feeling, and comparing alternatives becomes a short exercise instead of a six month project.

What should a GM look at first?

Active user rate. If a third of your licensed users have not taken a meaningful action in seven days, every other number on the scorecard is built on partial data and will mislead you. Fix adoption before you interpret anything else.

How often should the scorecard be run?

The six health metrics monthly, in a thirty minute review with the sales manager and BDC lead. The dead lead audit twice a year by hand. The full weighted vendor scorecard once a year, run against your current vendor as if they were pitching you.

Should I use average or median response time?

Median, by source and by person. A handful of overnight leads will drag an average into a number that tells you nothing about how the store performs at two in the afternoon.

How do I calculate cost per sold unit through the CRM?

Add base subscription, seats, every module you need, telephony and texting charges, integration fees and implementation, using the renewal price rather than the introductory one. Divide by units sold that touched the system.

What if the scorecard says my current vendor is fine?

Then you saved yourself a migration, which is a genuinely good outcome. Most CRM frustration is process rather than product, and switching to solve a discipline problem tends to produce another switch eighteen months later.

Does LeadLocate produce these numbers?

Yes. Three reporting layers cover activity, company and management views, including response time, touches, appointments set and shown by person and by source. We cannot guarantee sales results, but the measurement is there to manage against.

Bring your weighted criteria to the demo and we will answer every line, including the ones about contract, export and total cost. Month to month, so the scorecard runs again next month with real stakes.