office-worker-talking

How to Evaluate Any AI Investment Before You Spend a Dollar

The AI tools market is not getting simpler. New platforms, new capabilities, and new vendor claims are arriving faster than most business owners can evaluate them, and the pressure to do something, anything, with AI is real. That combination, a crowded market and organizational pressure to move, is exactly the environment where bad investments happen.

The businesses that are getting consistent returns from AI are not the ones that moved fastest. They’re the ones that asked the right questions before they committed, and then moved deliberately. The questions aren’t complicated. But getting honest answers to them requires more discipline than most companies apply before signing a contract or standing up a pilot.

The Surgeon Who Showed Up Prepared

Henry Hays uses a medical analogy that cuts to the core of what pre-investment assessment actually means. A surgeon doesn’t walk into the operating room and decide what to do when they get there. The patient has been evaluated. The procedure has been planned. The team knows exactly what they’re walking into before anyone picks up a scalpel.

Most companies approach AI investments the way a surgeon would if they just showed up and started cutting. They identify a use case that sounds promising, pick a tool that seems to fit, and start building without asking the questions that would tell them whether the initiative has any real chance of working.

The questions that need answering before any AI investment are organized around three areas: technology, data, and people. All three have to be in reasonable shape for an AI initiative to succeed. If any one of them is significantly out of alignment, the investment will underperform regardless of how good the tool is.

Is Your Technology Ready?

The first area to assess is the technology environment the AI will need to operate in. This doesn’t require a deep technical audit, but it does require honest answers to a few practical questions.

What systems does this AI need to connect to? AI that operates in isolation from your actual business systems is limited in what it can do. The more connected it is to the systems your team already uses, the more useful it becomes. Before investing, understand what integrations will be required and whether those integrations are straightforward or complex.

Are those systems stable and well-maintained? An AI layer built on top of unreliable or poorly maintained systems inherits those problems. If the underlying systems have known issues, those issues will show up in the AI’s outputs.

What does the implementation actually require? Some AI tools are genuinely low-lift to deploy. Others require significant configuration, integration work, or technical expertise that may not exist internally. Understanding the real implementation requirements before committing is basic due diligence that many companies skip.

Is Your Data Ready?

Data readiness is where the most AI investments fail, and it’s the area where the most honest self-assessment is required.

Hays is direct about this: if everything else is ready and the data isn’t, you are burning money. AI doesn’t generate insight from nothing. It operates on whatever information you feed it, and if that information is incomplete, inconsistent, or scattered across systems that don’t communicate with each other, the outputs will reflect that. No tool is good enough to compensate for genuinely bad data.

The questions to ask here are practical. Where does the relevant data actually live? Is it in one system, or spread across several? Who owns it, and how clean is it? Has anyone actually looked at the data that will be feeding this AI, or is the assumption that it’s probably fine?

That last question matters more than it might seem. In most growing businesses, data quality is assumed rather than verified. The CRM has records, the spreadsheets have numbers, the email archive has history, and the working assumption is that all of this is in good enough shape to be useful. Sometimes it is. Often it isn’t. And the way to find out is to look before you build, not after.

If the data assessment reveals problems, that’s not a reason to abandon the initiative. It’s a reason to fix the data first, which is almost always faster and cheaper to do before an AI implementation than during one.

Are Your People Ready?

The third area, and the one that gets the least attention in most pre-investment conversations, is people readiness. This matters as much as the technology and the data, and in many cases it matters more.

People readiness has two dimensions. The first is understanding: do the people who will be working alongside this AI know what it is, what it’s for, and what it isn’t? Do they understand that the goal is to make their work better, not to replace them? Hays makes this point directly: employees need to know that AI is coming to augment their work, not eliminate their jobs. Without that clarity, even a well-designed AI implementation will run into resistance at the point where it touches real people.

The second dimension is capability: do the people involved know how to work with AI effectively? Using AI well is a skill. It requires knowing how to prompt, how to evaluate outputs, how to push back when something isn’t right, and how to iterate toward a useful result. Teams that have never used AI before will need time and guidance to develop that skill. Building that time into the plan, rather than assuming the team will figure it out, is the difference between an implementation that reaches its potential and one that gets used inconsistently and eventually abandoned.

The Red Flags Worth Watching For

Beyond the three core readiness areas, there are a few patterns that consistently signal a company is about to make a bad investment.

The first is when the use case is too vague. “We want to use AI to improve customer service” is not a use case. It’s a direction. A real use case is specific enough to describe exactly what the AI will do, what inputs it will receive, and what outputs it will produce. The more specific the use case, the faster it’s possible to evaluate whether it’s worth pursuing and whether the conditions for success are in place.

The second is when the ROI case is based on potential rather than measurable outcomes. AI investments should be evaluated against specific, measurable results: time saved, error rates reduced, capacity created. If the best case for an investment is that it will be transformative in ways that are hard to quantify, that’s a signal to ask harder questions before moving forward.

The third is when no one has asked what happens if this doesn’t work. A good investment evaluation includes a clear-eyed look at the downside: what does failure look like, what would it cost, and what would the path forward be? Companies that skip this question tend to be the ones that are most surprised when a pilot underperforms.

Moving Forward With Confidence

A thorough pre-investment assessment isn’t a reason to slow down. It’s what makes it possible to move fast without making expensive mistakes. The companies that do this work upfront almost always move faster in the long run, because they’re not spending months fixing problems they would have found in week one if they’d looked.

The goal isn’t to find reasons not to invest. It’s to make sure that when the investment is made, it lands on a foundation that gives it a real chance of working. That foundation, solid technology, clean data, and people who are ready and clear on what’s being asked of them, is what separates the AI investments that deliver from the ones that don’t.

Listen to the full podcast episode here.

Related Resources