
Sign up to save your podcasts
Or


What happens when a dealership group starts building the software it used to pay vendors for?
Dustin Schuler, Marketing Director at Bud Clary Auto Group, is helping a 14-store organization rethink its technology stack using Claude Code, ChatGPT, automation, and internally developed tools. His goal is to reduce unnecessary vendor costs, speed up workflows, and give dealership employees better access to the information they need.
In this episode of AI for Dealers, host Daniel Kim digs into Dustin's journey from roofer to dealership marketing director, his experience training AI models, and the projects he's building today. They explore how AI can turn demographic research into targeted marketing campaigns, customize dealership websites, automate repetitive reporting, and help leadership teams make faster decisions.
Dustin also breaks down the economics of building versus buying software, including a $900-per-month website tool he believes his team could replace. With 14 stores, even modest recurring savings could add up quickly. But building internally also means taking responsibility for maintenance, security, and ongoing support.
For dealership operators looking to get started, Dustin shares a practical approach: find one repetitive workflow, explain it to AI in detail, and see what you can improve.
You'll hear about
How Dustin went from roofing to leading dealership marketing
Using AI to identify overlooked customer demographics and marketing opportunities
Customizing dealership websites with Claude Code and CSS
Why recurring vendor costs make internal AI development attractive
Running automations overnight to save employees hours of manual work
Building internal dashboards and creating a potential AI development department
Preparing dealership websites for AI agents that may negotiate on behalf of customers
Chapters
00:00 The $900 vendor replacement opportunity
00:42 Meet Dustin Schuler of Bud Clary Auto Group
03:25 How Dustin runs AI workflows overnight
05:48 From SEO to training AI models
10:05 His first game-changing dealership AI project
15:37 How to prioritize AI projects that save time and money
20:33 Using CSS and AI to customize dealership websites
22:56 Building a better dealership website experience
26:22 When to build software and when to buy it
34:09 Making the business case for internal AI tools
35:39 AI dashboards and unexpected successes
41:34 What a dealership AI department could look like
46:39 Replacing website vendors and preparing for agentic commerce
50:15 Where dealership employees should start with AI
53:20 Dustin's preferred AI models and tools
Links
Dustin Schuler LinkedIn: https://www.linkedin.com/in/dustin-schuler
Bud Clary Auto Group: https://www.budclary.com/
AI for Dealers: https://www.autoindustry.ai/podcast
AutoIndustry.ai newsletter: https://www.autoindustry.ai/
A service advisor shouldn’t have to open four platforms to figure out what a vehicle needs. But replacing the dealership’s entire software stack is a much bigger commitment than fixing that one workflow. Where should an internal builder start?
AI for Dealers host Daniel Kim, Director of Operations at Barnes Crossing Auto Group, welcomes Kyle Mountsier of More Than Cars and Auto Genius to tackle that question. Kyle explains how a frustrating event-scheduling process led him to build a custom Calendly replacement in roughly three days—one his company now uses. Daniel shares a recently launched Chrome extension that brings repair history, declined services, Hyundai maintenance recommendations, and service-contract information into the service advisor’s existing screen.
Their approach: build in the gaps. That can mean connecting information employees already need, adding a missing feature, or creating a prototype that helps a vendor understand the problem.
They also work through what happens after the first successful build: protecting customer data, assigning permissions, planning for future features, and keeping an internal tool running if its creator leaves. It’s a practical conversation about choosing a useful first project and understanding the responsibility that comes with it.
You’ll hear about
The scheduling requirements that pushed Kyle beyond Calendly
Why security and dependence on one employee still favor buying enterprise software
Using prototypes to close the communication gap between dealers and vendors
Combining DMS repair history, declined services, and manufacturer recommendations
Giving AI enough direction to avoid a database that limits your next build
Bringing builders into dealership workflows to understand the actual problem
Chapters
00:00 Build version one with version five in mind
02:27 How AI became approachable for dealership operators
06:03 From abandoned experiments to a custom scheduling app
11:27 Why Kyle still favors buying most enterprise software
15:24 Build in the gaps and prototype for your vendors
19:53 Bringing service-advisor data into one Chrome extension
23:15 How Daniel started building without being an engineer
27:33 Moving quickly while planning for future versions
30:41 Helping dealership teams recognize what they can build
34:35 Protecting customer data and defining user permissions
37:57 What to try next with coding tools and better context
Links
Kyle Mountsier on LinkedIn: https://www.linkedin.com/in/kylemountsier
More Than Cars: https://www.morethancars.com/
AI for Dealers: https://www.autoindustry.ai/podcast
AutoIndustry.ai newsletter: https://www.autoindustry.ai/
On this Episode 00, host Daniel Kim introduces himself and explains why the industry is ready for an AI for Dealers podcast.
From the publisher's feed