ServiceNow: the ratchet, the fulfiller count, and containing the platform.

Understand the business model and the renewal behavior explains itself. ServiceNow sells a platform disguised as products: the initial ITSM deal arrives generously discounted, because the deal desk is not pricing the ticketing tool, it is pricing the beachhead. Then the platform does what platforms do. Your teams build workflows on it, integrations grow into it, adjacent modules attach to it, and every quarter of successful adoption converts a little more of your operational muscle into switching cost. By the second renewal, the discount that landed the deal has served its purpose, and the pricing conversation starts reflecting what leaving would actually cost you, which the account team can estimate as well as you can.

None of this is a complaint. It is a well-run playbook, and the correct response is to run yours: know the number, own the count, and contain the sprawl, in that order, starting earlier in the relationship than feels necessary, because on this vendor, leverage is a depreciating asset from the day the first workflow ships.

The number and the count: net ACV per fulfiller, honestly counted

The benchmark metric is net annual contract value per fulfiller for the ITSM core, with the adjacent modules, CSM, HRSD, ITOM, SecOps, benchmarked as their own lines, and your position lands against modelled ServiceNow cohorts normalized for size and module mix. The percentile does its usual work: it tells you whether the renewal quote is the ratchet operating normally or operating optimistically, and what deals shaped like yours actually settled at.

But on ServiceNow the quieter money is usually in the count, because the fulfiller definition is where per-seat deals get relitigated. A fulfiller is, roughly, someone who works tickets rather than merely raising them, and the boundary between fulfiller and requester is exactly the kind of definitional gray zone that drifts expensive over time: the manager who approves two changes a month, the developer who glances at an incident queue, the part-time triager, each classified upward, each priced as a full working seat. The same discipline that governs Workday's worker count applies here: measure actual fulfillment activity from the platform's own usage data, reclassify the population the evidence supports, and nail the definition down in writing at signature, because a count you did not define is a count the vendor will.

Containment: the strategy when leaving is not the leverage

Be honest about the walkaway. Migrating core ITSM off a deeply adopted ServiceNow instance is a multi-year program few organizations will fund over a pricing dispute, and the deal desk knows it, so "we might leave" is theater on this account. What is genuinely credible, and moves renewals, is containment at the margin: the platform keeps what it has earned, and every further inch gets decided on merits.

Attach modules one decision at a time. The platform pitch is that each adjacent module is easier on the Now Platform than anywhere else, and it is often true operationally while being wildly variable commercially. Benchmark each attach as its own deal, priced against the standalone alternatives for that workload, because the modules where credible alternatives exist, and for CSM, HRSD, and parts of the portfolio they genuinely do, are where your negotiating leverage on the whole account actually lives. A bundle discount that buys module sprawl at the cost of account-wide lock-in is usually a bad trade dressed as a good one.

Install the caps while you still hold the pen. The moment of maximum leverage on a platform vendor is at expansion: when ServiceNow wants the next module or the multi-year commit, that is when the renewal cap, the fulfiller definition, the true-down corridor, and protected growth rates go into the paper cheaply. The rider families, in other words, funded by attach you were going to grant anyway. And time the close to the vendor's own pressure: ServiceNow's fiscal year ends in December, and a December signature buys terms a June signature does not.

The renewal, in five moves

The honest close: ServiceNow is usually excellent software run by a disciplined commercial machine, and most customers are right to stay and right to expect the relationship to get more expensive as it deepens. The playbook does not fight that gravity, it prices it: an honest count, a benchmarked rate for every module, caps installed at the moments of leverage, and expansion granted deliberately instead of accreting. The ratchet still turns. It just turns against a customer who counted first, and those customers pay for the platform they use rather than the dependence they showed.