ServiceNow ITSM pricing explained: what drives the quote for mid-market teams
Short answer
ServiceNow does not publish ITSM prices. Its ITSM pricing page, checked on Nov 3, 2026, lists three packages, ITSM Foundation, ITSM Advanced and ITSM Prime, and a "Get Custom Quote" button, with no list price for any of them. What you pay is set in a negotiated quote, and the things that move that quote are predictable: the package tier you choose, the number of fulfillers (the agents and resolvers who work records, which ServiceNow measures by role), how many approvers or business stakeholders you license (ServiceNow's documentation says the approver_user role carries a fee), any usage-based meters bundled with the package (custom tables, process mining records, AI and Workflow Data Fabric capacity), separate add-on products such as ITOM or HR, and the term and ramp you negotiate. Requesters, the employees who simply raise tickets, do not appear as a meter type in ServiceNow's subscription documentation. Implementation partner fees and the internal admin team you need to run the platform sit outside the licence quote and often decide whether ServiceNow is affordable for a mid-market team. We give no dollar estimates in this guide, because ServiceNow publishes none and any figure we quoted would be guesswork.
Contents
- Who this guide is for
- The current ITSM packages: Foundation, Advanced and Prime
- Licence types: fulfillers, approvers, business stakeholders and requesters
- What actually drives the quote
- Usage meters and Subscription Management
- Costs outside the licence: implementation and running the platform
- How the quote structure changes by team shape
- How to prepare for the conversation with ServiceNow
- How ServiceNow compares with tools that publish prices
- When ServiceNow is worth the quote, and when it is the wrong choice
- Frequently asked questions
Who this guide is for
This guide is for IT leaders at mid-market companies, roughly 300 to 5,000 employees with a service desk of 15 to 150 agents, who are either evaluating ServiceNow ITSM for the first time or facing a renewal and want to understand what is driving the number on the quote. It is also for finance and procurement partners who have been handed a ServiceNow order form and want to know which lines matter.
If you searched for "ServiceNow ITSM pricing" hoping for a per-agent price, here is the honest position: ServiceNow does not publish one. Its ServiceNow ITSM pricing page lists packages and capabilities and directs you to request a custom quote. Third-party sites publish estimates, but they are not ServiceNow figures and we do not repeat them. Instead, this guide explains the structure of a ServiceNow ITSM quote, using only what ServiceNow says on its pricing page and in its product documentation, and adds our practitioner view of where mid-market teams overspend or get surprised.
Everything stated as fact here comes from ServiceNow's own pages, checked on Nov 3, 2026: the ITSM pricing page, and ServiceNow documentation on subscription types, system roles and the Business Stakeholder role. Where ServiceNow does not publish something, we say so. Opinions are labelled as ours.
The current ITSM packages: Foundation, Advanced and Prime
On Nov 3, 2026 the ServiceNow ITSM pricing page presents three packages. Each is described in ServiceNow's own words below, followed by the main capabilities the page lists for it. ServiceNow marks ITSM Prime as its recommended package.
| Package | How ServiceNow describes it | Capabilities listed on the pricing page |
|---|---|---|
| ITSM Foundation | "AI agents and skills that accelerate IT service delivery with task-based, always-on support." | 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 | "Agentic workflows that automate complex IT processes, working side by side with your team." | Everything in Foundation, plus Major Incident Management and On-Call Management; AI Voice Agents; Platform Analytics Advanced; Process Mining; Now Assist and Platform AI Advanced; Moveworks for ITSM Advanced |
| ITSM Prime | "AI Specialists that independently manage IT workflows, make decisions, and drive results." | 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 |
The page also lists a wider capability grid that includes Problem Management, Change Management, Walk-Up Experience, knowledge management, mobile, Predictive Intelligence, App Engine Starter, Universal Request and Universal Request Pro, among others. Some grid entries show different allowances by package, for example App Engine Starter at "25 tables" and "50 tables", and Process Mining at "10K records/year" and "15K records/year". The exact package each grid item belongs to is easiest to confirm on the live page or in your quote, and we recommend you do that for the items that matter to you most.
Check where Problem and Change Management sit
For most mid-market IT teams, Problem and Change Management are core ITIL processes, not extras. ServiceNow's India-region pricing page summary, as indexed in search, lists Change Management and Problem Management under ITSM Advanced; the US page we fetched lists both in its capability grid without an obvious package marker in text form. Do not assume they come with Foundation. Ask your account team to confirm in writing which package includes the processes you plan to run in year one.
What happened to ITSM Standard, Pro and Enterprise?
Many existing ServiceNow contracts, partner documents and older ServiceNow onboarding material use the earlier package names ITSM Standard, ITSM Pro and ITSM Enterprise. The current pricing page uses Foundation, Advanced and Prime. ServiceNow does not publish a one-to-one mapping on the pricing page, so if you are renewing an older Standard or Pro contract, ask the account team which current package your entitlements map to and what changes if you move. Do not assume the new name at the same position means the same scope.
Our view on package choice
In our experience, mid-market teams are often shown the top package first. That is a reasonable sales motion, but it is not always the right fit. The question to answer is which processes you will genuinely run well in the first 12 to 18 months. If your team is replacing a simpler tool and will spend year one getting incident, request, knowledge and CMDB right, paying for AI specialists and DevOps change capabilities you will not configure yet is a cost without a return. If major incident management, on-call and change at volume are day-one needs, Advanced may be the realistic floor. Write down your year-one process scope before you see a quote, and test each package against it.
Licence types: fulfillers, approvers, business stakeholders and requesters
ServiceNow ITSM is licensed per user, but not per employee. The licence you need depends on what a user is allowed to do, and ServiceNow measures that by the roles assigned to the user. Understanding this is the single most useful thing a buyer can do before a quote, because the user counts on the order form are where most mid-market quotes are won or lost.
How ServiceNow measures users
ServiceNow's Types of subscriptions documentation describes a per-user subscription type that is a "measure of Fulfiller Users and Business Stakeholder Users", allocated by adding groups with measured roles or access rights to a product subscription. Its Subscription Management documentation states that entitlements for users with fulfiller-type access are tracked with a Fulfiller User meter, and that users "who have fewer access rights than fulfiller users" are tracked with a Business Stakeholder User meter. A separate Creator User meter tracks users with the now.assist.creator role. The same documentation says the active-user count excludes users who have not logged in to the instance in the last 365 days, users set to web service access only, and users with an empty User ID.
| User type | What they do | How ServiceNow documentation treats it |
|---|---|---|
| Fulfiller | Agents, resolvers, change managers, problem managers, asset managers, admins: anyone who works records | Tracked through a per-user subscription with a Fulfiller User meter |
| Business stakeholder | Managers and leaders who need to view and approve ITSM records but not work them | Tracked with a Business Stakeholder User meter; the Business Stakeholder role lets users "view and approve records at all ITSM product levels" |
| Approver | Users who only approve requests routed to them | The approver_user role "can modify requests for approval routed to them" and has "all capabilities of requesters"; ServiceNow notes "There's a fee associated with this role" |
| Requester | Employees who raise and follow their own tickets and requests | Not listed as a meter type in ServiceNow's subscription types documentation |
| Creator | Users who build with Now Assist creator capabilities | Tracked with a Creator User meter (now.assist.creator role) |
Two details from ServiceNow's System roles documentation are worth reading closely. First, the approver_user role carries a fee, and ServiceNow warns: "Don't assign it to users without confirming your organization has the appropriate entitlement." Second, the same page says use of the approval_admin role "requires a Fulfiller license" and use of the approver_user role "requires an Approver license". The Business Stakeholder plugin documentation explains that the Business Stakeholder plugin installs a role for users who view and approve ITSM records.
Why this matters for your quote
Most mid-market organisations have far more people who approve things than people who work tickets. Line managers approve access and equipment requests, CAB members approve changes, finance approves purchases. If every one of those people is given a fulfiller-type role by accident, or an approver role you have not bought, your measured usage rises and the true-up conversation at renewal gets uncomfortable. If they are modelled correctly as stakeholders or approvers, and requesters stay requesters, the user counts on the quote reflect reality.
Build your user count before you ask for a quote
- Fulfillers: list every group that will work incidents, requests, problems, changes or assets, and count active people, not headcount on paper.
- Admins and platform team: they are fulfillers too; include them.
- Approvers and business stakeholders: list who approves what, and whether they only approve or also need to see wider ITSM records.
- Requesters: total employees who will raise tickets; you need this for portal and self-service design even though requesters are not a listed meter.
- Occasional users: second-line teams who touch a few tickets a month are where over-allocation creeps in; decide deliberately whether they get a fulfiller role.
What actually drives the quote
With no list price, the quote is the product of a few levers. These are the ones we see move the number most often for mid-market teams. All are structural; we do not attach amounts, because ServiceNow publishes none.
| Driver | Why it moves the quote | What to do |
|---|---|---|
| Package tier | Foundation, Advanced and Prime bundle different processes and AI capabilities | Match the package to your year-one process scope, not your three-year ambition |
| Fulfiller count | The primary per-user meter for ITSM | Count active resolvers from real data; challenge padded estimates |
| Approvers and stakeholders | Separate, fee-bearing user types per ServiceNow documentation | Model them explicitly; avoid giving approvers fulfiller roles |
| Bundled allowances | Some capabilities come with limits, for example custom tables or process mining records per year, shown by package on the pricing page | Ask for the allowance for each bundled item and what happens above it |
| Capacity and usage meters | ServiceNow documentation describes capacity subscriptions (for example custom tables), transactions and portal visits as bundled items, and a token ratio for Workflow Data Fabric capabilities | Ask which meters apply to your package and how usage is reported in Subscription Management |
| AI capabilities | Now Assist and Platform AI are listed at Foundation, Advanced and Prime levels | Clarify what AI usage is included and how additional usage is purchased |
| Separate products | ITOM (discovery, event management), HR Service Delivery, Customer Service Management and others are separate products | Scope them separately; do not let them inflate an ITSM-only decision |
| Unrestricted user products | ServiceNow documentation describes an Unrestricted User meter that counts all active users, regardless of role, for some subscriptions | Check whether any product on the quote uses it; it scales with total employees, not agents |
| Term, ramp and growth | Multi-year terms and agreed growth affect the commercial structure | Negotiate ramps that match your rollout; avoid paying for full scope from day one |
The costs outside the licence section below covers the second half of the picture: implementation and the team you need to run the platform.
Usage meters and Subscription Management
ServiceNow instances include a Subscription Management application, and it is worth understanding before you sign, because it is how ServiceNow and you will both see your usage. According to ServiceNow's Subscription Management documentation, the application lets administrators see how each subscription is measured (its meter type), match a product subscription to the purchase order, view subscribed groups and users, and monitor bundled items such as custom tables, portal visits and transaction entitlements. It also shows a token ratio for Workflow Data Fabric capabilities included with a subscription.
Per-user subscriptions are allocated through groups: you add a group that has measured roles to a product subscription, and its active members consume that subscription. The documentation describes capacity subscriptions as automatically calculated, and the Unrestricted User type as an instance-wide count of active users.
What this means in practice
- Role hygiene is cost control. Because measurement follows roles and groups, a well-meant change such as adding a large department to a group with an ITSM fulfiller role can raise measured usage overnight.
- Custom tables count. If your team plans to build custom apps on the platform, ask how many custom tables your package includes. The pricing page shows App Engine Starter at different table allowances by package.
- Inactive users drop out. ServiceNow's documentation says users who have not logged in for 365 days are excluded from the active count, which matters when you clean up leavers and contractors before a renewal.
- Agree who watches it. Make a named person on the platform team responsible for checking Subscription Management monthly, not just before renewal.
How the quote structure changes by team shape
Because there are no published prices, the useful exercise is to see how different team shapes push the levers. These are illustrative patterns from our work, without amounts.
| Team shape | What dominates the quote | Watch out for |
|---|---|---|
| 20 to 40 agents, IT only, replacing a simpler tool | Fulfiller count and package tier | Being sold Prime capabilities you will not configure in year one |
| 40 to 100 agents with many approvers (managers, CAB) | Fulfillers plus approver or business stakeholder counts | Approvers accidentally given fulfiller roles |
| Strong infrastructure team wanting discovery and event management | ITSM plus separate ITOM products | ITOM scope creeping into the ITSM decision |
| Plan to extend into HR or customer service later | ITSM now, other products later | Signing an enterprise-wide commitment before the second use case is real |
| Heavy in-house development on the platform | Custom tables, App Engine and Creator allowances | Exceeding bundled table allowances |
How to prepare for the conversation with ServiceNow
These steps come from running evaluations and renewals with mid-market clients. None depends on a specific discount or price.
Before the first pricing call
- Write your year-one process scope on one page: which ITIL processes, which integrations, which portal experiences.
- Count fulfillers, approvers, business stakeholders and requesters from real directory and ticketing data.
- Decide what you will not buy in year one (for example DevOps change, AI specialists, ITOM) and say so.
- Ask for the quote broken down by package, user type, bundled allowances and any usage meters.
- Ask which current package your existing entitlements map to, if you are renewing an older Standard, Pro or Enterprise contract.
- Ask for a ramp that matches your rollout plan.
Questions to ask in writing
- Which package includes Problem Management and Change Management?
- What AI usage is included with Now Assist in the package, and how is additional usage purchased?
- How many custom tables, process mining records and other bundled allowances are included?
- Which products on the quote, if any, use an Unrestricted User meter?
- How will approvers be licensed, and can fulfillers approve within ITSM without additional entitlement?
- What does Subscription Management show us, and how are overages handled at renewal?
Run a parallel comparison. Even if you are confident ServiceNow is the right platform, price the same scope on at least one tool that publishes prices. It gives you a reference point and forces a clear answer to the question "what do we get for the difference?".
How ServiceNow compares with tools that publish prices
For context, two common alternatives in the mid-market publish per-agent prices. On Nov 3, 2026 the Freshservice pricing page listed Starter at $19, Growth at $49 and Pro at $99 per agent per month billed annually, with Enterprise on a custom quote. The Jira Service Management pricing page showed Standard at $21.50 and Premium at $55.28 per agent per month on monthly billing at the page's default team size, a Free plan for up to 3 agents, and Enterprise via sales on annual billing only. Prices for these vendors change and are localised by region, so check the live pages.
These figures are not a proxy for ServiceNow's price. They are useful because they let you build a published-price baseline for the same scope, which is the fairest way to judge what a ServiceNow quote buys you. Our Freshservice vs JSM vs ServiceNow pricing guide walks through that exercise at 10, 25 and 50 agents.
When ServiceNow is worth the quote, and when it is the wrong choice
Worth it when
You plan a genuine enterprise service management platform across IT, HR, security or customer service within a realistic horizon; you need deep CMDB, discovery and operations integration; you have, or will fund, a platform owner and admin capacity; your auditors or regulators expect enterprise-grade process control; you already have ServiceNow skills in-house or in a trusted partner.
Wrong choice when
You are a 15 to 50 agent IT team with no plans beyond IT; you cannot fund ongoing admin capacity; your main goal is a fast, low-administration rollout; you will customise heavily to replicate an old tool; the decision is being driven by brand rather than a written process scope.
If you are on ServiceNow today and the quote at renewal no longer matches the value, our guides on ServiceNow to Freshservice and ServiceNow to Jira Service Management migrations cover what moves and what you rebuild.
Frequently asked questions
How much does ServiceNow ITSM cost?
ServiceNow does not publish ITSM prices. Its pricing page, checked on Nov 3, 2026, lists the ITSM Foundation, Advanced and Prime packages and asks you to request a custom quote. The price depends on package, user counts by type, bundled allowances, add-on products and contract terms.
What are the ServiceNow ITSM packages?
On Nov 3, 2026 ServiceNow listed three: ITSM Foundation, ITSM Advanced and ITSM Prime. Older contracts and documents use ITSM Standard, Pro and Enterprise; ask your account team how your existing entitlements map to the current packages.
What is a fulfiller licence in ServiceNow?
A fulfiller is a user with fulfiller-type access who works records, such as an agent or resolver. ServiceNow documentation says these entitlements are tracked through a per-user subscription with a Fulfiller User meter.
Do requesters need a ServiceNow licence?
Requesters are not listed as a meter type in ServiceNow's subscription types documentation. Approvers are different: ServiceNow says the approver_user role carries a fee. Confirm the treatment of every user type in your own quote.
Do approvers need a separate licence?
ServiceNow's system roles documentation says there is a fee associated with the approver_user role and that its use requires an Approver license. Business stakeholders, who view and approve ITSM records, are tracked with a Business Stakeholder User meter.
Is ServiceNow too expensive for a mid-market company?
It depends on scope and on whether you can fund the platform team. Licences are only part of the cost; implementation and ongoing administration often decide affordability. Compare three-year totals against a tool that publishes prices.
Can I mix ServiceNow ITSM packages for different users?
ServiceNow does not address this on its pricing page. Ask your account team directly and get the answer in writing before you plan a mixed model.