Proof Doesn't Age Well: A Refresh Routine for Case Studies

There's a case study on your website that was accurate when it went live and is now only technically accurate. The figures come from a different financial year. The person quoted in the pull-quote has since moved on. The platform described as "newly launched" has been replaced twice. Nobody has opened the page in eighteen months, and yet it's still out there doing quiet work on your behalf — either building trust or, more slowly, chipping away at it.

Case studies are the closest thing B2B marketing has to a witness statement. That's precisely why they need looking after. Proof that's gone stale doesn't simply stop persuading; it hands the sceptical buyer a reason to start picking.

The half-life of a good result

Most proof expires faster than the file name suggests. Headline numbers age quickest: a 43% uplift means very little without a "since when" and a "compared to what". Logos age too — businesses get acquired, rebranded or quietly wound up, and the client who signed off on that quote three years ago may no longer be in a position to stand behind it.

Then there's the subtler decay. Your own business has shifted. The case study describes a service you've since reshaped, a sector you've stepped back from, or a problem you no longer really solve. The proof is genuine. It's just proof of a company you used to be.

None of that is a reason to panic. It's a reason to build a routine — the same unglamorous sort of routine you already have for checking broken links or renewing insurance.

Date-stamp the numbers, every time

Rule one: no statistic appears without a date attached to it. "Cut onboarding time by 60%" is a claim. "Cut onboarding time by 60% between January and June 2025" is evidence. The second version ages honestly, because a reader can see exactly what they're looking at and judge whether it still applies to them.

Where it's practical, add the comparison point as well: the baseline, the period measured, whether it was a pilot or the whole operation. British buyers — especially anyone who has sat through a procurement process — are naturally allergic to numbers with no context. Give them the context before they have to ask for it.

If you're refreshing an old case study rather than writing a new one, resist the temptation to quietly swap in fresher figures and keep the original publication date. Either change the date visibly, or leave the original result intact and add the new data as a separate note. People notice when a timeline doesn't add up, and the entire point of proof is that it survives scrutiny.

Add a 'what happened next' line

The best case studies don't stop at the result. They carry on for one more sentence.

"What happened next" is the cheapest credibility upgrade available. The client kept working with you for another two years. The pilot rolled out to three more sites. The team that adopted the new process is still using it. Or, more honestly: the early gains levelled off and the relationship moved into a maintenance phase.

That last version can feel like a risk, but a case study that admits a plateau reads as more truthful than one that ends on a triumphant chord and never mentions the client again. Sceptical readers assume the tidy ending has been edited. A line of follow-through makes the rest of the page feel less curated — and, oddly, more persuasive.

Keep it to a sentence or two, dated like everything else. It isn't a sequel. It's a postscript.

Retire proof that no longer reflects the business

Some case studies can be updated. Others need to come down, and the sooner the better.

If the client has asked you to stop using their name, that's straightforward. If the results no longer represent what you actually deliver, it's murkier but still clear-cut in principle: a case study about a service you've discontinued is a promise you can't keep. And if the numbers were only ever true because of unusual circumstances — a one-off campaign, a freak quarter, a client with an in-house team most buyers will never have — it's probably doing more harm than good.

Retiring a page doesn't have to mean deleting it. Take it offline, redirect the URL to a relevant replacement, and move the asset into an internal archive so sales isn't still emailing a PDF that contradicts the website. Set a rule for this rather than deciding case by case in the moment: anything older than three years gets reviewed, and anything that can't be verified gets pulled.

Write the update before you need it

Most case study refresh pain is caused at the writing stage. If the piece is one long, beautifully written narrative, updating it means rewriting it. Structure it in modules instead: context, approach, results, quote, follow-through. Swapping one module is a ten-minute job; unpicking a 1,200-word story is a project nobody volunteers for.

It also pays to keep a short internal record alongside each case study — client contact, date approved, source of the figures, and a next review date. That's not glamorous either, but it means the person refreshing the page in eighteen months isn't starting from guesswork.

A routine you'll actually keep

You don't need a full audit every month. A quarterly sweep of your five most-visited or most-quoted case studies, plus an annual pass over the rest, will catch almost everything. Give one person ownership of the list. Flag anything that fails three tests — is the date current, is the client still happy, does it still describe what we sell? — and either refresh or retire it.

Proof is an asset, and assets depreciate. A little maintenance keeps the good ones earning, and quietly removes the ones that have stopped doing you any favours.