A 4,000-seat enterprise we will call typical opened a renewal believing it had little room to move. Then the ITAM team pulled last-login data and found nearly a fifth of the fulfiller seats had not been touched in ninety days, two reporting modules were live on the contract but used by a single team, and the discovery tool was billing for more managed entities than the CMDB actually tracked. None of that was visible in the vendor's renewal quote, because the quote was built off entitlement, not usage. The data did not just trim the number. It changed who was setting the baseline.
How does ITAM data create leverage?
It creates leverage by replacing opinion with evidence. Vendors quote renewals off your current entitlement plus an uplift, and that entitlement is almost always larger than your real need. Without data, your only move is to ask for a discount off the vendor's number, which means you are negotiating on their baseline. With ITAM and discovery data, you rebuild the baseline from what is actually used, and every gap between entitlement and usage becomes a line you can challenge with proof. This is the core discipline in our buyer guide to ITAM and discovery costs inside ITSM contracts.
Book a license optimization review →What ITAM evidence matters most at renewal?
| Evidence | What it challenges | The buyer move |
|---|---|---|
| Last-login and activity by seat | Inflated fulfiller and agent counts | Reclassify or remove dormant seats before the quote |
| Module usage by team | Tier or add-ons carried for a few users | Drop or re-scope modules with no broad usage |
| Discovered assets and CIs vs billed | CI or managed-entity counts above reality | Reconcile billed units to discovery data |
| Tool overlap | Paying twice for the same capability | Consolidate and reclaim the duplicate spend |
Each row is a place where the vendor's number and your reality diverge, and each divergence is leverage you can document. The CMDB counting question in particular is worth its own attention, which is why we cover capping it in CMDB cost control: capping CI-based pricing at renewal.
How do you turn the data into a number?
- Reconcile entitlement to usage. Line up what you pay for against what last-login, module and discovery data show is used.
- Quantify the shelfware. Put a dollar figure on the dormant seats, unused modules and over-counted assets, so the gap is concrete.
- Build the defensible target. Your ask is the reconciled need plus a sensible buffer, not an arbitrary discount.
- Stage the evidence. Decide what you show and when, so the data anchors the conversation before the vendor sets its baseline.
- Protect it with terms. Lock a capped uplift so the reclaimed savings do not erode by the next cycle.
The reconciled-need step is the foundation of an effective license position, which we walk through in how to build an effective license position before an ITSM renewal.
Our gated ITSM License Optimization Field Guide includes the reconciliation worksheet and the shelfware-quantification model that turn ITAM data into a costed renewal target.
When should you pull the data?
Six to nine months before renewal. That runway is what lets you reconcile the data, reclaim the obvious shelfware operationally, and assemble a defensible target before the vendor opens the conversation. Pulled in the final weeks, the same data only tells you how much you overpaid. Pulled early, it sets the agenda. Across more than 500 ITSM engagements we average a 30% reduction, and the engagements that hit it almost always start with usage data, not with a discount request.
What to do next
Pull last-login, module usage and discovery counts now, reconcile them against your entitlement, and quantify the gap. If you want a buyer-side team to build the license position and run the renewal on the evidence, the engagement runs through our license optimization service on fixed fee or gainshare.
Frequently asked questions
- How does ITAM data create leverage?
- It replaces the vendor's entitlement baseline with evidence of real usage. Show which seats, modules and assets are actually used, and you negotiate down from the truth rather than from the inflated quote.
- What evidence matters most?
- Last-login and activity by seat, module usage by team, discovered assets and CIs versus what you are billed for, and overlap between tools doing the same job. Each is a line you can challenge with data.
- When should you pull the data?
- Six to nine months out, so there is time to reconcile it, reclaim shelfware and build a defensible target before the vendor sets a baseline.
Turn data into leverage.
We reconcile your ITAM and discovery data, quantify the shelfware, and build the costed target that anchors the renewal. Fixed fee or gainshare.
Book a license optimization review →