The anchor line: the active roster, the tier mix, and the three mechanisms that make renewals spike by design. 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 sixteen, and module four opens here. For three modules we have been building general discipline, the meters, the paper, the fulfiller line, the audit. Now we go product by product through the estate, because each one has its own counting unit and its own version of the same problems. And we start with ITSM, for the obvious reason. It is the largest single line in most estates, and it is the reference price the rest of the catalog gets sold against, which means the terms you set here leak into everything else you buy. Now, a lot of today will feel familiar, and that is deliberate, because ITSM is where the module three discipline gets pointed at your biggest number. But there are three things here that are specific to this product, the roster, the tier test, and the reason renewals on this line spike by design rather than by accident. Three checks, homework, let's go.
Five objectives. First, establish the roster, separating the true active fulfiller count from the licensed seat count, and understanding why that gap is pure waste rather than useful coverage. Second, apply the tier test, with a concrete buyer test for each step of the ladder so it gets climbed on measured use rather than on capability that merely sounds useful in a demo. Third, explain the spike, the three mechanisms that make ITSM renewals reset high by design and what each contributes, because you cannot answer a mechanism you have not named. Fourth, land the protections, the uplift cap, mid term additions at base discount, and anniversary alignment, one for each mechanism. And fifth, bridge the packaging, reading a legacy tier contract against the twenty twenty six model, which matters because most estates are still holding paper that names tiers ServiceNow no longer sells.
Four numbers, three leaks. Fifteen to thirty percent, how far active fulfiller counts ran below licensed seats once dormant and duplicate accounts came out. And I want to attach that immediately to the fourth number, free, requesters who only raise tickets cost nothing. Put those two together and you get the sentence that matters. Because requesters are free, every seat in that fifteen to thirty percent gap is pure waste rather than coverage. There is no safety argument for it, no upside case, no scenario where carrying it helps you, because the people it would supposedly cover already have free access. Twenty to forty percent, of top tier fulfillers using only mid tier capabilities and paying the step anyway, which is the second leak and it runs deep. And eighteen to thirty five percent, how far renewals reset above the prior term where no uplift cap was written, and notice the phrasing there, the spike is a mechanism rather than a surprise. One more line before we dig in. A blended estate, most agents on the entry tier with a smaller group above, beats a flat top tier block in almost every benchmark we have run. Let's hear that from the reviews.
Guest analyst clip. ITSM is where I start every engagement, and not because it is the most interesting product, it rarely is. I start there because it is the anchor, and I mean that in the negotiating sense as well as the commercial one. Two things follow from being the anchor. The first is arithmetic. It is usually the biggest line, so a ten percent error there outweighs a fifty percent error almost anywhere else, and I meet a lot of teams who have spent months optimising a small module while the large one drifted. The second is subtler and more important. The ITSM deal sets the reference price for everything after it. When your account team quotes you HRSD or CSM or SecOps, the shape of that quote, the discount level, the uplift, the terms, is anchored on what you accepted for ITSM. So a weak ITSM contract does not just cost you on ITSM. It quietly sets the terms for every expansion conversation for the next several years, because nobody re opens the commercial framework for a smaller product. That is why I tell clients to spend disproportionate effort on this one line. You are not just buying incident management. You are setting the precedent your whole platform relationship gets priced against.
You are setting the precedent your whole platform relationship gets priced against. That is why module four starts here rather than anywhere else, and it is worth carrying into how you resource this. If you have one person who can go deep on one product, put them on ITSM, because the terms travel. Now, the roster.
The first number to get right. Active fulfillers, not licensed seats, meaning the people genuinely working records, cleanly separated from the requester population. Dormant and duplicate accounts, which when removed dropped the true count fifteen to thirty percent below the licensed seats, and that is module three's audit pointed at your largest line. The gap is waste rather than safety, and I want to labour this because the instinct to hold headroom is strong and normally sensible. Here it is not, because requesters cost nothing, so an oversized fulfiller count buys you no coverage whatsoever. If someone unexpectedly needs to raise a ticket, they already can, for free. Sort by application scope, so fulfiller counts per scope with first and last activity dates, which lets the roster be defended team by team instead of as one aggregate number somebody can wave away. And then the discipline, never quote a seat count again, quote the roster. Every subsequent conversation, tier mix, renewal, expansion, prices off this number, which is exactly why it has to be right before anything else begins.
The tier ladder and the buyer test on each step. Entry tier, incident, problem, change, the service management core, and the test is that this is enough for core service desks and for most agents in most estates. Middle tier, predictive intelligence and analytics, and the test is measured active use of the analytics, not their availability, which is a sharper distinction than it sounds. Top tier, advanced AI and automation, and the test is that the automation programme is actually funded and staffed, because an unfunded automation ambition is a roadmap rather than a requirement. And the AI layer, generative AI on top of ITSM, sized against measured consumption, and since April twenty twenty six bundled with a meter above it, which is module two. Now notice what every one of those tests has in common. Each asks for evidence of use rather than evidence of intent. That is the entire method, and it is why twenty to forty percent of top tier fulfillers were found using only middle tier capabilities. Nobody lied to them. They were sold capability, they accepted it, and nobody ever went back and checked whether it got used.
Knowledge check one. You license two thousand ITSM fulfillers. Cleanup shows fifteen hundred active. And of those fifteen hundred, four hundred sit on the top tier but use only analytics. What are the findings? A, five hundred excess seats only, the tier is a separate question for later. B, five hundred excess seats, and four hundred fulfillers one tier too high. C, four hundred tier misfits only, because the five hundred will be reabsorbed by growth. Or D, nothing yet, both need vendor confirmation first. Pause here.
The answer is B, both, and the point of the question is that these are independent leaks that multiply against each other. Five hundred excess seats is your fifteen to thirty percent gap. Four hundred misfits is your twenty to forty percent tier leak. This estate is carrying both simultaneously, which is entirely typical. Answer A is the sequencing error, treating tier as a later question, and it matters because if you fix the count first and cap the price without fixing the tier, you have locked in the wrong mix for the term. Answer C is the argument you will hear from your own colleagues, growth will absorb it, and I want you to recognise it because it is how excess quietly becomes permanent, growth absorbs it, then grows past it, and the baseline never resets. And answer D waits for the counterparty to confirm your own instance data, handing them the opening number, which sessions five and fourteen both warned about.
Now, why renewals spike, and I want to be precise because this is where buyers feel wronged and the feeling is not quite right. Three mechanisms. The discounted first term, where the initial deal is priced to win against a list price you never actually pay, which means the baseline looks generous and the second term has room to rise toward list. The uncapped uplift, no named ceiling on the annual increase applied to the whole base, and that alone produces resets of eighteen to thirty five percent above the prior term. And mid term additions at list, where modules and seats added between renewals price outside the original discount, so growth you did not negotiate arrives at the worst available rate. Read the note under the table, because it is the professional attitude to hold. None of this is irregular and none of it requires bad faith. It is a designed commercial pattern, entirely visible in advance, which is exactly why it is answered with three specific contract terms rather than with indignation. Indignation is not a negotiating position. Terms are.
Knowledge check two. Mid term you need one hundred fifty more fulfillers, real growth, the business expanded. Your contract is silent on mid term pricing. What rate applies, and what is the fix? A, your original discount, because it is the same contract. B, list, and the fix is holding mid term additions to the base discount. C, renewal rates, since the renewal is the reference point. Or D, whatever you negotiate at the time, because there is no structural fix. Pause, and ask what silence buys the seller.
The answer is B, list, and the fix is one sentence in the order form. Silence favours the seller, exactly as in session four, and the mechanism is worth restating. Additions between renewals price at list unless the paper says otherwise, and mid term you have no leverage at all, because the need is real, it is visible to them, and there is no competing moment. Answer A assumes the discount travels with the agreement, and it does travel, but only to the volumes somebody contracted. Volumes nobody contracted have no discount attached to them. Answer C invents a reference point that does not exist. And answer D is the defeatist reading, no structural fix, when this is a term that gets granted routinely at signature because it costs the deal team nothing in the quarter they care about. Same lesson as always. Write the growth down before you need it, while it is still free to write.
Three protections, one per mechanism, and I want you to ask for all three together because each alone leaves a route open for the other two. A named uplift cap, a specific ceiling on the annual increase in low single digits, written into the order form, which answers the eighteen to thirty five percent reset. Mid term at base discount, so additions between renewals price at the same discount as the original deal and growth does not arrive at list merely for arriving early. Anniversary alignment, so module and seat additions align to the renewal date, nothing prices in isolation, and the whole estate negotiates together. And then the fourth card, which is not a protection but a warning. All three protect a base. If your base is fifteen to thirty percent too large, you have just protected the wrong number extremely effectively, and you will pay a capped, predictable, well governed price for seats nobody uses, every year, for the term. So the sequence is not negotiable. Clean the roster first, then cap what remains. Let's hear how that ordering plays out in practice.
Guest analyst clip. The sequencing mistake is one I have watched cost real money, and it is made by capable procurement teams, which is what makes it worth describing. Here is how it happens. The renewal is approaching, procurement engages properly, and they do a genuinely good job on the commercial terms. They win a cap on the uplift, they get mid term protection, maybe they improve the discount. Everyone is pleased, and rightly, those are hard terms to win. But nobody cleaned the roster first, because that is IT's data and it was not on the procurement checklist. So now you have locked in excellent protections around a seat count that is a quarter too big, and here is the cruel part, the protections make it harder to fix. A capped, well structured multi year agreement is a stable thing, and stable things are difficult to reopen. You have effectively converted a fixable problem into a contractual one. Whereas the team that cleans first and negotiates second gets the same terms on a smaller number, and the difference compounds for the whole term. So when I am asked what the single most important sequencing rule is in software negotiation, it is this one. Facts before terms. Always. Terms lock in whatever facts you bring them.
Facts before terms, because terms lock in whatever facts you bring them. And notice the organisational trap underneath that story, the roster is IT's data and the negotiation is procurement's job, so the cleanup falls in the gap between two competent functions. That gap is where this entire course lives, honestly. Now, the packaging bridge.
Reading legacy tier paper against the twenty twenty six model, five points. Most contracts still name the old ladder, because the legacy tiers were retired on the ninth of April and off sale from the first of July, but signed paper naming them governs until it is renewed. So you hold two maps at once, the tier your contract names and the tier you will be mapped to, and session seven's entitlement map is where those two get reconciled in writing rather than in somebody's head. The discipline transfers intact, roster first, tier on evidence, cap the uplift, because the names on the ladder changed and the buyer tests did not. The meter is the new variable, since the AI layer that used to price as a separate line now sits inside the packaging with usage metering above it, which is module two's arithmetic. And a right sized baseline still wins under either packaging, because a clean count tied to the renewal date remains the strongest lever, and ServiceNow negotiates hardest on expansion. Which means the buyer who controls the count and caps the uplift controls the deal, in either world.
Knowledge check three. Your contract names the legacy tiers and renews in nine months. What should you do about the tier mix now? A, nothing, since the tiers are being retired so the analysis is obsolete. B, run the tier test now, because the evidence drives the mapping to the new tiers. C, wait for ServiceNow to propose the mapping, then react to it. Or D, move everyone to the top tier to avoid a migration later. Pause, and ask what the remap actually prices against.
The answer is B, run the test now. The remap prices against demonstrated capability use, so your tier evidence is the input to the mapping rather than something the retirement makes irrelevant, and answer A gets that exactly backwards, discarding the evidence the migration will be argued with. Answer C is session seven arriving late, and you know the shape of it by now, a proposal exists because somebody already mapped your estate and it was not you. And answer D is uniform Prime wearing a different hat, buying the top tier for a population that demonstrably never used the middle one, which the benchmarks price at roughly a third again on top of the structural uplift. The retirement of the old ladder does not retire your usage data. Your usage data is the thing that survives every repackaging, which is precisely why it is worth maintaining.
So, the four ITSM levers in order, and the order genuinely matters because each is worth more once the one above it is done. One, the cleaned roster, active fulfillers only, by scope, with activity dates, and everything prices off this so it comes first and nothing waits for it. Two, the tier mix, each population on the lowest tier its measured use supports, because a blended estate beats a flat block in almost every benchmark. Three, the uplift cap, applied to the corrected base, in writing, with a named ceiling, and worth more than any first year discount across a three year term. And four, growth terms, mid term at base discount and anniversary alignment, so expansion prices predictably instead of arriving at list. Four levers, in that sequence, on your largest line. Next session the unit changes completely. ITOM does not count people at all, it counts managed configuration items, and the count grows without anybody being hired, which makes it a genuinely different problem.
Guest analyst clip. I want to make the case for the blended estate, because it meets resistance and the resistance is usually administrative rather than commercial. What people say is, managing multiple tiers is complicated, everyone on one tier is simpler, and simplicity has value. And that is true, simplicity does have value. But let us price the simplicity, because in the estates I benchmark it is one of the most expensive conveniences in enterprise software. Take a thousand fulfillers where two hundred genuinely need the higher tier. Putting the other eight hundred up there too, for administrative tidiness, costs you the tier delta on eight hundred people, every month, for the term, and then the uplift compounds on it annually. That is not a rounding error, it is frequently a seven figure decision over a contract term. Meanwhile the actual administrative burden is a field on a user record and a quarterly review, which is roughly a day a year of somebody's attention. So when the flat estate is proposed, and it usually is proposed by somebody sincere who is trying to reduce complexity, my advice is not to argue about principle. Just put both numbers on one slide, the cost of the flat estate and the cost of the blended one, and let the difference make the argument. It always does.
Price the simplicity, then let the difference make the argument. That technique generalises across this entire course, incidentally. Almost every expensive default in ServiceNow licensing is defended on grounds of simplicity or safety, and almost none of those defences survive somebody putting two numbers on one slide. Let's recap.
ITSM, in three sentences. The roster is the first number, because active fulfillers ran fifteen to thirty percent below licensed seats once dormant and duplicate accounts came out, and since requesters are free that entire gap is waste rather than coverage. The tier ladder is climbed on measured use rather than availability, and twenty to forty percent of top tier fulfillers were using only middle tier capabilities while paying the step anyway. And renewals reset eighteen to thirty five percent high by design through three mechanisms, answered by three specific terms, all of which protect a base that has to be cleaned first, because terms lock in whatever facts you bring them. Next session, ITOM, where the unit stops being people entirely. Managed configuration items, discovery schedules that scan wider than anybody intended, and a count that inflates through autoscaling groups and short lived containers while your headcount stays perfectly flat.
Homework, about an hour, and this week it is your biggest line. One, build the roster, active ITSM fulfillers by application scope with first and last activity dates, against your licensed seat count, producing one number and one gap. Two, test the tiers, and for every fulfiller above the entry tier find the evidence of the capability that justifies the step, treating no evidence as a finding rather than as an absence. Three, find the uplift language, read your ITSM renewal terms, note whether a named cap exists, and compound it across your remaining term either way, because seeing the compounded number is what makes people act. Four, check mid term pricing, does your paper hold additions to the base discount, and if it is silent, price a hundred hypothetical seats at list so you can see exactly what that silence costs. And five, name your tiers, writing down which tier your contract names and which twenty twenty six tier you expect to be mapped to. That pair is your session seven entitlement map, started.
Further reading, five guides. The ITSM pricing guide is today's session in written form, the roster, the tier tests, the three renewal mechanisms, and the benchmark data behind every number I quoted. The Standard versus Pro versus Enterprise guide covers the legacy ladder your contract probably still names, with the feature evidence method for the tier test. The annual uplift guide covers the cap that answers the eighteen to thirty five percent reset. The renewal negotiation playbook shows how a cleaned roster and a corrected tier mix become an actual negotiating position, which module six builds out fully. And the pricing tiers pillar covers the packaging your legacy paper will be mapped onto, with the meter that now sits above it. That is session sixteen. Build your roster, and I will see you in session seventeen for ITOM.