The April 2026 repackaging, what Foundation, Advanced, and Prime actually contain, and how to map what you own without overbuying the top. Three knowledge checks along the way, and 2 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. 2 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 six, and module two opens with the biggest commercial event on this platform in years. On the ninth of April twenty twenty six, ServiceNow retired the five tiers its entire installed base was contracted on, Standard, Pro, Pro Plus, Enterprise, and Enterprise Plus, and replaced them with three, Foundation, Advanced, and Prime. Legacy SKUs came off sale on the first of July. Now, ServiceNow describes this as a move to AI native packaging, and that is true as far as it goes. But I want you to hear it the way this course hears every packaging announcement. The SKUs your contract was written against are being retired, which means your contract cannot simply renew, it has to be remapped, which means every customer on this platform is walking into a renegotiation, whether they scheduled one or not. That can be a threat or an opportunity, and the difference is entirely in the preparation. Today, what changed, what each tier actually contains, where the gates are, how the meter stacks underneath the price, and how to map what you own onto the new shape without buying the top tier for people who will never use it. Three checks, homework, let's go.
Five objectives. First, tell the story straight, what was retired on the ninth of April, what replaced it, and what the first of July end of sale forces at your next renewal, because you will need to brief people who have heard three garbled versions of this. Second, read the new axis. The old tiers were named for module depth, the new ones for AI capability, and that is not marketing, it genuinely changes which tier a given team needs. Third, place the gates, what is bundled into every tier and what is Prime only, before a demo makes that decision for you. Fourth, do the overage math, stacking pool, unit rate, and environments into the real per user cost of any quote you receive. And fifth, map without overbuying, current entitlements onto the new shape, populations split across tiers, and the levers named. One sentence carries the whole session. Map what you own onto the new shape without overbuying the top, and price the meter underneath whatever you pick.
Four numbers. Three. Three tiers replace five, retired on the ninth of April, off sale from the first of July. The window where you could simply buy more of what you already have has closed. AI. That is the new axis. The old ladder stepped up in modules, the new one steps up in autonomy, how much the AI is allowed to do on its own. Different axis, different question, because a team that needed lots of modules does not necessarily need lots of autonomy. Fifteen to thirty percent. That is where consumption overage landed, as a share of tier spend, in estates where it had been waved off as a rounding error before the agents and Now Assist went live. Remember session three, the vagueness is load bearing. And six out of ten. In six of ten estates we reviewed under the new packaging, the pitch was a tier above the need, and here is the precise version of that finding, the buyer usually did need Prime, for a small population, and was quoted it for the whole seat count. Hold that distinction, it is worth more than any discount in this module. Before we take the change apart, the view from the renewals where it has already landed.
Guest analyst clip. I have sat in a dozen renewals since the new tiers landed, and I will tell you the pattern that repeats in almost every one. The account team opens with a slide that says something like, good news, you are moving to our simplest packaging ever. And it genuinely is simpler, three tiers instead of five, one decision instead of many. But watch what simplification does commercially. Under the old model, a sophisticated buyer had five price points to arbitrage, they could mix Standard here and Pro there and only step up where the features justified it. Under the new model the account team proposes one tier for the whole estate, because simple, and the tier they propose is almost never Foundation. In one renewal I worked, the opening proposal was Prime for eleven thousand seats. Eleven thousand. When we mapped who would actually invoke an autonomous agent, the honest number was under four hundred, the major incident team and part of the service desk. We closed at Foundation for the estate, Prime for four hundred and fifty, and the difference between the opening proposal and the closing contract was more than the customer's entire previous ServiceNow budget. The repackaging did not create that money. The mapping did. Simple packaging is not the same thing as a simple decision, and the vendor knows the difference even when the slide pretends otherwise.
Eleven thousand seats proposed at Prime, four hundred and fifty needed. That ratio is extreme but the shape is not, it is the same six in ten pattern from the slide, scaled up. And keep her closing line, simple packaging is not the same thing as a simple decision. Three tiers made the menu shorter. The decision, who in your estate needs what level of autonomy, got harder, because the cost of answering it lazily went up. Now, the change itself, precisely.
What changed on the ninth of April, five rows. The tiers, Standard, Pro, Pro Plus, Enterprise, and Enterprise Plus became Foundation, Advanced, and Prime, and the retired five went off sale on the first of July, so there is no staying put, only timing. The axis, and this is the conceptual heart of it, the old tiers were named for module depth, each step bought more features. The new tiers are named for AI capability, each step buys more autonomy. Same ladder shape, completely different question at each rung. The AI line, Now Assist used to be a separate SKU you could simply not buy. Now it is bundled into every tier with a consumption meter on top of every price, which means, session one told you this, every renewal now contains a consumption negotiation. Your contract, written against SKUs that are being retired, which makes the renewal a forced remap, and forced is not necessarily bad, forced means everything is open at once, and we will come back to why that is your moment. And list pricing, unpublished. The benchmarks are the market data now, roughly seventy to one hundred dollars per user for Foundation, one sixty to two hundred or more for Prime, before consumption. Before consumption, always say those two words together with the price.
What is bundled and what is gated. In every tier, Now Assist, the Moveworks layer, Workflow Data Fabric, and AI Control Tower. That is real capability shipping in Foundation, which matters for the mapping later, because the account team's pitch will imply Foundation is the empty tier, and it is not. The pool comes too, every tier carries a bundled assist allocation sized by tier, so the meter is inside every deal now, including deals that never asked for AI. Gated to Prime, two things, fully autonomous agents, the ones that act end to end without a human in the loop, and custom AI skill building. So here is the practical test you will use constantly. If the demo showed an agent acting alone, the demo assumed Prime. Higher tiers also carry bigger pools, part of what a step up buys is simply more metered headroom, which is worth knowing when someone proposes a tier upgrade to solve an overage problem, because sometimes a bigger pool on the lower tier is the cheaper answer to exactly the same math. And to be fair, the bundling cuts both ways. You can no longer decline the AI line, but you no longer pay a separate SKU for it either. The negotiation has moved from whether to how much is in the pool, and that is the negotiation this module trains. First check.
Knowledge check one. Your leadership saw a demo where an AI agent autonomously resolved an incident end to end, no human touched it, and they want that capability. Which tier was the demo assuming, and for whom must you buy it? A, any tier, autonomous agents are bundled everywhere now. B, Prime, and only for the population that will actually run agents. C, Prime, for every licensed user in the estate. Or D, Advanced, agents arrive there next release. Pause. What is gated, and to whom does the gate apply?
The answer is B. Autonomous agents and custom skills are gated to Prime, so A is wrong and D is wishful roadmap thinking that binds nobody, session four taught you what binds. But the gate applies to populations, not estates, and that is the half of the answer that saves the money. Answer C, Prime for everyone, is the expensive default, and it is exactly what six of ten estates were pitched. The demo shows a capability. The quote decides who pays for it. Those are two separate decisions, and the entire discipline of this session is refusing to let the first one make the second one for you. Your leadership can have the agent. The four thousand people who will never invoke it do not need to come along.
The three tiers side by side. Foundation, the pitch is the core workflows with out of the box Now Assist, the AI level is assisted, suggestions, summaries, Virtual Agent, the things that help a human who is still doing the work. The entry pool. Benchmarks around seventy to one hundred dollars per user per month. And the row that matters, who belongs here, most fulfiller populations, most of the time. I want to say that clearly because the sales motion implies otherwise. Advanced, adds depth, more process capability, AI voice, more embedded intelligence, a larger pool, priced between the two, deal dependent. Who belongs, teams whose measured usage, measured, not projected, exhausts what Foundation carries. And Prime, the full AI story, autonomous agents, custom skills, the largest pool, one sixty to two hundred plus. Who belongs, the specific population that runs agents. Not the estate, the population. Now notice what I keep doing with that bottom row, tying every tier to evidence, measured usage, demonstrated need. That is session three's ladder discipline transplanted onto the new ladder, price the tier against usage, and the tier you owe is the lowest one containing the features the record shows you using. The axis changed. The method did not. Second check, and this one is arithmetic.
Knowledge check two. A quote shows one thousand users on Advanced at one hundred twenty dollars. The bundled pool covers sixty thousand assists a year, overage bills at thirty cents per assist, and your own pilot burned ninety thousand assists a year on just one hundred users. What is missing from the one hundred twenty dollars? A, nothing, the pool will cover production use. B, roughly nothing, overage is a rounding error. C, a large overage line, because pilot burn scaled to a thousand users vastly exceeds the pool. Or D, the dev and sub production environments, which have their own separate pool. Pause here and actually scale the pilot numbers.
The answer is C, and the arithmetic is worth doing out loud. Ninety thousand assists on one hundred users is roughly nine hundred assists per user per year. Scale that to a thousand users, even assume the pilot users were your heaviest and cut the intensity in half, you are still around four hundred fifty thousand assists against a pool of sixty thousand. Everything past the pool bills at thirty cents, and I will let you multiply that yourself, it is not a rounding error, it is several times the size of the story the quote told. Answer D is wrong twice, there is no separate pool, dev and sub production draw on the same one, which makes the real burn higher still. And answer B is precisely how overage that was quoted as a rounding error landed at fifteen to thirty percent of tier spend in real estates. The rule is simple and it is yours from session three, price the meter with your own burn data. The pilot you already ran is worth more than any benchmark in this negotiation.
So let's stack the meter properly, four layers. Layer one, the tier price, per user per month, the number on the quote, and typically the only number anyone negotiates. Layer two, the pool, the bundled allocation the tier carries, consumed by everything AI does on your instance, the summaries nobody thinks about included. Layer three, the overage, usage past the pool billed per unit, and here is the asymmetry that matters, the unit rate is negotiable at signature and nearly impossible to negotiate mid overage, when the meter is already running and they can see it. Almost nobody negotiates it at signature, because almost nobody modeled reaching it. Layer four, the environments, dev and sub production drawing the same pool as production, the load test that ate a month of assists, that story is real and it will happen again. Put the four layers together and you get the only number that matters, the real price, tier price plus modeled overage, divided by users. That is what you compare across tiers, and against your legacy deal, and against the account team's simplest packaging ever slide. Now, the mapping.
Mapping what you own onto the new shape, four steps, and notice they are all module one muscles. Step one, inventory the old, every legacy SKU on your order forms with counts, rates, and the features actually exercised, which is your session three inventory read against the retiring catalog. Step two, map each population to the lowest new tier containing the features the record shows them using. Foundation absorbs more of your estate than the account team will suggest, that is not cynicism, it is arithmetic, their proposal defaults everyone to the old tier's nearest equivalent or higher. Step three, split the populations. Tiers apply per population, not per estate. The service desk that runs agents takes Prime, the four hundred approvers do not come along, and yes, mixed tier estates are how the well advised deals are closing. Step four, size the pool on evidence, pilot burn times realistic adoption, per environment, and then negotiate pool size and overage rate with the same energy as the tier price. And the note under the slide is the strategic point, do this mapping before ServiceNow does, because their default remap is a silent price rise wearing a migration. Third check puts it all together.
Knowledge check three. Five thousand licensed users. About two hundred service desk agents would genuinely use autonomous agents, and nobody else needs more than core AI assistance. What is the buyer side map? A, Prime for all five thousand, one tier is simpler to manage. B, Advanced for all five thousand, as a compromise. C, Foundation for four thousand eight hundred and Prime for the two hundred, with pools sized per population. Or D, stay on the legacy SKUs and refuse the migration. Pause. Tiers apply to populations.
The answer is C, the split. Run the benchmark arithmetic on answer A and you will see why this is the money question of the session, the Prime premium over Foundation is roughly a hundred dollars per user per month at the midpoints, times four thousand eight hundred users who will never invoke an agent, that is in the region of a seven figure annual difference, for simplicity. Answer B is the split the difference habit wearing a new tier name, it overpays four thousand eight hundred people and underserves the two hundred who actually needed the agents. And answer D has simply run out of road, the legacy SKUs went off sale on the first of July, so refusing the map does not preserve the status quo, it just means ServiceNow performs the mapping for you later, at a moment with less leverage in it. The population split is how six of ten estates should have answered the pitch they received. Be the estate that answers it that way.
The migration levers, in negotiating order. One, tier fit, the population map, defended with feature evidence. This lever moves the most money, as the check you just did demonstrates. Two, pool size, negotiated on your modeled burn rather than the tier default, because headroom bought now is cheaper than overage discovered later. Three, the overage unit rate, negotiable at signature, nearly impossible mid overage, so cap it while the pen is yours, and push for dev and sub production carved out or separately pooled, you will not always win that one, but you win it exactly never if you do not ask. Four, migration price protection, the remap prices against your current effective rates, and the session four uplift cap survives the transition rather than resetting at it, watch for that reset, it is quiet and it is expensive. And five, timing, which is really a meta lever. The forced remap opens everything at once, every SKU, every count, every clause, and a table where everything is open is precisely where the eight clauses from session four are cheapest to land. The repackaging you did not ask for is also the best contracting moment you will get for years. One more clip on that point, because it deserves a practitioner's voice.
Guest analyst clip. Here is the reframe I give every client who calls me anxious about the tier migration. You are looking at a forced renegotiation and seeing risk, and the risk is real, the default path is a price rise dressed as a product update. But flip the table around for a second. For years you have wanted to fix that uplift language, land swap rights, freeze the definitions, restructure the pool you got talked into. And for years the answer has been, we will address that at the next natural contracting moment, which somehow never quite arrives, because opening a working contract mid term costs leverage. Well, the moment has now been scheduled for you. Everything is open at once, by their choice, not yours. The SKUs are changing, the paper has to be rewritten anyway, and a rewritten contract can be rewritten in either direction. The clients who came out of this repackaging ahead, and some genuinely came out ahead, treated it as the contracting event of the decade and prepared accordingly, population maps, burn models, clause lists, the whole file. The ones who came out behind treated it as an administrative renewal with a new logo on the tiers. Same event, same vendor, opposite outcomes. The difference was never the packaging. It was which side arrived having decided what the event was for.
The contracting event of the decade, or an administrative renewal, same event, and the difference is which side decided what it was for. That is the posture for this whole module. You now have the map, the meter math, and the levers. Sessions seven, eight, and nine go deeper into each, the tier contents feature by feature, the assist pool mechanics, and the agentic layer. Let's close.
The tier reset, in three sentences. On the ninth of April twenty twenty six, ServiceNow replaced five module tiers with three AI capability tiers, bundled Now Assist and the AI stack into all of them, gated autonomous agents to Prime, and took the legacy SKUs off sale from the first of July. The tier price is the visible part and the meter is the moving part, pools by tier, overage per unit, every environment drawing on the same pool, and real estates saw overage land at fifteen to thirty percent of tier spend after it was quoted as a rounding error. And the remap is mandatory but its shape is yours, populations to the lowest evidenced tier, Prime only for the people who run agents, pools sized on measured burn, and the whole thing treated as the contracting moment it actually is. Next session we go inside the tiers feature by feature, and into the migration economics when the forced move lands at your renewal.
Homework, about an hour, and this week you are drafting the map you will eventually negotiate from. One, find your SKUs, list the legacy tiers on your current order forms, anything from the retired five is your migration scope. Two, draft the population map, split your licensed users into candidates, who needs agents, who needs heavy assistance, who needs the core. Rough is fine, evidence comes later. Three, pull the burn, assist consumption per user for your heaviest adopters, from the session five export, that is your pool sizing evidence. Four, price both maps, at the benchmark rates, cost ServiceNow's likely remap, everyone at their old tier's equivalent, against your population map. The gap between those two numbers is your negotiation, write it down, you will want it for module seven. And five, check the timing, note when your renewal forces the migration, and schedule the mapping work two full quarters ahead of it. If your renewal is inside two quarters, move this homework to the top of your actual job.
Further reading, five guides. The twenty twenty six pricing tiers pillar is this session in written form, the change, the bundling, the gating, and the levers. The tier migration guide does the remap arithmetic in detail, with the price protection language for the transition. The consumption and overage guide covers the meter, pool mechanics and the clauses to fix at signature. The Now Assist credit model white paper decodes the credit pricing and the governance, and it is the preparation for module five. And the Standard versus Pro versus Enterprise guide covers the legacy ladder your contract still names, with the feature mapping method the remap reuses. That is session six. Draft your map, price the gap, and I will see you in session seven, inside the tiers.