The $5-to-$1 Rule: What McKinsey's ROI Math Means for Your AI Business Case
For every dollar an organization spends on AI technology, McKinsey's State of Organizations 2026 research recommends investing five dollars in the people side of the equation — training, workflow redesign, and change management. That ratio is a useful corrective for how most AI business cases actually get built, which is almost entirely around the cost of the software.
Why the ratio isn't really about budgets — it's about not skipping the hard part
The $5-to-$1 recommendation isn't primarily a statement about how much money to spend; it's a statement about what determines whether an AI deployment actually works. The technology itself is rarely the limiting factor. What determines success is whether the workflow around it was actually redesigned, whether the team using it was trained well, and whether anyone measured the outcome against a real baseline. Those are people costs, not technology costs, and they're the ones most business cases underfund.
What's usually missing from an AI HR business case
Most business cases HR teams bring to finance include a licensing cost and a projected time-savings figure. Far fewer include a line item for training the team on the new workflow, redesigning the process the AI is dropping into, or the ongoing measurement needed to confirm the projected savings actually showed up. Skipping those isn't a rounding error — it's usually the difference between a deployment that delivers the projected ROI and one that quietly doesn't.
How to build a case that survives the 12-month review
- Include the people-investment line item explicitly, rather than assuming implementation is free.
- Define the specific metric that will prove the ROI — ticket volume reduced, hours saved per week, resolution accuracy — not a vague "efficiency" claim that can't be checked later.
- Set a real baseline before rollout, so the 12-month comparison means something.
- Build in a checkpoint, not just a launch date, to confirm the projected number actually materialized.
Using this with your own numbers
The $5-to-$1 ratio isn't a rule to apply literally to every budget — it's a reminder to size the people-side investment as seriously as the software line item, and to build the measurement plan before launch rather than after. Running your own numbers through a structured ROI framework, rather than a back-of-envelope estimate, tends to surface exactly where that investment is currently missing — see how executive teams typically frame this tradeoff.
Sources
Frequently asked questions
What is McKinsey's "$5-to-$1" rule for AI investment?
It's a recommendation from McKinsey's State of Organizations 2026 research: for every dollar an organization spends on AI technology itself, it should invest five dollars in the people side — training, workflow redesign, and change management — to actually realize the return.
Why does the people-to-technology spending ratio matter so much?
Because AI technology cost is usually the smallest part of what determines whether a deployment actually works. The software can be excellent and still fail to produce value if nobody redesigned the workflow around it or trained the team to use it well.
What's usually missing from an AI HR business case?
Most business cases account for licensing cost and a projected time-savings number, but skip the budget for training, workflow redesign, and the ongoing measurement needed to know whether the projected savings actually materialized.
How do we build a business case that survives a 12-month review?
Include a realistic people-investment line item alongside the technology cost, define the specific metric that will prove the ROI (not just 'efficiency'), and build in a checkpoint to measure that metric against a real baseline rather than assuming the projected number will hold.
Related reading
Stress-Test Your HR Team Before Reality Does
Eva HR Lab runs your organization through scenario-based simulations of the conversations that create litigation risk, and scores your team blind against Eva.
How to Reduce HR Ticket Volume with AI Automation
A practical breakdown of what actually drives down HR ticket volume, and the results enterprise teams have seen automating routine HR questions with Eva.
Build a business case that accounts for the people side, not just the software cost.
Build your business case