A vendor-run demo is a sales asset, built to show the platform at its best with every paid capability switched on and none of the cost attached. That is not deception, it is the format, and the buyer's job is to change the format. The way you do that is to script the scenario, run it identically across the shortlist, and interrogate the cost basis of every feature as it appears. This sits inside the wider procurement sequence in our ITSM procurement playbook from requirements to signature; this article is the demo-stage method.
What hidden costs should an ITSM demo expose?
Four categories hide inside a polished demo, and each becomes a line on your bill if you do not surface it. Tier gates: a capability shown as standard that actually lives in a higher plan, so adopting it lifts your whole base up a tier. Metered AI: features that look included but consume assists or actions you pay for by volume, which as of 2026 vendors are bundling and metering more aggressively. Connector and integration licenses: the integration shown as native that needs a separately priced connector. Implementation scope: the configuration that makes the demo work, priced outside the subscription as professional services.
| What the demo shows | The hidden cost to expose | Question to ask live |
|---|---|---|
| A slick feature, switched on | It sits in a higher tier | Which plan includes this, and what does moving the base cost? |
| An AI assistant answering instantly | It is metered per assist | Is this metered, and what is our volume at our ticket rate? |
| A native-looking integration | It needs a paid connector | Is the connector included or licensed separately? |
| A fully configured workflow | Configuration is paid services | What implementation cost produces this state? |
How do you stop a vendor demoing only the headline features?
Take control of the script. Send a written scenario in advance, built from your real workflows, and require the vendor to perform it rather than their prepared tour. The scenario should include the awkward parts: the integration you actually depend on, the approval chain that is messy, the reporting your leadership demands. When the vendor has to run your process, the gaps appear, and every gap is a negotiation point. The discipline carries straight into the proof-of-concept stage, covered in how to run an ITSM proof of concept that protects leverage.
Book a contract negotiation review.
We script the demos, run them across the shortlist, and turn every exposed tier gate and metered line into a negotiation point. Fixed fee or gainshare.
Book a contract negotiation review →How do you run the demo, step by step?
- Write the scenario from your real workflows, including the integrations and approvals that matter most.
- Send it to every shortlisted vendor in advance, identically, so the demos are comparable.
- Require live execution of your scenario, not a recorded or idealized walkthrough.
- Cost-tag every feature as it appears. For each capability, record the tier, whether it is metered, and the connector or services it implies.
- Score on total cost, not features. Feed the tagged costs into a side-by-side so the comparison is economic, not a beauty contest.
Our gated 2026 ITSM Negotiation Benchmark Report includes the demo scenario template and the cost-tagging sheet behind a comparable evaluation.
What will the vendor argue, and how do you counter?
The vendor will steer back to its strongest features; counter by holding them to your written scenario and noting any refusal to run it. It will describe paid add-ons as part of the platform; counter by asking, live and on the record, which tier and which license each one requires. And it will leave implementation cost for later; counter by requiring a configuration estimate for the demoed state before you score. The cross-stage method is the firm's Map, Benchmark, Leverage, Close, and across ITSM engagements disciplined evaluation is part of the 30% average reduction we see.
What to do next
Write the demo scenario before you schedule a single vendor, and commit to running it identically across the shortlist. Build the cost-tag sheet so the team records tier, metering, and add-ons in the room rather than from memory. When you are ready to turn the findings into a negotiation, the engagement goes through our contract negotiation service on fixed fee or gainshare, and the full sourcing sequence is in the ITSM procurement playbook.
Frequently asked questions
- What hidden costs should an ITSM demo expose?
- Tier gates on features shown as standard, metered AI that looks included, integrations needing a paid connector, and configuration priced as professional services. A scripted demo forces each into the open before pricing.
- How do you stop a vendor demoing only headline features?
- Send a written scenario in advance, require the vendor to run your workflow live, and ask the tier, metering, and license question for every feature shown.
- Should every vendor get the same script?
- Yes. One scenario run identically makes the demos comparable and feeds a total-cost comparison rather than a feature contest. It varies by deal size, but we average a 30% reduction across ITSM engagements.
Run demos that expose the cost.
We script the scenario, run it across your shortlist, and turn every tier gate and metered line into leverage.
Book a contract negotiation review →