How to Write a Case Study That People Actually Read

You've got a happy customer. Great results. A story worth telling. And somehow the case study still ends up reading like a product brochure that nobody finishes.

It happens constantly. The raw material is there, but the final product is flat. Too formal, too predictable, too focused on the company telling the story instead of the customer living it.

Writing a good case study isn't about following a formula. It's about telling a true story in a way that makes a future buyer think, "That sounds like my situation." When someone sees themselves in your customer's problem, they start to believe your solution could work for them too.

Here's how to write one that does that.

Start by Getting the Customer to Say Yes

You can't write a case study without a willing participant. And most companies handle this badly.

The typical approach: email the customer six months after the project, ask if they'd be willing to do a case study, and wait. The customer says they'll check internally. You never hear back.

Better approach: plant the seed early. During onboarding, mention that you'd love to document their results down the road. When a milestone hits, bring it up again. The best time to ask is right after a win, when the customer is excited about what you accomplished together.

Frame it around them, not you. "We'd love to highlight what your team accomplished" works better than "We need a case study for our website." Offer them editorial approval, a link back to their site, and a finished piece they can use in their own sales materials.

Joel Klettke, who runs Case Study Buddy and has written hundreds of B2B case studies, has said: "The best case studies come from customers who feel like partners in the process, not subjects of it." That mindset changes everything about how the conversation goes.

If the customer won't let you name them, that's okay. Anonymous case studies still work when the details are specific enough. "A 200-person logistics company" is credible if the numbers and context feel real.

The Interview Is Where the Story Lives

Don't skip this. Don't replace it with a questionnaire. Don't try to write the case study from project notes alone.

The interview is where you find the story. Not the facts you already know, but the human details that make it interesting. The frustration before. The moment things clicked. The reaction when results came in.

What to Ask

Start broad, then go specific.

About the problem:

• What were you dealing with before we started working together?
• What had you already tried?
• What was the cost of not solving this? (Time, money, sanity.)
• Who was affected most?

About the decision:

• What other options did you consider?
• What almost stopped you from moving forward?
• Who else was involved in the decision?

About the results:

• What changed first?
• What surprised you?
• Can you put a number on it?
• What would you tell someone considering the same thing?

That last question often gives you the best quote in the entire case study. People relax when they're giving advice to a hypothetical stranger, and what comes out sounds natural and convincing.

How to Listen

Record the call. Take minimal notes so you can focus on what they're saying. When they mention something interesting, follow up. "You said you almost didn't move forward. What was the concern?" That's where the real story is.

The details that make case studies memorable almost never come from the first answer. They come from the follow-up question.

Story Structure: The Arc That Works

Every good case study follows a simple arc. Situation, struggle, solution, success. It's not complicated. But most companies flatten the arc by rushing through the first two parts to get to the sales pitch.

The Situation (Set the Scene)

One or two paragraphs. Who is this company? What do they do? How big are they? Just enough context for the reader to understand the playing field.

Don't overthink this. "A 150-person manufacturing company in the Midwest, growing fast and struggling to keep up with order volume" is all the setup you need.

The Struggle (Make It Real)

This is the most important part of the narrative, and the part most companies rush through.

The struggle is where the reader connects. If your prospect is dealing with the same problem, this is the section that grabs them by the collar. So make it specific. Make it feel real. Use the customer's words, not your marketing language.

Weak: "The company faced challenges with their existing processes."

Strong: "Their sales team was spending four hours a day building proposals in PowerPoint. Every proposal looked different. Half of them had outdated pricing. And they had no way to know if a prospect even opened the thing."

The strong version creates a picture. The reader either recognizes themselves in it or they don't. Either way, the case study has done its job in 30 seconds.

The Solution (Keep It Short)

One paragraph, maybe two. What did you do? How did it work? How long did it take?

This is not the place for a product walkthrough. The reader wants to know what changed, not every feature you turned on. If they want the technical details, they'll visit your product page.

The Success (Lead With Numbers)

This is what people came for. Lead with the biggest, most specific result.

• Revenue impact: "Closed 23% more deals in the first quarter"
• Time savings: "Reduced proposal creation from 4 hours to 20 minutes"
• Efficiency gains: "Freed up 60 hours per month across the sales team"
• Customer satisfaction: "NPS score went from 32 to 71"

Stack three or four results. Mix hard numbers with qualitative outcomes. "The team also reported feeling less stressed about deadlines" is surprisingly persuasive after a row of impressive percentages.

Writing Tips That Make the Difference

Write in Third Person, Quote in First

The narrative should be third person: "Their team discovered..." Direct quotes add first person: "We couldn't believe the difference," said Name.

This creates a natural rhythm. You tell the story, the customer validates it.

Cut the Jargon

If a sentence would confuse someone outside your industry, rewrite it. Case studies reach buyers who might not be technical. The VP of Sales reading your case study doesn't care about API integrations. They care about whether their team will hit quota.

Use Specific Numbers, Not Vague Claims

"Significant improvement" means nothing. "42% reduction in processing time" means something. Always push for the specific number, even if it's approximate. "Roughly doubled" is still better than "significantly increased."

Keep It Under Six Pages

If you're going longer than that, you're including details the reader doesn't need. Most effective case studies run two to four pages in a designed format. Cut everything that doesn't serve the story or the results.

How Should You Present the Data?

Numbers are the backbone of a good case study, but how you present them matters as much as the numbers themselves.

Before-and-after comparisons are the clearest format. "From X to Y" is instantly understandable.

Pull out key stats as visual callouts. A large "73% faster" in the middle of a page gets noticed during a quick scan. The same number buried in a paragraph gets missed.

Charts work when the trend is obvious. A line going up and to the right tells a story faster than words. But if the chart needs explanation, skip it. If someone has to study the chart to understand the point, you've lost them.

Timelines work well for long implementations. "Month 1: onboarding. Month 3: first results. Month 6: full rollout." This answers the unspoken question: how long until I see results?

When your case study is a flipbook, each of these data points can get its own page. One page for the big stat. One page for the before-and-after. The reader flips through a visual story instead of reading a dense document.

What Kills an Otherwise Good Case Study

Too much about you, not enough about them. The customer is the hero. You're the guide. If more than 30% of the case study is about your product, rebalance.

No tension. A story where everything went smoothly isn't interesting. Include the moment of doubt, the challenge during implementation, the thing that almost went wrong. That's what makes it feel real and makes the success more satisfying.

Burying the results. If a reader has to get through three pages of setup before they find a single number, most of them will never get there. Put a results snapshot in the first 30 seconds of reading.

Corporate approval washing. Every stakeholder who reviews the case study will want to soften the language, remove specifics, and add qualifiers. Push back gently. "Can we keep the number but round it?" is a good compromise. "Can we say 'improved' instead of '42% faster'?" is not.

After You Write It, Then What?

A case study sitting on your website's resources page isn't working hard enough. Your sales team should have it in their outreach sequences. It should show up in email nurture campaigns. It should be easy to share with a link, not buried in a PDF that needs downloading.

The companies that get the most value from case studies treat them like sales tools, not marketing content. Every deal has a moment where the prospect thinks, "Has this worked for someone like me?" Your case study answers that question.

Learn more about case study use cases to see how to get your finished case studies in front of the buyers who need to see them.

What This Comes Down To

A case study is a true story about a real customer with a real problem who got real results. When you write it that way, it works. When you write it like a press release or a product pitch, it doesn't.

Interview the customer. Find the story. Write it simply. Lead with numbers. Keep it short. Get it into the hands of your sales team.

That's really all there is to it.