Data & AI Literacy ROI: Making The Case To The Budget Holder

"I need something practical. I hear you, but I need something practical. Give me an example. I don't know what you do. What is my return on investment here?"

This is what a VP of Data at a healthcare organization asked of us in a recent meeting. 

She understood the value of our education and implementation, but she needed to prove it to the people who weren’t in the room, and who would be the one signing off the budget. That gap is where most data and AI fluency programs stall. The business case needs to be clear to the right people, in the right language. Traceable and trackable.

Why your data initiative isn't landing

There's no shortage of data on what poor data and AI fluency costs at an industry level, and the numbers are significant. Workers lose the equivalent of 27 days per year to inefficient data and AI practices according to the Multiverse Skills Intelligence Report, 2025. But a CFO or COO isn't thinking about the industry. 

They're thinking about their organization, and what this returns for them specifically. In terms they can take to the rest of the board without needing to explain what any of it means. The industry benchmark and the specific business case are two different things, and most champions walk in with the former when they need the latter.

What ROI looks like when you name it properly

The strongest cases for data and AI fluency investment tend to start with three things the organization already knows about itself:

Time recovered

When people understand the data they're working with and can evaluate AI outputs critically, decisions get made faster. Reports that previously needed a data team to interpret get acted on directly, analysts stop fielding basic questions, and AI tools get used properly by more people, more often. This time is recoverable and it has a number attached to it, you just have to find it.

Risk reduced

In regulated environments especially, the cost of a data or AI error goes beyond operational. It shows up in audits, in complaints, in decisions made on outputs nobody properly reviewed, let alone scrutinized. Organizations with strong data and AI fluency tend to catch these issues earlier, when they're still cheap to fix. That's a return, even if it doesn't appear on a spreadsheet until something goes wrong.

Investment protected

Most organizations making this case already have a platform, a tool, or an AI system that isn't performing the way it was supposed to. The data warehouse the business can't interrogate. The dashboard nobody opens. The AI tool a handful of people are using well while the rest of the organization carries on as before. That spend has already happened.

Data and AI fluency is what makes it return something. The question stops being "why should we spend this?" and becomes "why are we leaving what we've already spent unrealized?"

Don't pitch to the data team

Most data and AI fluency programs are proposed by data teams, reviewed by data teams, and signed off, or not, by someone who has never thought about data and AI fluency as a wider company problem. That's the core issue. When the case stays inside the data team, it gets evaluated on data team terms. 

The budget holder hears a resource allocation argument when what they needed was a business argument. The shift is in who the investment is actually for. Data and AI fluency can’t just be a data team initiative. It's what determines whether the rest of the organization can use what the data team builds, trust what AI produces, and make decisions that support the strategy the board just signed off on.

That reframe changes the conversation before it starts. A VP of Operations who understands that their teams are making decisions on AI outputs nobody has properly evaluated isn't being asked to fund a training program. They're being asked to close a risk they already own.

Before you book the meeting, find where the risk lives. Which leader is accountable for the decisions being made on AI outputs nobody has properly evaluated. Which function is most exposed if a compliance incident surfaces. Which team is sitting on a platform investment that isn't returning anything yet. That's your key to sign off.

Answer the unspoken question

Read the VP's question back carefully. She isn't asking for a single number. She's asking you to trace value across an organization that she knows is more complicated than a line on a spreadsheet.

The case that answers her question is already inside the organization. It's in the AI tool that three people are using well while everyone else waits to be shown how. It's in the decision that is taking three weeks longer than it should. It's in the audit finding that landed as a surprise when it didn't have to.

Find those. Put numbers on them. That's the business case.

‍