Mistake #1: Letting Contracts Auto-Renew
This is the most widespread and costly mistake. The majority of IT contracts (software licenses, SaaS subscriptions, support agreements) contain auto-renewal clauses. If the organization fails to notify the publisher or vendor within a specified period — typically 30 to 90 days before expiry — the contract is renewed under the same terms, sometimes with a built-in price increase.
The real cost: an auto-renewal eliminates all negotiation leverage. The organization loses the ability to renegotiate pricing, reduce volumes, re-tender to competitors or migrate to an alternative. On a $500,000 contract, failing to renegotiate can mean $50,000 to $125,000 in missed savings — 10 to 25% of contract value.
How to avoid it: implement a centralized contract registry with automated alerts 6 to 12 months before each renewal date. This is exactly the type of tool that a structured IT contract management practice enables. Renegotiation preparation should begin at minimum 6 months before expiry for strategic contracts.
Mistake #2: Entering Negotiations Without Knowing Your License Position
Too many organizations enter contract negotiations with a publisher without knowing their ELP (Effective License Position) — the precise comparison between licenses owned and software actually deployed.
The real cost: without an ELP, you negotiate blind. You do not know whether you have over-licensing (you pay for unused licenses, giving you a reduction lever) or under-licensing (you are non-compliant, and the publisher can use this as pressure). Microsoft, Oracle and SAP are expertly trained to exploit this information asymmetry.
How to avoid it: conduct a SAM (Software Asset Management) audit before any major contract negotiation. The ELP gives you a clear view of your position and transforms negotiation from a defensive exercise into a strategic initiative. Nexus Conseils TI recommends calculating the ELP at minimum 6 months before an Enterprise Agreement renewal.
Mistake #3: Ignoring Price Escalation Clauses
Many IT contracts contain price escalation clauses — mechanisms for automatic price increases each contract year or at each renewal. These clauses are often buried in general terms and go unnoticed during signing.
The real cost: a 3 to 5% annual escalation clause, applied over a 3-year contract, can increase total cost by 9 to 16% over the initial price. On a $1 million contract, this represents $90,000 to $160,000 in cumulative overcharges.
How to avoid it: during negotiation, demand a price cap or negotiate fixed pricing for the contract duration. If the publisher refuses, negotiate a penalty-free termination right if the increase exceeds a defined threshold. Every clause in every contract must be read, analyzed and negotiated.
Mistake #4: Underestimating Publisher Audit Risk
Major software publishers — Microsoft, Oracle, SAP, Adobe, IBM — have contractual rights to audit their customers' compliance. These audits are increasingly frequent and the financial consequences of non-compliance can be severe.
The real cost: an Oracle audit revealing unlicensed database deployments can generate a regularization bill exceeding one million dollars. A Microsoft audit may reveal non-compliant Microsoft 365 or Azure usage. Beyond direct financial cost, an audit creates significant operational disruption and a weakened position in future negotiations.
How to avoid it: maintain an up-to-date SAM compliance position at all times. Anticipate audits by conducting regular self-assessments. Have a documented and tested audit response plan. If you receive an audit notification, engage an independent firm immediately to support and defend your interests — never handle a publisher audit alone.
Mistake #5: Signing Without Understanding Licensing Metrics
Major publishers' licensing models are extraordinarily complex. Microsoft offers per-user, per-device, per-processor-core and subscription licenses, with multiplexing rules and downgrade rights. Oracle applies processor-based license metrics that depend on processor type and a weighting factor ("processor core factor"). SAP uses metrics based on user types (Named User, Engine) with indirect access rules.
The real cost: misinterpreting licensing metrics can create unintentional non-compliance that is only discovered during an audit. Oracle's indirect access concept ("multiplexing") is one of the costliest traps: any third-party application accessing an Oracle database may require additional licenses, even if end users never access Oracle directly.
How to avoid it: never sign a contract with a major publisher without expert analysis of the licensing metrics. Microsoft Product Terms, Oracle License Definitions and SAP Named User Licensing Rules must be analyzed by specialists. An investment of a few thousand dollars in consulting can prevent hundreds of thousands of dollars in audit penalties.
Mistake #6: Neglecting Exit and Portability Clauses
In the rush to sign, many organizations neglect exit clauses and data portability provisions. Yet at the moment of signing — when the vendor wants to close the deal — negotiation power is at its maximum.
The real cost: without a clear exit clause, switching vendors becomes prohibitively expensive. Vendor lock-in is one of the most underestimated strategic risks in IT. The migration cost from an SAP ERP to an alternative, for example, can reach 3 to 5 times the annual contract cost if no portability clause was negotiated.
How to avoid it: systematically negotiate early termination clauses with reasonable conditions, data portability in standard open formats, and transition periods with outgoing vendor support. Maintain an up-to-date exit plan for each strategic vendor, including identification of alternative suppliers.
Mistake #7: Managing IT Contracts in Silos
In many organizations, IT contracts are managed by different teams without coordination: procurement negotiates pricing, IT defines technical requirements, legal validates contractual clauses, and finance manages budgets. This fragmentation creates dangerous blind spots.
The real cost: lack of coordination between stakeholders leads to sub-optimal decisions: procurement negotiating volume discounts without IT having validated actual needs, contractual commitments that contradict the company's cloud strategy, renewals that fail to account for ongoing migration projects.
How to avoid it: establish cross-functional contract governance involving IT, procurement, finance and legal. Appoint a dedicated IT contract manager (or engage an external firm) to coordinate all stakeholders and maintain an overall view of the contract portfolio. This is the role Nexus Conseils TI plays for its clients.
Need expert support?
Free, no-obligation initial consultation with our IT governance experts.
Free consultation →