Start with the definitional shift, because the vendor will present the move as a simplification rather than a price event. Under the old model, AI capabilities such as Now Assist were add-ons you could scope separately. Under Foundation, Advanced and Prime, AI moves inside the tier, so the tier price carries the AI cost whether the people in that tier use it or not. That is the mechanism that quietly raises the bill. The full landscape is in our 2026 guide to agentic AI ITSM pricing and negotiation.
We model which users belong in Foundation, Advanced or Prime and cap the migration uplift. Book an AI cost control review.
What are Foundation, Advanced and Prime?
They are the three consolidated packaging tiers replacing the four legacy editions. Treat the names as buckets of capability plus an AI allowance, not as a like-for-like rename of your current SKU. The risk in any consolidation is that the new mid or top tier is positioned as the natural home for what you have today, when a lower tier would in fact cover your real usage. The table below is the buyer-side framing, not a price list; ServiceNow pricing varies by deal size, so confirm the exact inclusions and rates against your order form.
| Tier | Position | AI in 2026 | Buyer-side question to ask |
|---|---|---|---|
| Foundation | Entry bundle | Baseline AI allowance bundled | Does most of my base actually need more than this? |
| Advanced | Mid bundle | Larger AI allowance, more capability | Which exact feature forces users up to here, and how many? |
| Prime | Top bundle | Fullest AI allowance and agentic scope | Is Prime serving the whole base to cover a handful of power users? |
Why does the repackaging raise prices?
Two mechanics do the work. First, bundling removes the unbundle: when AI sits inside the tier, you can no longer decline it line by line, so the allowance is priced into every seat in that tier. Second, consolidation sets a new floor: the end-of-sale of legacy SKUs on 1 July 2026 means the migration becomes the reference event ServiceNow uses to reset the baseline. If you let the new tier be chosen for you, the repackaging becomes a price increase wearing the language of simplification.
How do you negotiate the move tier by tier?
Run it as a re-mapping exercise, not a renewal of the status quo. These are the moves that hold the line.
- Segment the base by real capability need. Most estates have a large group that lives in core ITSM, a smaller group that needs the feature that forces a higher tier, and a handful of agentic power users. Price each group to the lowest tier that genuinely serves it rather than tiering the whole base up.
- Separate the AI allowance in the commercial schedule. Even when AI is bundled, ask for the AI component to be itemised so it can be re-priced at the next cycle. An allowance you cannot see is an allowance you cannot reduce. The mechanics sit in how to cap ServiceNow assist consumption before you sign.
- Hold price protection across the migration. Treat the legacy-to-new move as a continuation, not a new purchase, and cap the uplift on the migrated base. The end-of-sale date is the vendor's clock; price protection is yours.
- Secure a downgrade right. If usage data after a year shows Advanced or Prime was over-bought, you need the contractual right to step down at renewal without penalty. Without it, the top tier becomes a one-way door.
What about the agentic layer above the tiers?
Beyond the named tiers, ServiceNow is layering in agentic capability from its Moveworks acquisition, Workflow Data Fabric and the AI Control Tower, much of it metered in assists. The tier sets your entry allowance; consumption sets what you pay beyond it. Negotiate both together, because a low tier with uncapped overage can cost more than a higher tier with a capped pool. The wider pattern and the next wave are covered in ServiceNow agentic AI pricing, the next wave.
Our gated ServiceNow Now Assist Cost Control Guide includes the tier-mapping worksheet and the migration price-protection checklist.
What to do next
Before you accept a tier, segment your base, isolate the feature that forces each upgrade, and put a number on how many seats really need Advanced or Prime. Then negotiate the migration as a continuation with capped uplift and a downgrade right, and itemise the AI allowance so it stays visible. Across ITSM engagements the firm averages a 30% reduction, and on a tier consolidation that reduction comes from right-tiering the base, not from arguing percentage off a bundle you over-bought. When you are ready to run it, the engagement goes through our AI cost control service on fixed fee or gainshare.
Frequently asked questions
- What are ServiceNow Foundation, Advanced and Prime?
- The consolidated 2026 tiers replacing Standard, Pro, Pro Plus and Enterprise, with AI bundled in from April 2026 and legacy SKUs end-of-sale on 1 July 2026. Foundation is entry, Advanced is mid, Prime is the top bundle.
- What should I negotiate when moving tiers?
- The tier you actually need, price protection across the migration, an itemised AI allowance that can be re-priced, and a downgrade right so Prime is not a one-way door.
- Does the new packaging raise my price automatically?
- It can, because bundling AI into the tier prices it into every seat. Counter by mapping each user group to the lowest tier that serves it and capping the migration uplift.
Right-tier the base before you migrate.
We map users to Foundation, Advanced or Prime, cap the uplift, and keep the AI allowance visible. Fixed fee or gainshare.
Book an AI cost control review →