Most IBM customers pay support on entitlement they have stopped using, and the renewal cycle protects the spend unless someone forces the reconciliation.
Identify the entitlement that is paid for and not deployed, reclaim it before the next renewal, and reduce the support base. A methodical four phase engagement that pays for itself in the first cycle.
The renewal base is the single largest source of recoverable IBM spend.
License harvesting is the process of identifying entitlement that the customer is paying support on but is no longer using, and removing it from the support base at the next renewal. The work matters because IBM support is priced as a percentage of the entitlement, and the entitlement does not shrink unless the customer drives it down. Every IBM customer carries shelfware. Most carry it for years before anyone reconciles.
The work is not just an inventory exercise. The customer needs the deployment evidence to defend the reduction against IBM's renewal team, the contract reading to understand the reduction levers per product, and the cycle timing to land the reduction in the right window. Done badly, the customer triggers an audit by reducing entitlement IBM thinks is still deployed. Done well, the customer documents the position so cleanly that IBM has nowhere to push back.
Our work follows a four phase engagement that produces the deployment evidence, models the reduction, structures the renewal conversation, and documents the savings. See the related work on sub capacity, audit defense, and negotiation.
The categories of recoverable entitlement.
- Retired products still on the support order.
- Reduced footprint where entitlement did not follow.
- Edition over entitlement (ND where Base would cover).
- User counts that no longer reflect active users.
- Cloud Pak source entitlement that is now bundled.
- Mainframe MLC capacity above current consumption.
- Support on developer and test environments at full rates.
The four phase methodology.
Entitlement and deployment inventory
Reconcile the Passport Advantage support order against the actual deployment per product. Use ILMT, the IBM License Service, the discovery tools, and the operational evidence. Identify the candidates for reduction.
Reduction modelling
For each candidate model the contract levers, the financial saving at the next renewal, and the audit risk of the reduction. Prioritise the reductions that yield the most saving at the lowest risk.
Renewal conversation
Time the conversation with IBM's renewal team. Bring the deployment evidence and the contract reading. Defend the reduction. Document the agreed position.
Savings documentation
Document the saving against the prior renewal. Update the entitlement records. Set the operational governance to prevent the shelfware from rebuilding before the next cycle.
What the diagnostic typically surfaces.
- 10 to 30 percent of the support base is unused entitlement.
- Products retired in operations five years ago still on the order.
- ND editions paid for where Base would cover the deployment.
- User counts that have not been reconciled since the original sale.
- Cloud Pak source entitlement that has been bundled but kept on order.
- Support on environments that have been decommissioned.
- Mainframe MLC reductions that have not been claimed.
The structural reasons the base does not shrink.
- Renewals default to the prior position with annual uplift.
- Reductions require evidence that is hard to assemble.
- Reducing entitlement IBM thinks is deployed triggers audit risk.
- Internal cost owners do not feel the support cost directly.
- Decommissioning operations does not feed the licence record.
- Cloud Pak conversions do not retire the source entitlement.
- M&A activity leaves orphaned entitlement on the order.
How clients approach license harvesting.
How much saving is typical?
Across the engagements we have run the saving averages 10 to 30 percent of the support base, with outliers higher. The size depends on how long it has been since the customer last reconciled.
Does reducing entitlement trigger an audit?
It can if the reduction is not supported by evidence. The methodology produces the evidence in the right form. The audit risk is on the customer who reduces without the documentation.
When in the renewal cycle should we start?
Six to nine months before renewal. The first three months are evidence and modelling. The next three are the IBM conversation. The last two are documentation.
Can we harvest in the middle of a multi year deal?
In some contract structures yes. The lever depends on the specific clause. Most multi year deals allow a true up on renewal but not in cycle. The diagnostic identifies what is available.
What about Cloud Pak source entitlement?
The source entitlement that has been converted into Cloud Pak entitlement is often still on the support order. It should not be. The harvesting work surfaces it.
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.