How to use this assessment: How to use this assessment: Work through each item and mark it complete once confirmed. Items flagged High Risk represent the most common sources of material overspend. A score of 15 or more indicates a well-governed position.

Scoring Guide
Tally your confirmed items to determine your renewal readiness before engaging your vendor.
0 – 9 Not Renewal Ready
10 – 14 Partially Prepared
15 – 20 Renewal Ready

Section 1: Renewal Timeline and Preparation

Starting your renewal preparation at least 6 to 9 months before contract expiry provides the critical runway needed to conduct usage audits, assemble stakeholders, benchmark pricing, and develop negotiation strategy. Most enterprises fail at this stage, scrambling in the final 60 days when vendors have maximum leverage. Early preparation shifts the balance of power back to the buyer.

1. You have identified your exact renewal date and initiated your internal preparation process at least 6 months in advance.
Enterprises that begin preparation 6 to 9 months before expiry secure 15 to 25 percent better pricing and contract terms than those negotiating in the final 90 days. Late starts prevent you from exploring alternatives, gathering complete usage data, and aligning stakeholders across IT, finance, legal, and procurement. Set a calendar reminder 180 days before expiry and immediately convene your renewal committee to establish timeline, assign owners, and define success metrics for the negotiation.
● High Risk
2. You have assembled a cross-functional renewal committee including IT, finance, legal, and procurement with documented roles and decision authorities.
Siloed renewals lead to missed cost savings and weak contract protections. Your renewal team must include IT to define usage needs and technical requirements, finance for budget and payment terms, legal for audit protection and exit rights, and procurement for vendor relationships and negotiation tactics. Document RACI assignments so decisions do not stall on ambiguous ownership. Single-threaded sponsorship from the CFO or CIO significantly improves negotiation outcomes by creating executive authority behind key decisions.
● High Risk
3. You have conducted a detailed software asset inventory and usage analysis for the past 12 months, with usage reports by department and user group.
You cannot negotiate effectively without knowing what you actually use. Deploy SAM tools to capture licence entitlements versus actual deployment and usage. Identify unused or underutilised applications — 46 percent of enterprise licences are unused, a fact vendors exploit by inflating renewal quantities. Document the delta between licensed seats and active users; this becomes your negotiation anchor. Attach usage reports to your position paper and share selectively with competing vendors to pressure pricing.
● High Risk
4. You have reviewed the prior contract and documented expiry date, pricing escalations, auto-renewal clauses, audit provisions, and any material terms that changed unfavourably in the last agreement.
Most enterprises sign contracts without a thorough prior-term review; vendors exploit this by introducing hidden escalations and auto-renewal traps. Audit your current agreement for price escalation percentages typically running 2 to 5 percent annually, auto-renewal language, and audit frequency and scope. Check whether you have exit rights or termination for convenience clauses. Identify underused provisions such as professional services and training tiers that you can trim or renegotiate. This historical analysis is your baseline for worst-case renewal terms.
● Medium Risk
5. You have conducted internal stakeholder interviews with department heads and application owners to validate ongoing business need and identify candidates for reduction, consolidation, or discontinuation.
Renewal is your opportunity to eliminate shelfware and right-size your stack. Meet with finance, HR, marketing, engineering, and other major user departments to confirm which applications remain mission-critical and which are legacy or low-adoption. Identify consolidation opportunities such as migrating from three single-use tools to one integrated platform. Document business cases for any planned reductions so vendors cannot negotiate back in deprecated tools. Expect 10 to 20 percent of your current licensing footprint to be candidates for reduction.
● Medium Risk

Section 2: Licence Rightsizing and Usage Review

Licence rightsizing is where enterprises recover the most value in renewals. By removing shelfware, right-sizing seat counts to actual usage, and eliminating unnecessary features or service tiers, you can reduce your licence footprint by 15 to 30 percent while maintaining full coverage for active users. This section ensures you have conducted the forensic analysis needed to negotiate confident reductions.

