Ask ten companies for a case study and nine will send you something that reads like a press release. Logo at the top, a paragraph about how thrilled everyone is, a quote that could describe any supplier, and a number with no context. Nobody reads them and the sales team doesn't send them. They sit in a resources folder, and the money spent producing them is wasted.
Knowing how to write a case study that sells means doing something narrower and harder: helping a prospect recognise their own situation in another customer's story, then showing exactly what changed for that customer. That's the job. Below we cover how to choose the right customer, run the interview, structure the story and get it used, including the steps most teams skip.
Why most case studies fail
There are three common reasons, listed here in order of how often they come up.
They're about you instead of the customer. The subject of a good case study is the customer's problem. Your product is a supporting character that turns up partway through. When the first paragraph describes your platform's capabilities, readers lose interest, because they came to see someone like themselves solve a problem, not to admire your feature list.
The numbers aren't believable. "412% increase in productivity." Nobody buys it, and the exaggeration makes the credible numbers around it look made up too. A modest, specific figure that can be checked does far more than a spectacular vague one.
There's no "before". Plenty of published case studies describe an outcome with no starting point. "Now processes 3,000 orders a week" means nothing until you know they were managing 900 and drowning. The gap between the two is the story, and without the before there's no gap to show.
The reader isn't asking "is this product good?" They're asking "is this person me?" Everything in the case study should help them answer that.
Picking the right customer
The natural instinct is to ask your happiest customer. A better choice is the customer whose starting position looks most like your best prospects'.
Look for four things.
- A recognisable situation. The same size, industry and constraints as the buyers you want. A story about a 400-person enterprise won't help a ten-person team picture themselves.
- A real "before". They had a problem that was costing them something. Customers who were "already doing fine and just wanted to try something new" make weak stories.
- Numbers they'll let you publish. This doesn't have to be revenue. Hours saved, response time, conversion rate or hires they didn't need to make all work, as long as the figure is measurable and specific.
- Someone who'll talk openly. An enthusiastic champion beats a bigger logo with a nervous communications team. A famous name that goes through three rounds of legal review often ends up so smoothed over that it says nothing.
If you're early on and don't yet have customers of the right shape, write the story you do have and be upfront about the scale. A five-person agency's story, told properly, will persuade other five-person agencies far more than a Fortune 500 story with all the details removed.
Ask at the right moment
People say yes right after a win: a successful launch, a renewal, or a support ticket that ended with "this has been brilliant". That's the moment to ask. Six months later they'll have forgotten what things were like before, and that's exactly what you need them to remember. Our guide to getting testimonials covers timing and how to ask in more detail, and the same windows apply here.
Reply across all your platforms from a single unified inbox. Free for 15 days, no card required.
Unify your inbox →The interview is where the story comes from
Almost everything good in a case study comes out of the interview. Almost everything dull comes from writing it up from your own CRM notes.
Book thirty to forty-five minutes and record it, with permission. Don't send the questions in advance. You'll get prepared answers, and prepared answers are where the specific detail disappears.
These questions tend to produce usable material:
- Walk me through what a typical week looked like before. What was the most annoying part?
- What made you start looking? Was there a particular moment?
- What else did you consider? What nearly made you choose something else?
- What was the first thing that changed after you switched?
- What surprised you, good or bad?
- What would you tell someone in your position a year ago?
- Is there anything you'd still like to be better?
That last question matters more than it seems. A case study that admits one limitation is far more believable than one that doesn't, and prospects who see a fair caveat trust the rest of the numbers more. It also brings out product feedback you might not hear otherwise.
Listen for the moment the customer stops giving you the official version and starts telling you what happened. It often begins with "honestly" or "to be fair". Those are the quotes to use.
Get the numbers before you write
Ask for specific measurements during the interview, and ask what they were before. If the customer doesn't have the earlier figure to hand, ask what they remember. "Roughly two days to respond, sometimes three" is publishable and truthful. An estimate clearly labelled as an estimate is fine. A precise-sounding number you made up isn't.
A case study structure that works (use it as your template)
Use six sections, in this order. The sequence follows the way a sceptical reader judges a story.
1. The one-line result, at the top
Before anything else, say who it was, what changed and by how much. "A twelve-person recruitment agency in Bengaluru cut its time to first response from two days to under four hours, and doubled interview bookings without hiring." Many people will read this line and nothing else, so make it carry the whole story.
2. Who they are
Two or three sentences covering size, sector, what they sell and what makes their situation distinctive. Give the reader enough to compare themselves with this customer.
3. The before, with a cost attached
This is the most important section and the one most often rushed. Describe what was happening, why it was a problem and what it was costing in hours, money, lost deals or staff frustration. Use the customer's own words. This is the section where the interview pays off.
4. What they tried and why they chose you
Include the alternatives they looked at. A case study that pretends there was no competition reads like a brochure. "They trialled two other tools. One was too complex for a team without an operations person, and the other couldn't handle their approval process." A line like that tells a prospect more about fit than any feature list, and it answers an objection they were already starting to form.
5. What happened next
Describe the change in order: what went live first, what took time and where it was harder than expected. Include the friction. "The first two weeks were messy while we moved our old records across" makes everything that follows more believable.
6. The result, with numbers and a caveat
Give specific figures, the time period they cover and a fair note about what hasn't changed. Then finish with one line about what the customer is doing next.
Length, format and the version nobody makes
For a written case study, around 800 to 1,200 words works well. It's long enough to tell the story and short enough that people finish it.
The written page, though, is the format people use least. Make three versions from the same interview:
- A one-page PDF. This is what sales will send. Result at the top, three paragraphs, one quote and one chart.
- A web page. Indexed and linkable, with the full story and a clear next step.
- A 60-second clip. Three or four sentences of the customer talking, with captions. This is the version that travels on social media, and if you recorded the interview on video, you already have the footage.
Most teams only make the web page, which is why so many case studies go unused. Salespeople don't send links to a blog post. They send a PDF. Build the one-pager in the same sitting or it'll never get made.
Track reach, engagement, and ROI across every channel in one dashboard. 15-day free trial, no card required.
See your analytics →Getting approval without losing the story
The approval round is where good case studies get spoiled. Two habits limit the damage.
Send the draft with the quotes highlighted. Reviewers will focus on what they said, which is what they care about, instead of rewriting your narrative.
Ask specifically for factual corrections. "Please flag anything inaccurate or anything you can't publish" gets a much lighter edit than "let us know your thoughts", which invites a rewrite by committee.
If legal removes the numbers, negotiate for ranges or relative figures. "Cut response time by more than half" gets through review more often than exact hours, and it still does the job.
Making sure it gets used
A published case study with no plan for distribution is just a document. Build the rollout into the project from the start:
- Tell sales it exists, with one line on which deal stage it suits and which objection it answers. If nobody can find the case study when they need it, it may as well not exist.
- Link to it from the pages where people hesitate: pricing, the relevant feature page and any comparison page. Proof belongs where doubt appears.
- Turn it into social posts over the following weeks: one number, one quote, one before-and-after. Each should make sense on its own, and social media storytelling explains how to frame them.
- Add it to the nurture sequence for prospects who match that customer's profile. Relevance matters more than volume here. A well-matched story sent to twenty of the right people will do more than a generic one sent to two thousand.
- Update the numbers every year. A case study showing 2024 figures in 2026 looks abandoned. A one-line update such as "as of this year, they're at 6,000 orders a week" buys another year of credibility for ten minutes' work.
Four openings, and which one to use
The first sentence decides whether the rest gets read. Here are four openings that work, roughly in order of how often they suit:
Open on the frustration. "Every Monday, Priya's team spent the first three hours of the week copying order details between two systems." It's concrete and instantly recognisable, and readers know within a line whether this is their story.
Open on the number. "Four hours, then two hours, then eleven minutes." This works best when the result is striking and the metric needs no explanation.
Open on the decision. "They had two weeks to choose, and the obvious option was the one they didn't pick." Good when the buying process itself is the interesting part, which is useful in categories where prospects compare several suppliers.
Open on the quote, but only if the quote is strong. "I was ready to go back to spreadsheets" earns its place. "We're delighted with the partnership" doesn't.
Avoid opening with the customer's founding year, their headcount or a sentence that starts "In today's competitive landscape". That's throat-clearing, and readers scroll straight past it.
A shared calendar, approvals, and roles so your whole team ships on time. 15-day free trial, no card required.
Try Skyfliq free →How many do you need?
Fewer than you'd think, but spread across the situations your buyers are in. Three case studies covering your three main types of buyer will do more than twelve covering one. A prospect only needs to see themselves once.
If you can only produce one this quarter, choose the customer whose "before" matches the objection you hear most often. That's the one sales will send most.
Your next case study in four steps
Choose a customer who looks like your prospects rather than the one with the biggest logo. Interview them properly and listen for the moment they stop being diplomatic. Lead with the result, spend real time on the before, admit one thing that's still imperfect, and make the one-pager the same day.
Do that three times and you'll have something more persuasive than anything you could write about yourself.
Related guides: How to Write a Blog Post That Ranks on Google
Free tools for this: Caption generator · Engagement rate calculator · Free SEO checker — no signup. See all free tools.