They price the credibility of your exit, not the existence of your spreadsheet, and the credible challenger is different for every module. Three knowledge checks along the way, and 3 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 3 times in the session the frame splits and a senior licensing analyst gives the view from inside real ServiceNow negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session thirty two, and today we take the lever that buyers reach for most often and use worst. Competition. And I want to give you the finding up front because it is blunt. Across roughly twenty to thirty ServiceNow renewals and expansions advised between 2024 and 2025, generic we are evaluating alternatives language moved pricing in fewer than one negotiation in five. Four times out of five it did nothing at all. Meanwhile a funded pilot with a named competitor on one specific module moved net pricing fifteen to thirty percent on that scope. Same lever, wildly different outcomes, and the difference is not how firmly you said it. The sentence I would put on the wall is this. They price the credibility of your exit, not the existence of your spreadsheet. Three checks, homework, let's go.
Five objectives. First, stop making generic threats, for the reason we just covered. Second, find the contestable scope, because core ITSM is weak bluff territory and recently upsold modules with shallow adoption are where their stickiness model actually has gaps. Third, name the right challenger, because the credible alternative differs by module and the account team knows precisely which losses happen in the field and which do not. Fourth, fund it or do not raise it, because the sequence only works when you would genuinely execute at the modelled cost, and that truth is what the deal desk reads in your paperwork whether you intend it to or not. And fifth, run both levers at once, because competitive pressure works on unit price while licensing discipline works on unit count, and fulfiller role audits cut licensable counts ten to twenty five percent before any discount conversation even starts.
Four numbers. One in five, how rarely generic evaluation language moved pricing at all. Fifteen to thirty percent, the net pricing movement on contested scope when a funded pilot or a signed statement of work with a named competitor was on the table. Ten to twenty five percent, the cut to licensable counts from fulfiller role audits, achieved entirely before the discount conversation started. And nine to twelve months, which is when competition has to be tabled for it to price in at all, because tabled at sixty days it does not, and that is session thirty arriving in a new costume. The note underneath explains all four. Account teams price platform stickiness into every quote. They know what replacing your workflow automations, your integrations, and your trained fulfillers would cost, in detail, probably better than you do. So a threat that ignores those costs reads as theater, because it is theater, and everybody in the room knows it including you.
Guest analyst clip. I have sat on both sides of this and I want to describe what the generic threat actually looks like from the vendor's chair, because it is not what buyers imagine. The customer says they are evaluating alternatives. And the account team's first move is not fear, it is a series of quiet checks. Has anything changed in the architecture. Has anyone from a competitor been on site. Have the integration requests slowed down. Has the customer asked for their data in an exportable form. Has anybody senior stopped taking meetings. Those checks take about a day, and if the answers all come back no, then the threat is not a threat, it is a mood. And here is the part that costs you. The account team now knows something specific about you, which is that you make claims you are not backing. That does not just neutralise this negotiation, it discounts the next thing you say and the thing after that. Whereas a customer who says nothing at all about competition but arrives with clean usage data and a right sized count is read completely differently, as somebody serious who has done work. If you cannot fund the alternative, the strongest available position is not a weak threat. It is silence, plus evidence.
If you cannot fund the alternative, the strongest position is silence plus evidence, because a threat you cannot back discounts everything you say afterwards. So where can you actually back one.
Leverage starts where their stickiness model is weak, five points. Core ITSM is not it, because it is deeply embedded and expensive to move and they have priced exactly that, so threatening the core is the weakest ground available to you. Recent upsells are, because ITOM, CSM, and HRSD modules with shallow adoption are genuinely contestable, and the reason is simple, the switching cost you would actually pay there is small. Platform apps are the lock, because custom Now Platform builds are the real switching cost, which means their growth rate is your future leverage curve, and it points downward. Adoption data picks the target, so your contestable scope is decided by your own module usage dashboard rather than by any market comparison, and that is session twenty five's review earning its place again. And so the move is surgical. Pick the one module their stickiness model overrates, fund the alternative there, and let the core renewal price against that demonstrated willingness to carve.
The names, module by module, and using the right one matters more than people expect. ITSM at mid complexity, the credible challengers are Atlassian JSM and Freshservice, and the realistic contest is full replacement for sub enterprise tiers. ITSM at large enterprise, BMC Helix and Ivanti, and that contest is partial, strongest as pricing pressure rather than as an actual move. ITOM and monitoring, Datadog, Dynatrace, and BigPanda, and that one is strong because observability stacks overlap heavily and you may already own one. CSM, Salesforce Service Cloud and Zendesk, strong wherever CRM gravity already exists in your organisation. And HRSD, Workday Help and Applaud, moderate, with the HCM suite gravity deciding it. Now the note. Using the right name matters because the account team knows precisely which losses actually happen in the field, so naming a challenger nobody ever loses to signals that you have not done the work, and that costs you more than saying nothing would have.
Knowledge check one. You tell your account team you are evaluating alternatives to ServiceNow across the estate. What happens? A, pricing improves, competition always helps. B, very likely nothing, because a full estate threat against an embedded platform reads as theater. C, they escalate immediately to protect the account. D, the relationship is damaged beyond repair. Pause here, and ask what they know about your switching cost that you have not addressed.
The answer is B, very likely nothing. Generic evaluation language moved pricing in fewer than one negotiation in five, and full estate RFPs against an embedded Now Platform moved almost nothing at all, because the account team has already priced what replacing your automations, integrations, and trained fulfillers would cost. Answer D overstates the harm and I want to be accurate about this, because the real cost is not that you have offended anybody. Account teams are not offended by competitive pressure, they expect it. The cost is that you have spent a card and revealed that you do not know your own switching cost. And the surgical alternative, one contestable module with a funded pilot, moved fifteen to thirty percent on that scope, which is the same lever used properly.
So what makes an alternative real on paper, and the framing is that the deal desk reads your paperwork rather than your tone. Four things. A named platform, specific, and the right one for that module, and public pricing on challengers like Atlassian JSM makes the cost contrast easy to table in writing. A funded pilot, paid, running, with actual people on it, because a pilot with a budget line is the difference between an intention and a plan somebody has already spent money on. A published migration timeline, internal, dated, for the contested scope only, which shows the work has been thought through rather than gestured at. And a modelled cost you would genuinely accept, the number you would actually execute at. Now the note, which is the uncomfortable one. If ServiceNow calls the bluff, then the pilot was not funded enough. That is a hard test and it is the honest one, because this sequence only works when the exit is a decision you would really take.
Knowledge check two. Your CSM adoption is shallow, you already run Salesforce, and your renewal is ten months out. What is the strongest play? A, threaten to move the whole estate unless pricing improves. B, fund a Service Cloud pilot for the CSM scope and table it in writing, then price the core renewal against it. C, run a three vendor RFP across everything. D, say nothing and negotiate on volume. Pause here, and ask which scope you could genuinely carve, and who already has gravity there.
The answer is B, the funded Service Cloud pilot on CSM scope. Three things line up, and they need to line up. CSM is strongly contestable where CRM gravity already exists, shallow adoption means your genuine switching cost is low, and ten months sits inside the window where a funded pilot can actually be built and tabled. And this is not theoretical, because two clients in the advisory file moved CSM scope to Service Cloud, kept core ITSM on ServiceNow, and both reported that the following renewal priced materially better. Answers A and C are the theater versions we have just established move almost nothing. And answer D is the quiet mistake, giving up a lever you demonstrably hold, which is a different error from overplaying one you do not.
What they actually fear losing, and it is not what most buyers aim at. It is not the discount, because a discount is a number the deal desk can approve and move on from, whereas growth in module attach and platform consumption per account is what the entire account plan is built on. A stalled footprint hurts more, because a module footprint that stops expanding, or worse shrinks, damages the expansion narrative in a way that a price concession simply does not. Which is exactly why carving one module works, because it converts an abstract threat into a visible reduction in the thing their plan is measured on. And why shallow adoption is your evidence, because a module nobody uses is one you can credibly stop paying for, and they can see the same usage data that you can, which means you are not asking them to take anything on trust. And then contain platform sprawl to keep leverage, because every custom app on the Now Platform raises tomorrow's switching cost, which makes session twenty one's portfolio discipline a negotiating position as well as a governance one.
Guest analyst clip. The thing I wish more buyers understood is what an account plan looks like on the inside, because it changes what you aim at. An account executive is not primarily measured on protecting your current spend. Your current spend is the ninety eight percent, it is assumed, it is in the forecast, and nobody gets promoted for it. What they are measured on is expansion. More modules, more platform, more consumption, a bigger number next year than this year. That is the story the account plan tells and it is the story that gets reviewed internally. So when a customer says they want a lower price, the account team hears a negotiation, and they have a process for negotiations. When a customer says they are moving one module off the platform, the account team hears something entirely different, which is that the story they have been telling their own management about this account is about to become false. I have watched a modest, well documented plan to move one lightly used module produce more movement than a much larger and more aggressive demand about price, and the reason is not that the module was worth more. It is that one of them threatened a number on a slide that somebody upstairs is going to ask about.
Aim at the expansion narrative rather than at the discount, because one of those is a negotiation they have a process for and the other threatens a slide somebody upstairs will ask about. Now the sequence, because every step here has a lead time.
Six steps compressed into four cards, and the order is the method. One, audit at twelve months, fulfiller and module usage from session twenty five, and count discipline comes first because it cuts licensable counts ten to twenty five percent before any discount is discussed at all. Two, pick the scope and then the name, choosing the contestable module from your own adoption data and then selecting the challenger that is credible for that specific module, and in that order, because picking the competitor first is how you end up naming somebody nobody loses to. Three, fund the pilot at nine months, documenting the migration path and the cost, and tabling the alternative in writing nine months before term end so that it prices in. Four, negotiate then lock, pricing the keep scope against the funded exit on the contest scope, then locking renewal caps and downgrade rights into the order form. And the note. Competitive pressure works on unit price, licensing discipline works on unit count, and running both is what produces the outcome, because either one alone leaves half the bill untouched.
Knowledge check three. You table a funded competitive pilot at sixty days before term end. What does the timing cost you? A, nothing, a funded pilot is credible whenever it arrives. B, most of its value, because competition tabled at sixty days does not price in the way it does at nine to twelve months. C, only the pilot's own cost. D, it becomes more powerful, since the deadline adds pressure. Pause here, and ask who has time to act on it and who does not.
The answer is B, most of its value. At sixty days the deal desk knows perfectly well that you cannot execute a migration before your own term ends, so the alternative reads as a negotiating posture rather than as a plan, however genuinely funded it happens to be. And answer D deserves attention because the logic feels right and it is exactly inverted. The deadline is yours, not theirs. A customer who has to sign in eight weeks is not made stronger by producing a document about a migration that would take nine months. This is session thirty's rule showing up in the competitive lever, and it is why the audit starts at twelve months and the alternative gets tabled at nine.
Four rules for using competition well. Narrow beats broad, because one contestable module with a funded named pilot moved fifteen to thirty percent while a full estate RFP moved almost nothing. Funded beats hypothetical, because a paid pilot moved pricing where evaluation language did not, and the deal desk reads what you spent rather than what you said. Right name beats any name, because the credible challenger is module specific and naming one nobody loses to signals that you have not done the work. And both levers rather than one, because competitive pressure works on unit price while licensing discipline works on unit count, and role audits cut ten to twenty five percent before any discount is on the table. The buyer side move here is surgical rather than theatrical, and every one of those four is available to you without a single bluff.
Guest analyst clip. Should you ever actually switch. I get asked that and the honest answer is sometimes, on edge modules, and almost never on the core. And I want to be careful because this course could leave you with the impression that the goal is always to threaten and never to move, which is not right and is also not sustainable. If you never move, eventually they notice. What I have seen work is a customer who carved one genuinely poorly adopted module, moved it, and did so calmly and without drama. It cost them some effort. It was not free. And what they bought was not just the saving on that module, it was a permanent change in how every subsequent conversation went, because they had demonstrated that carving was a thing they would actually do. Their next two renewals priced better and nobody had to make a threat in either of them. So my advice is to look at your estate and ask whether there is one module where the move is genuinely right on the merits, ignoring leverage entirely. If there is, do it for the merits, and accept the negotiating benefit as a side effect. That is a much stronger position than manufacturing a migration you do not want in order to win an argument, and everybody can tell the difference.
Move something for the merits and take the negotiating benefit as a side effect, because everybody can tell the difference between that and a manufactured migration. Session thirty three takes the negotiation every customer now faces whether they asked for it or not, the tier migration, treated as a contract event rather than as a product update.
Three sentences. Generic evaluation language moved pricing in fewer than one negotiation in five because account teams have already priced your switching cost, while a funded pilot with a named competitor moved fifteen to thirty percent on the contested scope. The credible challenger is module specific, core ITSM is weak bluff territory, and the leverage lives in recently upsold modules with shallow adoption where the switching cost you would actually pay is small. And they fear a stalled expansion narrative more than they fear a discount, competition has to be tabled nine to twelve months out to price in at all, and licensing discipline runs alongside it because role audits cut licensable counts ten to twenty five percent before any discount is discussed.
Homework, about an hour, five items. Rank your modules by adoption, lowest first, because the top of that list is your contestable scope and it comes straight out of session twenty five's review. Name the challenger for each one using the module table, and if you cannot name a credible challenger for a module then that module is simply not your leverage and you should stop treating it as such. Price one exit properly, for your most contestable module, licence cost, migration effort, and timeline, and then ask yourself honestly whether you would execute at that number, because the deal desk will be asking the same question. Count your custom apps, because platform sprawl is tomorrow's switching cost and the growth rate of that number is your leverage curve pointing downward. And check the clock, how many months to term end, because under nine months the competitive lever is largely spent for this cycle and the right move is to plan it properly for the next one.
Five guides. The competitive leverage guide has the module by module challenger table, the funded pilot evidence, and the six step sequence, and it is today's session in written form. The ninety eight percent renewal rate and walk-away credibility explains what walk away credibility even means when both sides know you are almost certainly renewing, and what substitutes for it, which is the honest version of this whole topic. The competitive landscape in 2026 shows where each challenger genuinely competes and where it does not, so the name you table survives contact with the account team. The license rightsizing playbook is the count discipline that runs alongside the competitive lever and produces the adoption data that picks your contestable scope. And why independent advisory beats going direct covers where an outside read on your own credibility is worth having, which is harder to do for yourself than people think. Next time, the tier migration. See you there.