Priced per device rather than per user, dependent on data quality, and bought for savings that only land if you reconcile. Three knowledge checks along the way, and 3 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 3 times in the session the frame splits and a senior licensing analyst gives the view from inside real ServiceNow negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session eighteen, and today has a genuine irony sitting at the centre of it. We are going to license the licence management tool. ITAM and SAM are the products you buy specifically to get control of software spend, to find waste, to defend audits, and their own licensing has every single problem they were purchased to solve. Inflated counts, stale data, scope creep, a dependency chain nobody mapped. Nothing exempts them. And I do not say that to be clever about it, I say it because buyers approach these products with their guard down, in a way they would not for ITSM, because the product is on their side. It is a good product. It is also a line on an order form, priced per device, with a business case that lands in fewer than half of the estates that buy it. Three checks, homework, let's go.
Five objectives. First, read the layered model, platform underneath with SAM and ITAM as paid products on top, each carrying its own unit and its own dependency, because most buyers think of this as one purchase and it is three bills. Second, count the right thing, per device and per managed software publisher rather than per user, and understand what that changes about who actually drives the number. Third, test the business case honestly, because SAM delivers savings only where entitlements get reconciled against discovery, and in most estates they never were. Fourth, price Premier properly, what it adds, why it is quoted where it is, and what a credible alternative benchmark does to that number, which is a lot. And fifth, clean before you quote, because device counts arrive at quote time inflated fifteen to thirty percent by stale and duplicate records, and once that number is in a quote it is very hard to argue back down.
Four numbers. Fewer than half, the share of estates where SAM delivered real savings, because entitlements were never reconciled against discovery. Note the diagnosis carefully, the tool worked, the process stopped. Fifteen to thirty percent, how far CMDB device counts were inflated by stale and duplicate records at quote time, which means you get quoted on the dirty number unless you clean first. Twenty to forty percent, how far managed asset counts ran above actively managed assets, and scope creep on managed assets is the single commonest cause of overspend in these products. And thirty to forty percent, the SAM Premier discount off list once a credible alternative benchmark was on the table, which tells you something important, the quote assumes you have no comparison. Now the note underneath, which is the sentence I would put on the wall. This is the product you buy to control licensing, and its own licensing has every problem it was purchased to solve. Let's hear that from someone who has watched it play out.
Guest analyst clip. There is a particular sadness to a SAM implementation that has stalled, and I have seen quite a few. The business case was genuine. Somebody stood up in front of a steering committee and said, we are wasting money on software licences across the estate, this tool will find it, and it will pay for itself. All true. The tool was bought, implemented competently, dashboards built. And then the reconciliation programme, which is the part that actually produces savings, ran into the fact that nobody owns entitlement data. Purchasing has the contracts in a filing system. IT has the deployments. Nobody has both, mapped to each other, kept current. So the project quietly becomes a reporting project. You get beautiful dashboards showing what is installed, which is genuinely useful for other purposes, and no compliance position at all, because installs without entitlements is half a picture. Two years later somebody asks what the savings were, and there is an uncomfortable silence. My advice to anybody considering this purchase is blunt. Do not buy SAM as a tool. Buy it as a programme, with a named owner for entitlement data and a funded reconciliation effort, and if you cannot get that funded then you are buying a reporting product at a compliance product price.
Do not buy SAM as a tool, buy it as a programme. And notice the structural cause underneath, nobody owns entitlement data, because purchasing holds contracts and IT holds deployments and no one holds both mapped together. If that sounds familiar it should, it is the same organisational gap that produced the fulfiller problem in module three. Now, the layers.
Three layers, three bills, plus a dependency. The platform, the base subscription everything sits on, priced on fulfiller users and consumption, and usually the largest single line of the three. Hold that, we come back to it in the final check. ITAM, hardware and lifecycle asset management, priced on managed assets on a per device count. SAM, software asset management, priced on managed software publishers, with Premier as a high tier add on. And the dependency, Discovery from ITOM, which is not billed here but is a practical prerequisite, because without it the asset data quality collapses and everything above it becomes unreliable. So the note is the structural point. SAM and ITAM are paid applications on top of the platform subscription rather than features of it, and both depend on data the platform and Discovery provide. Three bills, one dependency chain, and if you bought these products without ITOM Discovery in place, that is worth knowing before you spend another quarter wondering why the data looks wrong.
Per device changes who drives the bill, five points. The count is devices rather than people, so ITAM licenses on a per device count, hardware assets plus the unique software install footprint, normalized through a published count rule. Which means the drivers move again, like ITOM this line grows with infrastructure and endpoints rather than with headcount, but unlike ITOM there is a second inflation source, because stale records inflate it as much as real growth does. A decommissioned laptop still in the CMDB is indistinguishable, to the count, from a live one. HAM and SAM are separate products, hardware asset management and software asset management sold distinctly, and buying one does not carry the other, which surprises people. Platform seats ride underneath, because the asset team still needs fulfiller licences on the platform, and the platform subscription grew twenty to thirty five percent on uncontrolled fulfiller and asset counts. So you end up with three counts to govern. Devices, publishers, and the fulfiller seats of the people running the tool. And in my experience most estates govern precisely none of them.
Knowledge check one. Your CMDB holds forty two thousand device records. Cleanup shows thirty one thousand are live and unique. You are mid quote for ITAM right now. What is the sequence? A, quote on forty two thousand, then true down later once cleaned. B, clean first, then quote on thirty one thousand. C, quote on forty two thousand for safety headroom. Or D, split the difference at thirty six thousand. Pause here, and ask which number the vendor prices against.
The answer is B, clean first. And notice this estate sits exactly in the documented range, forty two thousand down to thirty one thousand is a twenty six percent inflation, right inside the fifteen to thirty percent that stale and duplicate records produce at quote time. Answer A assumes a true down right you probably do not have, and sessions four and twelve both established that consumption falling does not reduce entitlement, so you would be locked into eleven thousand phantom devices for the term. Answer C buys headroom on a metric where the inflation is data quality rather than growth, which means you are paying for records, not devices, and no amount of future growth makes a duplicate record real. Answer D splits a number instead of resolving it. Same rule as session sixteen. Facts before terms, because the quote prices whatever number you hand over, and once it is in the quote the burden shifts to you to argue it down.
Why SAM savings do not land, four cards. The business case, buy SAM, find licence waste across your publishers, recover more than the tool costs, and I want to be clear that this is genuinely achievable and it was achieved, in fewer than half of estates. What stalls it, entitlements never got loaded and reconciled against what discovery found, and without both halves the tool reports installs, which is not a compliance position, it is an inventory. The false comfort, and this is the dangerous one, stale SAM data creates false compliance positions and cannot defend an audit, so a confident green dashboard built on unreconciled data is actively worse than no dashboard, because it stops anybody looking. And the honest test, which I would encourage you to apply this week. Can you name a publisher where SAM found a real, quantified recovery in the last twelve months? If you cannot, the case has not landed, whatever the tool reports. And the note matters, this is not an argument against SAM. It is an argument against buying SAM without funding the reconciliation, because the licence cost lands immediately and the savings do not.
Knowledge check two. Your SAM dashboard shows a clean compliance position across all publishers. Green everywhere. Entitlements were loaded once at implementation, two years ago. How much weight does that carry in an audit? A, full weight, it is the system of record. B, very little, because stale entitlement data cannot defend an audit. C, partial, discounted for age. Or D, full weight for the publishers that have not changed. Pause, and ask what the dashboard is actually comparing against.
The answer is B, very little. A compliance position is a comparison, deployments against entitlements, and if one side of that comparison is two years old then the comparison is decorative. That is the false comfort case, and the mechanism is worth naming, the dashboard is green because the entitlement side stopped moving, not because your estate is compliant. Those two produce identical colours and completely different realities. Answer D is the most tempting and I put it there deliberately, because it sounds like careful reasoning, full weight for the publishers that have not changed. But you cannot know which publishers have not changed without current entitlement data, which is exactly the thing that is missing. The claim requires the evidence it lacks. And the summary is one I would repeat to any executive looking at a green SAM dashboard, green on stale data is worse than no dashboard at all, because no dashboard at least prompts somebody to go and look.
SAM Premier, what it adds and what moves its price. Premier is the high tier add on, advanced reconciliation, publisher pack content, and engineering metrics, and it is justified where engineering metrics on the big publishers genuinely drive your exposure. Engineering metrics specifically are the content that drives the largest licence counts on Oracle, Microsoft, and IBM, and that is either the reason to buy Premier or the reason not to, depending entirely on your estate. If your Oracle exposure is significant, this content may be worth real money to you. If it is not, you are buying depth you will never reach. The list price, enterprise ITAM bundles reach the half million to multi million range at list, and list is an opening position on a product with no published pricing. And the benchmark effect, which is the practical lever, Premier discounts of thirty to forty percent off list once a Snow or Flexera benchmark was present. Thirty to forty percent, for having a comparison in the room. And the note adds the bundle math, ITAM bundled with ITOM and CSM regularly closed twenty to thirty five percent below the list of the same components separately, so bundle where the consumption is genuine, exactly as in session seventeen.
Guest analyst clip. The benchmark effect on Premier is the most reliable single lever I know in this product area, and I want to explain why it works so consistently, because understanding the mechanism tells you how to use it properly. SAM tooling is a competitive market. Snow, Flexera, and others sell products that overlap substantially with what Premier does, particularly on the publisher content and reconciliation side. ServiceNow's advantage is integration, everything already lives on the platform, and that advantage is real and worth paying something for. But it is worth a premium, not an unlimited one. So when a buyer has no alternative quote, the price is set by what the integration story can support in a room with no comparison. When a credible alternative is on the table, priced, from a vendor who actually responded, the conversation changes completely, because now the premium has to justify itself against a number. Thirty to forty percent off list is what that has been worth in our files. And here is the part buyers get wrong, they think they need to be willing to switch. You do not. You need to be willing to genuinely evaluate, which is a much lower bar, and it is also just good practice. An alternative you never seriously considered is not a benchmark, and account teams can tell the difference within one meeting.
You do not need to be willing to switch, you need to be willing to genuinely evaluate. And the warning at the end is worth taking seriously, an alternative you never seriously considered is not a benchmark, and experienced account teams identify a bluff quickly. Get a real quote from a real vendor you would actually deploy if the numbers demanded it. Now, right counting.
Right counting before anybody quotes you, five steps. Deduplicate the CMDB, since the same asset arriving from several sources is the largest single contributor to that fifteen to thirty percent inflation. Purge the retired, because decommissioned hardware still holding a record still counts, and lifecycle governance rather than archiving, which is exactly the ITOM lesson from last session repeating in a new product. Separate managed from present, because managed asset counts ran twenty to forty percent above actively managed assets, and presence in the CMDB is not management, any more than holding a role was fulfilling in session eleven. Fix Discovery first, because without accurate discovery the asset data cannot be trusted, which makes the ITOM work from session seventeen a prerequisite rather than a parallel track, and that sequencing matters if you are planning both. And then reclaim the fulfiller seats, the asset team's own platform licences counted with module three's discipline, because as we are about to see, the platform line is usually larger than either asset product.
Knowledge check three, and it is a simple question that most people get wrong. Where should you expect the largest of the three bills to sit? A, SAM, because software publishers are expensive. B, ITAM, because device counts are large. C, the platform subscription underneath both. Or D, SAM Premier, because it is the top tier. Pause, and ask which layer everything else sits on.
The answer is C, the platform subscription underneath. It usually carries the largest single line of the three, and it grew twenty to thirty five percent on uncontrolled fulfiller and asset counts, so it is simultaneously the biggest and the fastest drifting. Now the trap in this question is a general one worth naming, because it operates everywhere. Attention naturally follows the product being purchased. You are buying SAM, so you scrutinise SAM, and meanwhile the layer underneath it quietly costs more and nobody is looking at it, because it was bought years ago and feels settled. And here is the good news attached to that. The platform layer is the one you already know how to fix, because it is fulfiller seats, which is module three, which you have already done for the rest of the estate. You just have to remember to point it at the asset team as well.
Four levers. Right count the assets, deduplicated, purged, and separated into managed versus merely present, which is the single largest lever and requires no negotiation at all. Reclaim the fulfiller seats, module three's audit applied to the asset team's platform licences, on the layer carrying the biggest line. Drop the unused packs, publisher packs and Premier content you do not exercise, which is session three's shelfware test aimed at the asset products. And hold the platform price, a price hold on the layer underneath, because ITAM and SAM growth pulls platform consumption up with it, and without a hold you get charged twice for the same expansion, once on the product and once underneath it. And then the timing rule in the note, which is specific to this product family. ITAM negotiates better at renewal than at first purchase. So a first purchase should buy the minimum defensible scope, with the expansion terms agreed in advance, and then grow into it from a position where you have usage evidence. One more clip.
Guest analyst clip. The minimum defensible scope idea deserves unpacking, because it runs against how these purchases are usually made. The standard pattern is that a SAM or ITAM business case gets built once, it has to justify the whole programme to get approved, and so it is scoped to the full ambition. Every publisher, every device class, Premier content, the lot. And that is understandable, because a small pilot is harder to get funded than a transformative programme. But look at what it does commercially. You buy your maximum scope at the moment of minimum evidence, which is the worst possible trade in any negotiation, and then you spend the term discovering which parts you actually use. What I recommend instead is buying the scope you can defend with evidence today, with the expansion priced in advance, bands or agreed rates, so that growing costs you nothing in negotiating terms. Then at renewal you arrive with real consumption data for the parts you use, and you expand into the parts you have now justified. The vendor generally accepts this more readily than buyers expect, because a smaller deal that grows predictably forecasts better than a large deal that later shrinks in a difficult renewal. Nobody enjoys a shrinking renewal, on either side of the table.
You buy your maximum scope at the moment of minimum evidence, which is the worst trade in any negotiation. That single sentence applies well beyond ITAM, and it is worth carrying into every first purchase you make on this platform. Buy what you can defend, price the expansion, then grow into it with evidence. Let's recap.
ITAM and SAM, in three sentences. Three layers and three bills, the platform underneath, ITAM on managed assets per device, and SAM on managed software publishers, with Discovery as an unbilled but entirely practical prerequisite that most buyers discover only after the data disappoints them. SAM delivered real savings in fewer than half of estates because entitlements were never reconciled against discovery, and stale data produces a green dashboard that cannot defend an audit and stops anybody looking. And device counts arrive at quote time inflated fifteen to thirty percent, Premier moves thirty to forty percent off list against a credible benchmark, and the platform layer underneath is usually the largest bill of the three while receiving the least attention. Next session, HRSD and CSM, the employee and customer workflows, with their own user metrics and the particular problem of departments onboarding mid term on dates that never match your renewal.
Homework, about an hour. One, count three ways, CMDB device records, live and unique devices, and actively managed assets, producing three numbers, and note the gaps between them because those gaps are the whole session. Two, test the SAM case, naming one publisher where SAM produced a quantified recovery in the last year, and if you cannot name one that absence is the finding, not a failure. Three, date the entitlements, finding out when entitlement records were last reconciled against discovery, and treating an old date as a false compliance position rather than as a minor hygiene issue. Four, price the layers, platform, ITAM, and SAM as three separate figures, confirming for yourself which is largest, because I suspect the answer will surprise at least some of you. And five, find a benchmark, and if Premier is on your quote or your upcoming renewal, get a credible alternative properly priced, because that is worth thirty to forty percent and it costs you a few weeks of evaluation.
Further reading, five guides. The ITAM and SAM licensing guide is today's layered model, the cost drivers, the data freshness problem, and the four renewal levers in written form. The ITAM licensing page covers the per device metric in detail, hardware asset management against software asset management, Premier content, and the benchmark effect on price. The ITOM licensing guide matters here as the prerequisite, because without accurate discovery the asset data quality collapses and the two projects are sequential rather than parallel. The rightsizing playbook covers the fulfiller seat reclamation that applies to the platform layer under both asset products, which is your biggest bill. And the products list places ITAM and SAM among the technology workflows and shows how their units differ from the rest of the catalog. That is session eighteen. Count three ways, date your entitlements, and I will see you in session nineteen for HRSD and CSM.