Why Dealerships Keep Buying Tools They Never Really Use
The demo was good. I’ll give them that.
The rep clicked through the follow-up automation, the dashboard, the reports that show everything in color. The GM nodded. The internet director asked about the integration. Somebody said, “This is exactly what we’ve been missing.”
Three months later, nobody has logged in since the kickoff call.
The salespeople are doing the same thing they were doing before. The managers never mention it. The invoice keeps showing up every month until a year passes and somebody finally asks:
“Are we still paying for that?”
Then the search starts again.
New vendor. New platform. New promise.
And the dealership carries the exact same operating problem into the next one.
Different company. Different software. Same store. Same behavior. Same result.
Buying Something Feels Like Fixing Something
There are bad vendors.
There are tools that never worked, integrations that broke on day one, support departments that disappear once the contract is signed, and companies collecting a check every month that should have been cut loose a long time ago.
Sometimes firing the vendor is exactly the right move.
But sometimes the vendor isn’t the problem.
The store is.
Buying something feels like fixing something.
You picked a solution. You signed the agreement. There’s a kickoff call on the calendar. People are talking about change.
That feels like progress.
But it can also keep you from asking the more useful question:
Why didn’t the thing we already bought work here?
That question gets uncomfortable pretty fast.
Maybe nobody ever told the salespeople how the tool was supposed to fit into their actual day.
Maybe they got trained once and nobody coached it after that.
Maybe the CRM says 95% task completion and everyone in the building knows half of those tasks are being clicked complete because somebody has to get the red off the screen.
Maybe three managers have three different expectations and the salesperson just listens to whichever one is standing closest.
Maybe the BDC thinks sales owns the lead after the appointment is set, sales thinks the BDC still owns it, and nobody has ever sat down and decided who owns what.
Maybe the tool works fine.
Maybe the process around it doesn’t.
A different vendor doesn’t fix that.
It just gives the problem a new login.
The Vendor Carousel Exists Because It’s Easier
Changing something outside the store is usually easier than changing behavior inside the store.
It’s easier to sit through another demo than to sit your GSM down and say:
“We bought this a year ago and your people still don’t know how we use it.”
It’s easier to add another lead source than to listen to fifty phone calls and find out your people barely work the leads you already have.
It’s easier to blame lead quality than to pull twenty lost deals and look at what actually happened.
It’s easier to change the CRM than admit the store never had one clean follow-up process in the first place.
It’s easier to hire another trainer than ask what your managers reinforced from the last training after the trainer left.
Nobody is stupid here.
It’s just that action feels better than diagnosis.
Dealerships are built around action.
Solve the deal. Find the car. Get the approval. Call the bank. Move the customer. Get somebody involved.
That instinct is worth a fortune on a Saturday afternoon.
It can get expensive when you’re trying to fix a system.
Because the fastest-looking move can become the thing that keeps you from doing the slower work that would actually solve the problem.
Software Cannot Own a Process
Every tool eventually hits the same wall.
People.
A CRM can’t make a salesperson write notes worth reading.
An AI follow-up tool can’t make your message worth responding to.
An equity-mining tool can’t make somebody pick up the phone.
A dashboard can’t make a manager coach.
A training company can’t make your managers reinforce anything after the trainer flies home.
Software can make a good process easier.
It can also make a bad process faster.
That’s the part dealerships miss.
We spend a lot of time asking:
“What can this tool do?”
I’d rather ask:
What does somebody inside this store have to do differently for this tool to produce value?
That question changes the conversation.
Who has to use it?
When?
How often?
For what exact customer moment?
Who inspects it?
What happens when it isn’t done?
How will we know whether it’s working?
If nobody can answer those questions, you’re not buying a solution.
You’re buying capability.
Those are not the same thing.
Look at the Graveyard Before You Buy Anything Else
Before another contract gets signed, I’d put the leadership team in a room and answer five questions.
No vendor deck. No demo. No promises.
Just the store.
- What specific problem are we solving? Not “better follow-up.” Where exactly is the customer journey breaking?
- What do we already own that was supposed to help solve it? Pull the whole stack.
- Is the tool actually failing, or are we failing to use it consistently? Those are two very different decisions.
- Who inside the store owns the behavior after the vendor leaves? One name. Not “the managers.”
- Thirty days from now, how will we know anything changed? Name the behavior first, then the number that should move if that behavior improves.
If the room can’t answer those questions, I wouldn’t sit through the next demo yet.
You don’t know what you’re shopping for.
That’s how stores end up with five solutions bolted onto one unresolved problem.
Fire Vendors From Evidence
This isn’t a defense of vendors.
If the product doesn’t perform, the integration doesn’t work, support is a disaster, the data can’t be trusted, you’re paying twice for the same capability, or the economics don’t make sense, cut it.
But make that decision from evidence.
Otherwise you fire the vendor, spend the next three months onboarding another one, and the original problem is still sitting there in the same chair.
That’s the tell.
When the same problem survives two or three vendors, I stop looking at the vendor first.
I look inside the store.
Who owns it?
What is the expected behavior?
Was it actually taught?
Was it practiced?
Is anybody inspecting it?
What happens when it isn’t done?
Do the managers follow the process themselves?
Are you measuring the real behavior, or just activity around it?
That’s where the diagnosis starts.
Your Stack Is Probably Better Than Your Execution
Most dealerships already have an incredible amount of capability sitting in the building.
Leads.
CRM.
Phones.
Texting.
Email.
Automation.
Equity tools.
Inventory tools.
Desking tools.
Analytics.
Reports nobody has opened since last spring.
Training libraries people watched once.
The highest-return move isn’t always adding something else.
Sometimes it’s getting brutally good at using what you already pay for.
There’s no kickoff meeting for that.
Nobody gets a new login.
There might not even be a new invoice.
You just have to do the harder thing.
Find the leak.
Decide who owns it.
Change the behavior.
Watch what happens.
Adjust it.
Then decide whether the tool is actually the problem.
Because if you keep replacing the outside while protecting everything on the inside, the next vendor is going to look a lot like the last one.
And six months from now, you’ll be sitting through another demo wondering why nothing ever seems to stick.
Jason Rigby
Dealer Leadership
Call or text: 505-490-6502
jason@dealerleadership.com