6. You have identified and documented all unused or abandoned licences including shelfware, with cost impact calculated and an elimination plan in place.
The industry average shelfware rate is 18 percent, but poorly managed enterprises see 25 to 35 percent unused licensing. Use your SAM tool to flag licences with zero activity over the past 12 months, abandoned seats in departments that have downsized, and legacy applications with no active users. Calculate the annual cost of shelfware and present it to your vendor as a reduction target during renewal. Vendors would rather keep you as a customer at lower cost than lose you to a competitor over excessive pricing for unused capacity.
● High Risk
7. You have performed user-adoption and utilisation analysis by role and department, identifying over-licensed and under-licensed groups.
Licence distribution is often misaligned with actual usage. Your SAM data should show which departments are at 30 percent capacity utilisation while others are at 120 percent, indicating shared or unlicensed usage. Use this intelligence to propose tiered licensing: enterprise users with full features, power users with mid-tier licences, and casual users with low-cost access. Many vendors offer usage-based pricing or metered licensing tiers; request these options in your renewal position paper.
● Medium Risk
8. You have calculated the total cost of ownership including software, support, professional services, training, and infrastructure costs, and identified efficiency gains or modernisation opportunities.
Most enterprises view renewal as a line-item cost covering software plus support but ignore indirect costs: infrastructure to run the software, staff time for updates and administration, professional services for integrations, and training spend. Calculate your total TCO for the past two years including vendor invoices, internal labour, and third-party integration costs. Modernisation often reduces TCO; migrating from on-premise to SaaS may reduce infrastructure costs by 30 percent. Include TCO reduction as a success metric in your renewal strategy, not just price.
● Medium Risk
9. You have mapped feature and service tier utilisation to current licence allocation, identifying over-provisioned features or support levels that can be eliminated.
Vendors maximise pricing by selling premium tiers such as advanced support, premium features, and consulting hours that many customers never use. Audit your current agreement: are you on 24/7 critical-response support when business-hours coverage is sufficient? Are you licensed for advanced features when standard features meet your needs? Are you paying for on-site professional services when remote delivery is acceptable? Propose step-downs in non-core tiers during renewal. Vendors often accept feature and support reductions if licence quantity stays flat.
● Medium Risk
10. You have modelled three scenarios covering conservative full renewal at current scale, moderate reduction through shelfware elimination, and aggressive reduction through consolidation and tier optimisation.
Present your vendor with multiple renewal scenarios rather than just one ask. This gives you negotiating flexibility and shows the vendor the range of possible outcomes. Your conservative case is your walk-away position; your aggressive case is your opening. Model pricing for each scenario using the vendor's stated rate cards. If the vendor cannot offer meaningful discounts to move you from conservative to moderate or aggressive, you have leverage to explore competitors who can meet your target.
● Medium Risk

Section 3: Pricing Validation and Benchmarking

Most enterprises renew software without benchmarking pricing against market rates or recent deals by comparable organisations. Vendors count on information asymmetry — they know market rates, you do not. By acquiring benchmark data, requesting competitive quotes, and analysing price escalation history, you can identify inflated renewal pricing and negotiate 10 to 25 percent reductions with documented evidence.

11. You have obtained two to three benchmark pricing quotes from competing vendors or industry sources and validated the per-unit cost against your current agreement.
Request RFPs from two to three alternate vendors, even if you plan to renew with your incumbent. Vendors adjust proposals based on competitive threat; a credible alternative bid pressures your incumbent to improve terms. Work with analyst firms or procurement consortiums that maintain market pricing benchmarks for software categories. If your current vendor quotes $100 per user and competitors quote $65 per user, you have concrete leverage to negotiate down 30 to 40 percent or face a credible defection.
● High Risk
12. You have analysed your vendor's price escalation history and compared it to inflation, software market trends, and competitor pricing trends.
Track your vendor's escalation pattern: if they have increased prices by 5 percent annually while inflation is 2.5 percent and competitors are holding flat, the relationship is one-sided. Request that renewal pricing include a price-cap or step-down provision such as Year 1 at current price, Year 2 at 2 percent increase, Year 3 at zero percent increase. Many vendors reject hard price-caps but accept best-efforts commitments to stay under a target escalation rate. For multi-year deals, negotiate that you can adjust licences without triggering price increases within a defined variance band.
● High Risk
13. You have defined success metrics for renewal pricing including maximum acceptable per-unit cost, maximum total contract value, and acceptable price escalation caps for multi-year terms.
Before negotiating, establish your pricing floor and ceiling. Your floor is the competitive benchmark price; your ceiling is current price or less — never pay more for the same software without significant added value. Document the approved budget and escalation tolerance in writing, signed by finance and the business sponsor. During vendor negotiations, a clear pricing target prevents scope creep and keeps the team aligned when vendors apply pressure or introduce bundled services to obscure per-unit costs.
● High Risk
14. You have evaluated multi-year term discounts and modelled the total cost of ownership for 1-year, 2-year, and 3-year renewal options to determine the optimal commitment length.
Vendors offer deeper discounts for longer commitments such as minus 10 percent for 2 years or minus 15 percent for 3 years. However, longer terms lock you in and reduce your negotiating leverage at the next renewal. Model both scenarios: Year 1 at full price with annual renewal flexibility versus Years 1 through 3 at a discounted multi-year rate. If your software is mission-critical and stable, a 3-year term at minus 12 percent discount may save $200K. If adoption is uncertain or you are planning to migrate, stick to 1-year terms even at a higher per-year cost to preserve flexibility.
● Medium Risk
15. You have prepared a detailed RFP with clear scope, pricing terms, service-level expectations, and non-negotiable contract requirements, and shared it with your incumbent vendor and one to two alternatives.
A well-structured RFP disciplines the vendor and forces them to justify their renewal proposal against clear criteria. Your RFP should specify licence count and tier, support hours and SLAs, training and professional services included, pricing breakdown, payment terms, and contract duration. Include your non-negotiables: audit caps, exit rights, data portability, and service-level guarantees. Send the RFP to your incumbent 2 to 3 months before expiry with a formal response deadline. This creates competitive pressure and demonstrates you are serious about the evaluation process.
● Medium Risk

