Start a software renewal review before the contract's notice deadline, with enough time to assess usage, agree requirements and test alternatives. Build your negotiation position from evidence about what the business needs and what the contract actually commits you to.
1. Establish the dates and contractual position
Find the signed agreement, order forms, amendments and applicable product terms. Confirm the renewal date, notice period, renewal mechanism, price-adjustment provisions and any minimum commitments. Do not assume that stopping use or telling an account manager is sufficient notice.
Record who will approve and send any formal notice. Involve legal counsel where interpretation, notice validity or rights are unclear.
2. Compare what you buy with what you use
Reconcile purchased licences, active users, actual usage, product tiers and planned demand. Look for duplicated tools, unused modules and users assigned to a higher tier than they need. Check whether reductions are permitted and when they can take effect.
For consumption-based services, understand the unit of measurement, overage rates and how usage is monitored. A lower unit price may still produce a higher total bill if the commitment or consumption forecast is wrong.
3. Build the full cost view
Compare options over a consistent period. Include subscription charges, implementation, integrations, support, professional services, migration and exit costs. Separate recurring charges from one-time fees. Identify which assumptions depend on growth, currency or an unconfirmed project.
4. Assess operational and risk requirements
Bring together the business owner, IT, information security, privacy, finance, legal and procurement as needed. Confirm service levels, support coverage, data handling, subcontractors, continuity and exit requirements. If AI features are involved, establish which features will be used and assess the relevant data-use and AI terms with the appropriate specialists.
5. Test credible alternatives
An alternative is useful only if the business can realistically adopt it. Assess migration effort, integration dependencies, user disruption and available time. Where switching is not practical this cycle, identify what would make it feasible at the next renewal.
Avoid presenting a switch as a negotiating threat unless your stakeholders are prepared to act on it.
6. Agree your negotiation mandate
Set target outcomes, acceptable fallbacks and approval limits before discussions. Cover price, quantities, term, flexibility, service commitments and exit provisions. Treat these as connected trade-offs: a discount tied to a longer non-cancellable commitment may not serve the business.
7. Record and implement the outcome
Check the final documents against the agreed deal. Assign owners for licence changes, notices, obligations and the next review date. Validate financial benefits with finance, keeping avoided increases separate from reductions in actual spend.
A practical starting checklist
- Signed agreement and notice deadline confirmed.
- Usage and demand reviewed with the business owner.
- Total cost and credible alternatives assessed.
- Risk and operational requirements agreed.
- Targets, fallbacks and approval authority documented.
PC5's Commercial Value Sprint supports pricing analysis, supplier assessment and negotiation preparation. For ongoing ownership across a portfolio of renewals, explore fractional procurement leadership.