Convincing the CFO to fund ITSM modernization is notoriously complicated. Unlike a new application, an analytics solution, or a tool aimed at meeting specific security standards, an investment in the IT service management ecosystem is only indirectly linked to revenue or competitive advantage, even when the operational reasons are clear. The result is that IT as a whole is perceived primarily as a cost — one to be deferred or reduced in order to prioritize other spending more immediately associated with new revenue.

To overcome this perception, describing the features of a new ITSM platform in detail is not enough. A structured business case is needed, developed using the language that financial leadership understands, emphasizing the concepts of the cost of the current situation, risk reduction, and return on investment. This article offers CIOs and IT directors a four-step path to building a business case capable of securing financial leadership’s approval, especially when the budget is under pressure.

Step 1: What Does the Status Quo Cost?

The first of the four steps involves making visible a cost that no one currently measures. Maintaining the status quo is not free: it carries a cost that simply does not appear on balance sheets. To make it explicit, four items (plus one) need to be quantified.

The first is the loss of productivity among service desk operators, absorbed by manual and repetitive tasks that a well-structured process could automate. Quantifying the productivity loss is fairly straightforward: simply multiply the hourly cost of the staff involved by the hours dedicated to these lower-value activities. The result is a figure that often surprises — in a negative way — even the IT leadership itself.

The second is the overhead generated by escalations: the more a request is transferred to specialized support levels, the higher its handling cost becomes. A good way to size this item is to understand how to calculate the real cost per ticket, including re-openings.

The third is unplanned downtime linked to inadequate change management: according to an ITIC survey on the cost of downtime, for more than 90% of mid-sized and large enterprises, one hour of outage costs more than $300,000, excluding any penalties.

The fourth is compliance exposure: non-standardized processes and incomplete traceability translate into failed audits and potential fines.

To these items, a less obvious but equally concrete one is added: the cost of staff turnover. 69% of workers surveyed in a recent TeamViewer report on digital friction believe that technology frustrations have contributed to turnover in their organization. On the other hand, replacing a person requires an average of eight weeks of onboarding. Taken together, these figures describe a situation that financial leadership cannot ignore: the status quo entails a constant erosion of margins.

There is also an argument on which much of the business case rests: avoiding even a single major incident per year is often enough to pay for the entire ITSM investment. To use this argument effectively, however, a reliable baseline of current costs is needed: without it, any estimate of expected economic benefits remains easily contestable in a financial review. Collecting this data must therefore be addressed before drafting the business case.

Step 2: Change the Framework

The second step concerns the way the investment is presented. A CFO responds better to risk reduction than to the addition of new technological features. Describing ITSM modernization as the adoption of a more up-to-date platform with improved workflows places it among discretionary expenses. Presenting it as a means of reducing concrete risks moves it instead into the category of necessary investments.

The risks to highlight are those that senior business leaders already fear: service disruptions caused by poorly managed changes, regulatory exposure due to undocumented processes, security incidents arising from weak change control, and the risk associated with undistributed knowledge — which materializes when critical expertise is held by only a few individuals and is lost when those individuals leave the organization.

ITSM as a Form of Operational Insurance

An effective business case does not simply present the preferred solution: it defines the problem, compares the options — including the option of doing nothing, with its associated cost — and quantifies the risks associated with each option. A change released without an adequate control process, for example, can cause an outage quantifiable in hours of downtime and lost revenue, which a mature change management process would have intercepted in advance. In this framework, ITSM is a form of operational insurance: the request for funding is no longer about purchasing a tool, but about reducing a probable loss.

Step 3: Use the AI Budget as a Funding Lever

The third step leverages a well-established market trend. While traditional IT budgets are constantly under scrutiny, those allocated to artificial intelligence continue to grow: according to Gartner, global AI spending will reach $2.59 trillion by the end of 2026, an increase of 47% year over year. From this trend, a concrete opportunity emerges for the CIO.

