How quiet growth becomes a bill, what ServiceNow measures, and running the conversation when it arrives. 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 fourteen. For three sessions now we have been building counters. Session eleven gave you the fulfiller line, session twelve the audit that fixes it, session thirteen custom tables and the build boundary. Today we look at what happens when none of those counters is tracked, and the answer has a name. The true up. And I want to start with the single most useful reframe in this session, because it changes how you handle the whole conversation. The true up is almost never a decision. Nobody in your organisation sat down and chose to exceed the contract. Consumption grew, quietly, through ordinary use of the platform, by people doing their jobs well, and then it arrived as a bill. It is a tracking failure, not a compliance failure, and understanding that difference matters because it determines both how you talk about it internally and how you argue it externally. Three checks, homework, and by the end you will have a written plan for the week a claim arrives. Let's go.
Five objectives. First, explain the mechanism, why the true up is a tracking failure rather than deliberate overuse, and why that framing changes the conversation with both your own leadership and the vendor. Second, rank the creep, which sources consume units, how visible each one is, and which combination deserves your monitoring attention, and there is a clean answer to that. Third, read the timing, why the bill lands at renewal, what that does to your leverage, and how to break the two conversations apart, which is worth real money. Fourth, answer the letter, the first seven days after a claim arrives, in the order that protects your position, because week one sets the range the settlement lands in. And fifth, settle forward, turning an exposure conversation into contract terms you wanted anyway rather than a one off payment that buys you nothing at all. That last objective is where most buyers leave money, and it is the easiest one to fix.
Four framings. Ten to thirty percent, how far subscription unit consumption rose across a term without anybody monitoring it, in the compliance reviews we led. That is growth nobody authorized, nobody noticed, and nobody could have pointed to a moment where it was decided. All at once, because true ups are calculated against contracted entitlement at renewal, which means a full term of gradual growth lands as one bill rather than as a series of small decisions you could have managed. Low visibility, high risk, the dangerous combination, and custom tables and integrations sit exactly there, because you cannot manage what nothing reports. And twelve weeks, the window in which self monitoring removes both the surprise and the leverage loss, which is the same runway as the baseline from session ten, doing double duty. Now the note underneath is the honest summary of this entire session. The strongest position is a usage baseline reconciled to entitlement before ServiceNow runs the numbers. Everything else we cover today is what to do when that did not happen, which is most of the time. Let's hear it from the defences.
Guest analyst clip. The emotional shape of a true up is worth describing, because it affects decisions badly and nobody warns you about it. The letter arrives, or more often it is a slide in a friendly meeting, and there is a number on it that is much larger than anybody expected. And the first reaction inside the customer, almost universally, is a kind of institutional panic that expresses itself as blame. Somebody must have done something wrong. Who granted these roles. Why did nobody tell us. And I understand it, but it is the worst possible frame, for two reasons. First, it is usually not true, this is ordinary growth and not misconduct, and hunting for a culprit poisons the cooperation you need from the platform team who are about to do all the work. And second, it makes you negotiate defensively. A customer who feels they have been caught out concedes far more than a customer who believes, correctly, that they have a reconcilable difference of interpretation with a supplier. So the first thing I do in these engagements is take the temperature down. This is a normal event, it happens to well run organisations, the number is an opening position and not a verdict, and we are going to work it line by line. That framing alone changes the outcome, because calm buyers reconcile and worried buyers pay.
Calm buyers reconcile, worried buyers pay. And note the practical damage the blame frame does, it poisons cooperation with exactly the platform team whose help you need to run the count. If you take one thing into a true up, take the sentence, this is a normal event that happens to well run organisations. It is true, and it protects the working relationships you are about to lean on heavily. Now, where the growth actually comes from.
Where consumption creeps, four sources, and I want you to read the visibility column as carefully as the risk column. New fulfillers, consuming fulfiller licences, medium visibility, high risk, because teams adopt the platform, roles get granted, and nobody totals it up. Custom tables, consuming platform entitlement, low visibility, high risk, because the allowance is completely invisible in daily work, which is exactly what session thirteen was about. Integrations, consuming activity and records, low visibility, medium risk, because connected systems create metered activity that no human ever sees happen. And self service, consuming subscriber units, medium visibility, medium risk, growing with headcount as portal adoption spreads. Now the note, and it is the mechanism in one sentence. Units accrue as the platform is used. New fulfillers get added, integrations create records, applications consume capacity, all without an explicit licensing choice being made by anyone at any point. There is no moment of decision to point at, which is why blame is the wrong frame and monitoring is the right one.
Now the timing, and this is where a technical problem becomes a commercial one. The calculation is contractual, true ups are measured against contracted entitlement and the natural moment to measure is the renewal, so that is design rather than malice. But look at the consequence. Exposure and renewal arrive together, which means you are negotiating price while holding an unresolved claim, and that is the weakest configuration available to a buyer. Leverage evaporates, because a calm conversation about four hundred seats becomes an urgent one about a signature date, and urgency has never once improved a buyer's terms. And it is the vendor's preference, not sinisterly, just rationally, because settling exposure inside a bigger renewal is easier for them than invoking formal audit clauses, and it is genuinely easier for you too in some ways. But easier is not cheaper. So the move, and it is the practical heart of this slide, separate them deliberately. Insist the exposure question is resolved on its own facts, and then negotiate the renewal. Two conversations rather than one. That separation is worth real money and it is available simply by asking for it early enough.
Knowledge check one. Which combination should get your monitoring attention first? A, high visibility and high risk, because it is the biggest number. B, low visibility and high risk, because nothing reports it and it bills. C, low visibility and low risk, because the unknowns are the danger. Or D, high visibility and low risk, because easy wins build momentum. Pause here, and ask what makes a meter dangerous rather than merely large.
The answer is B, low visibility and high risk. Custom tables sit exactly there, integrations are close behind, and what makes them dangerous is precisely that they consume entitlement while producing no signal that anybody sees in the course of ordinary work. High visibility risks like fulfiller growth, answer A, are genuinely real and genuinely large, but somebody is already looking at them, they show up in headcount conversations and in access reviews. Low risk items, answers C and D, simply do not repay the monitoring effort, and monitoring effort is finite so spending it badly is a real cost. And the rule generalises well beyond ServiceNow, so it is worth keeping. Monitor what is both consequential and silent, because the consequential and noisy already has an audience.
So the claim arrives. The first seven days, four moves, in order. Acknowledge but do not concede, thank them, confirm you will review, commit to a date, and do not accept a number, agree a methodology, or apologise for anything in that first exchange, because early politeness gets remembered as early agreement. Ask what they measured, which counters, which dates, which definitions, and critically which contract version, because a claim you cannot reproduce is a claim you cannot responsibly settle. Run your own count, which is the session twelve audit at speed, and do the cleanup first where it is legitimate, because the count that matters is the one taken after the roles are correct. And reconcile privately, their number against yours, differences itemized, each one traced to a definition or a date, before you go back to them. Now the note, because people worry about this. Cleanup before the count is not gamesmanship. A dormant role removed today was never legitimately billable in the first place, and buyers who cleaned up first reduced claimed exposure by twenty five to forty five percent, which tells you how much of a typical claim is drift rather than usage.
Knowledge check two. A true up claim arrives eight months before your renewal, citing seven hundred excess fulfillers. What is the first substantive move? A, dispute the counters as inaccurate. B, ask what was measured, then run your own count after cleanup. C, offer to settle at half, to close it quickly. Or D, refuse to engage until the renewal negotiation begins. Pause, and note that you have met this pattern twice already, in session five and session twelve.
The answer is B, and by now the reasoning should be familiar. The counters read your own instance and are rarely wrong, so disputing them, answer A, burns credibility you will need for the classification argument that actually wins. Settling at half, answer C, is the impatient answer and it is worse than it looks, because it prices a number nobody has validated and the honest figure is very often well below half once dormant roles and machine accounts come out, so you would be negotiating down from an inflated anchor to a still inflated number and calling it a win. Refusing to engage, answer D, pushes the claim into the renewal, which is exactly where you do not want it, as the timing slide just showed. And I want to point at the eight months in that question, because it is a gift. Eight months is enough time to clean up, count properly, and resolve the exposure entirely separately from the price conversation. A claim that arrives eight months out is the best version of this problem.
What governs the conversation, four documents. The unit definitions, deciding what counts as a fulfiller, a subscriber, a table, and the definition drives compliance, with the version you signed being the one that applies. The order form, setting contracted entitlement per line plus any protections, and the gap is measured against this, so an unclear order form is an expensive one. The verification language, deciding what ServiceNow may examine and how, and most reviews stay commercial so this clause matters mainly when the tone changes, but you want to know what it says before that happens rather than during. And true up timing terms, deciding whether growth prices at renewal rates or at premium mid term rates, which is session four's clause finally doing the work it was written for. And the note is the payoff for everything we did in session four. If your definitions are frozen to a version, half the arguments in a true up disappear before they start, because both sides are counting the same things by the same rules. That clause costs nothing at signature and saves weeks of argument here.
Guest analyst clip. I want to give you a concrete example of what a frozen definition is worth, because it is abstract until you see it bite. Two customers, same year, both facing true up claims of broadly similar size. The first had a definition freeze in their order form, versioned and dated at signature. The second had the standard incorporation by reference, current version applies. Now, in the intervening two years, ServiceNow had revised how certain approval related access was described. Not dramatically, not in bad faith, just the ordinary evolution of a product document. For the first customer that revision was irrelevant, we counted under the version they signed, and the argument never happened. For the second customer, several hundred users who were plainly requesters under the old wording sat ambiguously under the new wording, and we spent about six weeks and a lot of goodwill arguing about it. We won most of it, eventually, but the cost of winning was real, in time, in relationship, and in the concessions we made elsewhere to close it. Same product, same vendor, same growth, and the difference was one sentence written two years earlier by somebody who had read this far into a licensing course. That is why I keep telling people the boring clauses are the expensive ones.
Six weeks and a lot of goodwill, against one sentence written two years earlier. That is the clearest return on a contract clause you will see in this course, and notice the second order cost in that story, the concessions made elsewhere to close the argument. Disputes are never free even when you win them. Now, how to run the conversation itself.
Five rules for running it well. Concede the data, argue the classification, because their counters are accurate and what those counters mean is where the discussion actually lives, and fighting the data loses a fight you never needed to have. Itemize every difference, line by line, each traced to a definition, a date, or a role removed, and the reason is tactical, a single aggregate number cannot be negotiated, it can only be accepted or refused, whereas forty itemized lines can be worked one at a time and most of them will resolve in your favour. Keep it commercial, because most reviews are run by the account team rather than an audit arm, and escalating to legal converts a manageable conversation into a formal one, rarely in your favour. Hold the two conversations apart, resolve the exposure on its facts then negotiate the renewal, and if they genuinely must be joined then join them on your terms and price the joining. And the fifth, which is the one people skip, never pay for the past without buying the future. A payment that changes no term is money with nothing attached to it, and the next slide is what you should attach.
Knowledge check three. You have reconciled the claim from seven hundred seats down to one hundred eighty genuine ones, which is good work. ServiceNow proposes you simply pay for the one hundred eighty. What is the better close? A, pay for the one hundred eighty, the number is now fair. B, convert the one hundred eighty into forward entitlement with the terms you wanted attached. C, push for zero, since the original claim was inflated. Or D, defer the whole thing to the renewal. Pause, and ask what a payment buys you beyond closure.
The answer is B. And I want to be precise about why A is wrong, because A is fair, and fair is seductive. Paying for one hundred eighty seats you genuinely consumed is entirely reasonable. It is also wasteful, because you pay for the past and buy nothing. Those one hundred eighty seats are real and you will keep needing them, so buy them as forward entitlement instead, and attach the things you wanted anyway, the definition freeze, true down rights, a capped uplift, a table allowance increase. Same money, and now it purchases something that pays for years. Answer C mistakes an inflated opening for the absence of any exposure, and pushing for zero after you have reconciled honestly spends the credibility that reconciliation just earned you. And answer D reunites the exposure with the renewal, undoing the separation that made this whole favourable outcome possible in the first place. Never waste a settlement.
So what do you buy with a settlement? Four things. The definitions frozen, versioned and dated in the settlement paper, so that the same argument cannot recur under new wording next term, and you have just seen what that is worth. True down rights, because if growth can be trued up then decline should be trueable down, and the moment you are conceding growth is precisely the moment that argument is most winnable, they are asking you to accept a principle and you are asking for its mirror image. Headroom where you grow, table allowance, subscriber units, whichever counter caused this in the first place, bought now at settlement rates rather than repeating the exercise in two years. And a monitoring commitment, agreeing what you will report and how often, which costs you a quarterly day you should be spending anyway and visibly ends the dispute, which has value with your own leadership as well as with them. And the context for all of it, settlements folded into renewals closed thirty to fifty percent below the opening claim when the buyer brought independent data. What you take instead of the discount matters as much as the discount does. One more clip.
Guest analyst clip. The settlement moment is the single most underused opportunity in enterprise software, and I want to explain why it is so favourable, because once you see the mechanics you will never waste one again. When a vendor has an open exposure claim, their internal position is awkward. The claim is not revenue until it is settled. It sits in a forecast as a maybe, it is being asked about by their management, and the account executive wants it closed and booked far more than they want to win every line of it. That is genuine leverage, and it is temporary, existing only in the window between the claim and the settlement. Now, what most buyers do with that window is try to make the number smaller, which is fine as far as it goes. What sophisticated buyers do is trade. They say, we will close this, at this number, this quarter, and here are the four contract changes that come with it. And here is the thing, those contract changes cost the account team almost nothing this quarter, because clauses do not show up in their number, and they close a claim that does. So you are exchanging something that is cheap for them and valuable to you, which is the definition of a good trade. I have watched customers buy protections in a settlement that they had failed to win in two consecutive renewals.
Protections bought in a settlement that two renewals had failed to win. And notice the mechanism, clauses do not show up in the account team's number and a closed claim does, which is exactly the same asymmetry we found at first signature in session four. Learn to spot that asymmetry, because it recurs everywhere in this relationship. Let's recap.
The true up, in three sentences. It is a tracking failure rather than a decision, consumption rose ten to thirty percent across a term while nobody monitored it, and the bill arrives all at once because it is calculated against entitlement at the renewal. Monitor what is consequential and silent, since custom tables and integrations combine low visibility with high risk, and when the claim comes concede the data while arguing the classification, because their counters are right and their interpretation is what is negotiable. And hold the exposure and the renewal apart, and never pay for the past without buying the future, meaning frozen definitions, true down rights, and headroom where you actually grow. Next session closes module three by going back to the beginning of the story. How to mitigate fulfiller and custom table exposure before any of this happens, which is always cheaper, and always available, and almost never done.
Homework, about an hour. One, map your creep, the four sources against your own estate, which are growing, how fast, and critically which of them anybody currently reports on, because the ones with no reporting are your low visibility high risk lines. Two, measure the term, unit consumption today against consumption at the start of your term, and if that number is above ten percent growth you are simply in the normal range, which is not reassurance, it is a prompt to act. Three, find the verification clause, read what your agreement says ServiceNow may examine and how, which takes about ten minutes and which most people have genuinely never done. Four, rehearse the letter, write out the four steps you would take in week one with names against each, because a plan written calmly is worth several times one written under pressure. And five, list your asks, deciding now, in a quiet room, which four terms you would take instead of a discount if you had to settle tomorrow. Decide that today, not in the meeting.
Further reading, five guides. The true up surprises guide is today's creep table and the self monitoring discipline in written form, with the unit definitions that drive compliance. The true up risks white paper covers where exposure concentrates and what triggers a reconciliation, plus the defence built on your own baseline. The license audit guide shows the review as it actually arrives, the triggers, and the settlement data behind the thirty to fifty percent reduction I quoted. The true up management page is for teams who want the process documented rather than improvised, which matters if this is going to outlive you in the role. And the eight clauses analysis covers true up timing, true down rights, and the definition freeze, which are precisely the terms a settlement should buy you. That is session fourteen. Rehearse your week one, and I will see you in session fifteen to close module three.