The standard B2B case study follows a format so predictable you could generate it in your sleep.
Client background. Challenge. Solution. Results. Quote from a satisfied customer. Logo at the top. Call it in.
Nobody reads this. they skim it for a number or two in the results section — a percentage improvement, a dollar figure, a metric that sounds impressive — and they close the tab.
The case study has technically communicated that you did something for someone. It has done that. But it’s done nothing to make a prospective client feel understood, make them trust you, or make them want to call.
The format is the problem. And the problem with the format is that it’s structured around what you did rather than what they experienced.
You made it about you, and that’s almost never the right answer.
Start with a Problem, Not the Client
The first thing most case studies do is describe the client. Their industry, their size, their situation.
This is exactly backwards. And I’ll tell you why.
The reader doesn’t care about the client. They care about whether this client’s problem sounds like their problem.
If you start with the problem — specifically, the problem a prospective client recognizes in themselves — you’ve created relevance before the first paragraph is finished.
The reader is no longer observing someone else’s case study. They’re reading about themselves. That’s all a reader wanted in the first place.
So instead of opening with: “A national fitness brand with 50+ locations came to us for help with their content strategy” —
Open with: “Their blog had 46 published posts, a content team that worked hard, and nearly nothing to show for it in search. The traffic numbers were fine but The leads weren’t there. Nobody ever asked whether the content was actually aimed at the right people. OR aimed anywhere in particular.”
Now, a marketing director at a mid-size company with the same problem is reading a case study about them. You have their attention.
A 3-Part Structure That Works
I. The problem.
Not what the client told you their problem was: What you discovered the problem actually was. These can be very different, and the gap between them is where your expertise lives. Show the diagnostic work — Show how you looked deeper than the presenting issue.
II. The thinking.
This is the part most case studies skip entirely — the reasoning that led from problem to solution. the most valuable part!
Anyone can describe what they did. Describing why you made the choices you made — what you considered and ruled out, what you were optimising for, what trade-offs you were navigating — is what demonstrates genuine expertise. It’s what makes the case study a proof of intelligence and not just the story of some activities you performed.
III. The outcome.
The number, the metric. The thing that changed. This section should be short — one or two paragraphs at most — because you’ve done the first two sections correctly, so the reader already believes the outcome before they read it.
The outcome is confirmation of a conclusion they already drew. The only thing your reader loves more than reading about themselves is feeling smart.
The Quote Problem
Most case study quotes are useless.
“Working with [Company] was a pleasure. We saw significant improvements across the board.”
That quote could have been written by the vendor. It probably was, in a first draft. It tells the reader nothing the rest of the case study didn’t already tell them, and tells it in the most generic possible language.
An actually useful quote is specific, honest, a little surprising. It captures something the client said in their own voice — something that couldn’t have been written by anyone but them. “I kept thinking our content was the problem — Turns out we were writing excellent content for the wrong people.”
That’s a quote. That’s a person talking.
Getting good quotes requires actually talking to the client after the work is done — not sending them a form to fill in, but having a real conversation and listening for the moment when they say something true.
What You’re Really Writing
A case study is not documentation of a project. It’s a short story with a protagonist who has a problem, an antagonist (the situation they’re in), a turning point (the decision to do something different), and a resolution.
The prospective client reading needs to be the protagonist. The case study works when they finish reading it and think: that’s exactly where I am. I want to be where they ended up.
That’s a storytelling problem, not a reporting problem. metrics and methodology matter, but only in service of a narrative — and the narrative is always the same one:
here is someone like you, who was where you are, who made a decision, and here is what happened next.
If you want to tell that story about your work — let’s talk about that. Examples of the format in action: a content audit case study, a real-world audit from a fitness brand, and why case studies are the agency’s most important content asset.
Jacob Clifton is the principal of Clifton Creative, an editorial strategy consultancy based in Austin, Texas. He spent fourteen years as a flagship staff writer at Television Without Pity and has written for Tor.com, Vulture, BuzzFeed News, and the Austin Chronicle.