How to Quantify ESM Shelfware Across Workflows

Most enterprise service management contracts grow faster than adoption. A platform bought for IT is extended to HR, then customer service, then facilities and legal, and each extension provisions fulfiller seats and premium add-ons ahead of the people who will use them. The result is shelfware that hides inside a healthy-looking platform total. This article sets out the buyer-side method to measure it precisely, workflow by workflow, so the number you bring to a renewal is evidence rather than an estimate. For the wider commercial picture, start with the buyer guide to ESM expansion pricing.

What exactly is ESM shelfware?

Shelfware is capacity you pay for and do not use. In an ESM estate it takes three forms: idle fulfiller seats (agents licensed in a workflow with no ticket activity), unused add-ons (pro or premium feature packs attached to seats that never invoke them), and dormant modules (whole workflows or apps licensed but not in production). Keep these three categories separate. They carry different list mechanics, and a vendor will concede an idle-seat reduction faster than a module cancellation.

Draw a hard line between shelfware and underuse. A seat with no activity in the measurement window is shelfware and should be reclaimed. A seat used occasionally is underuse and is an argument for tier downgrade or reclassification, not removal. Conflating the two weakens both asks.

Why measure shelfware per workflow, not platform-wide?

A single platform-wide utilization figure is the vendor's friend. It blends a busy IT service desk running at high utilization against an HR or facilities workflow rolled out months ago and barely touched, and the average lands at a comfortable-looking number that conceals the idle seats. Measuring per workflow is what surfaces them.

The pattern is consistent: the workflows added most recently and rolled out fastest carry the highest idle rates, because seats were provisioned on a plan rather than on observed demand. That is also where a vendor has the least defensible position when you present activity data.

How do you quantify it, step by step?

Run this sequence once per workflow, then consolidate. It is the Map and Benchmark phases of our method applied to a single question: how many seats and add-ons have no activity?

1. Pull the entitlement. List every licensed fulfiller seat, add-on pack and module per workflow from the order form, not the admin console, so you are measuring against what you pay for.
2. Pull 90 days of activity. Export login, ticket-touch and feature-invocation logs per seat. Ninety days catches monthly and most quarterly cycles; extend to 180 if the workflow has seasonal rhythms.
3. Classify each seat. Tag every seat as active, underused, or idle against the activity export. Idle equals zero qualifying activity in the window.
4. Separate add-ons from seats. A seat can be active while its premium add-on is never invoked. Count add-on shelfware independently, since it is often a richer reclaim than the seat itself.
5. Convert to money. Multiply idle counts by the per-unit rate on your order form. Where a rate is bundled and not itemized, flag it as a line to unbundle in negotiation rather than guessing the value.
6. Build the reclaim target. Sum idle seats, idle add-ons and dormant modules into one defensible figure, with the activity export as the proof.

What do you do with the number once you have it?

A quantified shelfware figure is a renewal lever, and its value depends on timing. Most subscriptions lock quantity for the committed term, so the reliable reclaim point is renewal or a co-termination event, not the middle of a term. Quantify early, then stage the reclaim for the next quantity reset. The exception is a contract carrying a documented true-down or swap right, where mid-term reduction is contractually available.

Sequence the reclaim with the rollout itself so you never re-buy what you just cut. The staging discipline is set out in how to stage an ESM rollout to protect your budget. When the count is built and the timing is set, the engagement runs through our contract negotiation service on fixed fee or gainshare, so the reclaim either lands or it costs you nothing.

What to do next

Pick the workflow you expanded most recently, pull 90 days of activity against its order-form entitlement, and classify every seat as active, underused or idle. That single workflow usually produces the first credible reclaim figure and proves the method before you scale it across the estate. Then repeat per workflow, consolidate, and time the reclaim to your next renewal.

Frequently asked questions

What counts as ESM shelfware?

ESM shelfware is any licensed fulfiller seat, pro or premium add-on, or workflow module with no measurable activity over a defined window, typically 90 days. It is distinct from low usage: a seat used once a quarter is underused, a seat never used is shelfware. Measure both, but separate them, because they justify different asks.

Why measure shelfware per workflow rather than platform-wide?

A blended platform utilization figure averages a busy IT desk against an idle HR or facilities rollout, hiding the idle seats inside the average. Per-workflow measurement isolates where the waste sits, which is where the negotiation leverage is. It also matches how vendors price, since each workflow is often a separate SKU.

How much ESM shelfware is typical?

It varies by deal size and how aggressively the platform was expanded. Idle rates are usually highest in workflows added last and rolled out fastest, where seats were provisioned ahead of adoption. Confirm your own count against usage logs rather than assuming an industry figure.

Can you reclaim shelfware mid-term or only at renewal?

Most subscription terms lock quantity for the committed period, so the reliable reclaim point is renewal or a co-termination event. The exception is a contract with a documented true-down or swap right. Quantify shelfware early so the reclaim is staged for the next quantity reset.