Buyers read case studies to find themselves

A case study is usually written the way the people who did the work remember it. Client, brief, process, deliverables, a testimonial at the bottom. That is a record of a project. It is not evidence, and it is not what the person reading it came for.

They came to find out whether you have solved their problem before. Not something adjacent to it. Theirs. So a useful case study opens by describing a situation precisely enough that a stranger sitting in the same one recognises it, and everything after that exists to show the situation was understood before it was designed for. What you delivered is the least interesting part of the story, because it is the part every competitor can also list.

What makes a good B2B case study

Start from where the reader is standing. They are qualifying you privately, from a browser, probably before you know they exist. Gartner's survey of 646 B2B buyers, published in March, found 67% prefer a rep-free buying experience, and its analysts warned that sellers "can't rely on static collateral to carry influence in those moments".

A case study is static collateral. It earns influence only by doing the thing a good salesperson does in the first two minutes, which is show they have met this problem before and can describe it better than the client can. That is a high bar, and most case studies do not attempt it. They describe the client instead. Founded in 2011, a leading provider of, growing rapidly. None of that is about the reader.

Lead with the problem, and make it specific

The test for a problem statement is whether it could belong to another company. "They needed a website that reflected their brand" belongs to everyone, so it belongs to nobody. Compare it with a statement that has edges: a service built for creatives that looked, at a glance, exactly like every other accountancy firm, which is a claim you have made before anyone reads a word of your copy. That is how we opened The3Key, and it is recognisable to anybody whose category has a uniform.

Specificity costs you readers, deliberately. A problem sharp enough for the right buyer to recognise is also sharp enough for the wrong one to leave, and the reader who leaves in paragraph one was never going to sign anything. Our client suitability page is the same instinct applied to a whole studio.

Why the deliverables list is the weakest part

Brand strategy, identity system, tone of voice, website design, front-end build. Read that back. It is a menu, and a competitor down the road can print an identical one this afternoon.

A list of deliverables tells a buyer what you sell. It never tells them what you noticed.

What a buyer is shopping for is judgement, and judgement only shows up in decisions: the thing you chose not to do, the constraint you designed around, the disagreement and how it resolved. A case study with no decisions in it reads like a project that had none, which is either untrue or worse.

Numbers help, though not in the way people hope. An outcome means nothing until the starting point is on the page. Hours saved is a figure. Hours saved from a job that meant searching six hundred pages of statutory PDFs is a story, and the second version is not longer. It is just less lazy.

Your case study is increasingly read second hand

Assume it will not be read the way you wrote it. Gartner reported in May that 45% of buyers used generative AI mainly to gather information on vendors and products, and that 69% then go to a sales rep to validate what it told them. Your work now gets summarised by a machine, for someone who fully intends to check the summary against a human.

That changes what has to be in the text. A vague case study survives a skim and collapses the moment anyone tests it, because there is nothing in it to test. A specific one gets summarised accurately, and when the buyer raises it on a call you can talk about it for twenty minutes, which is the impression you were after in the first place.

So put the sector, the constraint, the decision and the consequence in plain sentences near the top. Not because a machine prefers it. Because a person checking a machine looks for those same four things and gives up sooner.

How to fix one this week

Take the case study you are proudest of and delete its first paragraph. If nothing is lost, that paragraph was throat clearing, and the piece has been starting late for years.

Then find the sentence describing the problem and ask whether a competitor's client would recognise themselves in it. If they would, it is too broad to do any work. Rewrite it around something particular: an audience, a constraint, a deadline, a fact that was true and slightly awkward.

Then look at the ending. Most case studies finish on a testimonial, which is the client being polite. Finish on what changed and what it took, and let the politeness live somewhere else. A buyer who reads that and thinks "that is us" has already started the conversation on their own, and your contact form becomes a formality rather than a request.