Right-size ServiceNow Discovery by sizing subscription units to live, scanned IP addresses rather than to your theoretical network maximum or your raw CMDB. Discovery is metered in subscription units tied to the infrastructure it scans, so the single biggest source of overspend is buying units for addresses that are unused, decommissioned or duplicated. As of 2026 pricing the unit definition varies by deal size and should be confirmed against your order form, but the method to avoid over-buying does not change: measure what is actually live, then license that.
What are Discovery subscription units?
Discovery subscription units are the metric ServiceNow uses to price how much infrastructure you are licensed to scan and maintain in the CMDB. The exact mapping of units to devices or IPs varies by agreement, so the first move is always to confirm your own definition rather than assume the market standard. What is consistent is that the unit count is the price, and the count is easy to inflate by sizing against a network that is larger on paper than in reality.
How do you right-size Discovery subscription units?
Five steps take the count from theoretical to defensible.
- Pull the live scan data. Start from what Discovery actually finds responding on the network, not the full allocated address space.
- Strip the dead weight. Remove decommissioned hosts, duplicate records, and reserved ranges that never resolve to a real device.
- Separate cloud from on-premise. Ephemeral cloud instances and on-premise hardware behave differently under the meter, so size them on their real lifecycle rather than a static count.
- Reconcile against the CMDB. Align the unit count with the cleaned asset estate so you are not licensing scan capacity for assets you no longer run.
- Size the cap to growth, not to maximum. Buy for realistic in-term growth with a pre-agreed expansion rate, not for the largest the estate could ever be.
| Sizing basis | What it counts | Effect on the bill |
|---|---|---|
| Allocated address space | Every possible IP, used or not | Largest count, biggest overspend |
| Raw CMDB records | All historical assets, including retired | Inflated by uncleaned data |
| Live scanned devices | What actually responds on the network | Defensible, lowest justified count |
What does the vendor argue, and what do you counter with?
ServiceNow will size Discovery against the broadest reasonable view of your estate, because a larger count is a larger subscription. Counter with live scan evidence and a reconciled CMDB, and insist that the unit definition is written into the order form so it cannot drift. Where the estate is genuinely growing, negotiate a capped expansion rate rather than buying headroom up front, so you pay for growth as it arrives. The asset side of this pairs with ServiceNow HAM Pro and hardware asset management costs, and both sit under the buyer guide to ITAM and Discovery costs.
Our License Optimization Field Guide includes the Discovery unit worksheet that drives this right-sizing.
What to do next
Export your live scan data before the renewal conversation and build the unit count from what responds. That single exhibit reframes the negotiation from the vendor's estimate to your evidence, which is where the saving lives. When you want it sized and negotiated, our license optimization service runs it on fixed fee or gainshare.
Frequently asked questions
- How are ServiceNow Discovery subscription units counted?
- They are tied to the infrastructure Discovery is licensed to scan, with the exact mapping varying by agreement. Confirm your own unit definition against the order form, then size it to live scanned devices rather than allocated address space.
- How do I avoid over-buying Discovery units?
- Size to live scan data, strip decommissioned and duplicate records, separate cloud from on-premise lifecycle, reconcile against a cleaned CMDB, and buy for realistic in-term growth with a capped expansion rate rather than for the maximum estate.
- Why is my Discovery bill higher than expected?
- Usually because units were sized against allocated address space or an uncleaned CMDB rather than live scanned devices. The gap between possible and actual addresses is overspend you can remove with evidence.
Size to what responds.
We build the Discovery unit count from live scan data and negotiate a capped expansion rate so you stop paying for dead address space. Fixed fee or gainshare.
Book a license optimization review →