The Total Cost of Owning an ITSM Platform

Part of a series. This article is drawn from the L5 white paper on what a fragmented service portfolio really costs to run. Download The Hidden Cost of Fragmented Service Operations.

ITSM total cost of ownership is the license plus everything else it takes to run the service. Much of that never appears on the service's budget: admin time, training, undocumented knowledge, audit effort, the weekly report, integration upkeep, supplier dependency and downtime risk. Finance approves the license line. The rest is paid by other teams, in hours, rework and risk.

Each year the renewal arrives, finance approves it, and the figure looks reasonable. On paper, the service desk costs what the license says it does. Our white paper estimates that licensing, integration, internal IT management and vendor services together run 2.7 to 4.1 times the license line, drawing on SaaS portfolio data from Productiv and BetterCloud. Some of the eight costs below sit inside that estimate. Others, such as training, audit effort and downtime risk, sit in budgets it does not count.

This is why legacy service software looks inexpensive. It seldom fails outright. Tickets get closed, the service desk stays open, and the renewal looks modest next to the cost of replacement. The pattern holds in very large IT budgets too. US federal agencies spend about 80 percent of their IT budget operating and maintaining existing systems (GAO), and CIOs surveyed by McKinsey report that 10 to 20 percent of the budget meant for new products goes to resolving tech debt.

What does ITSM total cost of ownership include?

Ask what a service platform costs and the answer is usually one number: the license. Total cost of ownership asks a more useful question, which is what the platform costs to own and operate, including training, lost productivity and downtime (IBM, 2025). The distance between those two answers is the hidden cost of operational inefficiency.

It is the time, rework and risk that fragmented processes, manual work and disconnected systems move onto the rest of the organization. The table sets out where each cost appears and why no budget captures it.

Much of it is failure demand

John Seddon calls this failure demand: work that exists only because something was not done, or not done well, the first time. A follow-up on a missing laptop, a reopened incident and a second access request for the same system are all repeat work, and each one takes an agent's time as fully as a new ticket.

Failure demand also explains why a self-service portal on its own rarely closes the gap. Gartner puts a live contact at $8.01 and a self-service contact at $0.10, but that saving arrives only when the knowledge behind the portal exists and can be found.

Why does it stay hidden?

This cost recurs every week and belongs to no one's budget, so no review process is designed to examine it. Project costs are approved as capital expenditure, licenses are negotiated at renewal, and a difficult quarter is put down to a busy period.

It also grows over time. Disconnected systems create manual work, manual work invites workarounds, and each workaround becomes another system to reconcile. Meanwhile the few people who understand how things work spend their days on training and escalations, which is the time they would need to write down what they know.

Researchers writing in Harvard Business Review observed employees switching between applications about 1,200 times a day, which cost them just under four hours a week in reorientation.

What did our clients tell us?

We reviewed our discovery and delivery communications with seven client organizations across healthcare, financial services, chemicals, retail, media and semiconductors, plus a company emerging from restructuring. None of these were interviews about cost, yet every organization described at least one hidden cost, often in passing.

The weekly report and admin time came up most directly:

"The only reporting we effectively use today is number of tickets per technician this week. That is all we have today."

A client in media

"We don't want it to take 45 minutes to generate the change request in order to do a two-minute build."

A client in financial services

Training and undocumented knowledge followed close behind:

"A lot of the training time was actually on the system. How to navigate, what to do here, what to do there."

A client in retail

"If we're going to go down this road, someone has to maintain that, and it can't be just me."

A client in financial services

Two examples show the pattern. A semiconductor client's homegrown ticketing tool reached its limit at 5,000 items, so the team deleted older tickets to keep it running, and with them the history that would have shown recurring problems. A chemicals client that grew through three acquisitions inherited three service tools that did not connect, and change records that auditors could no longer rely on. In both cases the system still worked, and the cost had moved to other teams.

What does the research show?

