Everyone wants a great ITSM platform. Nobody wants to pay for the implementation.
I’ve been doing ITSM projects for a long time, and one thing I’ve learned is that organizations rarely underestimate the software. They underestimate the work it takes to implement it correctly.
A common scenario looks like this: months are spent evaluating products, attending demos, comparing features, and negotiating licensing. Then implementation begins, and suddenly the focus shifts to one thing: reducing hours. On paper, it sounds great. Faster deployment. Lower consulting fees. Smaller project budget.
Until six months later.
Now approvals don’t work the way the business needs them to. Reporting can’t be trusted. Users have gone back to email. Service desk teams are creating workarounds because the system doesn’t support how the organization actually operates. The implementation may have been cheap, but the long-term cost isn’t. The biggest misconception in ITSM is that implementation is mostly configuration. It isn’t. The hard part is understanding the business.
Who approves requests? What happens when managers are out of the office? Which departments have exceptions? What information does leadership need? How should future growth be handled? These conversations take time, but they’re also where most of the value is created. Skip them, and you’ll likely end up with a system that technically works but doesn’t solve the problems it was purchased to address. There’s also something many organizations overlook: technical debt exists in ITSM too.
Every shortcut creates a future problem. Every rushed workflow, undocumented customization, and quick-fix integration becomes something that needs attention later. What saves time during implementation often costs significantly more to fix once the platform is live and users depend on it. The best ITSM implementations aren’t always the biggest or most expensive. They’re the most realistic.
They devote enough time to discovery, challenge assumptions, and focus on building processes that will still make sense years from now. They recognize that ITSM is about improving service delivery, not simply installing software. Before choosing the lowest implementation estimate, ask yourself a simple question:
Are you actually reducing the cost, or are you simply moving the cost somewhere else?
Because in ITSM, shortcuts rarely disappear. They usually show up later, after the project is complete and your users are counting on the system every day. That’s when cheap implementations become expensive.