The Scale of the Problem
The question is not whether some enterprises are overcharged — it is how much, and whether yours is one of them. The honest answer for most large organisations is that IT vendor overcharging is the default state, not the exception, because the conditions that produce it are everywhere. Industry analyses estimate that roughly 25% of every SaaS dollar is wasted, somewhere between $60 billion and $100 billion globally each year, and Zylo's 2026 SaaS Management Index puts unused licences at around 43% of the average enterprise estate — costing a large organisation an average of about $80 million annually. A further 45% of applications are used at less than half their licensed capacity.
Crucially, most of this is not fraud. It is a governance gap that vendors are commercially incentivised to leave open. The same index found that IT controls just 15% of SaaS spend and 13% of application ownership, which means the majority of purchasing happens in the business, without benchmarks or central oversight — exactly the conditions in which a vendor's price drifts above the market without anyone noticing. Closing that gap is the central discipline of our enterprise software pricing pillar, and it starts with recognising the warning signs.
The Nine Red Flags
Overcharging shows up as a pattern of small signals rather than one obvious error. The following nine are the ones that, in our engagements, most reliably indicate that you are paying above the fair market rate.
| Red Flag | What It Signals | The Fix |
|---|---|---|
| No benchmark data | You cannot prove your price is fair | Obtain transaction benchmarks |
| High shelfware (>20% unused) | Paying for capacity you do not use | Utilisation audit + reduction |
| Uncapped renewal uplift | Compounding above-market increases | Negotiate an indexed cap |
| First offer = "best price" | Quote anchored at top of range | Counter with benchmark position |
| Forced bundling | Paying for unneeded products | Unbundle and price separately |
| Audit-then-upsell timing | Compliance used as a sales lever | Challenge methodology |
| Auto-renewal lock-in | No window to renegotiate | Diarise notice dates early |
| Edition you cannot downgrade | Premium tier with no exit | Right-size at renewal |
| Opaque consumption billing | Overage without visibility | Demand real-time monitoring |
The single most important of these is the first: the absence of benchmark data. If you cannot show what comparable enterprises — same size, same industry, same region — pay for the identical product, you have no way to know whether your price is fair, and that blind spot is precisely where overcharging lives. Everything else on the list is easier to argue once you can. The methods for closing it are set out in our guide to IT contract benchmarking, and the way vendors construct the prices you are benchmarking against is covered in how vendors calculate your discount.
If you cannot state what a comparable enterprise pays for the same product, you are not negotiating — you are accepting. With 43% of licences typically unused, the question is rarely whether there is overspend, only how much.
The Flags That Hide in Plain Sight
Three of the nine reward particular attention because they operate quietly. Auto-renewal lock-in removes the window in which you would otherwise renegotiate: a contract that rolls over automatically unless cancelled 60 or 90 days out leaves you paying last year's inflated rate by default, so diarising the notice date a full quarter early is a basic control. The edition you cannot downgrade is a close cousin — an E5-style premium tier sold on features a minority of users touch, with no contractual path to step down at renewal, locking in a premium that utilisation data rarely justifies. And opaque consumption billing is the newest, as usage-metered AI and cloud services bill for tokens, calls or agent runs without giving the buyer real-time visibility, so overage accrues unseen until the invoice lands.
What unites all three is that none looks like overcharging in the moment; each looks like a routine term you accepted. That is precisely why they persist. The defence is the same in every case: insist on a renegotiation window, a documented downgrade right, and live usage monitoring before signing, so the contract cannot quietly reprice you between one renewal and the next.
When the Audit Is the Sales Tool
A particular form of overcharging deserves its own warning, because it is dressed up as compliance. Software audits are sometimes used less to verify entitlement than to manufacture a sales event — and the structure encourages it. Where auditors are compensated in relation to the size of the compliance gap they identify, there is a direct incentive to adopt conservative assumptions and produce a finding larger than the underlying reality, which is then conveniently resolved by purchasing the products or editions the vendor was already trying to sell. The tell is timing: an audit that lands shortly before a renewal, or one whose findings map neatly onto the vendor's current upsell, should be treated as a negotiation, not a settled debt.
A licence audit finding is an opening position. It can and should be challenged on its methodology, its measurement window, and its interpretation of ambiguous licence metrics — the same disciplines we apply through the vendor audit defence practice. Enterprises that engage audit findings as a commercial dispute, rather than paying them as an invoice, routinely settle for a fraction of the headline number. Treating the audit as overcharging-in-progress, rather than a neutral fact, is the mindset shift that protects the budget.
How to Recover the Overspend
Recovering overspend is a sequence, not a confrontation. Begin with an internal utilisation audit to quantify shelfware in hard numbers — which licences are assigned but inactive, which editions are over-specified, which products have zero adoption. Pair that with current benchmark data establishing the fair market price for what you genuinely use. Together these convert a suspicion into evidence, and evidence is what moves a vendor. Then raise reductions and price corrections proactively at the next renewal, because vendors almost never volunteer them, using the leverage analysed in our guide to the renewal versus replacement lever.
Finally, close the gap so it does not rebuild. Cap future uplifts against a published index, secure the right to reduce quantities and downgrade editions at each renewal, and demand real-time visibility into any consumption-based billing. The recovery is rarely a one-off refund; it is a lower, benchmarked, capped baseline that compounds in your favour for the rest of the relationship. Our Price Benchmarking Report tracks effective vendor pricing so you can spot the gap, and the Oracle vendor hub illustrates how audit-driven overcharging works in practice. To have your largest contracts benchmarked for overcharging, request a confidential briefing.