How to Run an ITSM RFP That Creates Leverage

An ITSM RFP creates leverage when it produces a real, comparable, time bound alternative that the incumbent cannot dismiss. Most RFPs do the opposite: they are vague, late, and obviously a formality, so the incumbent reads them as theater and holds the line on price. Run one with intent and a single competing quote with matching scope can be worth a seven figure swing on a large renewal. This is how to structure the process so it moves your number whether or not you ever change platforms.

This article sits under our complete guide to ITSM competitive leverage, which covers the wider playbook. Here we go deep on the RFP itself, the single most powerful tension building tool a buyer controls.

Why most ITSM RFPs fail to create leverage

A vendor account team can tell within a page whether a request for proposal is a genuine evaluation or a box being ticked. The tells are familiar: it lands six weeks before renewal, the scope is copied from a template, the requirements do not match how you actually run service management, and the incumbent is clearly being invited to win. When the process looks like that, the discount you were hoping to unlock simply does not appear, because the risk of loss the vendor is pricing against is close to zero.

Leverage requires the opposite signals. Time, specificity, and a credible sense that the decision is open. If you cannot send those signals honestly, you are better off with a lighter approach. We cover that route in competitive tension without an RFP.

Start twelve months out

Timing is the foundation. The earlier you start, the more real your alternative can become before the renewal clock forces a decision. Twelve months gives you room to scope properly, run demonstrations, collect quotes, and, if it comes to it, plan a transition. Six weeks gives you a quote the incumbent knows you cannot act on. For the full timing logic, see how to time a competitive ITSM evaluation.

Scope the RFP to your real environment

The single biggest driver of a comparable quote is a scope that mirrors how you actually operate. Specify fulfiller and requester counts as they really are, not as the incumbent has license them. List the modules in genuine use, the integrations that matter, the ticket volumes, and the service levels. A precise scope does two things: it forces every bidder, including the incumbent, to price the same thing, and it surfaces the shelfware you are paying for today. Many buyers discover during scoping that they are licensed for far more than they use, which is leverage in itself. The license optimization guide covers how to find that gap.

Invite the right field

A credible field is not the entire market. It is two or three platforms that could genuinely carry your workload. For a ServiceNow incumbent that often means BMC Helix at the enterprise tier and Jira Service Management or Freshservice as a lower cost challenger. The mechanics of using those names well are in how to use BMC and Jira as leverage against ServiceNow, and the platform comparison is in BMC Helix vs Jira vs ServiceNow. Inviting bidders who clearly cannot meet your requirements weakens the process; the incumbent knows you will not pick them.

Run it as a real decision

Behave throughout as though you might switch. Score the responses against your published criteria. Hold demonstrations. Let your own stakeholders see the alternative so that your willingness to move is visible inside your organization, not just asserted to the vendor. The incumbent has back channels; if your team has genuinely engaged with another platform, that reaches the account team and changes how they price. This is the difference between leverage you hold and leverage you merely claim, which we unpack in how to build a credible ITSM switching threat.

Convert the quotes into a number

Once you have comparable bids, the negotiation begins. Bring the competing quote with matching scope to the incumbent and let the gap speak. Ask for the discount against your benchmark, not against their list. Capture transition incentives and migration credits even if you stay, since vendors will fund a buyer they are at risk of losing; see how to negotiate migration credits and incentives. Ground your target in real market data using the ITSM pricing benchmarks guide rather than the vendor's framing.

A retail client of ours ran exactly this process, a structured evaluation against Jira and Freshservice, and converted it into a renewal of $4.1M down to $2.7M, a 34% reduction, while staying on their existing platform. The RFP was real. The switch was optional. That is what a well run process buys you.

Run the evaluation honestly

An RFP loses its power the moment the incumbent suspects it is rigged in their favor or impossible to act on. Publish your scoring criteria and apply them. Give every bidder the same information and the same access. Let challengers demonstrate against your real use cases, not a sanitized demo script. The point is not to be neutral for its own sake; it is that a process which behaves like a genuine decision produces quotes the incumbent has to take seriously. If your own service owners walk away impressed by an alternative, that signal reaches the account team faster than any letter you could send. A buyer who has run a fair process holds far more leverage than one who has run a theatrical one, because the alternative is real enough to choose.

Protect the win in the contract

A lower first year number means little if year two erases it. Cap the True Forward uplift, fix the renewal mechanics, and lock the discount into the paper. The leverage you built in the RFP should buy durable terms, not a one time concession. The Competitive Leverage Playbook includes the full RFP to close sequence and a scope template you can reuse.