Section 4: Contract Terms and Risk Mitigation

The contract terms you negotiate shape your risk exposure and flexibility for the next 1 to 3 years. Enterprise software vendors use boilerplate language designed to maximise their leverage: unlimited audit rights, auto-renewal traps, broad IP indemnity, and service-level disclaimers. This section ensures you have negotiated protective terms that safeguard your organisation from vendor lock-in, surprise audits, and unfavourable escalations.

16. You have negotiated a price-escalation cap or step-down schedule that limits annual increases to inflation plus a fixed percentage, with approval required to apply any increases.
Auto-renewal contracts with undefined escalations give vendors unilateral pricing power at renewal. Demand a fixed escalation schedule in writing: Year 2 no increase, Year 3 two percent increase, subject to CPI not exceeding three percent. For multi-year terms, negotiate step-down pricing that improves with commitment such as Year 1 at $100 per user, Year 2 at $98, Year 3 at $95. Include a clause requiring 90-day written notice of any price increase with justification. If the vendor cannot commit to capped escalations, this signals they plan significant price hikes and you should not commit to multi-year terms.
● High Risk
17. You have eliminated or substantially limited the auto-renewal clause, requiring explicit mutual consent to renew and advance written notice of non-renewal.
Auto-renewal traps are among the most costly mistakes in software renewal management. A silent auto-renewal clause combined with short notice periods — often 30 days — locks you into unwanted renewals before you realise the contract has expired. Negotiate for no auto-renewal unless both parties agree in writing 180 days prior to expiry. If the vendor insists on auto-renewal, demand a 120-day notice requirement sent to your legal and procurement contacts. Include a clause stating that failure to send notice is waiver of the auto-renewal right.
● High Risk
18. You have capped audit rights to a maximum of once per 12-month period, limited to business hours, with defined scope and expense responsibility.
Unlimited audit rights expose you to surprise vendor audits, third-party auditors, and six-figure remediation bills if the vendor finds unlicensed usage. Boilerplate language often allows vendors to audit at any time with reasonable notice, which is vague and expensive to manage. Negotiate strict audit limits: no more than one internal audit per contract year, during business hours, no more than 30 days duration, with 30-day advance notice. Specify that vendor-initiated audits are at the vendor's expense. Include a materiality threshold where findings under a defined amount are waived.
● High Risk
19. You have secured explicit exit rights and data portability clauses, including termination for convenience and commitment to data export format and migration support.
Exit rights protect you from vendor lock-in. Boilerplate contracts require cause such as vendor breach to terminate; negotiate termination for convenience allowing you to exit for any reason with 60 to 90 days notice. Include a data portability clause: upon contract end, the vendor will export all customer data in standard formats such as CSV, JSON, and XML at no charge within 30 days. This is critical for cloud and SaaS applications where your data lives on the vendor's servers. If the vendor resists exit rights, demand a shorter initial term to preserve flexibility.
● High Risk
20. You have included service-level commitments with financial remedies such as service credits or termination rights if the vendor breaches uptime or support response SLAs.
Standard contracts disclaim all service-level guarantees and describe software as provided as-is with no availability guarantee. For mission-critical applications, negotiate explicit SLAs: 99.5 percent annual uptime with service credits for breach, critical issue response within 1 hour, and high-priority resolution within 4 hours. Include a termination right if SLAs are breached for two or more consecutive months without cure. Most vendors resist SLAs because they do not want to guarantee uptime, but will accept them for critical systems when the buyer is sufficiently prepared and has credible alternatives.
● Medium Risk

Ready to optimise your AI contract and cost position?

Download our AI Platform Contract Negotiation Guide — covering all major vendors, pricing structures, and negotiation tactics.
Download Free Guide →

Next Steps

Score your confirmed items against the benchmarks above. If you are in the High Exposure or Partial Governance bands, prioritise the items flagged High Risk — these represent the most common sources of material overspend and are addressable within a single procurement or FinOps cycle.

Redress Compliance works exclusively on the buyer side, with no vendor affiliations. Our GenAI advisory practice has benchmarked AI costs, negotiated enterprise AI contracts, and built governance frameworks across 500+ enterprise engagements. Contact us for a confidential review of your AI cost and contract position.