The AI Gold Rush: When Everyone Can Suddenly Do Everything
Is AI creating a new era of innovation in automotive retail, or are we heading down a familiar road?I've been noticing a trend lately, and I'm curious if others in the industry are seeing the same thing.
It seems like everyone can do everything now.
AI vendors, established technology companies, independent developers, dealership employees, and entrepreneurs are all discovering just how quickly they can build software with AI. And suddenly, the conversation has shifted from "Here's what our product does really well" to "Yeah, we can build that too."
Don't get me wrong. I think we're witnessing one of the most exciting periods of technological innovation in our industry's history. The barriers to developing software have dropped dramatically, and that's opening doors that simply weren't available a few years ago. The runway is short.
But I'm also starting to wonder if we're heading down a slippery slope.
Just Because You Can Build It Doesn't Mean You Should
Some of the best conversations I've had with AI developers lately have been with those who recognize what they don't do.They understand their lane. They recognize the specific problem they're trying to solve, and they're focused on becoming exceptionally good at solving it.
I find that refreshing.
On the other hand, I've had plenty of conversations where nearly every question about functionality, integrations, reporting, or capabilities is met with some variation of "We can do that."
And maybe they can.
That's the tricky part. With today's AI development tools, it's entirely possible they could create a working version of what you're asking for in a surprisingly short amount of time.
But there's a significant difference between building a feature, developing a product, and supporting an enterprise software solution.
Especially in automotive retail.
The Part That's Easy to Overlook
Our industry is complicated. Really complicated.It's not just about creating a CRM, a website, an AI agent, or a reporting dashboard.
New car dealers operate within an ecosystem of manufacturers, DMS providers, CRM platforms, OEM programs, certified vendors, compliance requirements, data integrations, and third-party organizations like Shift Digital.
Something that looks relatively simple on the surface can become considerably more complicated when you factor in OEM requirements, approved integrations, program eligibility, co-op reimbursement, security, and the operational realities of a dealership.
A developer might be able to build a functional replacement for a piece of your technology stack. But can that solution satisfy the requirements of your manufacturers? Will it qualify for applicable OEM programs? What happens to co-op eligibility? How does it handle the integrations, security requirements, and support expectations that dealers take for granted with established providers?
And perhaps most importantly, does the developer even know which questions to ask?
I'm not suggesting established vendors have all of this figured out. Far from it. Many of the frustrations dealers have with existing technology are precisely why these new opportunities exist.
But I'm concerned that we may have two parties entering these conversations who don't fully understand the complexity of what they're agreeing to.
A dealer who doesn't know what it takes to develop and maintain a complete software solution, and a developer who doesn't fully understand what it takes to operate within the franchised automotive retail environment.
That's where things could get interesting. And potentially expensive.
The Fear of Missing Out Is Real
Here's where I'll admit something.I have FOMO.
Every day, I see another AI tool, another development platform, another use case, or another person building something that would have required an entire development team just a few years ago.
And I catch myself thinking, "Should I be doing more of this? Should we be building our own solutions? Are we going to fall behind if we don't?"
The possibilities are almost overwhelming.
But like most people working inside a dealership group, I have a day job. Actually, several responsibilities competing for the same hours.
I can't spend every day experimenting with new AI tools or building applications. And yet, there's this underlying feeling that I should be.
But I've recently started looking at that FOMO a little differently.
The development cycle for AI is moving so quickly that the shelf life of FOMO might be 30 days instead of several years. The groundbreaking tool or capability we're afraid of missing today could be commonplace, dramatically improved, or even obsolete a month from now.
Ben Hadley at AutoGenius shared an analogy on a call yesterday that really stuck with me. "AI is like a continuously moving train, but it's still moving slowly enough that we can all jump aboard."
That aligned with my perspective. Maybe the question isn't whether I'm falling behind, but when it makes the most sense to jump on.
I've started to realize that I don't necessarily need to be on every train. I just need to recognize when it's time to get on one.
And perhaps there's an advantage to letting the technology mature a little before committing significant time, money, and resources to something that could look entirely different in another 30 days.
I suspect developers and technology companies are feeling that same pressure, perhaps even more intensely.
When the time required to develop new functionality has shrunk so dramatically, there's a real fear that someone else will build your next big idea before you do.
So instead of focusing on doing one thing exceptionally well, the temptation becomes trying to do everything. Everyone's racing to build the next feature, expand into the next category, or claim the next capability before someone else does.
And now we're hearing conversations that almost sound like, "Why do we need all these vendors? We can just vibe-code our entire technology stack."
Maybe someday that becomes a realistic option.
But I don't think we're doing ourselves any favors by confusing the ability to rapidly develop software with the ability to responsibly replace business-critical systems.
And perhaps that's the irony of all this. The same speed that's creating our fear of missing out might actually be giving us the luxury of waiting.
A Familiar Pattern With a New Twist
There's another part of this that feels awfully familiar.I've been in automotive retail for 25 years, and I've watched countless technology companies discover our industry.
They see the revenue generated by dealerships, recognize the amount of money spent on technology and marketing, and identify an opportunity.
And somewhere along the way, a product that might cost a fraction of the price in another industry becomes a substantial monthly subscription because it's being sold to a car dealer.
We've seen it with websites, lead management, digital marketing, equity mining, reputation management, chat tools, and just about every other technology category that's come through our doors.
Now AI is creating an entirely new wave of opportunity.
And I can't help but wonder how many companies are entering automotive because they've identified a legitimate problem they're uniquely qualified to solve, versus how many simply recognize an industry that's historically willing to spend money trying the next big thing.
Let's face it. Dealers will try just about anything if they believe it might sell another car, generate another lead, or improve efficiency and reduce expense.
That's not necessarily a bad thing. It's part of what makes our industry entrepreneurial and adaptable.
But it also makes us an attractive target for companies that are better at selling a vision than delivering a sustainable product.
And when AI makes it easier than ever to demonstrate something impressive, distinguishing between those two becomes even more difficult.
Where Do We Go From Here?
I'm not advocating that dealers slow down their adoption of AI. Quite the opposite.I believe AI will fundamentally change how our dealerships operate, how we interact with customers, and how we manage our businesses.
I'm excited about what smaller development teams and independent entrepreneurs can accomplish. In many cases, I think they'll challenge established vendors in ways that are long overdue.
But I also think we need to become more disciplined about separating what's possible from what's practical.
We need to ask better questions, understand the dependencies, and recognize that a compelling demo isn't the same thing as a production-ready solution.
And maybe we need to be a little more skeptical when every company we talk to suddenly claims it can solve every problem we have.
For the developers and vendors reading this, I'd be interested in hearing your perspective as well. Is the pressure to expand your capabilities as intense as it appears from the dealer side? Is specialization becoming harder to justify when everyone around you is promising everything?
And for my fellow dealers, I'm curious:
Are you seeing this same trend?
Are you finding it increasingly difficult to separate legitimate AI innovation from overpromising? Have you encountered situations where a solution looked great in a demo but couldn't navigate the realities of dealership operations, integrations, or OEM requirements?
Or am I being overly cautious, and we're actually witnessing the beginning of a much-needed disruption to the traditional automotive technology model?
I don't pretend to have the answer.
I just have this growing feeling that when everyone believes they can build everything, we might be overlooking what it actually takes to build something worth relying on.
Curious if anyone else feels the same way.
