ServiceNow ITAM licensing in 2026. Clean the device count before the quote.

ServiceNow prices ITAM on the managed devices in your CMDB, so the count sets most of the bill. Reconcile it before the quote, table a priced rival for SAM Professional, and decide the bundle last.

How is ServiceNow ITAM licensed in 2026?

ServiceNow licenses IT Asset Management per managed device. Hardware Asset Management (HAM) and Software Asset Management (SAM) are standalone subscriptions, and SAM Professional is the higher tier that adds the publisher packs. At 2026 list, an enterprise ITAM bundle lands between half a million and several million dollars.

That price range explains where to spend your preparation time. On a line that size, the number of devices ServiceNow counts changes the bill more than a few extra points of discount.

What does a subscription unit cover?

Order forms rarely say "per device" in plain words. ServiceNow meters ITAM in subscription units, and each resource type converts to units at a published ratio. A server consumes four times the units of a laptop, so the mix of your devices matters as much as the total.

Most ratios come from ServiceNow's subscription unit overview effective July 23, 2020, and the SaaS user line from its SAM overview effective January 21, 2021. Newer order forms can add resource types or change the definitions, and some older SAM Professional contracts count computers directly. Read the definitions in your own order form before you trust any count.

What does each ITAM component license, and where is there room to negotiate?

Why does the metric definition belong in the contract?

Per device and per managed asset are different numbers, and the gap depends on what counts as managed. Under loose wording, a stockroom laptop, a retired server still marked In use and a rebuilt virtual machine can all count. Fixing that wording is worth more than a point of discount, and it only happens if you ask for it.

Why does the quoted ITAM device count run high?

The count comes from the CMDB, and the CMDB holds every device that was ever discovered or received, whether or not it still exists. Across our ITAM engagements, stale and duplicate records inflated the count 15 to 30 percent at quote time. In each case the quote priced the database as it stood, including devices long gone.

This is a data cleanup, and it has to happen before the quote is built. It is worth a double digit percentage of a seven figure line, and it is entirely yours to fix. Once a number is on a signed order form, the cleanup only helps at the next renewal.

Where do stale and duplicate records come from?

• Disposals that never reach the CMDB. A laptop is wiped and recycled, but the asset record stays In use or In stock, so HAM keeps counting it.
• Two sources, two records. Procurement creates an asset from the purchase order and Discovery or a connector creates a CI from the device, and the serial numbers do not match.
• Rebuilt virtual machines. A server rebuilt under a new host name appears as a new CI, while the old one keeps its software install records.
• Lab, test and training kit. Devices that never needed asset management get picked up by a broad discovery range.
• Mergers and divestments. Records for a business you sold stay in your instance long after the devices left.

How do you check your own count before ServiceNow does?

What does a cleanup save in a worked example?

Say your CMDB shows 12,000 end user devices, 2,000 servers and 1,500 network devices, and a reconciliation finds 10,000, 1,600 and 1,200 that really exist. Assume both SAM and HAM, and an illustrative $100 per subscription unit per year. ServiceNow does not publish ITAM unit prices, so the dollar figures are for arithmetic only.

The cleanup removes 1,860 units, or $186,000 a year, about 18 percent of the line. Over a three year term that is $558,000, before any discount is discussed. Any percentage you later win applies to the smaller base.

Is SAM Professional worth its tier?

SAM Professional pays for itself when you face measurement by Oracle, IBM or SAP. Its publisher packs calculate the engineering metrics those vendors audit against, such as Oracle processor and partitioning rules and IBM processor value units. For a company without that exposure, the tier is overhead on top of basic SAM.

Check the name on your paperwork. Older order forms say SAM Professional, while ServiceNow's current SAM pricing page sells the product as SAM Advanced and SAM Prime. Ask the account team to map each package to the publisher packs it includes before you compare prices.

• Name the publishers whose metrics you need calculated for you. That list is the entire value case, and ServiceNow's data sheet names packs for Microsoft, Oracle, IBM, Adobe, SAP, VMware and Citrix.
• Price a best of breed alternative before you accept the tier. In our engagements a costed rival quote did more for the price than any argument about features.
• Check what Discovery already gives you. It is a practical prerequisite for accurate SAM reconciliation and a cost line of its own.

Do you need ServiceNow Discovery to run SAM?

For the Oracle publisher pack, in practice yes. ServiceNow's documentation says Oracle installation and usage data must come from a discovery process, and ServiceNow Discovery is verified by Oracle for that purpose. Desktop software can come from Microsoft Configuration Manager through a Service Graph Connector instead.

Put Discovery in the same business case as SAM, with its own scope and count. Discovery is metered separately, and our brief on ITOM Visibility and Discovery licensing covers what each discovered resource costs you. A discovery range drawn wider than SAM needs raises both bills.

Why we disagree that you should only table a rival quote you would sign

The common advice is to skip a competitive quote unless you are ready to switch, since account teams spot bluffs. Our engagements say otherwise. A costed Snow or Flexera quote changed the SAM Professional discount by 30 to 40 percent, though nothing suggests the buyers who tabled one meant to migrate, or had to.

