Discovery and Service Mapping are where ITAM spend quietly compounds, because both meters move on their own. Servers, containers and cloud resources appear and the managed-entity count climbs; map another business service and the Service Mapping line climbs again. Neither requires a salesperson to grow. That is the buyer's problem and the negotiation's focus. The full cost picture for this layer sits in our buyer guide to ITAM and Discovery costs inside ITSM contracts.
Book a license optimization review →How is Discovery actually priced?
Discovery prices on the infrastructure it manages, not on people. Depending on the vendor and the era of your contract that is expressed as managed entities or as subscription units, but the principle is the same: the more your estate grows, the more you pay, and cloud auto-scaling means the estate can grow without anyone deciding to grow it. The count is the cost driver, so the count is what you negotiate. The detail of how managed entities and subscription units are defined and tallied is in Discovery pricing by managed entities and subscription units.
Is Service Mapping included in Discovery, or priced again?
Priced again, almost always. Service Mapping sits on top of Discovery and generally meters on the applications or business services you map, while still consuming the Discovery subscription units underneath. Buyers who assume one covers the other get a surprise at renewal when the second meter shows up at full rate. Scope Service Mapping to the services that genuinely need a mapped dependency model, not to the whole estate, because mapping everything is the fastest way to double your ITAM line.
Discovery versus Service Mapping: what you are paying for
The table separates the two meters so you negotiate each on its own terms. Rates vary by deal size, so confirm specifics against your order form.
| Dimension | Discovery | Service Mapping |
|---|---|---|
| What it does | Finds and inventories infrastructure into the CMDB | Builds dependency maps of applications and business services |
| Typical pricing basis | Managed entities / subscription units | Mapped applications or business services, plus underlying units |
| What grows the bill | Estate growth, cloud auto-scaling, more device classes | Each additional service you choose to map |
| Buyer lever | Cap the count, define the unit, control true-up | Scope to critical services only, not the whole estate |
What are the steps to negotiate both down?
Run this sequence before the vendor sets the baseline off your current, likely inflated, counts.
- Define the unit in writing. Get an exact, documented definition of a managed entity and a subscription unit so the vendor cannot re-interpret the count in its favour at true-up.
- Right-size the count. Reconcile what is genuinely under management against what is being charged, and strip retired or duplicate entities first. The method is in how to right-size Discovery subscription units.
- Cap the growth. Negotiate a ceiling and a unit rate that holds, so cloud scaling does not become an automatic price rise. CI-based caps are covered in capping CI-based pricing at renewal.
- Scope Service Mapping deliberately. Map the services that drive incident and change value, not the long tail. Each map is a line on the bill.
- Control the true-up. Agree how and when counts are reconciled, with an audit right, so you are never surprised by a number you cannot verify.
- Benchmark the rate. Anchor the per-unit and per-service price to deals of your size, so the target is evidence, not hope.
Our gated ITSM license optimization field guide includes the entity-reconciliation worksheet and the cap and true-up language we use to keep Discovery and Service Mapping from drifting upward.
Why this is worth the effort
Discovery and Service Mapping are the lines buyers under-scrutinise because they hide under the platform total and feel technical rather than commercial. That is exactly why they drift. A defined unit, a capped count and a controlled true-up turn an open-ended meter into a predictable number, and predictability is where the saving lives. Across more than 500 ITSM engagements since 2019, covering over $420M of contract value, the firm averages a 30% reduction, and the ITAM layer is one of the places it most often comes from.
When you are ready to run it, the engagement goes through our license optimization service on fixed fee or gainshare, so the fee follows the saving rather than the hours.
How does the count drift between renewals?
This is the mechanic that quietly raises the bill, so it is worth seeing in slow motion. You sign for a Discovery footprint sized to today's estate. Over the term, a cloud migration spins up ephemeral instances, a new business unit is onboarded, and auto-scaling briefly triples a workload during a busy quarter. None of that involved a purchasing decision, yet each event raised the managed entity or subscription unit count the meter records. At renewal the vendor quotes off the peak it observed, not the steady state you actually run, and you are negotiating up from an inflated number you never chose.
The counter is to control both the count and the moment it is measured. Negotiate a defined steady-state baseline rather than a peak-based one, so a transient spike does not reset your price. Agree how often the count is reconciled and insist on an audit right, so you can challenge a number you cannot verify. And reconcile your own entitlement against real Discovery data before the vendor does, which is the same discipline covered in reconciling entitlements ahead of a renewal. A buyer who walks in with a defensible steady-state count negotiates from evidence; a buyer who lets the vendor present the peak negotiates from the back foot.
Service Mapping drifts the same way, one mapped service at a time, as teams request maps for systems that never really needed them. Periodic review of which services are mapped, and retiring maps that no longer earn their cost, keeps that second meter from creeping in parallel with the first.
Frequently asked questions
- How is Discovery priced?
- On the infrastructure it manages, as managed entities or subscription units rather than per user. The count grows with your estate and with cloud scaling, so it is open-ended unless capped. Rates vary by deal size.
- Is Service Mapping priced separately?
- Usually yes. It prices on the applications or business services you map, on top of the Discovery units underneath. Treat them as two meters and scope each to real need.
- What is the biggest Discovery cost trap?
- An uncapped, usage-based count. Cloud scaling and estate growth push counts up between renewals. The fix is a negotiated ceiling, a documented counting method, and an auditable true-up.
Cap the count, not just the rate.
We define the unit, right-size the count, cap the growth and control the true-up across Discovery and Service Mapping. Fixed fee or gainshare.
Book a license optimization review →