The ServiceNow ITSM Benefits a CFO Actually Buys, Two Years After Sign-Off

A CFO at a 500-person industrial services company sent me a note last month. He had been part of the decision to buy ServiceNow about two and a half years before, had signed the implementation statement of work, and had just finished a quiet internal review of what the platform had actually delivered. He wanted my view on something that was bothering him. The business case he had approved in 2023 was wrong on almost every line. The savings he had been pitched never materialised in the way the slides said they would. And he was still, two years later, enthusiastic about the investment.

He asked me whether that was normal. I told him it was more normal than most people in the industry want to admit, and that if he looked carefully at what the platform had actually delivered, he would find a different and better set of ServiceNow ITSM benefits than the ones he had been sold on. We spent an hour on the call working out what those were. I want to write up what we discussed, because it is a much more honest conversation about why ServiceNow is worth the money than most of the pre-sale material I see pitched into mid-market CFOs.

The business case the CFO signed, and what did not happen

The 2023 business case for his company was built around three numbers. A twenty-two percent reduction in time spent per incident, which was supposed to free up around four FTEs across his service desk and infrastructure teams. A fifteen percent improvement in change success rate, which was supposed to reduce outage-related revenue loss by about €600,000 a year. And a cost avoidance line for retiring three legacy systems, which added up to a bit over €200,000 in licence fees per year once the ServiceNow modules were live.

Total projected annual benefit, year two onward: around €1.4 million against an all-in platform cost of €520,000. A three-year payback, give or take.

What actually happened. The time-per-incident number came in at about eleven percent, not twenty-two. He did not free up four FTEs. He freed up roughly 1.6, and he reinvested all of them into platform work rather than taking them out as a cost reduction. The change success rate improved, but his finance team struggled to attribute any specific revenue loss avoidance to it because they had never been measuring that cleanly in the first place. The legacy system retirements happened, but on a slower schedule than planned, and the licence savings were about €140,000 a year, not €200,000.

If you had audited the business case against the delivered results on a line-by-line basis, you would have said this project missed by thirty to forty percent on every measurable number. In most finance organisations, that is a bad project.

But he was not describing a bad project. He was describing something he considered one of the best technology investments he had signed off in his career. The question is why.

What he was actually buying, which nobody told him in the sales cycle

When we worked through what had changed in his operation over the two years, three things came out that were not on the business case, and they were the ones that mattered.

The first was that his IT organisation had stopped being invisible to the rest of the business. Before ServiceNow, when a shop floor manager raised an issue, nobody in finance or operations had any way to see what IT was working on, how long things were taking, or whether their request was in a queue or lost. The whole function was a black box, which meant it was constantly accused of being slow and understaffed, and most of those accusations could not be refuted because there was no data. After ServiceNow, every operational conversation with IT could point at a dashboard. The dashboard was not perfect. The data had quality problems in the first year. But the function went from being argued about to being measured. That shift, which has no line on a business case, changed how IT was discussed at every executive meeting.

The second was that the platform forced his teams to agree on definitions. Before ServiceNow, his service desk had one definition of “resolved” and his infrastructure team had another. His application team had a different idea of what a “P1 incident” meant from either of them. Those disagreements never surfaced because nobody was tracking them in a shared tool. Once they were, the teams had to argue them out and settle on definitions. Painful, took months, generated real friction. But at the end of that process, he had an operational function that was speaking a single language for the first time in his tenure. That alone, he said, had probably saved him from two or three bad hires because it exposed where the real gaps were.

The third was that his ServiceNow instance had become the system of record for a lot of things that were not originally in scope. His procurement team had started raising vendor onboarding requests through the service catalog. His facilities team was using the asset module to track printers and meeting room equipment. His HR team had moved onboarding checklists onto the platform ahead of a proper HRSD build. None of that was planned. It happened because once the tool was there and people trusted it, the natural gravity pulled more processes onto it. He did not pay separately for most of these. They were absorbed into the platform he already owned.

Those three outcomes, taken together, were the real advantages of ServiceNow for his business. They were not what he had signed up for. They were considerably more valuable than what he had signed up for.

Why the sales case keeps missing on the measurable lines

I have seen this pattern often enough now to be clear about it. The quantified benefits in a ServiceNow business case tend to miss by thirty to fifty percent, and the direction of the miss is almost always the same. The hard efficiency savings underperform. The soft systemic effects overperform. The real ServiceNow ITSM benefits sit on the second side of that split, not the first.

