Before I worked in automotive SaaS, I worked inside a dealership. I understand the skepticism that shows up the moment another dealership technology company walks through the door with a pitch. Dealership leaders have heard it all before: the platform that will change everything, the partner who promises to be different from the last one.
I get asked some version of the same question all the time: “What can you do for me that everyone else hasn’t already promised?”
It’s a fair question, and it’s the right one to ask. Because here’s what I’ve learned on both sides of that conversation: technology providers don’t earn partnership status by making promises. They earn it in what comes after the promise, especially when things get hard.
My short answer: it’s not a bigger promise. It’s whether they understand your operation, follow through without you having to chase them, and stay invested after the sale.
A Partner Understands the Business Behind the Software
I haven’t sat in every role on a dealership floor, and I don’t think a partner needs to in order to be useful. But they do need enough operational understanding to see that software doesn’t exist in a vacuum. It exists inside a complicated, fast-moving environment with its own pressures.
That’s the perspective I try to bring to every conversation:
- I understand your pains. I know what you’ve been through.
- I might not be going through it right now, but I’ve also experienced it.
- The question isn’t just whether the software works. It’s whether it’s helping you accomplish what you brought us in to accomplish.
When a provider only measures success by whether the system is running, they’re missing the point. The dealership didn’t invest in another platform. They invested in a business outcome.
Follow-Through Builds or Breaks Trust
To me, partnership goes beyond answering questions when they’re asked. It means completing what you said you’d do and bringing the result back without making the customer chase you down.
If the customer has to call and follow up, you’ve already failed.
I think about this the same way I think about the service drive. When a customer has to call an advisor for a status update on their vehicle, some trust is already gone. The same is true when a dealership leader has to repeatedly follow up with their technology provider just to get answers. Time is one of the most valuable and finite resources a dealership has.
When Adoption Is Low, Get Curious Before Assigning Blame
This is where I think the real work of partnership happens. When adoption is low, I don’t start by assuming people are unwilling to change. I start by asking questions:
- What brought you to this technology in the first place?
- What were you expecting?
- What isn’t being given to you, or shown to you, that you need to complete what’s being asked of you?
- Is the workflow harder than it needs to be?
- Is the ask realistic for where the team is right now?
Low adoption isn’t a verdict, it’s information. It deserves a diagnosis before anyone decides who, or what, is responsible.
I want new technology to feel as manageable as integrating flossing into your brushing routine, something you build in gradually. If someone has never benched 20 pounds, you don’t hand them 200 and call it a training program. The rollout has to match what the team can realistically absorb.
Partnership Requires Enough Trust to Ask "Is It Me?"
A genuine partner has to be willing to look inward too. I ask myself, and sometimes I ask the customer directly: Is it me? Is it something I’m missing that you don’t feel comfortable telling me?
I want you to win, even if it’s not with me. That’s not a line. That’s the standard.
At the same time, accountability has to stay clear on both sides. This is the dealership’s work. It’s their business. I’m simply the vessel to help them get there. A provider’s job is to offer useful technology and perspective, remove avoidable obstacles, and be honest about what might be getting in the way.
The Best Partnerships Become Proactive
Support begins when a dealership reports a problem. Partnership looks different. It expands into broader conversations about what’s changing, what’s challenging, and where the business is headed.
I know a relationship has matured when the dealership is leading the conversation and I’m doing more of the listening. When a customer actively asks for my feedback on their business, not just their software, that tells me we’ve built something deeper than a vendor relationship.
If the customer has to call and follow up, you’ve already failed.
Sometimes Trust Is Built When Things Go Wrong
Years ago, at a previous company, I met a dealer group that had already been through real frustration with technology providers before me. I showed up, I listened, and when I promised them lunch, I made sure I delivered.
The next day, I went back out and I bought them all In-N-Out burgers and fries.
The lunch itself wasn’t the point. The point is that I did what I said I would do. That relationship grew through honest conversations, candid answers about what could and couldn’t be done, and follow-through that didn’t waver. Years later, when that group became a Dynatron customer, the trust we’d already built shaped how openly we could work together right away.
Some of the best relationships in this industry are the ones formed after working through something difficult together.
The Real Difference Between a Vendor and a Partner
| What to evaluate | Vendor relationship | Partner relationship |
|---|---|---|
| Focus | Product access and functionality | The business objective behind the technology |
| Follow-through | Responds when asked | Closes the loop without being chased |
| Adoption | Measures activity or logins | Asks why friction exists and helps diagnose it |
| Communication | Primarily provider-led or support-driven | Transparent, two-way, and increasingly customer-led |
| Accountability | Defends the product or assigns blame | Examines the provider's own role while preserving dealer ownership |
| When problems arise | Treats difficulty as a ticket to close | Uses candor and consistent follow-through to build trust through challenges |
Five Questions to Ask Any Dealership Technology Provider
If you’re trying to evaluate whether a provider is a vendor or a partner, these are the questions I’d start with:
- Do they understand our business? Can they explain what we’re trying to accomplish beyond simply using their software?
- Do they follow through? Are we routinely chasing answers and action items, or do they close the loop themselves?
- Do they diagnose before assigning blame? If adoption is low, do they help figure out why?
- Do they bring perspective? Are they only answering support questions, or helping us see things we might not see on our own?
- Are both sides invested? Are we giving them the engagement, transparency, and execution the relationship needs from us in return?
Ask More From the Relationship
The standard shouldn’t just be whether the technology works. It should be whether the company behind it understands your operation, respects your time, follows through, diagnoses adoption challenges instead of assigning blame, brings you perspective you didn’t already have, and stays engaged when things get difficult.
The best technology relationships aren’t necessarily the ones where nothing ever goes wrong. They’re the ones where both sides trust each other enough to work through it when something does.
At Dynatron, that’s the kind of relationship we try to build with every dealership we work with, combining Fixed Ops data intelligence with real automotive expertise to help leaders turn insight into action, not just access.
Book a 30-minute demo to see what that looks like for your dealership.
About the Author
Kim Skovold
Senior Client Performance Coach, Dynatron
Kim Skovold brings more than 20 years of automotive experience spanning dealership operations and automotive SaaS. At Dynatron, she helps dealership teams turn technology and data into practical action, with an emphasis on adoption, accountability, and building partnerships that support lasting performance. Connect with Kim on LinkedIn.
