Everyone wants AI. Most organizations haven't done the work to be ready for it.
I've watched this pattern play out across industries — automotive, healthcare, trucking, public safety. A leadership team gets excited about machine learning, someone builds a slide deck about AI strategy, and six months later the data science team is still cleaning spreadsheets wondering why nothing is working.
The problem usually isn't the algorithm. It's the foundation.
Before you can do anything meaningful with AI or ML, you need to understand where you actually are in the analytics maturity curve. There are three stages, and they're not optional — you can't skip from one to three.
Descriptive Analytics — What happened?
This is your baseline. Historical data, dashboards, reports. Who did what, when, from where. Most organizations think they have this handled. Many don't. They have data — but it's fragmented, inconsistently defined, and living in four different systems with four different answers to the same question.
If you can't tell a clean, consistent story about what happened, you're not ready for what comes next.
Predictive Analytics — What's likely to happen?
Now you're using historical patterns to forecast. Which customers are likely to churn? Which leads are most likely to convert? Which vehicles are approaching a service milestone? ML lives here — models trained on your data to surface probability and likelihood.
This is where it gets interesting. It's also where most implementations start struggling, because the predictive models are only as good as the descriptive data underneath them. If your historical data is dirty, your predictions will be confidently wrong.
Prescriptive Analytics — What should we do about it?
This is the layer everyone wants to jump to. The system doesn't just predict — it recommends. Do this, for this customer, right now, for this reason. Autonomous decisions, targeted actions, real-time personalization.
It's powerful. It's also the hardest to do right — and the easiest to do badly in ways that quietly erode trust in the entire system.
What Most AI Implementations Get Wrong
The data isn't ready. I know that's not a compelling thing to say in a room full of people excited about AI. But "garbage in, garbage out" has never been more true, and the bar for what counts as garbage has never been higher. Implementing a sophisticated ML model on top of inconsistent, incomplete data doesn't give you AI — it gives you an expensive way to automate bad decisions at scale.
Data preparation is unglamorous, time-consuming work. Cleaning, standardizing, integrating across sources, reconciling conflicting definitions of the same field. I've seen this phase take longer than the entire model development that followed. That's not a failure. That's what it actually costs.
Domain expertise gets undervalued. Algorithms don't know your business. They don't know that Q4 data looks anomalous because of a one-time promotional event. They don't know that a particular customer segment behaves differently in your market than the broader pattern suggests. They don't know which data points are meaningful and which are noise. That context lives in people — your operators, your analysts, your subject matter experts. The best AI implementations I've been part of treat domain knowledge as a first-class asset, not an afterthought.
Expectations are wrong from the start. AI and ML projects are iterative. The first model is a starting point, not a solution. Organizations that expect a one-time implementation and a clean result consistently end up disappointed. The ones that treat it as a continuous refinement loop — and staff and resource accordingly — are the ones that actually get somewhere.
Where to Start
Audit where you actually are. Not where you want to be — where you are. Can you answer basic descriptive questions consistently and confidently across your organization? If not, start there. Get your data house in order before you invite the architects in.
It's not the most exciting recommendation. But in a world where AI is embedded in nearly every software platform and every boardroom conversation, the competitive advantage isn't in having AI — it's in having the data foundation that makes AI actually work.
Most of your competitors are skipping the foundation. They're going to feel that eventually.
That's your window.