Government auditors, analyst firms and academic researchers point the same way. Their figures describe different populations, so read them as indicators of direction and scale.

No single study measures the whole cost. Read together, they show much of the money, and much of every working week, going into keeping existing operations running, mostly outside the budget that owns the service. Two findings cited in our white paper complete the picture. Gartner puts implementation services for enterprise ITSM at 3.1 to 4.8 times the license, and IDC found that platforms run by a dedicated operator kept 89 percent of their initial deflection rate at 18 months, against 51 percent for platforms run by IT generalists as a secondary job.

How do you calculate ITSM total cost of ownership?

Five established frameworks turn a hidden cost into a number. Used together, they settle what a budget owner needs to know before acting: how large the cost is, how much of it is avoidable, where it originates, what a single request costs and who owns it.

Pricing one request

Kaplan and Anderson's time-driven activity-based costing needs two estimates: the cost of a minute of team capacity, and the minutes each request type consumes, including follow-ups and rework. They recommend basing the cost per minute on practical capacity, usually around 80 percent of paid time, since no team is productive for every paid minute.

Cost per request type equals minutes per request, including chasing, switching and rework, multiplied by cost per minute, which is team cost divided by practical capacity.

Finding where it is caught

The cost-of-quality model, after Juran and as defined by ASQ, shows where hidden cost builds up. Prevention and appraisal are planned and visible, and failure is neither. External failure, such as a reopened incident or an audit finding, is the most expensive category and the least visible to the budget.

How does the industry respond?

Most organizations respond with a platform decision. Each option fixes something real, yet most leave the recurring, off-budget costs in place, because those costs live in process and ownership.

AI deserves its own caution. Automating a process that nobody owns speeds up the same gaps, which is the subject of the hidden cost of unoperated AI.

How does L5 approach it?

L5 deploys and operates AI on purpose-built service management platforms, Zendesk, ClickUp and Workday, for mid-market organizations. We treat hidden cost as an operating problem, and our three motions map onto ITIL's continual improvement model.

Assess takes one week and ends with a maturity scorecard, a roadmap and a business case. Onboard puts the first use case live in production by week three, with trained users and the next Drive in the backlog. Operate runs every week, with a scorecard, production changes and an updated roadmap. Each Drive ends with a defined change in production, and done is agreed before the Drive begins.

The operator is the part a one-off program leaves out. Fewer than 10% of L5's 600+ customers reach Operated without an active operator. Our ACT methodology (Accelerated Customer Transformation) compressed ClickUp onboarding from 55 days to 7.

Frequently asked questions

What is ITSM total cost of ownership?

It is everything it costs to own and run an ITSM platform beyond the license: integration, internal IT management and vendor services, plus costs that land in other teams' budgets, such as admin time, training, audit effort, the weekly report and downtime risk.

What is a typical ITSM total cost of ownership multiple?

Our white paper estimates that licensing, integration, internal IT management and vendor services together run 2.7 to 4.1 times the license line. Training, audit effort and downtime risk sit outside that estimate.

Why does legacy service software look cheap?

The renewal only shows the license. Licensing, integration, internal IT management and vendor services together run an estimated 2.7 to 4.1 times the license line, and the eight hidden costs sit in HR, finance, risk and every team that raises a request.

How do you calculate ITSM total cost of ownership?

Add integration, internal IT management and vendor services to the license, then price the time the service consumes elsewhere with time-driven activity-based costing: the minutes each request type takes, including chasing and rework, multiplied by the cost per minute of practical capacity.

Does replacing the platform remove the hidden cost?

It rarely does on its own. A replacement usually moves the old process onto a new tool, so training and audit effort start again. The cost falls when someone owns the process after go-live and measures it every week.

See what your own platform costs

The white paper sets out the cost mechanisms of a fragmented service portfolio in full. To see where your own operation stands, book an assessment: in one week you get a maturity scorecard, a roadmap and a business case.