How to choose an ITSM solution in 2027, without regretting it by Q3.

Before you shop: the uncomfortable question

I've sat through more ITSM demos than I can count. Somewhere around the fortieth one, a pattern emerged: the tools almost never fail to match the requirements spreadsheet. They fail because nobody in the room could answer one question honestly.

Why is the current system being replaced?

Not "we outgrew it," not "we want AI." The real reason. Is the helpdesk drowning because three times as many people are submitting tickets through email and a shared inbox that nobody triages? Is the CFO furious about a renewal quote that doubled? Did a new CIO arrive with a vendor they trust from a previous job? Each of those points to a different purchase, and buying the wrong one is how you end up with a seven-figure platform that three people log into.

So before you open a single vendor tab, write down, in one sentence, what would have to be true twelve months after go-live for everyone to agree the project worked. "Tickets stop arriving by email." "New starter onboarding takes an hour instead of three days." "We can tell the CFO exactly what the helpdesk costs per ticket." If a tool can't serve that sentence, nothing else on its feature list matters.

A requirements spreadsheet is how you buy software. A sentence about what success looks like is how you buy the right software.

What changed since you last bought ITSM

If you picked your current tool four or five years ago, the market has quietly rearranged itself. Three shifts matter for anyone evaluating ITSM software in 2027.

First, the middle of the market got good. There was a time when the choice was brutally binary: pay enterprise prices for enterprise workflow engines, or settle for a glorified shared inbox. That's over. Tools like Mint Service Desk now ship configuration management, service catalogs, SLAs, and asset management that would have been mid-market premium features in 2019, at prices that make the big suites' quotes look like a rounding error gone wrong. The gap between "affordable" and "capable" has mostly closed.

Second, AI moved from slide deck to line item. Every vendor now sells AI somewhere. The question is no longer "does it have AI" but "what is the AI actually doing, and who pays for it." The honest answer for most tools: the AI drafts replies, tags tickets, deflects the password-reset flood, and summarizes conversations. That is genuinely useful. It is not, however, worth a per-interaction fee that scales with your ticket volume, which is exactly how several major vendors price it. More on that in the pricing section, because it's where budgets quietly bleed.

Third, consolidation became the story. The giants swallowed the independents, and the survivors are learning what it's like when their roadmap becomes a slide in a shareholder deck. If your tool got acquired recently, check who's actually answering the support line. Plenty of teams shopping in 2027 aren't choosing their first ITSM tool. They're fleeing an acquisition.

The real cost, decoded

Nobody in this industry quotes prices honestly, so here's the map. ITSM pricing comes in four flavors, and the one a vendor picks tells you what they think of you.

Per agent, per month. The classic. You pay for every person who answers tickets. Transparent, predictable, and fair as long as "agent" means what you think it means. Ask what happens when your headcount dips in a quiet quarter. Some vendors let you flex down. Some will happily invoice a ghost.

Per technician. The same thing with a nicer name and a subtle trap: some platforms charge for every person who can see a ticket, not just the ones working them. A "read-only stakeholder" that costs full freight adds up fast when your approvers, managers, and auditors want visibility.

Per usage. Tickets, API calls, AI interactions, records. This is the model that looks cheap in the demo and ruins someone's quarter in month nine, when ticket volume doubles and so does the bill. Usage pricing isn't automatically bad. It is automatically hard to forecast, and finance people hate surprises more than they hate high prices.

"Contact us." The enterprise special. The quote arrives after three discovery calls and lands somewhere between a car payment and a small mortgage. There's nothing wrong with enterprise pricing per se, but the opacity is the point, and the discount you "win" at the end of the quarter is the price the vendor decided you could bear.

Whatever the model, remember the number on the quote is the floor, not the ceiling. Implementation, data migration, training, and the integrations you didn't think about until week three routinely add 30 to 50 percent on top of year-one license costs for enterprise suites. This is one of the quiet reasons tools like Mint Service Desk keep winning shortlists: the setup is measured in days, the pricing is published, and there's no services arm quietly tripling the bill.

The twelve questions that actually matter

Feature checklists are noise. These twelve questions, asked in this order, will tell you more about a vendor than any G2 grid ever will.

