Pre-Purchase Checklist for Evaluating Any ITSM Platform

Most software gets chosen after one good demo. The questions below are the ones worth answering before that happens, while you can still judge a platform coldly instead of looking for reasons to justify a decision you have already made emotionally.

None of this is specific to us. It is the same list we would want a buyer to run us through.

Check Whether You Can Actually Change Anything Yourself

This is the one people underestimate the most, and it is becoming more important, not less. Can you add a new field to a form yourself? Can you build a new workflow rule without filing a support ticket to the vendor and waiting on their timeline instead of yours? Is the underlying data shared across the whole platform, or does each additional piece, asset tracking, a knowledge base, project management, function like its own separate product bolted awkwardly onto the side?

Your needs today are not going to be your needs in eighteen months. A tool that feels perfect right now but requires a support ticket for every small adjustment is going to feel a lot less perfect the first time you need something changed quickly, and you will need something changed quickly eventually. Every team does.

Ask Who You Will Actually Talk to When Something Goes Wrong

During setup, is there a real, named person helping you, or do you get dropped into a rotating support queue and pointed toward a community forum? What is the honest response time once you are an actual paying customer, not a prospect they are still trying to win over? And is there some lower-commitment way to try the product for real before you sign a full annual contract, and if so, what does that genuinely include?

Add Up the Full Cost, Not Just the License Fee

This is where quotes quietly spiral. Beyond the sticker price, factor in implementation services, any required add-on modules, the cost of a certified administrator's salary if the platform genuinely needs a specialist to run it, and any usage-based charges. Per-asset or per-configuration-item pricing is a common one, and it can grow faster than your headcount ever will.

Ask the vendor directly what a company your size typically pays in year one, everything included, not just the license line. A vendor who is genuinely confident in their pricing will usually just tell you a real number without dancing around it. Ours is published, if you want a sense of what that looks like when nobody is hiding it.

Watch These Signs During a Demo

A few things are worth paying close attention to while you are sitting through a sales demo, since this is where a lot of the real information hides in plain sight:

• How many separate screens or logins does it take to complete one simple task, like resolving a basic ticket start to finish?
• When you ask a pointed question about pricing or contract terms, does the rep answer directly, or redirect it to "let's talk about that after the demo"?
• Does the rep show you making a configuration change live, on the spot, or do they wave at the idea of flexibility without ever actually demonstrating it?
• Are they showing you their best case, cherry-picked workflow, or are they willing to show you something messier and more realistic, closer to how your actual team works day by day?
  

Know What Happens If You Ever Want to Leave

If the relationship does not work out down the road, is your data yours to take with you, in a format you can genuinely use elsewhere? Is there a clear, defined export process laid out in writing, or just a vague promise to "work with you" that turns out to mean nothing until you are trying to leave and discover the fine print says otherwise?

It is also worth asking, very specifically, what migrating your existing tickets, assets and knowledge base articles involves in practice. "Yes, we support imports" is not a real answer. Ask them to walk you through exactly what that process looks like, start to finish, for a company your size.

Weight These Differently Depending on Where You Are

Not every item on this list matters equally for every company. A five-person IT team getting its first real system should weight setup speed and self-configuration heavily, since you do not have the headcount to manage a long implementation project. A larger, more established team might reasonably weight governance, audit trails and role-based permissions more heavily, since the operational risk of getting that wrong is bigger at scale. Know which situation you are in before you decide which items here matter most.

How to Actually Use This

Copy these questions into a spreadsheet and score every vendor on your shortlist against the exact same set, not just the one you already have a demo booked with next week.

Here is the honest, slightly uncomfortable truth about how most people buy software: they fall for the first genuinely good demo and then spend the rest of the process quietly looking for reasons to justify the choice they had already made emotionally somewhere around minute ten. Running through these questions cold, before you have sat through a polished pitch, is really the whole point of doing this at all.