Co-termination
Aligning several contracts with the same vendor onto one shared end date, so they renew together and are negotiated once rather than piecemeal through the year.
Also known as: Co-terminus, Co-termed, Co-terminated, Coterminous
Co-termination is the practice of aligning several agreements so that they end on the same date. It usually comes up with a vendor you buy more than one thing from, or after adding seats or a module part way through an existing term: rather than starting a fresh twelve months for the addition, the new line is co-termed to the end date already in place. Vendors will often price that stub period pro rata to make it possible, because it suits them too.
The reason to ask for it is leverage and effort. Four agreements with one vendor landing on four different dates means four negotiations, four notice periods to track, and no single moment where the whole relationship is on the table. Pulled onto one date they become one conversation a year, with the full spend visible. The cost is concentration: a single missed cancellation deadline now carries everything rather than a quarter of it, so a co-termed vendor deserves a longer reminder lead time, not a shorter one.
Worked example
A vendor's main platform costs £48,000 a year and renews on 31 March. In September you buy a module from the same vendor at £18,000 a year. Left alone it starts its own twelve months and renews every 30 September, so the relationship now has two dates, two notice periods, and two conversations. Co-termed instead, the module is given a stub term from 1 October to 31 March, priced pro rata at six twelfths of £18,000, which is £9,000. From 1 April both lines renew together at £66,000.
The stub is not a discount and not a premium: you pay for the months you get. What changes is what sits on the table at the next renewal. Separately, the vendor defends £48,000 in March and £18,000 in September, each on its own merits, at a moment when the other product is mid-term and cannot be moved. Aligned, the whole £66,000 comes up at once, which is the only version where leaving is a credible thing to say. That is the entire mechanism, and it is why the ask is usually granted at the point of purchase and resisted afterwards.
How StackTrackr handles it
There is no co-term button, because co-termination is something you negotiate with a vendor rather than something software does to your data. What the register gives you is the view that makes the case: vendor is a column on every record, so sorting by it puts a vendor's agreements next to each other with their renewal dates alongside, and the scatter that nobody chose becomes visible in one screen rather than inferred from a spreadsheet.
Once dates have actually moved, you update the renewal date on each record and the derived dates follow, including the cancellation deadline column, which is calculated from the notice period rather than typed in. The part worth doing deliberately is the reminder lead time. Every tool carries its own set of reminder offsets, 90, 60, 30 and 7 days before renewal by default, and they are editable per tool. A co-termed date now carries the whole vendor relationship instead of a quarter of it, so it is the one that deserves the longest lead you will actually act on, not the standard one.
Related terms
- Perpetual licenceA licence bought once that lets you use a specific software version indefinitely, often with a separate optional support fee.
- OverageA charge for going beyond what a plan includes, such as extra storage, API calls or seats, applied on top of the subscription you already pay for.
- Seat (per-seat licensing)A single user's licence to a piece of software. Per-seat pricing charges by the number of seats you buy, not by usage.