1. Can we get to a working service desk in a week? Not a pilot of one module. A real desk, real tickets, real portal. If the answer involves a partner and a statement of work, note it.
2. What does a ticket cost us at 5, 50, and 500 agents? Make them run the math for your actual org chart, including the read-only people.
3. What happens when we cancel? Data export formats, lock-in on workflows you've built, and whether your service catalog is portable.
4. Who builds workflows, and how? If changing a form requires a certified administrator or a professional services engagement, every process change becomes a project.
5. What does the end-user portal look like? Not the admin view. The thing your employees see. If it looks like it was designed in 2011, they'll email the helpdesk instead.
6. How does the AI get billed? Included, metered, or per seat? Ask for a customer reference your size and their actual deflection numbers.
7. Can we run a second service desk for HR or Facilities? If ESM is anywhere on your horizon, this question decides whether you buy once or twice. Separate portals, separate permissions, one engine.
8. What's the asset management story? If CMDB-lite is included, great. If it's an upsell with per-CI pricing, get that quote in writing now, not later.
9. Where does support sit, and what's the response SLA? The support you get as a prospect is the best support you will ever receive. Time the real answer.
10. Show us the audit trail. Who changed what, when, and why. This one question separates serious tools from toys, and auditors ask it before you do.
11. What breaks at our peak? Every tool handles Tuesday. Ask what happens on the Monday after a ransomware drill, or during a merger's onboarding surge.
12. Why did your last three customers leave? A vendor that can't answer this is a vendor that hasn't thought about it. A good answer is specific and unflattering in places.

Run a demo that tells you the truth

Standard demos are theater. The vendor shows you their fastest configured path, the features that photograph well, and a dashboard someone spent a weekend polishing. To get truth out of a demo, you have to change the format.

Send every shortlisted vendor the same three scenarios a week before the call. Real ones. "A new hire starts Monday and needs a laptop, accounts, and building access." "An exec's mailbox is full and they're furious." "A routing rule needs to change because the networking team reorganized." Ask them to perform those, live, in their own environment, with their own clicks.

Then watch for three things. How long the setup took them. Whether they clicked through it or asked you to wait while someone "checks the backend." And whether the workflow looks like something your team could maintain or something a consultant built that your team will inherit like a haunted house.

One more trick: ask them to demonstrate a failure. What does the ticket look like when an SLA breaches? When an automation misroutes? Vendors rehearse the happy path. How they handle the unhappy path, live and unrehearsed, tells you everything about the product's maturity.

Any tool can demo a ticket lifecycle. The product is what happens when the ticket goes sideways.

The 2027 shortlist

We'll keep this honest and brief, because you can read a hundred listicles. The right answer depends almost entirely on your size and your tolerance for ceremony.

If you're genuinely enterprise. Global scale, thousands of agents, dozens of business units, a procurement team that enjoys a pilgrimage: ServiceNow and Jira Service Management are where those conversations end. You'll pay for the ecosystem, the partner network, and the brand that survives your CIO's departure. That can be worth it. It's rarely cheap, and the implementation is a project with a steering committee, plan accordingly.

If you're small and budget-first. Freshservice, Zoho Desk, and Freshdesk cover the sub-15-agent ground respectably. You trade some workflow depth for speed-to-value, and for a lot of teams that's the right trade.

If Microsoft is your gravity well. If the company lives in Teams and the path of least resistance is everything else, Microsoft's own service management surface keeps improving. It's better than its reputation, though "included in an EEA you already pay for" is doing a lot of work in that evaluation.

Whatever direction you lean, run the battle card comparison on your final two. It takes four minutes and it has a way of ending arguments that spreadsheets keep alive for weeks.

Red flags that predict regret

• The price is hidden until a "custom quote call." If transparency starts at the pricing page, it ends at the renewal.
• AI is a separate line item that scales with volume. Your bill should not rise because your service desk got popular.
• Every admin change needs a certified partner. You're not buying software, you're renting a consultancy.
• The demo ran on a pre-built environment they wouldn't deviate from. The happy path is rehearsed. So is the disappointment.
• Acquired within the last 18 months. Roadmaps stall, support moves, pricing changes. Sometimes it works out. Ask pointed questions.
• "Read-only" users cost full seats. Visibility shouldn't be a luxury good.
• The reference customer is 40x your size. Ask for a reference that looks like you, or accept that you're an experiment.

FAQ