Short version: vendors quote ITAM and Discovery add-ons as a bundled annual figure, which hides the per-unit rate where the real comparison lives. The job is to break the quote down to a per managed device for SAM and a per managed entity or subscription unit for Discovery, then place that rate against what comparable buyers actually pay. A quote that "feels high" is not a negotiating position; a quote that sits above the market range for an estate your size is. The full meter context sits in our hub on ITAM and Discovery costs inside ITSM contracts.
Book a license optimization review →How do you benchmark ITAM and Discovery add-on pricing?
Five steps, in order. Skip the normalization and every later comparison is apples to oranges.
- Normalize to a per-unit rate. Divide each add-on by its true count: SAM per managed device, Discovery per managed entity or subscription unit, Service Mapping per mapped service. Now you have a rate you can compare.
- Define the unit. Confirm how the vendor counts an "entity" or "subscription unit," because two quotes at the same headline rate can differ wildly if one counts every virtual machine and the other counts hosts. The counting problem is detailed in how CMDB CI counts drive hidden ITSM cost.
- Control for volume and term. Larger estates and longer commitments earn lower per-unit rates, so only compare against deals in the same band. A small-estate rate is not a fair benchmark for a large one.
- Strip the bundle. Separate the add-on from anything bundled with it, so you are pricing the SAM or Discovery line on its own, not hidden inside a suite discount.
- Compare on negotiated, not list. List price is the vendor's opening position. Benchmark against what comparable buyers pay after negotiation, which is the only number that sets a realistic target.
What does a normalized benchmark look like?
Here is the shape of the comparison, with the variables that have to match before a benchmark is fair. The rates themselves vary by estate size, term and counting method, so the table shows the structure, not invented numbers.
| Add-on | Normalize to | Control for | What good looks like |
|---|---|---|---|
| SAM | Per managed device / node | Device count band, term | Rate at or below comparable-estate median |
| Discovery | Per managed entity / subscription unit | Entity definition, cloud sprawl, term | Defined unit plus a growth cap, not just a low rate |
| Service Mapping | Per mapped service or add-on | Services actively mapped | Scoped to live services, not the whole catalog |
Your move: build this table for your own quote, fill the rate column from the vendor's breakdown, and leave the "what good looks like" column as your target. The gap between them is your negotiation.
Where do you get reliable benchmark data?
From actual negotiated deals of the same shape, which is exactly what an independent buyer-side firm accumulates and a single buyer cannot see. You only ever negotiate your own contracts; a firm that has run 500+ engagements across 10 platforms sees the range. That is the difference between guessing and benchmarking. Our cross-platform benchmark data is summarized in the 2026 ITSM negotiation benchmark report, and the platform-specific SAM detail behind it is in what ServiceNow SAM Pro licensing actually pays for and software asset management inside Freshservice cost drivers.
Our gated 2026 ITSM negotiation benchmark report gives the per-unit ranges and the deal variables you need to set a defensible ITAM and Discovery target.
How do you turn the benchmark into a target?
Set the target at the negotiated median for your band, not at the best deal you have heard of, because an outlier is not a credible ask. Pair the rate target with a counting-method clause and a growth cap, so the saving survives the term. Then bring the evidence to the table: "for an estate of our size and term, comparable buyers pay this, and here is the data." That is what moves a vendor, and it runs the Benchmark step of our Map, Benchmark, Leverage, Close method.
Your move: write the target, the cap and the counting method into a single one-page negotiation brief before the first call, so the benchmark drives the conversation instead of getting lost in it.
What to do next
Pull your add-on quote, normalize it to per-unit rates, confirm the counting method, and place each rate against comparable-band benchmarks. Set a median-anchored target, attach a growth cap and a counting-method clause, and build the one-page brief. Then negotiate the rate and the definition together.
When you want the benchmark data and the negotiation run for you, it goes through our license optimization service on fixed fee or gainshare, no savings, no fee. We have negotiated more than $420M in ITSM contract value since 2019, and that deal history is the benchmark.
Frequently asked questions
- How do you benchmark ITAM and Discovery add-on pricing?
- Normalize the quote to a per-unit rate, define the counting unit, control for volume band and term, strip the bundle, and compare against negotiated, not list, deals of the same shape.
- What is a good per-entity Discovery rate?
- It varies by estate size, term and how an entity is counted. What matters is where your quote sits in the range for comparable buyers, with the count defined and capped.
- Why benchmark before negotiating?
- Because a target without evidence is a wish. A benchmark grounded in comparable negotiated deals is what moves a vendor off its opening rate.
Book a license optimization review.
We normalize the quote, benchmark every per-unit rate, and set a target the vendor cannot wave away. Fixed fee or gainshare.
Book a license optimization review →