The piece buyers read last
Ask any B2B marketer to name their most persuasive asset and you'll usually hear the same answer: the case study. It's the piece of content a buyer reads when they're close to a decision, when the shortlist is down to two or three names and someone on the buying committee asks the obvious question. Have they done this before, for someone like us? It's often the objection your reps keep losing to.
That makes the case study one of the most important documents a B2B company publishes. It's also one of the most neglected. Case studies get written once, approved by a long list of people, posted to a resources page and rarely looked at again. Nobody asks whether they actually work.
So we decided to find out.
What we read
We collected the newest case study from 200 established B2B companies across nine industries. We chose the newest one on purpose. It's the one a company is most likely to send to a prospect today, and it reflects how the team writes case studies now, not five years ago.
Then we read every one of them closely and coded each on 42 elements. We looked at the headline, the structure, how the client was described, whether there was a measurable result, where that result appeared, how the vendor talked about itself and how the piece ended.
The goal wasn't to grade anyone's writing. It was to answer a simple question: how much proof do B2B case studies actually contain, and how much of it does the reader ever see?
Results sections without results
The first finding was the hardest to ignore. 41% of the sections labeled “Results” didn't contain a result anyone could measure.
They described a successful partnership. They mentioned a smooth launch, a strong relationship or a team that was happy with the work. Some quoted the client saying the project went well. What they didn't do was say what changed.
For a buyer, that's a problem. The whole reason they're reading a case study is to see evidence. When the section promising results doesn't deliver one, it quietly tells them there may not be one to share.
The proof is already there
The more surprising finding wasn't that proof was missing. It was that, so often, the proof was already on the page and buried.
Of the case studies that did include a boxed or highlighted result, 74% kept that number out of the headline. The single most persuasive fact in the document sat in a sidebar or a callout box, after the logo, the background section and several paragraphs about the client's industry.
In other words, the team had done the hard work. They had the result, they had permission to share it and they'd even designed a box to show it off. Then they put it somewhere most readers would never get to.
Most case studies already hold proof that never gets used.
Why the number gets buried
It's easy to see how this happens. Case studies tend to follow a template that was built years ago: background, challenge, solution, results. The template puts results last, so that's where the number goes.
There's also a natural instinct to tell the story in order. Writers want to set the scene before they reveal the ending. That works in a novel. It doesn't work for a buyer who's skimming on their phone between meetings.
That buyer reads the headline and maybe the first sentence. If the number isn't there, then for that reader it doesn't exist. The most important part of the story gets cut by the reader's own attention span.
Too much about you
The third pattern was about who the story is really about. In 28% of the case studies we read, the vendor was named more often than the customer.
That might sound like a small thing, but it changes how the whole piece reads. When a case study is about the vendor, the reader has to do the work of translating it into their own situation. They have to imagine themselves in the client's shoes while being told, over and over, how impressive the vendor is.
When the case study is about the customer, that translation happens on its own. The reader sees a company like theirs with a problem like theirs, and they see how it got solved. The vendor is still there. It just isn't standing in front of the story.
Let the customer be the hero
The strongest case studies we read had one thing in common. They treated the client as the main character and the vendor as the guide.
They opened with the client's situation in plain language. They described the problem the way the client would describe it, not the way the vendor's sales deck would. And when the result arrived, it was framed as something the client achieved, with help.
This isn't about being modest. It's about being persuasive. A buyer trusts a story about someone like them far more than a story about how good you are.
What a strong case study looks like
Put those patterns together and a strong case study starts to look quite different from the template most teams use. It leads with the outcome. It names the client early and often, and it describes their problem in words the reader would use about their own company.
It keeps the background short. A buyer doesn't need three paragraphs on the client's industry before they learn what happened. One or two sentences of context is usually enough to make the result meaningful.
It shows the work without turning into a product brochure. The middle of the story explains what changed and why, in plain language, with just enough detail that a skeptical reader believes it.
And it ends with a reason to keep talking. The reader finishes the piece knowing what happened, why it matters to them and exactly what to do next.
None of these ideas are new. What our research shows is how rarely they're all applied at once. Most case studies get one or two of them right and miss the rest.
No next step
The last pattern showed up at the very end. 31% of the case studies we read had no call to action at all.
Think about when someone reaches the bottom of a case study. They've read the problem, the solution and, hopefully, the result. This is the moment they're most convinced, and most likely to want to take a step. And in almost a third of cases, there was nowhere to go.
A call to action doesn't have to be pushy. It can be an invitation to talk, a related piece to read or a simple way to ask a question. What matters is that the reader isn't left at a dead end at the exact moment they were ready to move.
How to close the gap
None of this needs a bigger budget or a new agency. It mostly needs a different order and a little more discipline.
Start by moving the result up. If a case study has a number, it belongs in the headline or the first sentence, not at the bottom of the page. If the result is qualitative, make it specific and put it near the top anyway.
Next, check the results section itself. If it doesn't contain something a reader could measure or verify, it isn't a results section yet. Go back to the client and ask what changed. More often than not, there's an answer nobody thought to write down.
Then read the piece again and count how often you name yourself versus the client. If you appear more often, rewrite it until the client is clearly the main character.
Finally, give every case study an ending. One clear next step at the bottom, and ideally one in the sidebar for the reader who's already convinced halfway through.
Start with the case studies you have
The good news is that most B2B companies don't need to write new case studies to fix this. They need to rework the ones they already have.
Your case studies are already doing the hard part. They exist, they're about real work and they've been through approvals. Closing the proof gap is mostly a matter of getting out of their way, so the evidence a buyer is looking for is the first thing they see.