The License Isn't the Cost
Let me start with something obvious that somehow surprises people every single time: the contract you signed with your ITSM vendor is not your actual expense. It's just the opening act.
You know the number. It's in your budget spreadsheet. ServiceNow or BMC or Atlassian or whoever you went with quoted you X dollars per user per month, and you multiplied it out and presented it to your CFO and everyone nodded and moved on. That number is a fiction. It's what you're paying. It's not what it costs.
The real cost lives in the margins of your operation, in the hours your people spend doing things that the platform was supposed to eliminate, in the integration projects that somehow take three times longer than promised, in the customizations that lock you into a version of the software from 2019.
The Implementation Overrun You Already Knew About
Okay, this one is less hidden. You probably budgeted for implementation and it went over. Everyone's implementation goes over. But here's what's interesting: most IT leaders treat this like a one-time wound that heals. They don't factor it into the cost per year, which means they're fundamentally underestimating their spend.
If your implementation cost 40 percent more than budgeted, and you amortize that across a five-year contract, that's real money added to your annual expense every single year. Build that into your mental model of what this thing costs. Don't pretend it was a one-off that doesn't matter anymore.
The Hidden Tax of Your Own People
This is where it gets expensive. Every mature ITSM platform requires dedicated resources to keep it running. Not just licensing management, though that's part of it. I'm talking about the architect who understands your workflow customizations. The analyst who knows which reports actually matter and maintains them. The integration specialist who keeps your API connections alive when vendors update their systems.
These people aren't free. They're not doing other things while they're keeping your ITSM platform functional. At a mid-sized organization, you're probably looking at one and a half to two full-time equivalents dedicated to ITSM administration and maintenance. That's salaries, benefits, everything. For a $150,000 per person fully loaded cost, you're spending $225,000 to $300,000 annually on your own people just to prevent the platform from falling apart.
Nobody tells you that when you're buying the platform. They should.
The Adoption Tax Nobody Measures
When your ITSM implementation doesn't stick, what happens? Usually your organization creates workarounds. Some teams go back to email. Others use spreadsheets alongside the system. A few maintain shadow IT services because they don't trust the ticketing system to actually get things done.
This costs you in lost efficiency, in the time your people spend working around the platform instead of with it, in the data integrity problems that come from multiple systems of record. You can't put a clean line item on a P&L for this. It just lives as ambient inefficiency in your IT organization. But it's real, and if your adoption rate is below 80 percent across your user base, you should be asking yourself whether the platform is solving the problem you bought it to solve.
The Vendor Lock-in Interest Rate
Here's the part that keeps me up at night on behalf of IT leaders. Once you've deeply customized your ITSM platform, your switching costs become astronomical. That BPMN workflow that took six months to build the way your organization needs it? It doesn't port to another vendor. That custom dashboard your security team lives in? Gone. That API integration that connects your ITSM system to twelve other tools in your stack? Someone's rewriting it from scratch.
So when you're evaluating the true cost of staying with your current vendor versus moving to something new, you have to factor in the cost of your own customizations as a switching cost. It's like being charged rent forever for decisions you made years ago.
Vendors understand this perfectly. They count on it. They build customization-friendly platforms specifically because they know it makes you less likely to leave, even if their roadmap stalls or their pricing goes north at renewal time.
The Reckoning
Here's my advice: go back to your annual ITSM spend and audit it honestly. The license cost is fine. Add in the implementation burden amortized across five years. Add in your dedicated staff. Add in the adoption drag. Divide by the value you're actually getting.
If that number makes you uncomfortable, that's the actual cost of your ITSM platform. That's the one you need to have a conversation about. Not the one in the vendor contract.