SAM delivered a real saving in fewer than half of the estates, because the entitlement data was loaded and then never reconciled against discovery
The module was bought for a saving that only lands with continuous work. Meanwhile the platform subscription underneath it grew 20 to 35 percent.
Prepared by Redress Compliance · August 19, 2026 · ServiceNow engagements. 15 to 20 engagements advised, 2024 to 2025.
Executive summary
SAM delivered real savings in fewer than half of estates, because entitlements were loaded once and never reconciled against what discovery actually found.
The platform subscription grew 20 to 35 percent on uncontrolled fulfiller and asset counts. That line, not the module, usually carries the largest number on the order.
Managed asset counts ran 20 to 40 percent above actively managed assets. Discovery finds everything; management applies to a subset, and the license should follow the subset.
Stale SAM data is worse than no SAM data. It produces a dashboard that looks complete and cannot defend an audit, so the tool bought to cut risk creates it.
How does ServiceNow license SAM and ITAM?
As paid applications sitting on top of the platform subscription, each carrying its own line. The products are documented on the Software Asset Management and IT Asset Management pages.
Three layers, three separate bills
- Platform: the base subscription, priced by fulfiller user and by transaction.
- SAM: priced on managed software publishers.
- ITAM: hardware and lifecycle management, priced on managed assets.
The layer nobody prices is the one that grows
Both modules depend on data the core subscription provides, so buying them raises the platform metric as well as adding two lines. The growth shows up on the largest line rather than the newest one.
What actually drives the asset management bill?
The count of managed assets and software publishers, the fulfiller user count, and any premium content packs. Scope creep on managed assets is the most common cause of overspend.
| Module | Typical metric | Overspend driver | Buyer lever |
|---|---|---|---|
| Platform | Fulfiller user | Occasional users licensed as full fulfillers | Reclaim to a lighter role |
| SAM | Managed software publishers | Publishers in scope that are never reconciled | Scope to reconciled publishers |
| ITAM | Managed assets | Discovered assets counted beyond active management | License the managed subset |
| Premium SAM | Content pack | Pack bought but publishers not loaded | Drop packs with no load |
Each module counts something different
Aligning the licensed count to what the organization actually manages, rather than to the full discovery inventory, is the core discipline. It is also the part most estates skip.
The ten step ServiceNow renewal toolkit
The sequence that caps the uplift before you reach the table, across platform, modules and packs.
Get the brief →What 15 to 20 ServiceNow engagements showed
Across roughly fifteen to twenty ServiceNow engagements Morten Andersen advised between 2024 and 2025, the SAM module was bought for savings that never landed because the data was never reconciled. Three patterns recur.
- SAM delivered real savings in fewer than half of estates because entitlements were never reconciled.
- The platform subscription grew twenty to thirty five percent on uncontrolled fulfiller and asset counts.
- Managed asset counts ran twenty to forty percent above actively managed assets in most estates.
ServiceNow SAM only cuts cost when entitlements are reconciled against discovery every cycle. Bought without that, it is an expensive inventory viewer.
- Entitled vs deployed vs active seats compared, priced at your actual contract terms
- Duplicate tools and unused capacity surfaced across the portfolio
- A ranked savings queue with dollar values, not license counts
Why does data freshness decide whether SAM pays?
Because the saving comes from reconciliation, not from the software. Stale data produces false compliance positions, so the tool bought to cut audit risk instead creates it.
The data freshness trap
Many estates buy SAM, load discovery, and never reconcile entitlements. The result is a dashboard that looks complete and cannot defend an audit.
Reconciliation is the work
The value comes from reconciling discovered installs against owned entitlements every cycle. The data discipline is set out in the ISO 19770 standard.
Watch the briefing · 4:085 Ways to Win Your ServiceNow RenewalThe tier change, the seat count, and locking the overage rate before you depend on it.
Which renewal levers actually move the number?
Right counting managed assets, reclaiming fulfiller seats, dropping unused content packs, and holding the platform price across a multi year term.
Right count the assets before anything else
- Asset right count: license to actively managed assets, not the discovery total.
- Fulfiller reclaim: move occasional users off full fulfiller licenses.
- Price hold: cap the platform uplift across a multi year term.
Benchmark the rate you are being held to
List rates are visible on the ServiceNow Store, which is the starting point rather than the answer. The wider pricing model sits in the pricing reference and the ServiceNow pillar.
Where the common advice on ServiceNow SAM is wrong
The standard pitch is that SAM pays for itself by finding license savings across your publishers. We disagree.
The module is a process, not a product
Across roughly fifteen to twenty engagements advised in 2024 and 2025, SAM delivered real savings in fewer than half the estates because entitlement data was never reconciled, while the platform subscription itself grew twenty to thirty five percent on uncontrolled counts.
The buyer side move is to treat SAM as work that needs ongoing reconciliation and to control the platform metric first. A SAM module with stale data is a cost rather than a saving. Run the spend health check against the estate before the quote arrives.
What the engagements measured, 2024 to 2025
Two cuts, and both are about counting rather than discounting.
Where fulfiller and asset counts were allowed to rise without a control, on the largest line of the agreement.
In most estates, where the licensed figure followed the discovery inventory rather than the assets under active management.
Neither number is recoverable through a discount. Both are recoverable by counting what the organization actually manages.
Your first five moves
- Separate the platform subscription line from the SAM and ITAM module lines, because the platform is where 20 to 35 percent of the growth happened.
- Compare the licensed managed asset count against actively managed assets, which ran 20 to 40 percent apart in most estates.
- Reclaim fulfiller seats from occasional and read only users, since an occasional user licensed as a full fulfiller is the quietest line on the order.
- Confirm entitlement data is reconciled against discovery rather than just loaded, because that is the difference between a saving and an inventory viewer.
- Negotiate a multi year platform price hold. The ServiceNow practice runs the count before the quote arrives, which is the only sequence in which it helps.
Frequently asked questions
How does ServiceNow license SAM and ITAM?
As paid products on top of the platform subscription. SAM prices on managed software publishers and ITAM on managed assets, and both depend on data the core subscription provides.
Which line is actually the largest?
The platform subscription, not the module. It grew 20 to 35 percent on uncontrolled fulfiller and asset counts in the reviewed estates.
How often does SAM pay for itself?
In fewer than half of the estates reviewed. The saving comes from reconciling entitlements against discovery, and that work was skipped more often than it was done.
What is the data freshness trap?
Buying SAM, loading discovery, and never reconciling entitlements. The dashboard looks complete and cannot defend an audit, so the tool bought to cut risk creates it.
How far off are managed asset counts?
They ran 20 to 40 percent above actively managed assets in most estates. Discovery finds everything, management applies to a subset, and the license should follow the subset.
What drives the bill up fastest?
Scope creep on managed assets, followed by occasional users licensed as full fulfillers. Both grow quietly because nothing on the invoice separates them.
Are premium content packs worth it?
Only where the publishers are actually loaded and reconciled. A pack bought for publishers that were never loaded is a line with no output at all.
What are the strongest renewal levers?
Right counting managed assets, reclaiming fulfiller seats, dropping unused content packs, and holding the platform price across a multi year term.
Does a discount fix any of this?
No. The overspend sits in counts rather than rates, so a better percentage applied to the wrong count still bills for assets nobody manages.
Where should the work start?
By separating the platform line from the module lines on the order. Until those are read apart, the growth is invisible and the levers cannot be aimed.
