When Savings Create Costs: The ICT Negotiation Paradox
Article contents
Introduction
A cloud provider offers a 22% discount on a three-year plan. In ICT negotiations, this is how it typically plays out: procurement closes the deal, logs the saving. Six months later, the IT department has moved to a different stack. The committed use commitments remain.
The Saving That Shifts the Problem
Aggressive negotiation in ICT contracts almost always follows the same logic: drive down the unit price, extend the commitment period, secure volume discounts. It is a measurable win — reportable, presentable, celebrated in the quarterly review.
The problem is that the unit price is only one of many variables. The others — flexibility, volume reduction options, early exit clauses, migration rights — carry real value that appears nowhere in the contract, yet materialises at exactly the wrong moment.
Those who negotiate aggressively on price almost always concede on these variables. Not out of incompetence, but because the vendor presents them as technical details rather than cost levers. And because whoever signs off on the contract evaluates the declared saving, not the potential cost of what is being given away.
The vendor already knows which flexibility clauses you will trade away to secure the discount. They frame them as standard technical details because they know that whoever approves the contract is focused on the saving, not the risk perimeter. Flexibility, volume reduction rights and migration entitlements are not details — they are the hidden cost of the discount.
The ICT Negotiation Paradox: When Savings Become a Structural Cost
The paradox works like this: the saving reduces visible spend, but increases contractual rigidity. And rigidity, in ICT environments where requirements shift every six to twelve months, is a structural cost.
It does not appear in the TCO. It does not appear in the budget. It appears when a project slips, a supplier changes, or a technology becomes obsolete — and you cannot exit without paying penalties that nobody anticipated because they seemed a remote possibility at the time of signing. It is the structural cost that never makes it into the TCO until it is too late to manage.
As I have explored when analysing cloud spend predictability, the issue is not the absolute level of expenditure but the ability to govern it over time. A negotiation that optimises price at the expense of flexibility does exactly the opposite: it makes the contract attractive on signing day and inflexible for the twelve months that follow. The same mechanism that turns unvalidated assumptions into costs that nobody had budgeted for.
A 20% saving on a rigid contract can end up costing twice as much if early exit becomes necessary. This calculation is rarely made before signing — almost always after, when the contract is already closed and the vendor knows you cannot walk away.
The CFO sees the saving. They do not see the opportunity cost of being unable to exit when the infrastructure needs to change. Nobody brings that number to the table.
How Effective Negotiators Approach It Differently
Those who have understood this dynamic approach ICT negotiations differently: they do not start from the price — they start from the risk perimeter.
Before closing a three-year contract, they ask: what happens if consumption halves in twelve months? If the primary project closes? If a better offer comes from a competitor? The answers to those questions need to be in the contract, not in the optimism of the business plan.
This does not mean walking away from discounts. It means putting them in context. In negotiations that work, procurement brings two numbers to the table — the achievable saving and the potential cost of rigidity under a changed scenario. Only when both figures are visible does the decision make sense.
Saving is a process metric, not a value indicator. A procurement function evaluated solely on declared savings has a structural incentive to negotiate aggressively on price — and concede on everything else. The problem is not who signs the contract: it is how the person who negotiates it is measured.
Saving Is a Metric. Not an Objective.
Those who use saving as a primary KPI in ICT negotiations optimise for the report, not for the business. Aggressive negotiation solves this quarter’s problem and defers it to next year — by which point the contract is already signed and the vendor knows you cannot leave.
Further Reading
Flexera 2026 State of the Cloud Report
Why can a discount on an ICT contract end up becoming a cost?
Because discounts are almost always secured by trading away flexibility: longer commitments, fixed volumes, exit penalties. If requirements change before the contract expires — and in cloud environments they often do — the contractual rigidity costs more than the discount obtained.
What are cloud committed use commitments and why are they risky?
They are guaranteed minimum spend commitments made to the provider in exchange for discounted rates. They become a problem when actual consumption falls below the committed volume: the organisation pays regardless of real usage.
How do you assess the flexibility of an ICT contract before signing?
By verifying three elements before agreeing to any discount: the conditions for volume reduction mid-contract, early exit penalties, and data migration rights without additional charges. If none of these are negotiable, the discount already has a hidden price.
Share this article