Fifteen to twenty five percent of licensed fulfillers sit unused, paid in full, and lifted by every uplift, so the review that finds them pays for itself before the negotiation starts. 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 twenty five, and module five closes here. Today is shelfware, and I want to open with the arithmetic rather than the definition, because the arithmetic is what makes people act. Fifteen to twenty five percent of the licensed fulfiller count sits as shelfware in the estates we benchmark. Paid in full. And here is the part that matters, it is inside the base that your annual uplift is applied to. So it does not sit still. It gets more expensive every single year, by the exact percentage you negotiated so hard over. Waste in a perpetual licence is a sunk cost you can be philosophical about. Waste in a subscription is an annuity you are paying to the other side. Three checks, homework, and by the end you will have a review you can actually run.
Five objectives. First, define shelfware properly, and by that I mean not just unused seats, because modules, capabilities, tables, connectors, pools, environments, and whole tenants can all be paid for and unused, and every meter in this course has a version of it. Second, run the four pass review, entitled, deployed, used, and valued, where each pass narrows the last and the gap between deployed and used is where your money is. Third, see the multiplier, which is that the uplift applies to a base including your shelfware, so every renewal that skips this pass reprices the waste upward. Fourth, choose the right action, reclaim, redeploy, retire, or renegotiate, because four kinds of finding need four different answers and picking the wrong one wastes the finding entirely. And fifth, time it to the runway, nine to twelve months out, because renewals opened that early absorbed half the realized increase of renewals opened inside sixty days.
Four numbers. Fifteen to twenty five percent, the licensed fulfiller count sitting as shelfware, paid in full and lifted by every uplift applied to the base. Ten to twenty percent, subscribed units unused and never trued down, which is why the true down is described as the largest overlooked saving at renewal, and notice the word overlooked. Half, the realized increase absorbed by renewals opened nine to twelve months out against those opened inside sixty days, and I want to be careful about attributing that correctly, the difference is not negotiation skill, it is time to right size. And every year, which is how often unreviewed waste gets repriced, because a renewal that skips the right sizing pass does not hold the waste flat, it lifts it. The note underneath is the sentence to take away. Waste in a perpetual licence is a sunk cost. Waste in a subscription is an annuity you are paying to the other side.
Guest analyst clip. The moment that changes the conversation about shelfware, in my experience, is never the percentage. You can tell a CIO that twenty percent of their seats are unused and they will nod, and they will file it under things to look at, because twenty percent waste sounds like something every large organisation has and survives. What changes the conversation is the multiplication. I sat with a finance director and we did it on a whiteboard in about four minutes. Unused seats, times the per seat cost, times the uplift, times the remaining years of the term. And she stopped me halfway through and asked me to go back a step, because what she had suddenly seen was that the waste was not a fixed leak, it was a growing one, and it was growing at a rate she had personally approved when she agreed the uplift. That reframing is the whole battle. Nobody funds a project to tidy up licensing. Plenty of people will fund a project that stops a compounding cost. It is the same project. It is just described in the language of the person who has to pay for it, and I would encourage anybody trying to get this work resourced to do that arithmetic on a whiteboard, in front of the person holding the budget, rather than putting the percentage in a slide.
Do the multiplication in front of the person holding the budget. Nobody funds a tidy up, plenty of people fund stopping a compounding cost, and it is the same project. So, where is it hiding.
Seven places, and every one of them is a callback, so this slide is really a summary of the course so far. Fulfiller seats, licensed users below any meaningful activity threshold plus the duplicates across tenants, sessions eleven, twelve, and twenty four. Tier features, paying for a higher tier whose differentiating capabilities nobody used in production, sessions seven, sixteen, and nineteen. Whole modules, a product that arrived in a bundle with no team, no workflow, and no go live date, sessions three and twenty. Custom tables and applications, the ones nobody owns, drawing on your allowance permanently, sessions thirteen and twenty one. Connectors and integrations, deployed during a proof of concept, never removed, priced at renewal, sessions twenty and twenty two. The assist pool, capacity you paid for inside the tier that adoption never reached, sessions eight and twenty three. And environments and tenants, sub production copies and inherited instances nobody retires, session twenty four. Now read the session column as a whole. Every module of this course found the same thing in a different shape, which is exactly why the review is one exercise rather than seven.
So why does it survive, and I want to be clear that none of this is negligence. Nobody is punished for it, because an over provisioned team experiences no friction at all while an under provisioned team files tickets, so the incentive runs in exactly one direction. Removal takes effort and returns nothing locally, because the person who reclaims fifty seats gets no budget back, and the saving lands in a contract they do not own and may never see. It is invisible in the tools people use every day, because every system reports what exists and almost none reports what exists and is not used, and that is a genuinely different query that somebody has to decide to run. The renewal rewards inertia, because renewing the same numbers is a short meeting and changing them is a project that has to start months earlier. And it accumulates from correct decisions, because every single item on the previous slide was reasonable when it was made. Shelfware is a governance gap. It is not a competence problem, and treating it as one is how you make people defensive instead of helpful.
Knowledge check one. Why is twenty percent shelfware in a subscription worse than twenty percent shelfware in a perpetual licence? A, it is not, unused is unused. B, the uplift applies to a base that includes it, so the waste is repriced upward every year. C, because subscriptions cost more per unit. D, because support is bundled into subscriptions. Pause here, and ask what happens to unused seats at the next renewal.
The answer is B. Every percentage point of uplift applies to seats nobody uses, so unreviewed shelfware compounds rather than sitting still, and a renewal that skips the right sizing pass actively reprices your waste upward. Answer A is the intuition most organisations genuinely run on, and it is exactly why this review gets deferred year after year, because unused feels like a static problem and it is not. Answers C and D are about the pricing model rather than the mechanic. And the practical consequence is the one I want you to hold on to. The right sizing pass is not housekeeping you do when there is time. It is the step that decides what the uplift is calculated on, which makes it the most commercially significant thing on your list.
The method, four passes, each narrowing the last. Entitled, what the contract says you own, from the order form and the entitlement export, which is session ten's baseline and it is the easy one. Deployed, what is actually provisioned, switched on, and configured in your instance, and the gap between entitled and deployed is pure unallocated capacity. Used, what has been touched in ninety days by a person or by a scheduled process, and the gap between deployed and used is your shelfware number, the one you take to the table. And valued, what the owning team can say actually produced something, which is the only pass that needs a conversation rather than a query. Now the note, because it is the difference between a review that holds and one that collapses. Pass four is what separates a defensible finding from an attackable one. A finding that says nobody logged in invites an argument about your data. A finding where the owning team has agreed that it produced nothing does not, because there is nobody left to argue with.
Knowledge check two. Your review shows nine hundred entitled, eight hundred and fifty deployed, seven hundred used in ninety days, and owners can name value for six hundred and forty. What is your negotiating number? A, nine hundred, the entitled count is what you pay for. B, around seven hundred, defensible on activity, with the six forty as the internal target. C, six hundred and forty, cut to what has proven value. D, eight hundred and fifty, since deployment is the real commitment. Pause here, and ask which number you can defend and which one guides you.
The answer is B, around seven hundred externally with six forty as your internal target, and the reason is that those two numbers do genuinely different jobs. The activity number is the one you can evidence to a counterparty straight out of your own instance, which makes it very hard to argue with. The value number is the one that tells your own organisation where the next sixty seats are going to come from. You need both and you should not confuse them. Answer C takes an internal working figure into an external conversation, which converts a discussion about data into a discussion about your judgment, and you will lose that one. Answer A concedes the entire finding before you start. And answer D counts provisioning as use, which is the same mistake sessions eleven, twenty, and twenty two each corrected in a different product, and by session twenty five you should be catching it on sight.
Now the arithmetic that explains why this session sits where it does in the course. Right sizing usually gets sold as a saving, and its larger effect is that it changes what the uplift is calculated on, which is worth more than the seats themselves across a term. Four cards. The base is the argument, because a cap on the rate binds the rate and does absolutely nothing about how many units that rate is applied to, and the number of units is the one this review moves. The compounding, because if you reduce the base before the uplift then every future year is calculated on the smaller number, and if you reduce it after then you have paid an increase on waste first. The sequence, right size, then benchmark, then negotiate, because reversing the first two means you are benchmarking a price against a quantity you were about to change. And the timing, nine to twelve months out. Module six opens on the renewal itself, and this is precisely why it opens where it does. The right sizing pass is the last thing that belongs to you alone. Everything after it is a conversation with the other side.
Guest analyst clip. There is a conversation I have had many times and it always follows the same shape. A customer tells me, with some pride, that they have negotiated a hard cap on their annual uplift. Low single digits, written into the contract, and they are pleased with it, and they should be, because that is a real win and plenty of buyers never get it. And then I ask what the cap is applied to. Because a cap is a percentage, and a percentage needs a base, and the base is your entitlement count. So a five percent cap on a base carrying twenty percent shelfware is a beautifully negotiated increase on money you should not be spending in the first place. And the reason I labour this is that the cap feels like the finish line. It is written down, it is enforceable, it survives the account team rotating, everything you want from a clause. What it does not do is protect you from the quantity. I have seen buyers spend an entire renewal cycle fighting over a point and a half of uplift, and win, while carrying two hundred seats that nobody had logged into in a year, and the two hundred seats were worth several times the point and a half. Fix the base first. Then argue about the rate. Both, ideally, but in that order, because only one of those two things is entirely within your control.
A five percent cap on a base carrying twenty percent shelfware is a beautifully negotiated increase on money you should not be spending. Fix the base, then argue about the rate, and note which of those two is entirely within your control. So what do you do with a finding once you have one.
Four findings, four different answers, and matching them correctly is most of the value. Reclaim, for unused seats and orphaned accounts, taken back before the renewal so that the count you carry into it is the count you can defend rather than one you are asking for. Redeploy, for capacity a different team genuinely needs, and this is the cheapest expansion available anywhere in your estate because it never touches an order form at all. Retire, for modules, applications, connectors, and environments that nobody owns, and this one needs a funded owner because switching things off is work that nobody gets rewarded for, which is why it does not happen by itself. Renegotiate, for what you cannot reclaim or retire but can reprice, retier, or restructure, and notice that this is the only one of the four that requires ServiceNow to agree to anything. And then the fifth line, record the ones you keep, because a knowing decision to hold unused capacity for a planned rollout is completely legitimate. An unknowing one is the fifteen to twenty five percent. Write down which is which, and the following year you will know the difference.
Knowledge check three. You find a hundred and twenty unused fulfiller seats eight weeks before your renewal. What is the realistic outcome? A, full reclaim, the data is clear. B, partial at best, because eight weeks is inside the window where a finding becomes a negotiating item rather than an operational fix. C, nothing, findings inside ninety days cannot be used. D, full reclaim plus a credit for prior years. Pause here. This course has now answered this question in four different products.
The answer is B, partial at best. At eight weeks you have no time to reclaim those seats operationally, so the finding arrives as a request inside a negotiation you are already in, which is the weakest possible form it can take. The same hundred and twenty seats found at nine months would simply have been gone, and nobody would have needed to agree to anything. Answer C is too absolute, because a late finding still has real value as a counter and you should absolutely still use it. Answer D asks for retrospective credit on capacity you contracted for, which is not how a subscription works and asking damages your credibility on the things you can win. The lesson is the one sessions fifteen, twenty two, and twenty three each made in their own product. The cost of a finding rises with proximity to a signature date, and that is the single most portable idea in this course.
Module five closes, five sessions on the platform layer, one conclusion. Everything accumulates, seats, tables, transactions, assists, environments, tenants, and nothing in the platform reduces on its own or asks permission to grow. The register is the control, because four separate sessions produced the same answer independently, an inventory with named owners and review dates, and it is unglamorous and it is the entire discipline. Use is the evidence, because entitled is a contract, deployed is a decision, and used is a fact, and only the third one moves a price, and only you can produce it. And early is the multiplier, because nine to twelve months out the same finding is worth roughly twice what it is worth at sixty days, which makes it the highest return habit in this whole course. The platform layer is governed rather than negotiated, and the governance is what makes the negotiation cheap.
Guest analyst clip. I want to end module five with something practical about who runs this review, because that is where it usually dies. It does not work as a procurement exercise, because procurement cannot tell whether a module produced value and will not be believed if they claim it did. It does not work as a platform team exercise either, because the platform team has no reason to care about the contract and is quietly the group most likely to defend keeping capacity, entirely reasonably, because they are the ones who get the ticket when something is missing. What works, and I have watched this succeed and fail on exactly this point, is a joint pass with a named owner and a deadline tied to the renewal date. The platform team produces the usage data, because only they can. Procurement holds the entitlement and the contract, because only they have it. And a single named person owns the finding list and takes it to the business owners for the value pass. Three groups, one list, one deadline. When I see this fail, the failure is almost never analytical. Nobody got the numbers wrong. What happened is that the review was everybody's job, which means it was nobody's, and it slipped until it was eight weeks from the renewal and had turned into a negotiating position instead of a saving.
Three groups, one list, one deadline, and a named owner, because a review that is everybody's job is nobody's. Module six opens next time with the renewal machine itself, the uplift that gets presented as policy, the tier drift that quietly beats it, and the auto renewal clause that triggered silently in seven out of ten contracts we reviewed.
Three sentences. Shelfware sits at fifteen to twenty five percent of the licensed fulfiller count and hides in seven places this course has already visited, from tier features and whole modules through to tables, connectors, pools, environments, and entire tenants. It survives because nobody is punished for it, removal returns nothing to the person doing the work, and every system reports what exists rather than what exists and is unused, which is a different query that nobody runs. And the review runs in four passes, entitled, deployed, used, and valued, and it belongs nine to twelve months before the renewal, because the uplift is applied to a base that includes the waste and renewals opened that early absorbed half the realized increase.
Homework, about an hour, five items. Run the funnel on one product, entitled, deployed, used in ninety days, valued by an owner, and note carefully where your data ran out, because that gap is a finding in itself. Put a percentage on it, your shelfware share against the fifteen to twenty five percent benchmark, and whether you land above or below tells you how urgent the rest of this is. Multiply by your uplift, shelfware times annual uplift times the remaining term, and that figure is what this review is worth before anybody negotiates anything at all, which is the number that gets it funded. Sort the findings into four, reclaim, redeploy, retire, renegotiate, and notice that only the last one needs ServiceNow, which usually comes as a surprise. And check your runway, how many months to your renewal, and if it is under six then the honest answer is that this year's review defends next year's renewal, and that is still worth doing.
Five guides. The license rightsizing playbook has the four pass review in written form, the exports that produce each number, and the sequencing that keeps your cuts defensible. The 2026 cost creep report is where the fifteen to twenty five percent shelfware benchmark comes from, along with the arithmetic showing how every uplift reprices it upward, and it is the one to send to whoever funds this. Fulfiller versus requester licensing explained sits underneath the largest single category of shelfware, with the activity thresholds that make a reclaim defensible. Avoiding true up surprises is the other direction of the same review, because the pass that finds waste also finds exposure and you want both before they do. And the renewal playbook shows where the right sizing pass sits inside the twelve month runway, which is exactly where module six picks up. Next time, the renewal machine. See you there.