AI adoption depends not only on the availability of financial resources, but also — and above all — on the maturity of organizational processes. This is a decisive observation: an AI trained on fragmented service data, a disorganized knowledge base, and unstructured processes produces unreliable results. ITSM modernization can therefore be presented as the infrastructure that prepares the organization for the implementation of AI initiatives. Clean data, consistent workflows, and systematic, well-organized knowledge are the prerequisites for any artificial intelligence initiative in IT support to truly work.

Interest in these solutions is already widespread: according to the same TeamViewer survey cited earlier, 48% of workers believe that AI can reduce technology malfunctions, and half say they are willing to let AI handle basic tasks such as resolving simple issues or resetting passwords. Presenting ITSM modernization as the foundation for AI initiatives in IT support — rather than as an isolated line item in the IT budget — connects it to a growing area of spending rather than a shrinking one. For the CIO, this means shifting the funding request away from the traditional IT budget, which is increasingly contested, toward the fastest-growing expenditure category in the entire organization.

Step 4: Set ROI Expectations That Will Hold Up to First-Year Review

The fourth step is the most delicate because it is the one on which the business case is judged in retrospect. The temptation, in order to secure approval from business decision-makers, is to promise too much: very significant cost reductions in very short timeframes and near-immediate returns. This is, however, the fastest path to losing credibility at the first end-of-fiscal-year review, when the real numbers do not match those promised. A solid and sustainable ROI forecast is built on measurable, time-phased objectives, anchored to the baseline defined at the outset.

A realistic objective, for example, is a progressive reduction in resolution times and cost per ticket over the course of the first year, with interim indicators verifiable as early as the first few months: it is preferable to demonstrate a partial but concrete return early on, rather than waiting for an overall result that is difficult to demonstrate.

The Most Common Mistake to Avoid

It is worth honestly distinguishing tangible benefits — such as reduced ticket volume, fewer SLA breaches, lower cost per ticket, fewer hours of downtime — from less tangible ones, such as user satisfaction and reduced turnover, and avoiding presenting the latter as if they were measurable with the same precision as the former.

And it is essential to avoid the most common mistake: underestimating the resources dedicated not only to technical implementation, but also to adoption by operators and users, on which the actual return depends. A solution that is adopted but used inadequately produces no ROI and undermines the credibility of those who championed the investment. A more conservative but solid return, verifiable quarter by quarter, is preferable to an ambitious promise destined to be disproved.

From Cost Center to Value Center

For the CIO, the business case is the tool that translates the value of IT into the language of business. Built well, the business case can change the way ITSM is perceived: from an unavoidable cost to an investment that reduces risks, unlocks productivity, and prepares the organization for the technologies to come.

When IT budgets are tight, the path forward is clear: quantify current costs from a real baseline, frame modernization as risk reduction, tie foundational upgrades directly to the AI budget as critical enabling infrastructure, and set return expectations that hold up to scrutiny. Ultimately, the goal is to prove—with data in hand—that maintaining the status quo is by far the most expensive choice.

FAQs

1. Why is it difficult to justify an investment in ITSM? Because unlike a specific application or a particular security tool, ITSM is difficult to link directly to revenue. This is why a business case is needed that translates its value in terms of avoided costs and reduced risks.

2. How is the cost of the status quo quantified? By measuring concrete items starting from real baselines: productivity lost by operators, escalation overhead, unplanned downtime due to inadequate change management, compliance exposure, and the cost of turnover.

3. What does it mean to position ITSM as “AI-readiness infrastructure”? It means presenting it as the enabling foundation — clean data, structured processes, organized knowledge — without which AI initiatives do not produce reliable results, thereby connecting the project to the growing AI budget.

4. How are realistic ROI expectations established? With measurable, time-phased objectives, anchored to a baseline and verifiable as early as the first quarter. A conservative but demonstrable ROI is preferable to an ambitious promise that does not survive the end-of-year review.