Full narration of the briefing. Click a section heading to jump the player to that moment.
ServiceNow renewals in this cycle carry more structural change than any in the platform's history: three new AI-native tiers, assists metered on consumption, legacy SKUs retired from sale, and renewal quotes arriving 20 to 40 percent above the last term. Against that, the account team will be prepared. The only question is whether you are. Here is the preparation, in five workstreams.
Workstream one. Start with the fulfiller data, because it is where the money hides. In the renewals we benchmark, 12 to 28 percent of fulfiller seats behave as light or read-only users: full-price licenses doing part-time work. Pull twelve months of activity, user by user: who creates and resolves, who merely views, who never logs in at all.
Reclassifying that population before pricing starts typically recovers 15 to 25 percent, and it is the one saving the account team will never propose for you.
Workstream two. Do the tier mapping before ServiceNow does. The April 2026 restructure collapsed five tiers into three, Foundation, Advanced, and Prime, and moved capabilities you may own at Standard or Pro, like Change Management, Problem Management, and Process Mining, up into Advanced or higher, while ITOM and CSM customers lost the Foundation option entirely. Build your own map: every module in production, and the lowest new tier that genuinely contains it.
Buyers who arrive with their own mapping negotiate a translation. Buyers who wait for ServiceNow's mapping are handed an upgrade.
Workstream three. Measure the assists before you commit to them. Now Assist is bundled into every new tier and metered in assists: roughly 25 for a small action, up to 150 for a complex agentic one, with heavy-use teams depleting pools about twelve times faster than light ones. If you are piloting AI features now, instrument everything, because your own consumption curve is the only defensible basis for sizing pools and negotiating overage terms.
A pilot you did not measure becomes a baseline ServiceNow measures for you, and their reading always runs high.
Workstream four. Arm the file. Two documents move ServiceNow pricing. First, independent benchmarks for your size and module mix, because the spread between prepared and unprepared buyers on identical scope is wide and quiet.
Second, a real evaluation of an alternative for some workload: Jira Service Management or BMC Helix on the ITSM side, Salesforce Service Cloud for customer workflows. Nobody migrates a mature ServiceNow estate overnight, and nobody needs to: a documented evaluation with architecture and costs changes the price of staying. A vague threat changes nothing.
Workstream five. Sequence it. Start 180 days out, not at the 90-day quote: usage audit first, tier mapping second, AI baseline third, benchmarks and alternatives fourth, and only then engage. Time the close against ServiceNow's fiscal year end, December 31st, when a prepared buyer meets a seller with a number to hit.
And before any signature, audit the order form for legacy SKUs left on by default, quietly repricing capabilities you already replaced. Preparation in a ServiceNow renewal is not an advantage. In this cycle, it is the whole game.
One last point. At Redress Compliance we prepare and run ServiceNow negotiations for large enterprises on a pure contingency basis. Our fee is 25 percent of what we save you. If we save you nothing, you pay nothing.
Wherever you are in the 180 days, let us take a look. com.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded.
Talk to a ServiceNow negotiator