25 Questions to Ask an ITSM Vendor That Go Beyond the Demo

A customer once asked us to build something highly specific. A one-off feature, custom to their business, that would never apply to anyone else. We said no.

They left for a vendor who said yes.

The demo they got was great. The system that got built was so heavily customized around their unique request that when it came time to move from testing into production, the data transition broke. The whole thing fell apart. They lost confidence in that vendor and came back to Xurrent, where they remain a customer today.

This is not a rare story. It is close to a composite of what we hear, again and again, from organizations that have switched ITSM platforms more than once. The grass is not always greener on the other side, and the vendor willing to say no to over-customization might be protecting you from exactly this outcome.

The demo shows you the software. It doesn't show you the partnership.

Buying ITSM software is not really a purchase. It's the start of a multi-year relationship, and most buyers evaluate it like a transaction instead. Feature comparisons dominate the evaluation process because features are easy to see and score. What's much harder to see in a 45-minute demo is what happens after the contract is signed: how support actually responds at 2 a.m., whether the roadmap moves when you ask it to, what an upgrade feels like eighteen months in.

Those are the things that show up later, usually at the worst possible time. Here are 25 questions worth asking before they do.

Product philosophy & customization boundaries

Every vendor will show you flexibility in a demo. Fewer will tell you where their flexibility ends, and that boundary matters more than the flexibility itself.

Release cadence & upgrade experience

Xurrent ships product updates on a weekly cadence, with changes released to a QA environment first so customers can review them and shape what ships before it reaches production. That is a meaningfully different experience from a vendor that upgrades once or twice a year.

• How often do you release updates, and does upgrading require downtime or a change window?
• Do customers see and test changes before they go live, or only after?

Customer support model

• Is support delivered by the vendor directly, or handed off to a partner or outsourced team once the contract is signed?
• What does your escalation path look like for a critical issue at 2 a.m.?

Customer success / relationship ownership

• Will I have a named point of contact after go-live, or does my account get routed to a general queue?
• How do you measure whether my organization is actually succeeding with your platform, beyond renewal?

Roadmap influence

• If my team requests a change, what's the realistic path from request to shipped feature, and who decides?
• Can you show me something that shipped in the last year because a customer asked for it?

Pricing & packaging philosophy

Xurrent doesn't publish fixed pricing tiers because plans are built around each organization's needs, and the company has said its licensing is designed to avoid surprise overage penalties if a team temporarily exceeds its user count. That's a useful contrast to ask about directly.

• What happens if we temporarily exceed our licensed user count?
• Are there hidden costs for support tiers, API access, or add-on modules I should know about now?

Community & peer network

• Is there an active user community where customers exchange ideas directly, and can I talk to someone in it before I sign?
• How does the vendor use community feedback to influence what gets built? Can you show me an example?

Target market focus

A platform built primarily for 50,000-seat global enterprises tends to carry assumptions that don't fit a 1,000-person IT team, and vice versa. Xurrent has been recognized on industry lists specifically for how its roadmap is built around midsize organizational needs, which is a different design center than platforms built for the largest enterprises first.

• Who is your platform actually designed for, and how does that show up in the product?
• Can you introduce me to a customer close to my size and industry?

Vendor financial stability / staying power

• How long has the company been profitable or well-funded, and what's the ownership structure?
• What happens to my data and my instance if the vendor is acquired?

Culture and values alignment

• How does your team talk about customers internally, as accounts or as partners?
• What's a decision your company made that cost you revenue but was the right call for customers?

Company mission / vision

• Where do you see this product in five years, and does that vision match where my organization is headed?
• What won't you build, even if customers ask for it?

Implementation & onboarding philosophy

• What does a realistic implementation timeline look like for an organization my size, not the best-case number in your marketing?
• Who owns onboarding: an internal team, a partner, or a mix, and how does that affect accountability if something goes wrong?
• What's the single most common reason implementations with your platform go sideways, and how do you prevent it?

The partnership is the product

Every ITSM platform on the market can mostly check the same feature boxes. What separates a good five-year relationship from a bad one rarely shows up in a demo. It shows up in how a vendor responds to your requests, how seamless your interactions are, and whether your feedback changes anything.

Ask these questions before you sign. The answers you get, and the ones a vendor avoids, will tell you more than any feature walkthrough ever could.

Want a closer look at how Xurrent approaches implementation and long-term partnership? Explore Xurrent's customer success stories.

Frequently Asked Questions