At a glance
- Challenge
- Major renewals are approached without validated consumption data, owner-confirmed demand or executed optimisation, so the vendor's numbers set the agenda.
- Approach
- Baseline entitlement and deployment, forecast demand with business owners, execute optimisation before the window, then model scenarios and trade-offs.
- Primary KPI
- % of renewal spend supported by validated usage, demand and optimisation scenarios before negotiation opens.
- Impact
- Negotiation from an evidenced position, fewer defensive purchases and commitments the organisation can actually consume.
01
Executive Summary
A large enterprise agreement renewal is decided months before anyone sits down to negotiate. It is decided by whether the organisation can state, with evidence, what it consumes today, what it will consume over the term, and what it has already stopped consuming. An organisation that cannot state those three things negotiates on price alone, which is the one dimension where the vendor has the better information.
This playbook describes renewal preparation as a programme with a deadline rather than an event. The critical sequencing point is that optimisation must complete before the renewal, not during it. Shelfware identified during a negotiation is a talking point; shelfware removed six months before it is a reduced quantity in the baseline.
The second point is demand forecasting with business owners rather than by extrapolation. A forecast built by adding a growth percentage to last year is indistinguishable from the vendor's own model and carries no negotiating weight. A forecast built from owner-confirmed headcount, project pipeline and decommissioning plans is a position.
02
Business Challenge
Renewal preparation typically starts too late and with the wrong data. Procurement is engaged sixty days out, asks technology for a quantity, and receives current deployed count. Nobody has time to validate whether the deployed count reflects actual need, whether the product mix is still right, or whether the metric has changed since the last agreement. The safe answer is last year plus growth, and the safe answer becomes the commitment.
The consequence is compounding. Excess quantity agreed in one term becomes the baseline for the next. Products bundled into the agreement for a project that never delivered are renewed because removing them requires evidence nobody has assembled. Commitments made for volume discounts go unconsumed and are quietly written off, then renewed at the same level.
03
Typical Symptoms
Organisations that need this playbook usually recognise several of the following.
- Renewal preparation begins when procurement is engaged, typically well inside the notice window.
- The renewal quantity is current deployed count plus a growth percentage.
- Nobody has validated whether the current deployment reflects genuine business need.
- Products bundled in the last agreement for a cancelled initiative are still being renewed.
- Prior-term commitments went unconsumed and no analysis of why was performed.
- Business owners are not asked for demand input, so the forecast has no organisational backing.
- Optimisation is discussed during negotiation rather than executed before it.
- Post-signature, nobody tracks whether the committed volumes are actually being consumed.
04
Business Risks
Business risks by domain, with the risk and its impact
| Domain | Risk | Impact if unaddressed |
|---|
| Operational |
Renewal preparation compressed into the notice window |
There is no time to validate deployment, engage owners or execute optimisation, so the organisation negotiates whatever position it happens to be in. |
| Commercial |
Quantity anchored to deployment rather than to validated need |
Accumulated excess is renewed for the full term at a discount, and the excess becomes the baseline for the following renewal. |
| Compliance |
Product-use rights and metric changes not reviewed before signature |
The organisation commits under terms that differ materially from the expiring agreement, and discovers the difference during an audit or a true-up. |
| Technology |
Prior-term commitments unconsumed with no root-cause analysis |
The same over-commitment is repeated because nobody established why the volume was not consumed — a delayed project, a changed architecture, or a forecast that was always optimistic. |
05
Operating Workflow and Reference Architecture
Operating workflow
11 stages, each producing a defined output. This workflow is specific to this
playbook; the category lifecycle on the
Software Value index is an overview of how the playbooks relate,
not how any one of them runs.
↔ Wide diagram — scroll horizontally, or use the
arrow keys once it has focus. A text description is available to screen readers.
Illustrative renewal readiness workflow. Optimisation executes before the negotiation window, not during it — shelfware removed in advance is a reduced baseline, whereas shelfware identified at the table is only a talking point. Outcomes are not guaranteed.
Reference architecture
The systems, data and controls the workflow above runs on.
↔ Wide diagram — scroll horizontally, or use the
arrow keys once it has focus. A text description is available to screen readers.
Illustrative reference architecture. The forward-demand layer is what distinguishes a negotiating position from a purchase order — it is also the layer that requires business engagement months before the window opens.
06
Implementation Approach
A representative implementation sequences in 5 phases. Duration and overlap
vary with estate size, data quality and the number of source systems in scope.
Phase 1
Baseline and current-state evidence
Establish, twelve months out, what is contracted and what is actually used. The gap between them is the entire preparation opportunity.
- Agreement baseline. Establish expiring quantities, metrics, terms, commitments and true-up history, and identify any terms that were negotiated rather than standard.
- Deployment evidence. Evidence current deployment per product with the same rigour that would be applied to an audit response.
- Usage evidence. Establish demonstrable usage, distinguishing assigned from active, since assigned counts will always favour the vendor's position.
- Commitment consumption review. Analyse prior-term commitments against actual consumption and establish the root cause of any shortfall.
- Data completeness assessment. Report which products have negotiation-grade evidence and which do not, so the gaps can be closed while there is still time.
Business value
The organisation knows, with months to spare, which parts of the renewal it can evidence and which it cannot — and can act on the difference.
Phase 2
Demand forecasting with business owners
Build a forecast that has organisational backing. This is the step that converts data into a position.
- Owner engagement. Engage business owners for headcount plans, project pipeline and known changes, and record their input as the forecast basis.
- Decommissioning input. Capture planned application retirements and platform changes that will reduce demand during the term.
- Growth scenario definition. Build low, expected and high demand scenarios rather than a single number, since a single number invites the vendor to challenge it.
- Forecast validation. Have finance and the business sponsors validate the forecast before it is used as a negotiating input.
- Assumption register. Record every assumption behind the forecast so it can be defended and later assessed for accuracy.
Business value
The demand forecast carries business and finance endorsement, which makes it a position the vendor has to engage with rather than a number they can dismiss.
Phase 3
Pre-renewal optimisation execution
Execute the reductions before the window. Timing is the whole point of this phase.
- Shelfware reduction. Reclaim unused entitlement and remove inactive quantity from the baseline while there is still time for it to affect the renewal quantity.
- Product mix review. Remove products bundled for initiatives that did not proceed, with the business owner's confirmation recorded.
- Edition and tier alignment. Align editions and tiers to actual requirement so the renewal reflects need rather than historical over-specification.
- Metric change assessment. Assess whether vendor metric changes since the last agreement advantage or disadvantage the organisation, and model the effect.
- Baseline restatement. Restate the entitlement baseline post-optimisation so the negotiation starts from the optimised position.
Business value
The renewal negotiation begins from a reduced, evidenced baseline rather than from accumulated excess that must be argued down at the table.
Phase 4
Scenario modelling and position setting
Model the commercial options and agree the position internally before the first conversation with the vendor.
- Scenario modelling. Model quantity, product mix, term length and commitment level combinations, each with its assumptions and sensitivities stated.
- Trade-off quantification. Quantify the commercial trade-offs — a longer term against flexibility, a higher commitment against unit price — so the choice is informed rather than instinctive.
- Lever identification. Identify the specific levers available: consolidation, competitive alternatives, timing, multi-year commitment, product substitution.
- Position agreement. Agree target, acceptable and walk-away positions internally with finance and the business sponsor before engaging.
- Position pack. Assemble a negotiation pack with the evidence, forecast, scenarios and levers in a form the negotiation team can use in the room.
Business value
The negotiation team enters with an agreed internal position, quantified trade-offs and the evidence to support each — rather than discovering the position during the meeting.
Phase 5
Post-signature baseline and commitment tracking
The renewal is not finished at signature. Unconsumed commitments are next term's problem.
- Agreement baselining. Baseline the signed quantities, metrics, commitments and any changed product-use rights into the entitlement system immediately.
- Commitment tracking. Track consumption against committed volumes throughout the term with sufficient warning to act on a shortfall.
- Term-change monitoring. Monitor for changed rights and obligations that affect operational practice, and communicate them to the teams affected.
- Benefit realisation. Track the realised benefit against the modelled scenario and have finance validate it.
- Next-term preparation. Begin the next cycle's evidence collection immediately rather than twelve months from now.
Business value
Committed volumes are consumed or renegotiated in time, and the next renewal starts from a maintained evidence base rather than from scratch.
07
Technology Components
Capability categories rather than named products, since renewal preparation draws on the organisation's existing entitlement, inventory and finance systems. The constraint is lead time and business engagement, not tooling.
Contract and entitlement
- Contract repository
- SAM platform entitlement
- Commitment and true-up tracking
- Product-use-rights records
Consumption evidence
- Deployment inventory
- Usage and activity data
- SaaS subscription data
- Optimisation action records
Forecast and modelling
- Demand forecast model
- Renewal scenario model
- Trade-off analysis
- Assumption register
Governance
- Negotiation position pack
- Finance validation
- Commitment consumption dashboard
- Benefit tracking
08
Governance Considerations
Governance should be proportionate. The six areas below are the minimum set that has to be
explicit for this capability to hold up under internal review.
Ownership
A named renewal owner accountable for readiness against the notice deadline; business sponsors accountable for demand input; procurement accountable for the commercial process.
Decision rights
The business sponsor and finance approve the demand forecast; the governance forum approves the negotiation position including the walk-away; procurement executes within that mandate.
Policies
Renewal readiness policy setting a minimum lead time before the notice deadline; optimisation-before-renewal policy; commitment policy requiring consumption evidence before volume commitment.
Approvals
Demand forecast approved by business and finance; negotiation position approved before vendor engagement; any commitment above a threshold approved with a consumption plan attached.
Evidence
Deployment and usage evidence at negotiation-grade rigour, the forecast with its assumption register, scenario models, and the signed baseline retained for the term.
Controls
Notice-deadline alerting with sufficient lead time, data-completeness gate before position setting, and commitment consumption alerting through the term.
09
Success Metrics
Primary KPI
Renewal spend supported by evidence
Share of renewal spend supported by validated usage, an owner-confirmed demand forecast and modelled optimisation scenarios before negotiation opens.
≥ 95%
Operational KPIs
Data completeness at position setting
100% of in-scope products
Products with negotiation-grade evidence.
Applications and owners validated
100% of in-scope
Business owners confirmed and engaged.
Scenario turnaround
< 5 working days
Time to model a new scenario during negotiation.
Preparation lead time
≥ 9 months before notice
Elapsed time from programme start to notice deadline.
Governance KPIs
Contract terms reviewed
100% before signature
Terms and product-use rights assessed against the expiring agreement.
Position approved before engagement
100% of renewals
Internal position agreed before vendor contact.
Assumption register completeness
100% of forecasts
Forecast assumptions documented and validated.
Commitment tracking active
100% of committed volumes
Consumption monitored against commitment.
Value KPIs
Inactive quantity removed pre-renewal
Against identified
Shelfware reduced before the baseline was set.
Optimisation actions completed pre-renewal
≥ 90% of planned
Reductions executed before the window.
Negotiation levers identified
Documented per renewal
Specific, evidenced levers available at the table.
Forecast accuracy
Within ±10% over the term
Forecast demand against realised consumption.
Post-signature benefit realisation
Finance-validated
Realised benefit against the modelled scenario.
Indicative targets
Every target above is an indicative KPI for a typical enterprise, intended to support
planning discussions. Baselines should be measured in the first operating cycle and targets
set from them. These are not benchmarks, commitments or achieved client results.
10
Positive Business Impact
Negotiation from evidence, not from preference
Consumption, demand and optimisation are all documented before the first vendor conversation, so price is one dimension among several rather than the only one.
Defensive purchasing reduced
Quantity comes from an owner-confirmed forecast with a stated assumption register, which removes the protective margin that turns into next term's baseline.
Optimisation reflected in the baseline
Reductions execute before the window, so the negotiation starts from an already-optimised position rather than arguing accumulated excess down at the table.
Commitments the organisation can consume
Volume commitments are made against a validated demand plan and then tracked, so shortfalls are visible in time to renegotiate rather than written off.
Commercial trade-offs made deliberately
Term, volume, mix and flexibility are quantified against each other, so the concession made is the one the organisation intended to make.
A maintained evidence base for next time
Post-signature baselining and continuous tracking mean the following renewal starts from a current position rather than a twelve-month reconstruction.
Outcomes depend on estate, contracts, data quality and organisational context, and are not guaranteed.
11
Related Playbooks
Playbooks commonly delivered alongside, before or after this one.
Important — please read
This playbook describes a typical implementation approach and a representative operating
model. It is illustrative guidance, not a statement of results. Any figures, targets or
ranges shown are illustrative and are intended to support planning discussions rather than
to predict or promise an outcome. Outcomes are not guaranteed and depend on the estate,
contracts, data quality and organisational context of each engagement.
No client names, client data, engagement detail or confidential delivery material is
disclosed anywhere in this library. Technology named in these pages appears only as an
illustrative example of a capability category and does not imply a partnership,
certification or recommendation.
