One document that states what you own, what you use, and what you will defend, and the gap between the first two. 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 ten, and this one closes module two. It is also, in a quiet way, the session the first nine were building towards. Every one of them ended with you holding a piece of evidence. Session two gave you a user file. Session three gave you a product inventory. Session four gave you a clause scorecard. Session five gave you quarterly counter readings, and sessions six through nine gave you a tier map and a consumption model. Today all of it gets folded into one document. The entitlement baseline. What you own, what you actually use, the gap between those two, and the evidence that makes anyone believe you. And I want to be honest about the ambition here, because it sounds administrative and it is not. This document decides whose numbers the renewal happens inside. That is the entire game, and it is settled before anybody talks price. Three checks, homework, and by the end you will have started your own. Let's go.
Five objectives. First, name the four parts, entitlement, consumption, the gap, and the evidence, and understand why a baseline missing any single one of them collapses in a room. Second, source every number, meaning you can point at the document or the counter each figure came from, so that nothing in your baseline is an estimate wearing a fact's clothing. That phrase matters, because estimates dressed as facts are exactly what gets found out under pressure. Third, read the gap, applying two thresholds mechanically, below sixty five percent of entitlement is a rightsizing candidate and below thirty five percent is a hard cut. Fourth, build it in four weeks, with a sequence that does not require anybody to pause their day job. And fifth, use it as a position rather than a report, opening a renewal from your document instead of reacting to theirs. That distinction, position versus report, is the whole difference between knowing things and having leverage.
Four numbers. Twenty to thirty five percent, the shelfware most ServiceNow estates carry, and I want to pair that with a structural observation. Estates grow faster than they shrink. New apps, new fulfillers, new credit packs, new modules all arrive between renewals, and not one of them retires on its own, because outside the renewal window the path to removing volume runs through a sales representative who is paid to keep it on the order form. The renewal is the only moment when removal is procedurally easy. Sixty five and thirty five, the thresholds, applied line by line, and I will walk them properly in a moment. Ninety, the days before renewal that your data pull should happen, twelve weeks rather than four, and the reason is not the analysis, it is that the gaps you find need explaining internally before they need negotiating externally. And one. One document, one owner, one signature, because a baseline nobody signed is a spreadsheet, and a spreadsheet does not survive contact with an account team. Let's hear how this looks from the engagements.
Guest analyst clip. I can usually tell within ten minutes of a first call whether a renewal is going to go well, and the tell is what happens when I ask a simple question. What do you own. Not what do you spend, what do you own. Most people reach for the invoice, which is the wrong document, because an invoice tells you what you paid, not what you are entitled to, and those two drift apart quietly over years. The customers who answer well pull up a single sheet. Product, entitlement, consumption, percentage, one row per line item. And what strikes me about that sheet is how unglamorous it is. There is no methodology in it, no sophistication, it is arithmetic anybody could do. What makes it powerful is simply that it exists, and that somebody put their name at the bottom. Because here is what happens in the room. ServiceNow arrives with their read of your estate, and they always have one, they can see your instance. If you have nothing, the meeting is you reacting to their document, line by line, from behind. If you have a baseline, the meeting inverts. They have to reconcile to you. Same facts, same instance, same numbers underneath, completely different conversation, and the only variable is which side did four weeks of arithmetic beforehand.
They have to reconcile to you. And notice the observation about the invoice, because it is a genuinely common error. An invoice tells you what you paid, not what you are entitled to, and after a few years of amendments and add ons those two documents describe different estates. The baseline is built from the order forms and the counters, never from the billing. Now, the four parts.
Four parts, and each answers one question. Entitlement answers what do we own, exactly, and under which definitions, and it comes from the order forms, the pricing exhibit, and the frozen definition versions from session four. That phrase, under which definitions, is doing real work, because an entitlement counted under one version of the unit definitions is a different entitlement under another. Consumption answers what are we actually using, per meter, and it comes from the four counters in session five plus the assist burn model from session eight. The gap answers where does what we own exceed what we use, and by how much, and it is simple arithmetic with two thresholds applied. And the evidence answers the question nobody asks out loud but everybody is thinking, which is why should I believe the first three. Dated exports, activity records, the quarterly position statements. The note under the slide is the one to keep. A baseline without the fourth part is an opinion. Evidence is what converts your numbers into something an account team argues with rather than politely ignores.
Every number traced to a document, five sources. Fulfiller counts by application scope, and critically, with first and last activity dates for each user, because the activity dates are what make the count arguable in your favour rather than just accurate. A count tells you how many. Activity dates tell you how many matter. Requester and stakeholder counts, split active from dormant, and dormant accounts are the cleanest cut in the entire exercise, both technically and politically, because nobody defends a leaver. Product and scope inventory, which is session three's licensed, live, or leaving list with feature evidence attached for anything tiered. Consumption meters, assist burn by use case with the unit price applied, so it reads as money rather than as credits, plus ITOM units and custom table counts against their allowances. And integration users, every service account with its last activity timestamp from the audit log, because machine credentials sitting on named licences are pure recovery, uncontested, nobody's job at risk. Notice what all five have in common. Every one of them is a number you can pull yourself, this week, without asking anyone's permission.
Knowledge check one. Your entitlement export and your order form disagree on the licensed fulfiller count. What is that? A, a data error, use whichever number is lower. B, a finding to resolve in writing before signing anything. C, normal drift, the instance is always ahead of the paper. Or D, proof of over licensing, claim a refund. Pause here, and ask what an unexplained gap between paper and platform actually means.
The answer is B, a finding. And these mismatches are common, which is exactly why the check exists. Every one of them means one of two things. Either you are paying for entitlement nobody ever provisioned, which is money sitting on the table, or you are consuming beyond what the paper grants, which is exposure sitting on the table. Both matter, they point in opposite directions, and both are dramatically cheaper to resolve before a signature than after one. Answer A picks a number without understanding it, and picking the lower one feels prudent while actually discarding evidence. Answer C normalizes precisely the drift this whole course exists to catch, and I hear it often, usually from people who have stopped looking. And answer D assumes the conclusion before doing the work, which is how you end up making a claim you cannot substantiate. Resolve it, in writing, before the signature.
Reading the gap, four bands. Above ninety percent consumption against entitlement, that is healthy, or tight enough that you should be asking whether growth needs headroom or a cap. Sixty five to ninety, normal slack, not free money but not a finding either, so renew as is and watch the trend across quarters, because a line drifting downward year over year is telling you something. Thirty five to sixty five, a rightsizing candidate, and the honest description of this band is that something was bought for a plan that changed. That happens legitimately all the time. And below thirty five percent, a hard cut, because this line is not in use in any meaningful sense, so it gets terminated, swapped under your swap rights from session four, or traded explicitly for something you want more. Here is how to run it. Apply the thresholds mechanically first, across every line, without exceptions or explanations. Then go and collect the exceptions. A line defended by a real reason survives that conversation, and a line defended by nobody funds the rest of your negotiation. Do it in that order, because doing it the other way round means every line arrives pre defended.
Knowledge check two. A module sits at twenty eight percent consumption, so on the thresholds it is a hard cut, but the owning team insists a big rollout is coming next year. What belongs in the baseline? A, leave it at full entitlement, the team has a plan. B, mark it a hard cut and terminate regardless. C, record the twenty eight percent, the stated plan, and a named owner with a date. Or D, exclude it, because disputed lines weaken the document. Pause, and ask what the baseline is actually for, deciding or recording.
The answer is C, and the reasoning goes to the nature of the document. The baseline records, and the record is what forces the decision later. A plan with a named owner and a date is a completely legitimate defence of an underused line, and you should accept it. But look at what recording it does. If that same line is sitting at twenty eight percent next year with the same plan attached and the same owner's name on it, the argument has already been made and lost, publicly, in a document everyone signed. You do not have to win that fight this year. You just have to write it down. Answer A accepts an unevidenced promise, and promises about next year are the most abundant commodity in enterprise IT. Answer B ignores real intent and will cost you internal credibility you need. And answer D removes exactly the lines the document exists to surface. Disputed lines make a baseline stronger, not weaker, because they show it was built by someone willing to write down inconvenient things.
Four weeks to a signed baseline. Week one, pull. Entitlement from the order forms, then counts, activity dates, consumption, and integration users from the instance. Raw exports only in week one, no interpretation, because interpreting while pulling is how you unconsciously smooth the numbers you do not like. Week two, reconcile, entitlement beside consumption on one sheet, line by line, and the design constraint is that the gap should be visible to anyone in the meeting without explanation. Week three, classify, apply the thresholds and then walk the exceptions with the owning teams, and I will tell you what week three really is. It is a rehearsal. The arguments you hear from your own teams in week three are almost exactly the arguments you will hear from ServiceNow at the renewal, delivered earlier and by friendlier people. And week four, sign. The licence owner signs, evidence attached and dated, circulated to sourcing, the platform team, and finance so nobody is surprised later. Four weeks, starting twelve weeks out, which leaves eight weeks to act on what you found. Let's hear about the sheet itself.
Guest analyst clip. I want to push hard on the one sheet discipline, because it is where most of these exercises quietly fail. What tends to happen is that the analysis gets sophisticated. Somebody builds a model, there are tabs, there are weightings, there is a methodology note. And it is genuinely good work, and it is completely useless in the room, because a document that requires its author to explain it can only be presented by its author, and its author is usually not the person in the negotiation. I ask clients for a sheet a CFO can read cold in ninety seconds. Product, what we own, what we use, the percentage, and a colour. That is it. And the reason is not simplicity for its own sake. It is that a simple sheet transfers. It gets forwarded to the CIO who was not in the meeting, it gets read by the finance business partner who joins late, it goes into the board pack. Complexity does not survive being forwarded. And the moment your position can only live in one person's head, it stops being an institutional position and becomes an individual opinion, which is exactly what an account team is trained to wait out. They know the analyst who built the model will move roles eventually. The sheet is how you outlast that.
Complexity does not survive being forwarded. That is a good test for any document you build in this discipline. And note the last point, about outlasting the person who built it, because it connects to something we saw back in session three, the knowledge that walks out the door when somebody changes role. A signed one page baseline is institutional memory in its cheapest possible form. Which brings us to what makes one defensible.
Five tests. Every number has a source, an export, an order form line, or a counter, named on the sheet, and the rule I would give you is blunt, anything you cannot source you delete rather than defend. One unsourced number found in a meeting contaminates the credibility of every sourced number beside it. It is dated, because a baseline without a date is a claim about no particular moment, and dated it becomes a position at a point in time, and four of them become a trend, which is far more powerful than any single snapshot. It is signed, one owner by name, turning a spreadsheet into an institutional position. It survives internal challenge first, and this is the week three rehearsal, if your own platform team can dismantle your baseline then ServiceNow certainly can, so take the internal beating early while it is free. And finally, it states what you will defend. Not merely what is true, but which lines you intend to hold and which you are willing to trade. That last one is the difference between a report and a position, and most baselines I see stop at true.
Knowledge check three. At renewal, the account team's numbers differ from your baseline. What does having the baseline let you do that a spreadsheet would not? A, prove them wrong outright, since the counters are yours. B, open from your dated, sourced, signed position and make them reconcile to it. C, refuse to discuss their figures at all. Or D, escalate to their management with a discrepancy claim. Pause here, and ask what the baseline is actually for.
The answer is B, and the key word is burden. Without a baseline you spend the meeting explaining why their number is wrong. With one, they spend the meeting explaining why yours is. Same facts, opposite work. Answer A overclaims, and I want to be careful here because it is tempting, but both sides are reading the same instance and their raw counts are usually perfectly accurate. What differs is the classification underneath, which is an argument about interpretation rather than about data. Answer C refuses information you actually want, their read tells you what they will price. And answer D escalates before the substance has been worked, which spends a relationship card on a problem that has not been diagnosed. So the win here is not proving anyone wrong. It is deciding whose document the conversation happens inside, and that is decided weeks before the meeting.
So what does the baseline change at the table, four things. It sets the opening, because whoever presents the reconciled position first anchors the conversation, which has been true since session one, and the baseline is simply the artifact that lets you go first. It funds the trades, because the hard cuts are currency, and lines below thirty five percent get terminated, swapped, or explicitly traded for the clause set from session four, which means your shelfware pays for your uplift cap. It prices the migration, because the tier map from session seven sits directly on top of the baseline, and you genuinely cannot map populations you have not counted. And it survives the year, refreshed quarterly from the session five rhythm, so your next renewal starts from a maintained document rather than from a panic. That is module two complete. One more clip, and then we close it out.
Guest analyst clip. There is a moment in a renewal I have come to watch for, and it happens in the first fifteen minutes, long before price. It is the moment where it becomes clear whose numbers the meeting is going to run on. Usually it is decided by something small. Somebody opens a laptop and shares a screen. Whoever shares first, with something credible on it, sets the frame, and everything afterwards is measured against that frame. I sat in a renewal where the customer opened with their baseline, one page, signed, dated three weeks earlier. The account executive's first response was not to argue. It was to ask for a copy. And that request, which sounds like a courtesy, is actually the whole negotiation resolving, because from that point forward their proposal had to explain itself in the customer's terms. Every line they wanted to add had to be justified against a document that already said what the customer used. Contrast that with the meetings where the customer has nothing. The vendor shares first, and now every reduction the customer wants has to be argued for individually, from behind, against a document built by someone whose incentives point the other way. It is the same estate. It is the same money. The only difference is who brought a page.
The only difference is who brought a page. That is module two's closing thought, and it is worth sitting with because it is unusually cheap advice. Not cleverness, not leverage you have to manufacture, not a tactic. A page, built from numbers you already own, signed by someone with a name. Let's recap.
The baseline, in three sentences. It has four parts, entitlement, consumption, the gap, and the evidence, and any one of them missing turns it from a position into an opinion. Read the gap mechanically first, below sixty five percent of entitlement is a rightsizing candidate and below thirty five percent is a hard cut, then let real plans with named owners and dates defend the exceptions. And four weeks of work, none of it requiring the vendor, produces a dated and signed document that decides whose numbers the renewal happens inside. That closes module two. Next session opens module three, and module three is the signature topic of this entire platform, the fulfiller problem. We start with where the line between fulfiller and requester actually sits, and with the uncomfortable fact underneath the whole thing, which is that you count activity and ServiceNow counts roles.
Homework, about an hour, and this week you start the real document. One, start the sheet, one row per order form line, product, entitlement, consumption, percentage, and leave the blanks visible rather than guessing, because a visible blank is a task and a guess is a liability. Two, apply the thresholds, mark every line into the four bands, and count how many fall into the bottom two, because that count is the size of your opportunity. Three, reconcile one line, take your largest product and check the export against the order form, and note any mismatch as a finding. Four, list the integration users with their last activity dates, marking the ones sitting on named licences. And five, name the owner, decide who signs this document. And if the honest answer to that last one is nobody, then that is the finding that matters more than any number on the sheet, and it is the one to take to your leadership this week.
Further reading, five guides. The rightsizing playbook is today's baseline and thresholds as a full twelve week workflow, with the data pull list and the cuts that survive a CFO review, and it is the single most practical companion to this session. The rightsizing tool gives you a working sheet so you are not inventing the format. The true up white paper shows what an unmaintained baseline turns into. The renewal negotiation playbook is what happens after the baseline exists, which module six builds properly. And the license types guide sets up module three, the classification rules behind what is almost certainly the largest line in your baseline. That is session ten, and that is module two complete. Start your sheet, name your owner, and I will see you in session eleven where we take the fulfiller line apart properly.