There is a reason. Efficiency savings assume that the behaviour of your people is the thing you are automating. In practice, your people are not the bottleneck. The bottleneck is coordination. It is the handoff between the service desk and infrastructure, the misunderstanding between application support and the business, the fact that a change needs sign-off from four different people none of whom were formally identified as needing to sign off. ServiceNow does not make individual tickets faster to work. It makes the handoffs between teams visible, measurable, and arguable. The gains show up as fewer failed changes, less rework, less blame, better decisions. Those gains do not sit cleanly in a spreadsheet.

So when a vendor or a Big 4 implementation partner writes you a business case, they write the one you can defend to your audit committee. Twenty-two percent faster per incident. Four FTEs freed. A tidy ROI table. They write that case because it is quantifiable, not because it is true. The actual gain from the platform is systemic and arrives on a longer timeline, in forms that do not have a line on your P&L.

This is why I tell CFOs who are evaluating a ServiceNow build not to anchor on the efficiency numbers. Anchor on the operational maturity you expect to buy. Ask what dashboards you will be running your Monday morning with in year three. Ask whose job gets easier because the data exists. Ask what you will stop arguing about once everybody is in the same system. If the answers to those questions are serious, the project is worth doing.

The benefits of using ServiceNow that show up on your P&L anyway, just not where you expected

I want to be fair to the finance perspective here. “Operational maturity” is not a budget line. CFOs cannot defend a €500,000 annual platform spend by telling their board the IT function stopped feeling invisible. There do have to be numbers.

The place to look for the numbers is not the ones the business case promised. It is the ones that quietly moved in year two and year three.

Vendor spend tends to come down, not because you negotiated harder but because you can finally see what you have. Several of my mid-market clients have found that their third-party support contracts were larger than they needed to be, because nobody had an accurate picture of their estate. A clean CMDB on ServiceNow surfaces that.

Audit costs tend to come down. External auditors spend less time on your IT general controls when access reviews, change records, and incident evidence all come out of one tool with proper audit trails. I have seen audit fees drop by five to ten percent in year two after a clean ITSM build.

Business continuity exposure tends to come down. The number is harder to see because it only shows up when something bad happens, and even then it shows up as the absence of a loss. But if your major incident process is run on a tool that captures the sequence of events, your postmortems are better, your repeat failures reduce, and your worst outages get shorter.

Insurance premiums have started to be sensitive to this. A few of my clients have had cyber insurance renewals where the underwriter asked specific questions about change control and incident management maturity, and where a demonstrable ServiceNow process meaningfully affected the premium.

None of these line items were on the original 2023 business case. All of them turned up in year two or three. All of them were part of why the CFO on the call told me the investment was worth it.

Where to start, practically

If you are inside a mid-market company that is either considering ServiceNow or two years into an ITSM build and quietly wondering whether the numbers add up, here is what I would do.

Review your original business case with fresh eyes. Line by line. Do not be gentle with yourself. If the efficiency numbers missed, admit it and move on. The question is not whether you hit the slide deck. The question is what you actually have today.

Then write the honest version. What is now visible that was invisible before. What arguments have stopped happening in meetings. What processes have moved onto the platform without being specifically planned. What audit, insurance, or vendor conversations have gone differently because the data is better. That is your real year-two scorecard.

If you are earlier in the cycle and still evaluating, ask the firm pitching you how often their delivered business cases match their proposed ones. The honest answer is “not often, and the delivered benefits are usually different in shape from the proposed ones.” If the firm cannot have that conversation with you, they are selling you a slide, not a project.

And if you are two years in and feeling like the platform has drifted, that is often an instance health question more than a business case question. The investment is still valuable. The configuration may need a hard look. That is what the ten-day Milic Media Instance Health Report is built for. It gives you a short, independent read on where your platform actually sits, so your next twelve months of spend is directed at the places where it will compound. You can also look at the broader range of services we offer if the question is bigger than a diagnostic.

The CFO on the call I started this post with asked me what I would have done differently if I had been in the room when his original business case was signed. I told him I would have written a shorter one. Three paragraphs, no table, saying: we are buying operational visibility, a shared language across our IT teams, and a platform that other functions will quietly adopt. Expect the efficiency numbers to come in at about half what the vendor pitches. Expect the real value to be larger than the vendor pitches. Expect it to take three years to see clearly. Sign if you believe that trade. Do not sign if you only want the efficiency.

He said that would have been easier to defend to his board than the one he actually signed. I think he is probably right.

Mladen Milic runs Milic Media Kft, a boutique ServiceNow consultancy delivering implementation, health audits and HRSD work across the EU. Reach him at mladen@milicmedia.com.