For CEOs, CIOs and CFOs
ROI Audit · ServiceNowAdoption is up. Hours saved is a big number. The ROI slide is accurate.
And yet Finance still asks one question the slide can't answer: which line in the budget is lower because of this? The gap is rarely the numbers. It's that benefits are counted where IT can see them and judged where Finance can.
Most platform ROI slides are built from usage: tickets deflected, hours saved, workflows automated. This piece is about what happens when that slide meets the ledger — and three questions that decide whether an ROI claim holds up or quietly falls apart.
1. The Renewal Meeting Where the Slide Stalled
A company is deciding whether to renew and expand its ServiceNow contract. IT presents a clear ROI slide: tickets deflected, hours saved, workflows automated. Every figure is accurate and every chart points the right way.
The CFO asks a different kind of question: “Which budget line is lower this year because of this?” IT can point to hours returned to teams, and to incidents that didn't happen. Nobody can point to a line that moved.
The renewal isn't refused. It's deferred while the two teams work out what the slide was actually claiming.
The slide wasn't wrong. It measured something Finance can't see.
This isn't a rare failure. It's what happens by default when benefits are reported in the language of the system and approved in the language of the budget.
2. Three Kinds of Benefit, and Only One Is in the Ledger
Most ROI slides add very different kinds of benefit into a single number. Separating them is the first step to a slide that holds up.
| Cost saved | Money that used to leave the business and no longer does: a retired license, a reduced contractor spend, a closed support contract. It shows up in the ledger. |
| Cost avoided | A cost that would have happened and didn't: an outage, a penalty, a breach. Real value, but an estimate, because it can't be seen in any budget line. |
| Capacity freed | Hours returned to people. It becomes cost saved only when that time is redeployed to measurable work, or a role isn't backfilled. Until then it's capacity. |
None of the three is worthless. The problem is presenting them as one kind of money. A CFO reads “hours saved” and looks for the line that fell; if there isn't one, the whole slide loses credibility, including the parts that were solid. It's the same pattern as savings that stay on paper after a migration: the benefit was real in the plan, and nobody confirmed it in the budget.
3. The Ledger Line
The specific budget line a benefit is expected to show up on — with a named owner for that line and a date when someone checks that it moved.
A benefit with no ledger line is a claim. A benefit with one is a forecast that someone can test. That difference is what Finance is really asking about, and it costs almost nothing to add to a slide that already exists.
4. Why Your Current ROI Reporting Doesn't Catch This
Most platform reporting is built to answer questions like these: Is it adopted? Is the data accurate? Is the dashboard live? These are necessary controls, but they test whether the platform is used, not whether the money moved.
A slide can pass every one of those checks and still be unprovable. The questions that catch it are ownership questions, and they belong to Finance as much as to IT. It's the same gap as a KPI that stays green while the business doesn't improve: the number is accurate, and what it means has drifted.
- Which budget line should this benefit show up on?
- Who owns that line?
- When will someone check that it moved?
Ask these about the three biggest benefits on your last ROI slide. If you can't answer all three quickly for each, that isn't an analytics problem. It's a governance gap — and it's cheaper to close before the next renewal than during it.
5. A 30-Minute Exercise: Rebuild Your Last ROI Slide
You don't need a new tool. Take the last ROI slide your team presented, and do this:
- List every benefit on the slide. One line each, in plain words, with the number attached.
- Label each one: saved, avoided or capacity. If the team can't agree on the label, you've found the claim most likely to be challenged.
- Write the ledger line next to each saving. The budget line, the cost center or the contract it should reduce. For avoided costs, write the assumption: what would have happened, and why.
- Name the owner and set a check date. The date should be in someone's calendar. Anything with no line, owner or date goes on the slide as “unproven.”
The aim isn't a smaller ROI number. It's a slide where every number says what kind of value it is and how it will be confirmed.
6. What an ROI Slide Finance Accepts Looks Like
Every number carries a label
Saved, avoided or capacity. The slide never lets one kind of value pass as another.
Savings point to a ledger line
Each saving names the budget line, cost center or contract it should reduce, and who owns it.
Avoided costs show their assumption
What would have happened and why, agreed with Finance in advance, not defended afterwards.
Someone checks after go-live
Benefits are confirmed on a date, at the line, and again at each renewal, not assumed from usage.
None of this makes the slide longer. It changes what the slide is allowed to claim.
7. The 5-Question Self-Assessment
Run these against your last ROI slide. Three or more answers that aren't a clear yes means your ROI is still a claim, not a result.
| # | Question | Yes / No / Unsure |
|---|---|---|
| 1 | Can you name the budget line each headline benefit should show up on? | |
| 2 | Is every number on the slide labeled as saved, avoided or capacity? | |
| 3 | Does every saving have a named owner for the line it should reduce? | |
| 4 | Is there a date when someone checks that the line actually moved? | |
| 5 | For each avoided cost, is the assumption written down and agreed with Finance? |
8. Three Questions We Hear Most Often
Isn't cost avoidance still real value?
It is, and it should stay on the slide. The problem is presenting an estimate as if it were a budget result. Label it as avoided, write down the assumption, and agree the assumption with Finance before the meeting, not during it.
Most of our benefit is productivity. How do we count hours saved?
As capacity, until the time is put to work. Hours become cost saved when they're redeployed to work with a measurable outcome, or when a role isn't backfilled. Show them as capacity first and say what they will be used for.
Does this apply to AI and automation projects?
Yes, and more so. AI features are often justified on hours saved, which is the easiest number to overstate. The same ledger line test applies. It's also the ownership question we raised in who owns the risk when AI acts: everyone can explain their part, and nobody owns the outcome.
The Question for Your Next Renewal Review
Pick the biggest benefit on your last ROI slide and ask one thing: which budget line is lower because of it, and who confirmed it? If the answer takes more than a minute to give, the benefit is still a claim.
Facing similar ServiceNow challenges?
Get a free ServiceNow assessment and understand where your platform may be losing value.
No spam. No sales pressure. Only actionable insights.