The renewal date was public the whole time
UK public bodies announce their IT contracts, values, and end dates in public registers. Almost no vendor watches them.
The pain in one sentence
Sales teams at mid-sized IT vendors find out a public-sector contract was up for renewal after the incumbent has re-won it — even though the award, its value, and its end date sat in a public register the entire time.
The receipts
- The registers are public and free. Every UK public-sector contract award above threshold is published on Contracts Finder or Find a Tender, as machine-readable open data. Award notices routinely carry contract end dates — a public expiry calendar nobody reads.
- The money is real and named. A single June 2026 pass over those two registers surfaced 43 IT and software awards worth £67.2m across 33 distinct public buyers — education, health, justice — including one Ministry of Justice line of £21.2m. Every record is publicly checkable by anyone with a browser.
- Transparency is rising by law. The Procurement Act 2023 regime (live since February 2025) expands what buyers must publish and when — including forward pipeline notices, i.e. advance warning of what's coming to market.
- The miss is expensive by design. Public IT contracts run in multi-year cycles; a vendor who misses one renewal window typically waits 3–5 years for the next open door on that account.
- The existing answer is priced for whales. Procurement-intelligence platforms (Tussell and peers) sell enterprise-grade breadth at enterprise prices, aimed at the largest bidders — the mid-sized vendor chasing a dozen specific accounts is priced out.
Why it persists
The data is fragmented across two registers plus framework call-offs, the field quality is inconsistent, and nothing about a register row looks like a sales trigger. Sales teams live in their CRM pipeline, not in procurement registries. The intelligence platforms that do parse this sell to the enterprise vendors who already have public-sector desks — the buyers who need the alert most are the ones the incumbents don't serve.
The wedge
An expiry-watch for public-sector IT: parse both registers daily (the data is free), map buyer → installed system → contract end date, and alert subscribers 9–12 months before a renewal window opens. The MVP is honest and small: a weekly digest plus a searchable public calendar of upcoming expiries. No scraping grey areas, no proprietary data — just reading the public record on the buyer's behalf, every day, which no human sales team actually does.
The honest catch: the raw data is free to everyone, so the moat is coverage discipline and workflow fit, not access. And framework call-offs are messier than the headline registers — coverage will be honest-incomplete at first and should say so.
How the buyer arrives (no cold outreach)
- Publish the calendar itself. Each named upcoming expiry is its own indexable page — "«buyer» «system» contract end date" is a search a competing vendor runs the moment they start planning an account. The page answers it and offers the digest.
- Vendors watch their own turf. The fastest route in is a vendor searching their own customer's renewal — and finding it listed publicly where every competitor can see it too. Urgency arrives without a single email sent.
- The digest is shareable inside sales teams. One useful weekly list gets forwarded to the whole public-sector desk; the signup lives at the bottom of it.
- This newsletter and the public board carry the story of the gap itself.
The give-away
The manual recipe, free, works today: on Contracts Finder, filter awarded contracts by CPV codes 48 (software) and 72 (IT services); sort by end date; repeat on Find a Tender for above-threshold awards; put the end dates in a spreadsheet with a reminder 12 months out. That is the entire product, done by hand for one account patch — and doing it by hand for a week is exactly how to learn what the alert product must say.