CRM & DMS strategy
Choose and use the systems that fit the business, the team, and the way work really gets done.
AUTO CRM GUY / AUTOMOTIVE CONSULTING
Dealer technology from someone who’s actually lived in it.
I help dealers, vendors, and automotive technology companies make better decisions about CRM, DMS, product, integrations, implementation, and the work that happens between them.
THE WORK
The right answer starts with the real workflow.
A system can look great in a demo and still create friction at a dealership. I bring automotive operating context and product experience to the decisions that affect both the people building a solution and the people using it every day.
WHERE I HELP
From selection to the messy middle.
Vendor evaluation
Ask better questions, compare real tradeoffs, and look past the demo before committing.
Implementation & migrations
Plan the transition, manage the details, and protect the workflows people depend on.
Dealer workflow
Map what actually happens in the store, then make technology support it.
Integrations & APIs
Connect the right systems, define the data flow, and untangle where handoffs break.
Compliance & AI
Evaluate practical applications and the operational risks that come with them.
DEALERSHIP CRM DECISIONS
A closer look at the system your team lives in.
Choosing or changing a CRM affects more than the sales screen. I can help evaluate vendor options, dealership requirements, DMS and communications dependencies, migration plans, and the gaps between a demo and daily work.
For a focused look at that work, explore my CRM consulting approach.
EXPERIENCE THAT CONNECTS
I’ve spent my career in the space between dealerships and the technology they depend on.
I spent more than a decade at DealerSocket, first managing data implementation and then managing third-party integrations and reporting. That experience gave me a foundation in how dealership CRM works at the workflow, data, integration, and platform level — knowledge that extends well beyond any one CRM. My work there included dealership software implementations, two-way integrations, API adoption, vendor relationships, and making connected systems more usable.
At Carvana, as a Senior Product Manager, I owned the roadmap, design, and implementation of a business-facing platform for dealers and partners. Today, my product leadership work at Call Box / Car Wars focuses on automotive communications technology and product strategy.
That background connects the dealership’s needs with the product decisions, data flows, and implementation work behind the software. It shapes how I ask questions and evaluate a proposal. This consulting practice is my independent work; my employers do not sponsor or participate in these engagements.
BUILT AROUND REAL AUTOMOTIVE WORK
Product & strategy
Product roadmaps, design, and implementation at Carvana; product leadership in automotive communications today.
CRM & dealership systems
Deep understanding of automotive CRM at the workflow and platform level — how leads, customers, communications, processes, integrations, reporting, and data move through a dealership. My experience spans the broader CRM landscape, not just one platform.
Integrations & data
Two-way integrations, APIs, reporting, and the dependencies between dealership software and its partners.
Dealers & vendors
Dealer implementation work, vendor discussions, and platforms built with internal and external partners.
For dealers
An independent second set of eyes on consequential technology decisions: how the workflow fits, what the vendor can demonstrate, which dependencies matter, and what implementation and adoption will require.
For vendors and product teams
Help translating dealer needs into product requirements, integration strategy, and usability decisions that reflect how the work happens in the store.
I don’t evaluate dealership technology from a feature checklist alone.
I start with what the dealership is trying to accomplish and how the work moves through the store. Then I ask the vendor to demonstrate it: the handoffs, the connected systems, who owns each dependency, and what happens when something breaks.
The decision also needs a plan for what happens after the contract is signed: implementation, adoption, and how the team will know the system is working. My dealership CRM demo checklist and scorecard puts that approach into a practical evaluation.
LET’S TALK
Let’s make the next technology decision a better one.
Tell me what you are working through. We will start with the actual problem and find a useful next step.