Why List Price Is the Wrong Benchmark
IT spend benchmarking begins by discarding the benchmark most enterprises rely on: the vendor's list price. Enterprise software is not priced on a cost-plus basis; it is priced by market segmentation, with each customer charged what the vendor believes they will accept based on account history, switching cost, and urgency. A discount off list, in that world, is meaningless — a 40% discount off an inflated list is worse than a 10% discount off a keen one. The only reference point that tells you anything is what comparable enterprises actually pay for the same product, and that figure is precisely the one vendors work hardest to keep out of your hands.
This matters more every year. With software spend growing roughly 14.7% in 2026, the gap between a benchmarked price and a list-anchored one compounds across the portfolio. Benchmarking is the second pillar of a complete enterprise IT contract strategy — the discipline that converts negotiation from an argument about list discounts into a comparison against market reality.
The Ratios That Matter
Benchmarking operates at two levels. The macro level uses ratios to sense-check overall spend. The cross-industry average is about 3.6% of revenue, but the useful figures are sector-specific: manufacturing typically runs 1–3%, healthcare 3–5%, and banking and financial services 7–10%. Within the budget, cloud services account for roughly 30% (up to 50% in cloud-forward organisations), security around 10% (12–15% in regulated sectors), and infrastructure 20–25%. These ratios will not win a negotiation, but they reveal where an estate is an outlier and therefore where to look.
Ratios tell you where to dig; unit prices tell you how much to ask for. A benchmarking programme that stops at the percentage-of-revenue level has done the easy half and skipped the half that moves money.
The ratios also frame the board conversation, because a board understands an outlier far faster than a SKU — the link to board-level IT spend reporting is direct. But ratios are a diagnostic, not a lever.
The ratios are also easy to misread without context, which is why they must be paired with trend and mix. An enterprise spending 4% of revenue on IT might be efficient or wasteful depending entirely on what that 4% buys: if cloud has crept from 30% to 50% of the budget through unmanaged consumption rather than deliberate migration, the ratio looks stable while the underlying position deteriorates. Benchmarking that stops at a single year's percentage misses exactly this kind of drift. The useful diagnostic compares the ratio over time and against sector peers simultaneously, so that a number which looks reasonable in isolation reveals itself as an outlier once direction and composition are taken into account.
Internal vs External Benchmarking
The lever is comparison, and it comes in two forms. Internal benchmarking compares your own units — cost per seat across business units, price paid for the same product in different regions, this renewal against the last — and it is free, because you already own the data. It routinely surfaces inconsistencies worth reclaiming, particularly across a sprawling SaaS estate where 25–30% of licences typically go unused. External benchmarking compares you against the market, and it is harder because the data is not public; it requires advisors who track transaction data, benchmarking consortia, or independent reports. The two are complementary: internal benchmarking finds the waste, external benchmarking sets the target, and together they feed IT budget planning and contract optimisation.
Per-Unit Price Benchmarking
The benchmark that actually moves a renewal is per-unit price: what a comparable enterprise pays per seat, per core, per gigabyte, or per transaction for the identical product. This is granular, vendor-specific work — the price of an M365 E5 seat, an Oracle processor licence, a cloud commitment tier — and it is where independent benchmark data earns its keep, because it lets you tell a vendor not merely that their price is high but that it is high by a specific, evidenced margin against named comparators. Our Price Benchmarking Report and the vendor-by-vendor positions across our vendor intelligence hub are built for exactly this purpose.
Turning Benchmarks Into Leverage
A benchmark only becomes leverage when it is deployed. Presented well — as evidence that the vendor's proposal sits a defined margin above what comparable enterprises pay — benchmark data reframes the negotiation from a discussion about discount percentages into a demonstration of overpayment, and it is the foundation on which the tactics in vendor negotiation are built. Benchmarking also informs risk, because a price far above market is itself a flag in the IT vendor risk management framework. The enterprise that benchmarks before it signs negotiates from evidence; the one that does not negotiates from hope. If you do not know how your largest commitments compare to the market, request a confidential briefing and we will benchmark them against what comparable enterprises actually pay.