Most ITSM line items track users. Discovery does not, and that catches finance teams that budget it like a seat-based product. Because the meter follows infrastructure, the bill grows with cloud sprawl, virtual machine churn and every decommissioned host that nobody removed from the CMDB. The cluster context for this sits in our buyer guide to ITAM and discovery costs inside ITSM contracts; this page is the unit-level view.
What is a managed entity?
A managed entity is an item Discovery finds and keeps current in the CMDB: a physical or virtual server, a network device, a storage array, a cloud resource. Subscription units are the currency you buy, and different entity types can draw different amounts of those units. That is the detail that matters for forecasting, because it means the mix of your estate drives the bill as much as the raw count. An estate weighted toward cloud resources prices differently from one weighted toward network hardware, even at the same headline entity number.
How do subscription units translate into cost?
You buy a pool of subscription units, and your discovered entities consume from it according to type. The exact unit ratio per entity type and the price per unit both vary by contract, so any ratio you are quoted should be confirmed against your own order form rather than treated as a standard. What does not vary is the direction: discover more, or discover heavier entity types, and you draw down the pool faster. When the pool is exhausted, you are into a true-up or an expansion, both negotiated from a weaker position than the original deal.
| Cost driver | Why it grows | Buyer-side control |
|---|---|---|
| Entity count | Every discovered device draws units | Discover only what the CMDB genuinely needs |
| Entity mix | Heavier types consume more units | Forecast by type, not headline count |
| Stale CIs | Decommissioned items stay in scope | Reconcile and retire before renewal |
| Cloud churn | Ephemeral resources inflate counts | Scope cloud discovery deliberately |
| Per-unit price | Uncapped at expansion | Cap the unit rate and growth uplift |
How do you control Discovery cost at renewal?
Reconcile before you renew. Pull the discovered entity list, separate what the CMDB genuinely needs to manage from what is being swept up by default, and retire decommissioned and duplicate items so they leave the unit count. Then forecast growth by entity type rather than a flat percentage, cap the per-unit price, and tie any expansion to a pre-agreed rate so a cloud migration does not become an uncapped true-up. The reconciliation method is in how to right-size Discovery subscription units, and the way CMDB counts ripple into other line items is in how CMDB CI counts drive hidden ITSM cost.
This is the License Optimization discipline applied to infrastructure rather than seats. Across more than 500 engagements and $420M-plus in ITSM contract value, the 30 percent average reduction comes from matching what you pay for to what you actually use, and Discovery is one of the clearest cases because the gap between discovered and needed is usually large and rarely audited. The platform-level context sits on the ServiceNow platform page.
Our ITSM license optimization field guide includes the entity reconciliation worksheet and the unit-cap language we use on Discovery renewals.
What to do next
Before your next ServiceNow renewal, reconcile the discovered estate against genuine CMDB need, forecast by entity type, and bring a unit-rate cap to the table. The earlier you do it, the more of the discovered-versus-needed gap you can remove before the vendor sets a baseline off the inflated count. When you are ready to run that reconciliation and the negotiation, the work runs through our license optimization service on fixed fee or gainshare.
Book a license optimization review.
We reconcile discovered entities to genuine CMDB need, forecast units by type, and cap the per-unit price before renewal. Fixed fee or gainshare.
Book a license optimization review →Frequently asked questions
- How is Discovery priced?
- On subscription units tied to managed entities, not user seats. Cost scales with the number and type of devices and cloud resources you discover. The unit ratio per entity type varies by contract; confirm it on your order form.
- What is a managed entity?
- An item Discovery finds and maintains in the CMDB, such as a server, network device or cloud resource. Different types consume different unit amounts, so estate mix drives the bill, not just the count.
- How do you control the cost at renewal?
- Reconcile discovered entities to genuine need, retire stale and duplicate items, cap the per-unit price and growth uplift, and scope discovery to real CMDB requirements rather than discovering everything by default.