Why Your Case Studies Aren't Converting (And How to Fix Them)

You've got the case study. The school said nice things. Marketing made it look beautiful. It's on the website. It's in the pitch deck. And it's doing absolutely nothing.

I see this constantly. Companies selling into education with five, ten, sometimes twenty case studies — and none of them are moving deals forward. They exist because someone somewhere decided "we need case studies" and ticked the box. But nobody stopped to ask what the case study was actually supposed to do.

Here's the uncomfortable truth: most case studies in education sales are testimonials wearing a longer jacket. And testimonials don't close deals.

The wrong person problem

The biggest mistake I see is case studies written for the person who already said yes.

Think about it. You go back to the school that loves you. You ask them to say how great you are. They do — because they are lovely people and they genuinely like your product. You write it up, add a photo of some happy children, and put it on the website.

Who is that for? It's not for the head teacher at the school down the road who has never heard of you. It's not for the MAT finance lead who needs to justify spending. It's not for the procurement officer comparing you against three other providers. It's for you. It makes you feel good. And it sits on a page that nobody who matters is reading.

This is a stakeholder mapping problem. If you've done your homework on a deal — if you know who the decision makers are, who the influencers are, who holds the budget and who holds the veto — then you already know that a single case study cannot speak to all of them at once. The head teacher needs to see classroom impact. The finance lead needs to see value. The trust CEO needs to see strategic alignment. Send the same document to all three and you've impressed none of them.

A case study that converts is written for a specific person who hasn't bought yet. It speaks to their problem, not your product. It shows someone in their role dealing with something they recognise. That's a completely different document from the one most companies are producing.

The timing problem

Case studies get sent at the wrong moment. Usually too early.

Someone has had one conversation with you. They're vaguely interested. You send them three case studies, a one-pager, and a link to a webinar recording. Congratulations — you've just made their inbox feel like homework.

A case study lands when the buyer is past curiosity and into justification. They already think what you're offering might work. Now they need evidence to take to someone else. That's the moment. Not before.

If you're sending case studies before a second conversation, you're not selling — you're hoping. And hope is not a strategy.

What most case studies actually say

I've read hundreds of these. Most of them follow the same structure: here's the school, here's what they bought, here's how much they liked it. Three paragraphs of context nobody asked for, a couple of quotes that could apply to any product in any sector, and a call to action that says "book a demo."

None of that is useful to the person reading it. They don't care about the school's name. They care about whether the school had the same problem they have. They don't care that the head teacher said something nice. They care about impact. What actually changed? For whom? By how much?

The most common line I see in education case studies is some version of "it's been a game changer for our school." That tells me nothing. What changed? Over what time period? What does the data say? If you can't answer those questions, you don't have a case study. You have a review. And reviews don't give a deputy head what they need to go to their head teacher and say "we should buy this."

What a converting case study actually does

Three things. That's it.

First, it names a problem the reader recognises. Not your version of the problem — theirs. "This school was struggling with teacher workload during assessment periods" is better than "this school wanted to improve their assessment process." One is something a deputy head has actually said out loud in a meeting. The other is marketing language. And if you've done your stakeholder mapping properly, you already know which problems keep which people awake at night.

Second, it shows measurable impact. Not "teachers loved it." Not "it transformed our approach." What specifically changed, for whom, and by how much. If attendance improved, say by what percentage. If teacher time was saved, say how many hours. If outcomes shifted, show the data. Impact is the thing that lets the person reading your case study walk into their next internal meeting and make the case for you when you're not in the room. Without it, they've got nothing to say except "it looked good in the demo."

Third, it makes the next step obvious. And the next step is almost never "book a demo." The next step is whatever removes the biggest remaining barrier for that specific stakeholder. For the head teacher, it might be a conversation with the school in the case study. For the finance lead, it might be a pricing conversation. For the trust board, it might be a pilot proposal. Make it concrete, make it easy, and make it relevant to where the reader actually is in their decision.

The MAT problem

If you're selling into multi-academy trusts, the case study challenge gets harder. Because you're not writing for one person — you're writing for a system. And systems have layers.

The trust CEO cares about outcomes and strategic alignment. The head teacher cares about whether it actually works in a classroom or a corridor. The finance lead cares about cost per pupil and contract terms. The IT lead cares about whether it integrates with what they've already got. The SENCO cares about whether it reaches the children who need it most.

One case study cannot speak to all of them. So stop trying.

This is where stakeholder mapping and case studies meet. If you've mapped the buying committee properly — and you should have done that in your second conversation at the latest — you already know who needs convincing and what they need to hear. Your case studies should reflect that map.

The companies I've seen do this well produce case study variants — same school, same implementation, but framed differently depending on who's reading it. The head teacher version talks about teacher experience and classroom impact. The finance version talks about cost efficiency and renewal justification. The trust board version talks about outcomes data and strategic fit. Same story, different lens, different evidence.

It's more work. It converts significantly better. Pick one.

The evidence gap

Here's the thing that surprises people: schools are increasingly asking for evidence of impact before they'll buy. Not testimonials. Not "the teachers loved it." Measurable impact. Data that stands up to scrutiny.

This applies whether you're selling software, CPD, curriculum resources, assessment tools, or services. If your case study says "it was really well received" but can't say what changed as a result, you're going to lose to the company that can. Even if what you're offering is better.

This doesn't mean you need a randomised controlled trial. It means you need to be specific. How many people used it. Over how long. What measurable outcome shifted. If those numbers don't exist yet, that's fine — but then your priority is building the evidence alongside the implementation, not retrofitting a case study twelve months later and hoping the school remembers. Don't dress up opinion as proof. Schools can tell the difference. And increasingly, trusts are demanding the difference.

Start here

Pull up your best case study. The one you're most proud of. Read it as if you've never heard of your company. Ask yourself three questions.

Does it describe a problem I'd recognise as my own? Does it show someone like me dealing with it? Does it tell me what to do next?

If the answer to any of those is no, it's not converting because it's not supposed to. It's doing a different job — and probably not doing that one particularly well either.

Fix those three things and your case studies stop being brochure filler and start being sales tools. Which is what they should have been from the start.