The Case Against the Case Study: Why 'Challenge, Solution, Result' No Longer Sells

There is a genre of business writing so ubiquitous that it has become invisible: the case study. You know the form. A client (unnamed, for confidentiality, naturally) faced a challenge. Our firm applied a proven methodology. The result? Transformation. Growth. A quote from a grateful director.

I would go further: the standard case study has stopped functioning as a sales asset altogether. It is content theatre — produced because someone once said websites need them, consumed by nobody, credited with deals it did not close.

What Buyers Actually Do With Your Portfolio

Having sat on both sides of the procurement table, I can describe how decision-makers at British firms actually read these documents. They skim. They hunt for two things: a company like theirs, and a number. Anything else is skimmed past.

Yet the typical case study withholds both. The client is anonymised into uselessness ('a leading Midlands manufacturer' could be fifty businesses). The numbers, when they appear at all, are vague percentages untethered from any baseline. And the narrative is flawless — no false starts, no caveats, no sense that reality intervened. Buyers are not naive. Flawless reads as fiction.

The Anatomy of a Case Study That Works

The alternative is not clever. It is simply honest and specific.

Name names where you can. A named client with a named contact is worth ten anonymised ones. Where confidentiality genuinely prevents it, say precisely why, and be as granular as you can about sector, size and geography — 'a 40-employee food manufacturer in Yorkshire' lets a prospect self-identify.

Lead with the number, and give it a denominator. 'Reduced costs by 20%' is noise. 'Cut freight spend from £310k to £252k over eleven months, against a baseline of the prior full year' is evidence. Baselines, timeframes and absolute figures are what a sceptical finance director is scanning for.

Include the caveat. This is the counterintuitive one. 'It took six weeks longer than planned because the client's ERP migration overran' does not weaken a case study — it authenticates every other claim in it. Prospective buyers know projects go wrong. A firm that admits it, and explains what it did next, is immediately more credible than one whose engagements apparently run on rails.

Quote the sceptic, not the cheerleader. A testimonial from the managing director who hired you proves nothing. A quote from the operations director who initially opposed the project and was won over is worth its weight in signed contracts.

The Structural Fix

If I were redrafting a firm's portfolio tomorrow, I would impose three rules. First, one page per case, structured around the client's decision to hire — because that is the decision your reader is facing. Second, every case must contain at least three verifiable figures and one admitted limitation. Third, each case ends not with praise but with a sober line on what the client would do differently — ideally quoting them saying so.

None of this is glamorous. All of it is persuasive. The firms winning work in a cautious UK market are not those with the sleekest PDFs; they are the ones whose past clients sound like real people describing real outcomes, warts included.

The case study is not dead. The template is. Kill the template, and your portfolio might finally start closing deals.