How we sourced this: every figure below names where it comes from, with the date it was published or checked. If we could not trace a number to a named source, we left it out and listed it under "What we could not verify".
The short answer
ServiceNow pricing is not published. The ServiceNow ITSM pricing page lists three packages (Foundation, Advanced and Prime) with a "Get Custom Quote" button and no prices (ServiceNow, checked 25 Sep 2026). The best public benchmark comes from Vendr: across 109 ServiceNow purchases, the median buyer pays $129,871 a year (Vendr, updated Feb 2026).
What moves your number: the package tier, how many paid users you license, which products you add beyond ITSM, how much AI you consume, and the terms you negotiate at renewal. Below, we take each in turn, then give you a framework to compare staying with switching.
What we could not verify
- An official per-user price. ServiceNow, Vendr and the US General Services Administration (GSA) publish no per-fulfiller list price. Per-user monthly figures that appear in other pricing articles have no traceable source, so we do not repeat them.
- Assist allotments and overage rates. ServiceNow has not published how many AI "assists" each tier includes, how many a given action consumes, or what top-up packs cost. A June 2026 ServiceNow Community guide says the same (ServiceNow Community, 29 Jun 2026).
- An official end-of-sale notice for legacy packages. The 1 July 2026 date comes from partner and community sources, not from a ServiceNow press release.
- Prices for Foundation, Advanced or Prime. No public source gives them.
Foundation vs Advanced vs Prime: the ServiceNow pricing model after 9 April 2026
On 9 April 2026, ServiceNow repackaged its products so that AI is included rather than sold separately. In its words: "AI, data, security, and governance are now in every ServiceNow offering — not a separate purchase" (ServiceNow newsroom, 9 Apr 2026).
For ITSM, that produced three packages, with Prime labelled "Recommended" on the vendor's page:
| Package | What it includes (per servicenow.com, checked 25 Sep 2026) |
|---|---|
| ITSM Foundation | Service Catalog and Request Management, Incident Management, Asset Management and CMDB, Virtual Agent, Workflow Data Fabric, Service Graph Connectors for end-user computers, Now Assist and Platform AI Foundation, Moveworks for ITSM Foundation |
| ITSM Advanced | Everything in Foundation, plus Change Management, Problem Management, Major Incident Management, On-Call Management, AI Voice Agents, Platform Analytics Advanced, Process Mining, Now Assist and Platform AI Advanced, Moveworks for ITSM Advanced |
| ITSM Prime | Everything in Advanced, plus L1 Service Desk AI Specialist, AI Agents for ITSM, AI Agent for Digital End-User Experience (DEX), DevOps Change Velocity, Digital Product Release, Now Assist and Platform AI Prime, Moveworks for ITSM Prime |
No prices are shown for any tier (ServiceNow ITSM pricing page).
The practical point for buyers: Change and Problem Management sit in Advanced, not Foundation. A team that runs formal change control cannot choose the entry package without losing that capability.
What happens to legacy packages
Before April 2026, ServiceNow sold five legacy tiers: Standard, Pro, Pro Plus, Enterprise and Enterprise Plus (The Cloud People, 26 Jun 2026). Two points matter here:
- End of sale. Partner and community sources report that legacy SKUs reached end of sale on 1 July 2026, after which "legacy pricing cannot be reinstated" (The Cloud People, 26 Jun 2026; ServiceNow Community, 29 Jun 2026). We found no ServiceNow press release that states this date.
- What triggers the move. According to The Cloud People, existing customers stay on their current SKUs "until a triggering event moves them onto the new model. That trigger is a renewal, a new subscription, add-on, or any other contractual change" (26 Jun 2026).
In practice, your next renewal is likely to be when you are mapped to a new tier. The same article warns that capabilities moved between tiers, and advises you to "audit which processes, modules, and roles are genuinely in use, before anyone presents you a mapping."
ServiceNow license types: fulfillers, requesters, approvers and assists
ServiceNow licenses people by role, and it meters AI usage separately in "assists". Your contract's user definitions are what count. The summary below comes from a ServiceNow Community explainer, not from ServiceNow's contract terms (ServiceNow Community):
| Role | What the user can do | Paid? (per the Community explainer) |
|---|---|---|
| Requester (end user) | Submit and track their own requests and incidents; use the portal and knowledge base | No; described as "essentially 'free' users" |
| Business stakeholder (approver) | Everything a requester can do, plus approve or deny requests and view detailed reports | Yes |
| Fulfiller | Full rights in the application: create, edit and delete records, run processes (agents, developers) | Yes |
| Unrestricted user | Any active user in the instance, under a pooled licence model | Yes (a purchased pool) |
The ServiceNow license cost therefore depends mostly on how many people work tickets, not on how many people raise them. Check how your contract defines each role, and which roles your instance treats as fulfiller roles, before you count seats.
AI "assists": the metered part of the bill
An assist is "a unit to measure usage of Now Assist skills via performed skill actions" (UpperEdge, 11 Sep 2025). According to UpperEdge, customers receive a fixed annual allotment of assists, and once it is used up they must buy additional assist packs.
Under the 2026 packages, each tier carries its own assist allocation (ServiceNow Community, 28 May 2026). ServiceNow has not published pool sizes, per-action values or overage rates, so any specific assist count you see in partner material should be treated as an estimate (see the box above). NPI advises buyers to require order-form language that states the assists included per license each year, and to get overage pricing in writing (NPI, 6 Apr 2026).
What does ServiceNow cost? Verified benchmarks
The most reliable public figure for ServiceNow cost is Vendr's transaction data: a median of $129,871 a year across 109 purchases, a range of $43,245 to $702,488, and an average saving of 8.1% (Vendr, updated Feb 2026). This is very likely where the "$130K average" quoted without a source in other pricing articles comes from.
Two caveats: the sample covers buyers in Vendr's own dataset, and ServiceNow purchases generally, not ITSM alone. Use it as a sense check, not a quote.
| Benchmark | Figure | Scope | Source and date |
|---|---|---|---|
| Median annual spend | $129,871 | 109 ServiceNow purchases | Vendr, Feb 2026 |
| Annual spend range | $43,245 to $702,488 | Same sample | Vendr, Feb 2026 |
| Average negotiated saving | 8.1% | Same sample | Vendr, Feb 2026 |
| US federal discount | Up to 70% off list on upgrades to an ITSM Pro and Pro Plus bundle, through Sep 2028 | US federal agencies (GSA OneGov) | GSA, 3 Sep 2025 |
| US federal discount | 40% off list on upgrades to standalone ITSM Pro, through Sep 2026 | US federal agencies (GSA OneGov) | GSA, 3 Sep 2025 |
| Pro Plus premium (historical) | "a 60% uplift relative to Pro SKUs" | Legacy packages; CFO Gina Mastantuono | Constellation Research, 5 Mar 2024 |
| Upgrade to AI tiers (historical) | 30 to 60% increase in per-user cost | Legacy Pro Plus and Enterprise Plus; advisor claim | NPI, 6 Apr 2026 |
What these tell you:
- List prices exist, and deep discounts from them are possible. The GSA terms show this, but do not publish the list prices, and apply only to US federal agencies.
- The 60% figure is history. It describes how AI was priced as an add-on before the April 2026 repackaging, not a 2026 price.
- Cost is a common complaint. On G2, ServiceNow ITSM rates 4.5/5 from 1,985 reviews, and high licensing and implementation cost is the second most-mentioned con (59 mentions), after the learning curve (70) (G2, as of 25 Sep 2026).
Costs beyond the ServiceNow license cost
The subscription is only part of total cost. Public data on the other lines is thin, so the table attributes what exists and describes the rest.
| Cost line | What drives it | What public sources say |
|---|---|---|
| Implementation and partner fees | Scope, number of processes, integrations, how much you customize | Vendr notes that implementation and professional services can be a significant share of annual software spend, depending on complexity (Vendr, Feb 2026). We found no public rate card. |
| Add-on products | Anything outside your ITSM package: HR Service Delivery, Customer Service Management, IT Operations Management, Security Operations and others | Vendr lists the modules selected as a main pricing variable (Feb 2026). |
| AI assist overages | Volume of Now Assist and agentic usage beyond your allotment | Overage packs are sold on top of the allotment (UpperEdge, 11 Sep 2025). UpperEdge reports that Now Assist usage grew 9x between January and June 2025. Rates are not published. |
| Admin and developer headcount | Platform ownership, upgrades, configuration, integrations | Qualitative only. On G2, configuration complexity is the third most-cited con (53 mentions, as of 25 Sep 2026). |
| Renewal uplifts | Contract clauses, tier remapping, license growth | NPI reports unit-price increases of 8 to 12%, renewals that "increasingly" include 3% compounding annual uplift clauses, and a historical pattern of opening at 15 to 25% increases and settling near 10% (NPI, 6 Apr 2026). These are advisor observations, not audited data. |
One line is easy to miss: tier remapping. If your legacy footprint maps to Advanced or Prime rather than Foundation, the package change alone can move the price.
Renewal timeline: what to do 18, 12 and 6 months out
NPI calls 9 to 12 months before renewal "the minimum effective preparation window" and 18 to 24 months the optimal one (NPI, 6 Apr 2026). Here is a practical sequence built on that guidance, and on basic ServiceNow cost management.
18 months out: know what you use
- Reconcile contracted SKUs against what is actually deployed and used (NPI).
- Separate "enabled" from "actively deployed" licenses, and list fulfillers who no longer work tickets (NPI).
- Identify which legacy SKUs you hold and which new tier they are likely to map to (The Cloud People).
- Start a light market scan. If switching is a real option, it needs this much lead time.
12 months out: model the new deal
- Model AI assist consumption before you commit to a tier, and ask for overage pricing in writing (NPI; The Cloud People).
- Align IT, procurement and finance on one negotiating position (NPI).
- If you are evaluating alternatives, get firm quotes now. Vendr notes that competitive evaluation of alternatives commonly unlocks better pricing (Feb 2026).
- Decide whether you are negotiating to stay or planning to leave. The migration work described below does not fit into six months.
6 months out: negotiate terms, not just price
- Challenge compounding uplift clauses and ask for flat-rate caps (NPI).
- Require the order form to state assists included per license (NPI).
- Validate consumption data independently rather than relying only on vendor reports (NPI).
- Confirm that any tier mapping matches what you use, not the package ServiceNow recommends.
Cost of staying vs cost of switching (3-year view)
We found no public source that gives a reliable total cost for staying on ServiceNow or leaving it, so we will not invent one. Instead, fill in the framework below with your own quotes and contract terms. Use the same three-year window for both columns, because switching costs land early while subscription savings build over time.
| Cost line | Stay on ServiceNow (Years 1 to 3) | Switch platform (Years 1 to 3) | Where to get your number |
|---|---|---|---|
| Licences / subscription | Renewal quote × 3 years, at the tier you will be mapped to | New vendor quote × 3 years, plus ServiceNow fees until the contract ends | Renewal quote; competitor quotes; current order form |
| Price uplift | Year 1 price × (1 + uplift)^(year − 1), using your contract's uplift clause | New vendor's uplift clause, same formula | Contract terms. NPI reports 3% compounding clauses are becoming more common (6 Apr 2026). |
| AI usage | Expected assists beyond allotment × top-up price | Equivalent AI consumption charges, if any | Order form; written overage pricing |
| Implementation / re-implementation | Cost of any tier change or new modules | Configuring the new platform: processes, portal, workflows, SLAs | Partner statements of work |
| Data migration | Usually none | Your number: scoped from the effort drivers in the next section | Migration scoping exercise |
| Running both platforms | None | Months of overlap × monthly cost of both subscriptions and support | Cutover plan; contract end dates |
| Training | New features and tier changes | All agents, approvers and admins on a new tool | Headcount × training time × loaded hourly cost |
| Admin and support | Current platform team cost × 3 years | New platform team cost × 3 years, plus any retained ServiceNow skills during overlap | Internal HR / finance data |
| Total | Sum of rows | Sum of rows | Compare the two totals, then test them against a higher uplift and a longer overlap |
How to read the result: if the switching column only wins under optimistic assumptions (short overlap, no rework, fast training), the case is weak. If it wins even with a longer overlap and a full migration line, it is worth pursuing. Either way, the completed table is also useful leverage in the renewal negotiation.
What a ServiceNow migration costs (in or out)
We found no reliable public benchmark for what a ServiceNow migration costs, in either direction. The cost comes down to effort, and a small number of factors drive that effort. Scope them before you trust any quote.
| Effort driver | Why it adds cost | Question to ask |
|---|---|---|
| Custom tables and fields | Each one needs a target in the new data model, or a decision to drop it | How many custom tables do we have, and which are still in use? |
| Scoped apps and custom workflows | Logic built on the platform does not transfer. It must be rebuilt or retired | Which scoped apps support live processes? |
| CMDB | Configuration items are only useful with their relationships and service maps intact | Will CI relationships and their links to incidents and changes survive the move? |
| Attachments and history | Years of tickets, audit trails, SLA records and attachments are large and hard to map | How much history must stay reportable for audit, and how much can be archived? |
| Integrations | Monitoring, identity, HR, asset and DevOps tools all need reconnecting and testing | Which integrations are business-critical on day one? |
| Running both platforms | You pay for two tools, and staff work in two places, until cutover is complete | How long is the realistic overlap, and what does each month cost? |
The same drivers apply when moving into ServiceNow. History is the line most often left out of scope, because configuring a new platform is simpler than bringing years of records across intact.
Is ServiceNow cost-effective? When it's worth it, and when to look elsewhere
ServiceNow tends to justify its cost when you use a lot of it: several workflows on one platform, a well-maintained CMDB, strict change and audit requirements, and a platform team able to run it. The 2026 packages also bundle AI that previously cost extra, which helps if you would have bought it anyway.
It is harder to justify when you pay for a tier you only partly use, when most of the budget goes on fulfillers working basic incidents and requests, or when upgrades and customization absorb more admin time than they save. G2 reviewers most often cite the learning curve and cost as drawbacks (as of 25 Sep 2026).
If that sounds like your situation, start with our guide to ServiceNow alternatives, compare with Jira Service Management, or browse the top ITSM tools. If a platform change is on the table, the rightsizing consultation offered after the cost of staying vs cost of switching section above is the place to start.