ServiceNow retired Standard, Pro, Pro Plus, Enterprise, and Enterprise Plus on 9 April 2026 and moved to three AI native tiers. Foundation, Advanced, and Prime change the renewal math for every customer. Read the pillar before your next true up.
On 9 April 2026 ServiceNow replaced its five legacy tiers with three AI native tiers: Foundation, Advanced, and Prime. Now Assist is bundled into all three, autonomous agents are gated to Prime, and a consumption meter sits on top of every tier price. This pillar covers the change, the bundling, the agent gating, the overage math, and the levers.
ServiceNow rebuilt its commercial model around AI in April 2026. The old tiers were named for module depth. The new tiers are named for how much artificial intelligence they let you run. That is a different axis, and it changes which tier a given team actually needs.
This is not a cosmetic rename. It is a repackaging that every customer renegotiates at their next renewal, because the SKUs a contract was written against are being retired. The buyer side task is to map what you own onto the new shape without overbuying the top tier.
On 9 April 2026 ServiceNow replaced its five legacy tiers with three AI native tiers, and set legacy end of sale for 1 July 2026. The five retired tiers were Standard, Pro, Pro Plus, Enterprise, and Enterprise Plus. The ITSM licensing change published by ServiceNow frames the move as a shift from module tiers to capability tiers.
ServiceNow needed a way to price the AI it had been giving away or selling as fragmented add ons. Bundling Now Assist into the base and adding a consumption meter lets it monetize usage as adoption grows. The TechTarget report on the pricing change ties it directly to enterprise return on investment pressure.
Two dates drive planning. The 9 April 2026 launch made the new tiers available. The 1 July 2026 end of sale means any renewal quoted after that point is written on Foundation, Advanced, or Prime. Contracts mid term keep their legacy SKUs until renewal.
Legacy tier to new tier, at a glance
| Legacy tier (retired) | Closest new tier | What to watch |
|---|---|---|
| Standard | Foundation | Base rose to fund bundled Now Assist |
| Pro / Pro Plus | Foundation or Advanced | Confirm which workflows moved up a tier |
| Enterprise | Advanced | Process mining and voice sit here |
| Enterprise Plus | Prime | Only tier with autonomous agents |
Every tier bundles Now Assist, the Moveworks layer, Workflow Data Fabric, and AI Control Tower, and the tiers differ by how much agentic capability they unlock. ServiceNow sets this out in its AI native product tier overview. The move from add on pricing to bundled AI is the core of the repackaging.
Foundation is the entry tier. It covers incident, request, and asset management with the CMDB, Virtual Agent, and Now Assist for generative tasks such as summarization, insight, and data extraction. It is the right floor for teams that want AI assistance but not autonomous execution.
Advanced adds change and problem management, AI voice agents, process mining, on call management, and higher Now Assist allowances. It supports both deterministic and AI agent executed workflows that carry out specific tasks. It suits teams automating defined actions but not replacing whole roles.
Prime contains everything in Advanced and adds fully autonomous AI agents, the Level 1 service desk AI specialist, and the highest assist allocations. It is the only tier that lets you build net new custom AI skills and agents on the platform. It targets role replacement, not task assistance.
The practical read is that the tier name now signals ambition, not module breadth. A team that only automates known tasks does not need the top tier, however attractive the autonomous agent story sounds in a demo. The capability you pay for should match the capability you will run.
Autonomous AI agents sit in Prime only, and that gating is the most consequential design choice in the whole repackaging. The ServiceNow practical guide to AI native licensing confirms that building custom skills and running fully autonomous agents requires the top tier.
Prime unlocks agents that plan and act, not just assist. The headline example is replacing a Level 1 service desk role with an AI specialist that triages, resolves, and escalates. That is a labor substitution pitch, and it is priced accordingly.
The account team will push Prime across the full seat count. In practice, autonomous agents rarely need to run on every user. A common pattern is Foundation or Advanced for the bulk of users and Prime scoped to the population that actually runs agents.
The standard reseller advice is to standardize the whole estate on Prime so every user is agent ready. We disagree. In roughly 6 out of 10 estates we benchmarked in 2025 and 2026, autonomous agents were needed by a small operations team, not the whole company, and full Prime standardization inflated the bill by a third with no added value. The buyer side move is to buy Prime for the agent building and agent running population, hold the rest on Foundation or Advanced, and negotiate a documented right to expand Prime later at a locked rate. Uniform tiering is easy to quote and expensive to own.
Consumption overage stacks as a variable charge on top of the fixed per user tier price, so the annual bill has two moving parts, not one. Each tier includes a bundled pool of assist capacity. Once that pool is spent, top up packs bill at a per unit rate.
Higher tiers ship larger assist pools. The pool is the buffer before overage begins. The buyer side question is not the tier price alone, it is whether the bundled pool covers realistic usage for a full year before the meter starts.
Usage in sub production and development instances draws on the same pool as production. Teams that test agents heavily can burn the pool in non production without noticing. Model dev and test consumption, not just production, before you agree a pool size.
This is a real behavior change from legacy licensing, where a development instance carried no incremental cost. Under the consumption model, every environment that runs assist features draws on one shared meter, so a busy test cycle can move the annual bill on its own.
Seat based forecasting understates the new bill every time, because consumption scales with how much users and agents actually do, not with how many licenses exist. Build an actions based forecast that separates interactive prompts, agentic tasks, and autonomous runs, then add non production load on top.
The two part bill on the new packaging
| Cost component | How it behaves | Buyer side control |
|---|---|---|
| Per user tier price | Fixed by tier and seat count | Right size the tier per population |
| Bundled assist pool | Included, larger at higher tiers | Pin the allowance to modeled usage |
| Overage top up | Variable, per unit past the pool | Cap the unit rate and add rollover |
| Dev / sub production | Draws on the same pool | Model non production before signing |
Source: Redress Compliance advisory engagement file, 2025 to 2026.
The tier price is the sticker. The consumption meter is the engine. Buyers who negotiate only the sticker sign a bill they cannot forecast.
You map current entitlements by listing what each user population actually uses today, then placing that population on the lowest new tier that still covers it. Mapping by seat count alone overbuys. Mapping by workflow keeps the bill honest.
Pull the trailing twelve months of module and feature usage per role. Separate the users who need change and problem management or process mining from the users who only need incident and request. That split decides Foundation versus Advanced.
Identify the small group that will build or run autonomous agents. That group needs Prime. Everyone else does not. The CSM packaging redesign note from ServiceNow shows the same capability gating logic applies across product lines, so the mapping discipline carries beyond ITSM.
The buyer side levers are tier fit, consumption pool size, overage unit rate, and migration price protection, in that order of impact. Discount percentage matters, but on the new packaging the structure matters more than the headline rate.
Refuse the uniform Prime pitch. Scope Prime to the agent population and hold the rest on Foundation or Advanced with a documented right to expand at a locked rate.
Pin the bundled allowance to modeled usage, cap the overage unit rate, and secure rollover so unused capacity is not forfeited. These three terms decide the variable half of the bill.
Because legacy SKUs are being retired, ask for price protection on the transition, a defined mapping of old entitlements to new, and a cap on year over year uplift across the term.
Start the renewal 9 to 12 months out. Early planning gives time to inventory usage, model consumption, and price a blended mix, and it preserves the option to walk. A vendor timeline compressed into the last quarter is a negotiation the vendor controls.
The reset does not weaken your position. A DR 71 buyer side benchmark, a defensible usage inventory, and a modeled consumption forecast give you more leverage on the new packaging than on the old, because so few buyers arrive with the meter already understood.
The most common mistakes are treating the tier price as the whole bill, accepting uniform Prime, and ignoring non production consumption. Each one is avoidable, and each one recurs because the account team quotes the simple version.
Buyers anchor on the per user rate because it is the number on the quote. The consumption meter is where the bill actually moves, so a hard win on the seat rate paired with an open ended overage clause is a false victory.
Standardizing the whole estate on Prime is simple to quote and expensive to own. Most users never touch an autonomous agent, so the top tier is prepaid capability that sits idle. A blended mix is the correct default.
Development and sub production usage draws on the same pool as production, and the ServiceNow ITSM licensing note is explicit that the meter spans environments. A busy test cycle can exhaust the pool with no production user involved.
A renewal opened in the final quarter hands the timeline to the vendor. Nine to twelve months of runway is what makes the inventory, the consumption model, and the walk away option real rather than theoretical.
The tier reset means a multi year ServiceNow contract now carries a variable cost line that did not exist before, so the old practice of locking a fixed per seat rate for three years no longer covers the whole bill. The fixed part is the tier price. The variable part is consumption.
That split changes how a term deal should be structured. A three year commitment on tier seats is still worth negotiating, but it must be paired with terms that govern the consumption meter across the same period, or the protection is only half complete.
The fixed component is the per user tier price for Foundation, Advanced, and Prime seats. Lock it per tier, cap the year over year uplift, and document the blended mix so the vendor cannot quietly shift users up a tier at each anniversary.
The variable component is consumption above the bundled pool. Pin the pool size to modeled usage, cap the overage unit rate for the full term, and secure rollover. Without these, a multi year deal simply fixes the smaller half of the cost while the larger half floats.
Ask how and when consumption is trued up. Annual true ups are easier to forecast than quarterly ones, and a documented review threshold is better than an automatic invoice. The goal is a conversation before a surprise, not a bill after one.
Buyers who treat the term deal as covering only the seat price are the ones most exposed to the meter. The reset rewards those who negotiate both halves of the bill in the same contract.
Because ServiceNow publishes no list pricing, a benchmark against comparable deals is the only way to know whether a quote is fair. Bring independent pricing evidence to the table, and use it to test both the tier rate and the consumption terms against what similar estates actually paid.
ServiceNow replaced its five legacy tiers, Standard, Pro, Pro Plus, Enterprise, and Enterprise Plus, with three AI native tiers on 9 April 2026: Foundation, Advanced, and Prime. Legacy SKUs reach end of sale on 1 July 2026, so every renewal after that date maps onto the new packaging.
The three new ServiceNow tiers are Foundation, Advanced, and Prime. Foundation is the entry tier, Advanced adds agentic workflow execution and higher AI allowances, and Prime is the only tier that includes fully autonomous AI agents and the ability to build custom AI skills.
In most cases yes, because Now Assist AI is bundled into every tier and the entry price rose to fund it. Public list pricing is still not published, but benchmarked deals run roughly $70 to $100 per user for Foundation and $160 to $200 or more per user for Prime, before consumption.
No. Now Assist, the Moveworks layer, Workflow Data Fabric, and AI Control Tower are bundled into every tier from April 2026, rather than sold as separate add ons. The trade off is that a variable consumption charge now sits on top of the tier price.
You need Prime. Autonomous AI agents, the Level 1 service desk AI specialist, and the right to build net new custom AI skills and agents are gated to the Prime tier. Foundation and Advanced can consume assist features but cannot build or run fully autonomous agents.
Each tier includes a bundled pool of assist capacity. When that pool is exhausted, top up packs apply at a per unit rate, and usage in sub production and development instances counts against the same pool. Annual cost now carries a variable component tied to how users and agents behave.
Practically yes for any renewal after 1 July 2026, because the legacy SKUs are no longer sold. You can often negotiate a transition period, price protection, or a phased mapping, but the direction of travel is fixed and should be planned 9 to 12 months out.
The consumption pool size and the overage unit rate are the biggest levers, because the tier price is only half the bill. Pin the included allowance, the per unit overage rate, rollover terms, and a cap before you sign, not after the first true up.
The Foundation, Advanced, and Prime tier map, the Now Assist consumption model, the overage math, and the buyer side levers for the April 2026 repackaging.
Built from the Redress Compliance advisory engagement file. Independent. Buyer side. Written for procurement and IT asset leaders running the next ServiceNow renewal.
Join procurement and IT asset leaders who get our ServiceNow, Oracle, SAP, and Microsoft negotiation briefings. No vendor spin. Unsubscribe anytime.