The quote has to be real, scoped to the same publishers and device counts and priced by the vendor. Flexera completed its purchase of Snow Software in February 2024, so one Flexera proposal can price Flexera One or Snow Atlas. Get it in writing, with a price per device and a validity date that runs past your ServiceNow signature date.

When is bundling ITAM with ITOM and CSM cheaper?

When you were going to buy the modules inside the bundle anyway. Bundling ITAM with ITOM and CSM cut 20 to 35 percent off the standalone stack in our engagements, a real saving rather than repackaged list price. That is not true of every ServiceNow bundle.

• ITOM. Is Discovery or Service Mapping scheduled for production during the term, and how many resources will it count?
• CSM. Will a customer service team work cases in ServiceNow, and how many fulfillers will it need?
• ITAM. Is the reconciled device count agreed and the SAM tier decided?
• Term. Do all modules in the bundle share one end date, so you can reopen them together?

The usual warning still applies. A discount on a module you never deploy is a higher bill, and the Now Platform makes it easy to license capability that never reaches production. Before you accept a bundle, write down the go live date for each module in it.

The neighboring modules price on their own logic, covered in our ITOM licensing guide and CSM licensing guide. The measurement side, including how ServiceNow checks usage against entitlement, is in our license audit guide.

Why reopen ITAM at every renewal?

ITAM carries higher list discounts and more flexible bundle pricing than the core platform license, which makes it one of the most negotiable modules on the ServiceNow paper. Rolling it forward at the old count and price gives that room away. Treat each renewal as a new ITAM quote, built from a fresh reconciled count.

What have we seen in ServiceNow ITAM negotiations in 2024 and 2025?

Across roughly 30 to 45 ServiceNow ITAM and SAM engagements we ran from 2024 to 2025, the device count on the quote ran well ahead of the cleaned environment. Three findings account for most of the money.

1. The quantity was wrong first. Stale and duplicate CMDB records inflated the count before anyone discussed a rate.
2. The price responded to outside evidence. SAM Professional discounts widened once a priced Snow or Flexera alternative was on the table, and the buyer did not have to switch.
3. The bundle paid off only when the modules were wanted. ITAM with ITOM and CSM saved money where each module had a deployment plan.

The order matters. Clean the count, table the benchmark, then decide the bundle. Take the bundle first and you negotiate its discount on an inflated count, and the rival quote loses credibility once you have committed to the suite. Reversing the order gives away the two steps that were free.

One problem is data and one is competition, and both are settled before the commercial conversation begins.

How do you negotiate the ServiceNow ITAM line at renewal?

Send ServiceNow a reconciled count and a costed alternative before they send you a quote, then negotiate the bundle and the contract wording. Our ServiceNow renewal negotiation guide covers timing across the whole platform, and our discount benchmarks show where ITAM sits against other modules.

What will the account team say, and what should you say back?

• "The count comes from your own CMDB." Agree, and send the reconciled count with the exclusions you applied. Ask for the quote on that number, with the unit ratios written into the order form.
• "No third party tool matches the publisher packs inside the platform." Hand over the Flexera proposal for the same publishers and devices, and ask them to price against it.
• "The bundle price expires at quarter end." Say you will decide the bundle once the count and the SAM price are settled, and ask for each module to be priced separately inside it.
• "Accurate SAM needs full Discovery." Accept it for Oracle, point to your Configuration Manager connector for desktops, and ask for Discovery to be quoted with its own scope.

Which contract terms should you ask for?

• A metric definition with exclusions. Resource types and ratios named, with Retired, Missing, duplicate and lab records excluded, so the count cannot drift back up.
• A count method for true up. The report, the table and the date used to measure usage, so a mid term true up uses the same rules as the quote.
• A unit price hold. The same price per subscription unit for additional units during the term and at the first renewal.
• A reduction right at renewal. The ability to reduce ITAM units or drop SAM Professional without losing the discount on other modules.
• Itemized bundle pricing. Each module priced on its own line, so you can drop one later without repricing the others.
• A named publisher pack list. The publishers covered by SAM Professional listed in the order form.

How does the approach change for a small and a large company?

A company with around 3,000 devices and no Oracle, IBM or SAP exposure often gets enough from the asset features included with ITSM plus endpoint manager reports. SAM Professional rarely earns its tier there, so the task is to confirm you need it before cleaning any count. Our SAM tool comparison sets out the alternatives.

At 60,000 devices with large Oracle or IBM server footprints, the publisher packs usually justify themselves, and most of the money sits in the count. Servers carry the heaviest ratio, so reconcile them first. At that size, Discovery scope, the rival quote and the bundle decision can each change the bill by six or seven figures.

What to do next

1. 12 months before renewal. Reconcile the CMDB against endpoint managers, the directory and the asset register, and retire or merge stale and duplicate records.
2. 9 months out. List the publishers whose metrics you need calculated, and decide whether SAM Professional is justified.
3. 6 months out. Obtain a costed Flexera or other rival proposal for the same scope, and send ServiceNow your reconciled count before the quote is built.
4. 4 months out. Pin the metric definition, the count method and the unit ratios in the draft order form.
5. 3 months out. Decide the bundle last, taking ITOM and CSM only where each module has a go live date.
6. At every renewal. Reopen ITAM from a fresh count. Our ServiceNow practice cleans the count before the quote, the one point at which it changes the price.

Frequently asked questions