I've sat in a lot of business cases for automation and AI. Most of them lead with the same number: hours saved.
Ten thousand hours a year. Forty thousand. I've seen decks claim six figures of hours.
Boards nod politely at that number and then don't sign. They're right not to. Hours saved is not money. It only becomes money if something else happens next, and most business cases never say what.
There are two numbers a board actually runs the company on. EBIT and cash. If your AI case can't be expressed in those two, it isn't finished.
Why hours saved doesn't land
Say you save a team of ten people 20% of their week. What happens?
In most organisations, nothing visible. The work expands. People catch up on the backlog, do things more carefully, go home on time. All good outcomes. None of them appear in the P&L.
Hours only become EBIT in one of three ways. You reduce cost, which means fewer people or fewer contractors, and you have to be willing to say so. You avoid cost, by absorbing growth without hiring. Or you redirect the time to something that earns revenue, and can show that it did.
If the business case doesn't name which of the three it is, with an owner, the saving is theoretical.
Where the EBIT really is
The labour saving is usually what gets a project started. It's rarely what pays for it.
The money is in leakage. Payments going out that shouldn't. Rework. Exceptions handled three times. Overpayments, under-billing, missed rebates, penalties, duplicate handling, write-offs. Nobody has measured it, because the process has always run that way. It's hiding in most operational processes, and it goes straight to EBIT when you stop it.
I've seen cases where the labour saving alone didn't pay back inside three years on honest assumptions. It would have been easy to tune the inputs until it did. The right answer was to go and find the leakage, and that's where the case stood up.
The cash side nobody models
Cash is the other half, and it's usually missing from the deck altogether.
Automation changes timing. Invoices that go out the day the work completes instead of at month end. Disputes resolved in two days instead of three weeks. Orders processed same day. Claims paid accurately first time.
Every one of those moves cash forward. Shorten the gap between doing the work and being paid for it, across your whole revenue, and you have a number your CFO will take very seriously. It often dwarfs the labour saving, and it arrives faster.
How to build the case properly
- Start with the process, not the technology. Measure what it really costs today, including errors and rework.
- Put every benefit into one of four boxes: cost out, cost avoided, leakage stopped, cash accelerated. If it doesn't fit a box, leave it out.
- Give each benefit an owner in the business who agrees to the number.
- Show the version where only half of it comes true. If it still works, you've got a case.
That last point matters. A board trusts a case that has been stress-tested by the person presenting it far more than one that only shows the good outcome.
It's also the theme of my podcast, AI & Automation: The Route to Unlocking EBIT and Cash.