The Renewal That Renews Itself: A Board Triage for Subscription Contracts
Photo: financial documents contract signing desk overhead calculator, via ipaintyousip.com
Subscription spending has a property that most other operating costs lack: it renews without a decision. Salaries are re-committed annually through budget rounds, rent through lease events, but software often rolls forward on a click, a purchase order or simply the absence of a counter-instruction. By the time a finance team sees the invoice, the commercial terms are fixed for another twelve months.
For UK mid-market boards, the renewal cluster between October and February is the practical moment to intervene. Suppliers know it, which is why so many contracts are timed to expire when management attention is consumed by year-end and budgeting. A short, disciplined triage run in November or December is worth more than a procurement review conducted in March, when the options have gone.
Why renewals escape scrutiny
Three reasons recur. The first is ownership: the tool was bought by a function, adopted by a team, and now sits in a cost line nobody regards as theirs. The second is information asymmetry. Contract terms live in a supplier portal, not in the finance system, and the person who negotiated them may have left. The third is anchoring. The renewal quote arrives with a modest uplift, which reads as acceptable against a budget that was set months earlier.
None of these is a failure of intelligence. They are failures of process. The remedy is a structured set of questions asked in the same order, every time, before anything is signed.
Question one: how many seats are actually in use?
Ask for the last 90 days of active user data, not the licence count. The difference between provisioned and active seats is the single most common source of waste in mid-market software estates, and it is routinely between 10 and 30 per cent.
Two traps sit here. Some contracts define a seat as a named individual who has ever been granted access, so dormant accounts still count. Others price by named user but enforce by concurrent session, which means the true ceiling is lower than the invoice suggests. Establish which model applies before negotiating, and ask whether a downgrade tier exists for occasional users.
Question two: what exactly triggers the renewal, and when?
Most boards assume renewal happens on the anniversary. Many contracts say otherwise. Look for auto-renewal clauses with notice windows of 30, 60 or 90 days; uplifts tied to CPI or to a supplier's published list price; and terms that convert a monthly arrangement into an annual commitment after a set period.
Record three dates for every contract: the notice deadline, the renewal date, and the date on which a price change becomes effective. Diarise the earliest of the three. A renewal calendar maintained by one named owner is the cheapest control available to a mid-market firm.
Question three: which tools are doing the same job?
Overlap is rarely visible in a cost report because each tool serves a slightly different audience. Two collaboration platforms, three analytics products, four sources of customer data. The symptom is not duplicate invoices but duplicate reconciliation work.
A pragmatic test: for each paid tool, name the single business outcome it delivers and the person accountable for that outcome. Where two tools map to the same outcome, one is a candidate for consolidation. Where no outcome can be named, the tool is a candidate for removal. Neither decision needs to be taken in the renewal meeting; both need to be taken before it.
Question four: how would we leave, and what would we take?
Exit terms are negotiated when leverage exists, which is before signature, not after. Four points deserve attention: the notice period required to terminate without penalty, any early termination charge, the format and timing of data extraction, and the period for which the supplier will continue to provide access after termination.
Data portability is the practical crux. A commitment to "return data on request" is not the same as a documented export in a usable format within a stated period. Ask for the specific format and a realistic timescale, and test it once with a small export before renewal rather than after.
Question five: what does it cost to run, not just to buy?
The subscription line is rarely the full cost. Implementation resource, integration work, internal administration, training and the specialist contractor retained to keep the thing working all belong in the calculation. Where a supplier charges for support tiers, onboarding or premium modules, the headline price understates the commitment.
Calculate a three-year cost to serve for each material contract: subscription, expected uplift, implementation and integration amortised, internal hours at a loaded rate, and an allowance for change requests. Rank contracts by this figure, not by licence value. The ordering frequently surprises boards.
Running the triage in five steps
- Build the register. List every subscription above a defined threshold, typically £10,000 a year, with owner, function, renewal date and annual value.
- Pull the terms. Extract notice windows, uplift mechanisms, exit provisions and support inclusions into a single comparable table.
- Get usage data. Request active-user and consumption figures for the trailing quarter from each supplier.
- Score and sort. Rate each contract on utilisation, overlap, exit flexibility and three-year cost. Contracts scoring poorly on two or more dimensions go to the board.
- Decide in one sitting. For each flagged contract, record one of four outcomes: renew as is, renegotiate, consolidate, or serve notice. Attach an owner and a date.
Governance that holds between cycles
Three controls prevent the register from becoming a document nobody opens. Set a delegated authority threshold above which any renewal requires finance sign-off. Require a renewal calendar review at each board meeting, taking five minutes and covering the next 120 days. And require that any new subscription above the threshold is entered in the register before the first invoice is paid.
None of this requires a procurement function. It requires a named owner, a single list, and the discipline to ask the same five questions before the window closes. Firms that do it this winter will enter 2027 with a software estate they can defend line by line, which is a better position than most of their competitors will be in.