You don’t know what you don’t know. I do.
Part car guy, part software developer. I give you clarity — what to look for, what to ask, and where it breaks. Here’s the kind of question I bring to the table that a vendor hopes you never ask.
The vendor gut-check
A demo always works. I ask the question that shows whether the integration holds up at 2 a.m. when your DMS is slow — because I’ve shipped the code that has to survive it.
The hallucination guardrails
These models are known to hallucinate exactly this kind of context. There are three guardrails that keep one honest. I know in one question whether a vendor has them — or whether their “AI” will confidently make things up to your customers.
The architecture underneath
The slick interface isn’t the product. The architecture under it decides whether this works on your floor or falls over at scale. That’s the layer I surface — the part you can’t see in a sales deck.
I understand what you’re trying to add, build, or implement. Let me be the segue between the idea and the execution.
The vendor treadmill
- Ten vendors, ten dashboards, zero strategy tying them together
- Salespeople who’ve never desked a deal telling you what your store needs
- Long contracts for tools that look great in a demo and stall on the floor
- “AI” that’s really just a chatbot — and your team quietly stops using it
- No one accountable for the outcome, only the invoice
One person on your side
- A single advisor who’s actually run dealerships — front and back
- Vendor-neutral counsel — I tell you what to skip, not just what to buy
- A real dev team that can build what no vendor sells you
- A blueprint mapped to your store, not a generic playbook
- Accountable for results — measured the way dealers measure: PVR, gross, closing ratio