ServiceNow pricing in 2026 runs on three different billing bases at once: ITSM, CSM, and the developer products bill per fulfiller from about $100 per user per month, HRSD bills per employee from about $4 per employee per month, and ITOM bills per subscription unit from about $0.50 per node per month, so a single enterprise estate can be metered three different ways on one contract. The most expensive misunderstanding in a ServiceNow renewal is assuming the platform has one price. It does not. Each workflow carries its own unit, its own tiers, and its own growth driver, and the total only makes sense when you model all three together.
This page maps ServiceNow pricing across every major package for 2026, shows which billing basis each uses, and points to the deep-dive cluster pages for each. It is the hub for the pricing detail in the ServiceNow licensing guide and the reference behind every package-specific page.
Inside This Guide
The three billing bases
Every ServiceNow product reduces to one of three meters. Per-fulfiller products charge for named users who work on others' behalf and ignore the much larger requester population. Per-employee products charge for the entire served workforce regardless of who operates the tool. Per-unit products charge for infrastructure the platform discovers and monitors, with no user concept at all. Knowing which meter applies to each workflow tells you what drives its cost: agent count, total headcount, or infrastructure footprint.
This matters because the growth drivers point in different directions. Hiring agents grows ITSM cost but not HRSD. Growing total headcount grows HRSD but not ITOM. Expanding cloud infrastructure grows ITOM but touches neither of the others. A forecast that treats the platform as a single line will be wrong in three different ways at once.
ITSM and the per-fulfiller products
ITSM, IT Service Management, is the anchor product and the clearest example of per-fulfiller billing across its Standard, Professional, and Enterprise tiers, detailed in ITSM pricing tiers. The same per-fulfiller model carries through several adjacent workflows. Customer Service Management bills per fulfiller, often with additional metering on cases or transactions for the customer-facing side. The developer and platform products, App Engine and the custom-application tooling, also resolve to a per-user or per-application basis, and Now Assist rides on top of the fulfiller tiers as the GenAI uplift covered in Now Assist pricing.
The discipline across all per-fulfiller products is the same: control the named-user count, match the tier to real feature use, and reclaim dormant seats. The seat count and the tier together, not the rate, decide the cost.
HRSD and per-employee products
HR Service Delivery is the headline per-employee product, priced across the served workforce as set out in HRSD pricing. Several employee-facing workflows share this basis, because they are designed to reach every worker rather than a team of agents. The Employee Center portal, Workplace Service Delivery, and related employee-experience products generally meter by the population they serve. The cost discipline here is the opposite of ITSM: agents are free, but the employee definition and the headcount basis are everything, because they scale with the whole company.
The overlap audit. Because ServiceNow products share components such as the Employee Center portal and the platform foundation, multi-product estates frequently pay for the same component inside more than one subscription. A single overlap audit across the full order form, reconciling shared entitlements against duplicated lines, recovers a median of 16 percent in our first-pass platform reviews and is the highest-return analysis on a multi-workflow ServiceNow deal.
ITOM and per-unit products
IT Operations Management is the per-unit product, billing by subscription units against discovered and monitored nodes as detailed in ITOM licensing and subscription units. Security Operations and some governance, risk, and compliance products also carry unit or asset-based metering rather than a pure user model. The defining risk across the per-unit products is that the meter tracks infrastructure the licensing team does not control, so the count drifts with deployment unless the discovery scope and the counting method are deliberately managed.
CSM and the customer-facing products
Customer Service Management deserves separate attention because it blends two billing logics. The agents who work customer cases are licensed per fulfiller, much like ITSM, but CSM deals frequently carry additional metering on the customer-facing side, whether by case volume, by transaction, or by the number of external accounts served. That hybrid structure means a CSM forecast has to model both the agent count and the customer-interaction volume, and a deal sized only on agents can be surprised by the volume component as customer adoption grows.
Field Service Management, which often accompanies CSM, adds its own per-user licensing for dispatchers and field technicians, sometimes with a distinction between full and occasional users. The practical effect is that the customer and field workflows can carry three or four interacting meters, and the only reliable way to price them is to model each meter against its own growth driver. Buyers who treat CSM as simply ITSM for customers undercount the volume and field components and build a forecast that drifts upward as the customer base expands.
Security, GRC, and platform products
Beyond the headline workflows, ServiceNow sells a layer of products that meter against assets, risks, or platform usage rather than users. Security Operations bills against the assets and vulnerabilities it covers. Integrated Risk Management and the governance, risk, and compliance products meter against entities such as risks, controls, or users depending on the module. These products often run against infrastructure or data that overlaps with ITOM and other workflows, which is why the overlap audit above is so valuable on a broad estate.
The platform foundation itself is a cost element. ServiceNow includes platform capabilities with the workflow subscriptions, but heavy custom development, large data volumes, and extensive integrations can push an estate toward additional platform or App Engine licensing. Custom tables built outside a properly licensed scoped application can trigger separate charges, a liability that builds silently over years of development and which we cover in custom table charges.
Package and basis map
The table maps the major 2026 packages to their billing basis and benchmark entry price.
| Package | Billing basis | Cost driver | Benchmark entry price |
|---|---|---|---|
| ITSM (Standard to Enterprise) | Per fulfiller | Agent count + tier | $100 / user / month |
| CSM | Per fulfiller (+ case/transaction) | Agent count + volume | $110 / user / month |
| HRSD | Per employee | Total headcount + tier | $4 / employee / month |
| ITOM | Per subscription unit | Discovered node count | $0.50 / unit / month |
| Now Assist (Pro/Ent Plus) | Per-fulfiller uplift | AI-enabled seats + assists | 30-60% tier uplift |
| App Engine / custom apps | Per user / per application | Builder count + custom tables | Varies by deal |
Six packages, four distinct billing bases. The custom-application line is its own cost story, because tables built outside scoped applications can trigger separate charges, which we cover in custom table charges.
What good ServiceNow discounts look like
Across all these products, the discount off list is where the negotiation lands, and benchmarks matter because ServiceNow publishes no prices and every buyer negotiates in the dark without them. Discounts deepen with total contract value, term length, and the breadth of the platform relationship, so a single-workflow deal earns less than a multi-workflow platform commitment of the same dollar value. The specific bands we see across deal sizes are set out in ServiceNow discount benchmarks, and they are the reference point for judging whether any given quote is competitive.
The structural protections matter as much as the headline discount. A strong ServiceNow deal pairs a competitive discount with a capped renewal uplift, co-termed adds at the negotiated rate to neutralize true-ups, and a clear definition of every billing basis so growth is priced predictably. A deep discount with none of these protections erodes within two renewals, which is why the basis-by-basis model and the protective clauses, not just the discount percentage, define a deal worth signing.
Modeling the total
The only reliable ServiceNow forecast models each package on its own basis and then sums them, with a separate growth assumption for each driver: agent hiring for the per-fulfiller products, workforce growth for the per-employee products, and infrastructure expansion for the per-unit products. A single blended growth rate applied to the whole platform will mis-forecast every line. Layer in the renewal uplift and the true-up mechanics, and you have a model that reflects how the bill actually moves.
Bundling and platform deals
ServiceNow rewards breadth, so the discount on any single product deepens when it is bought as part of a wider platform commitment rather than alone. An organization adding HRSD or CSM to an existing ITSM relationship can usually secure a better rate on the new workflow, and sometimes on the renewal of the existing one, by structuring the whole estate as a single platform deal with a unified term. This is the central reason to plan ServiceNow purchases together rather than letting each workflow be bought by a different team on its own timeline.
The risk in a platform deal is over-commitment: bundling in products the organization is not ready to deploy, in exchange for a headline discount, simply buys shelfware at a discount. The discipline is to bundle only what has a real adoption plan, size each component to genuine need, and use the breadth of the committed spend, not speculative future products, as the discount lever. The negotiation tactics that turn platform breadth into price sit in our ServiceNow negotiation practice.
This three-meter discipline is what separates a controlled ServiceNow estate from one that grows on autopilot, because each meter responds to a different decision made by a different team, and only a unified model makes those decisions visible in one place before they reach an invoice.
One practical output of the basis-by-basis model is a single platform dashboard that tracks each meter against its entitlement: fulfiller seats and tier mix for the per-user products, employee count for HRSD, and discovered node count for ITOM. Maintained quarterly, that dashboard turns the next renewal from an exercise in reconstructing what was bought into a conversation about a position the organization already understands, and it surfaces drift on any of the three meters while there is still time to act on it rather than pay for it.
An organization that models the platform by basis controls its ServiceNow spend, while one that treats it as a single number is surprised on three fronts at once. Our ServiceNow optimization team builds the unified model across every package, and our software licensing advisory practice turns it into the negotiating position for your next renewal.