How to Write a Case Study (Step-by-Step, 2026)

Why Most Case Studies Fail

Most case studies fail because they are written as brochures about the company, not stories about the customer. The tell is right there in the first line: a failed case study opens with the vendor ("Acme is a leading platform for..."), while a great one opens with the customer and the problem they were living with. Buyers do not read case studies to learn about you. They read them to find someone like themselves who had their problem and solved it, so they can borrow that person's confidence before they buy. When the story is about the vendor, the reader has no one to identify with, and identification is the entire mechanism.

The second failure is the missing before and after. A case study with no clear starting state and no measurable ending state is just praise. "They love our product and use it every day" tells a buyer nothing they can act on. "They were spending eleven hours a week on manual reporting, and now they spend under one" is a story, because it has a gap the reader can feel and a number that closes it. Without the before, the after has nothing to stand against, and the whole thing reads as a nice quote rather than proof.

The third failure is no real numbers. Vague results ("significant improvement," "major time savings," "much faster") are the sound of a case study that either did not ask for the metric or was told not to print it. Buyers have learned to read those phrases as an admission that the result was not big enough to name, which is worse than saying nothing. A single concrete number, even a modest one, outperforms a page of superlatives, because it is falsifiable and superlatives are not.

The fourth failure is confusing a case study with a testimonial. A testimonial is a sentence of praise: it says the customer is happy. A case study is a narrative: it shows how the customer got from a problem to a result, with enough detail that a stranger could imagine the same path for themselves. Testimonials are decoration you sprinkle across a site. A case study is a structured argument that a specific kind of buyer, in a specific situation, gets a specific outcome. Teams that treat the two as interchangeable ship long testimonials and wonder why they do not convert.

I have seen genuinely great customer results turned into useless case studies because the write-up buried the story under company boilerplate, dodged the numbers, and never let the customer actually speak. The result was real. The transfer failed. A case study is the transfer, and if it is vague, the reader fills the vagueness with doubt, exactly the doubt you were trying to remove.

The Anatomy of a Case Study That Converts

Every case study that actually moves a buyer, whatever its length or format, carries the same six parts in the same order, whether the writer labels them or not. Some are a single scrollable page and some are a designed multi-page PDF, but the working parts do not change. Here is the anatomy, in the order a reader wants to meet them.

1. The customer and their goal. Who the customer is, in the buyer's terms (industry, size, role), and what they were trying to achieve. This is where the reader decides whether this story is about someone like them.
2. The challenge or problem. What was in the way: the pain, the cost, the broken process, the stakes if it went unsolved. This is the before state, and it has to be specific enough to hurt.
3. Why they chose you. What they tried or considered, and what made them pick you over the alternatives or the status quo. This is the moment of decision, and it quietly handles the buyer's own objections.
4. The solution and how it rolled out. What they actually did with your product or service, and how the rollout went. Not a feature list: the story of the change, including any friction, so it reads as real.
5. The results, with specific numbers. The after state, quantified. The metrics that matter to this buyer, with the before-and-after gap made explicit, plus any softer wins that round out the picture.
6. A forward-looking quote. The customer in their own words on where they are now and what is next, which turns a finished story into an ongoing relationship the reader wants to join.

The order is deliberate. The reader meets the customer to see themselves, feels the problem to care, learns the choice to trust the decision, follows the rollout to believe it is doable, sees the numbers to be convinced, and hears the forward-looking quote to want it. Each part answers the doubt the previous one raises. Skip one and the reader's doubt lands there and stays: skip the numbers and it reads as hype, skip the challenge and the result has no weight, skip why-they-chose-you and the buyer's own objection goes unanswered. The rest of this guide is how to build each part so the doubt never gets a foothold.

Quick Picks: Where to Build a Case Study

Best for structuring the story and organizing all the proof before you write: Storyflow. The infinite canvas where the interview quotes, the metrics, the screenshots, and the six-part story arc all live in one place, and the AI reads the whole board so it can help you draft the narrative and pull the strongest quotes from everything at once. Free plan is $0 forever; Plus is $9.99/month billed annually. The honest limit: it structures the story and organizes the evidence, but the final written page or designed PDF is built in a doc or a design tool.

Best for a clean written case study page: Google Docs or Notion. When the case study lives as text on your site or in a shared doc, a straightforward writing surface is fast, universal, and easy to review. Free.

Best for a designed one-page PDF: Canva or InDesign. When sales needs a leave-behind that looks finished, with the logo, the pull-quote, and the metrics laid into the page, a design tool is the right final step. Free-to-paid (Canva) or paid (Adobe CC).

Best for boarding screenshots and visual proof: Milanote. If you mainly want a wall of product screenshots and result graphs beside the copy, Milanote is built for it. Free with an item cap, paid from around $12.50/month (verify current pricing).

The honest split: most teams structure the story and gather the proof where they can see it all at once, then write and design the final case study in a doc or a designed PDF depending on where it ships. Try Storyflow free to structure your case study.

Comparison Table: Where to Build a Case Study

Pricing checked July 2026. Competitor prices move and are quoted per plan, so verify on each vendor's page. Storyflow's Free plan runs the whole structuring method below at no cost; the paid tier adds the 200+ Story Blueprints and unlimited file uploads. Whichever tool you structure in, the final case study is delivered as a page, a PDF, or a video, so choose the delivery format for where the buyer will meet it, not for the tool.

How to Write a Case Study, Step by Step

Here is the full method, from a customer result to a finished case study you can publish. It assumes one customer and one result at a time. Work the steps in this order, because each one produces the raw material the next one needs, and you cannot structure a story you have not yet interviewed for.

Step 1: Choose the customer and the result worth featuring

Start by choosing well, because the wrong customer makes every later step harder and the right one almost writes itself. The best case-study candidate has three things: a result specific and provable enough to quantify, a starting situation that looks like your ideal buyer's, and a willingness to go on the record with numbers. A modest result you can prove beats a spectacular one you cannot. Look for customers who hit a clear milestone, who represent a segment you want more of, and who are enthusiastic enough to give you an hour and a real quote. Avoid the customer whose success is real but unquantifiable, the one who cannot get legal approval to name numbers, and the one whose situation is so unusual that no future buyer will see themselves in it. I decide what the case study is for before I pick the customer: if the goal is to sell to mid-market SaaS teams, the ideal subject is a mid-market SaaS team with a number, not the biggest logo who happens to be handy. Choose the story you need, then find the customer who tells it.

Step 2: Run the interview that gets quotable answers and real numbers

The interview is where the case study is actually made, and it is the step most teams rush or skip. Treat it the way a documentary interview is treated: come prepared, ask open questions, and shut up so the person can talk. The questions that get quotable answers are the ones that ask for the story, not a rating. Ask "what was a normal week like before you switched?" instead of "were you happy with your old process?" Ask "walk me through the moment you decided to try us" instead of "why did you choose us?" Ask "what number changed, and by how much?" and then wait, because the pause is where they reach for the real figure. Chase specifics every time the answer goes vague: when they say "it saved a lot of time," ask "a lot compared to what, in hours?" Record the call (with permission), because the best quotes are almost always the offhand ones you would never think to write down, and you want the customer's own words, not your paraphrase of them. A good case-study interview produces two things: the metrics that prove the result, and five or six sentences in the customer's voice that no marketer could have written. Both come from asking for the story and letting the person tell it.

Step 3: Gather the proof: quotes, metrics, and screenshots

A case study is an argument, and an argument needs evidence, so gather it before you write a word of prose. There are three kinds of proof and you want all three. Quotes are the human proof: the customer in their own words, which is the one thing a competitor cannot fake. Metrics are the hard proof: the before-and-after numbers, ideally two or three that matter to your buyer, sourced from the customer or your own data and cleared for publication. Screenshots and visuals are the tangible proof: the dashboard showing the result, the product in use, a chart of the trend, a photo of the team. Collect more than you will use, and keep every piece tied to where it came from, because a metric with no source is a liability and a quote you cannot attribute is worthless. This is also the moment to handle approval: confirm what the customer will let you name, quote, and show, ideally in writing, so you are not rewriting the whole thing later because legal killed the one number the story rested on. Proof gathered up front is proof you can arrange; proof chased afterward is a case study that stalls.

Step 4: Structure the story before you write it

Now arrange the raw material into the six-part arc from the anatomy above, before you write a single sentence of final prose. Lay out the six beats (customer and goal, challenge, why they chose you, solution and rollout, results, forward-looking quote) and slot every quote, metric, and screenshot under the beat it supports. This is the step where you can see whether you actually have a story or just a pile of nice comments: if the challenge beat is empty, your before state is weak and the interview needs a follow-up; if the results beat has no number, you do not yet have a case study. Structuring visually, with the beats as columns and the evidence as cards you move under them, makes the gaps obvious in a way a blank document never does. This is exactly the part I build on one canvas in Storyflow: the six beats laid across the board, the interview quotes and metric cards and screenshots grouped under each one, and the AI reading the whole board so it can draft the narrative from the actual evidence and flag where a beat is thin. You are not writing yet. You are deciding what the story is and proving you have the proof to tell it, so that writing becomes transcription instead of invention.

Step 5: Write it tight and scannable

Only now do you write, and the goal is tight and scannable, because almost no one reads a case study top to bottom. Write so a buyer who skims in fifteen seconds still gets the whole story: a headline that states the result ("How Acme cut reporting time by 91%"), a one-line summary under it, the metrics pulled out as big bold numbers, subheads that carry the arc so the beats are legible from the scroll, and pull-quotes that let the customer speak from the margin. Keep the prose lean: short paragraphs, plain sentences, the customer as the hero and your product as the thing that helped, never the star. Lead every section with the point and then support it, rather than building to it, because the reader may leave at any line. Cut the adjectives and let the numbers and the quotes do the persuading, since a specific figure is more convincing than any sentence you could write around it. The finished piece should work at two speeds: skimmable in fifteen seconds for the buyer in a hurry, and rewarding to read in full for the buyer doing their diligence. If it only works at one speed, it is not done.

Step 6: Choose the format: written page, one-page PDF, or video

A case study ships in one of three formats, and the right one depends on where the buyer meets it. A written page on your site is the workhorse: it is searchable, linkable, easy to update, and the format most buyers find on their own, so nearly every case study should exist as a page first. A one-page PDF is the sales leave-behind: designed, portable, and built to be attached to an email or dropped into a deal, with the logo, the headline metric, and a pull-quote laid out to be understood in a glance. A video case study is the highest-trust format, because seeing and hearing the real customer say it is harder to fake than any text, and it suits your flagship stories and your homepage, though it costs the most to produce. Many strong results deserve more than one format: the page for discovery, the PDF for sales, and a short video for the stories worth the investment. Decide the format before you design, because a page, a PDF, and a video are laid out differently, and retrofitting one into another is how case studies end up looking wrong for where they live.

Step 7: Build it on one board, then write and design the final where it lives

Do not do all of this in the document the case study will finally live in. The structuring, the interview quotes, the metric cards, and the screenshots want to be seen all at once, and a linear doc hides half of them while you work. So I build the case study on one infinite canvas first: the six beats across the board, every quote and number and screenshot grouped under its beat, the format decided, and the AI reading the whole canvas to draft the narrative and surface the strongest quotes. When the story is structured and the proof is arranged, I make a deliberate move to the final surface: I write the page in Google Docs or Notion, or I design the one-page PDF in Canva or InDesign, pulling from the board where everything already sits in order. The board is where the case study is thought through; the doc or the design tool is where it is finished. Keep those two steps separate on purpose, because trying to structure and design at the same time is how you end up with a beautiful layout wrapped around a story that does not hold.

Where to Write and Design the Final Case Study

Here is the honest part, because the tool you structure in and the surface you finish in are two different choices, and getting this wrong wastes hours.

A written page (Google Docs, Notion, or straight into your CMS) is the right finish when the case study lives on your site or in a shared doc. Most case studies should exist as a page first, because that is where buyers find them, where search indexes them, and where you can update the numbers when the customer's result grows. Write the page as text, keep it scannable, and let your site's design system handle the styling. Do not build a site case study as a PDF and bury it behind a download, because you are hiding the exact proof a self-serve buyer came to find.

A designed PDF (Canva if you want speed and templates, InDesign if you want full art direction) is the right finish when sales needs a leave-behind that looks finished, or when the story is a flagship you want to present rather than publish. A one-page PDF with the logo, the headline metric as a big number, a pull-quote, and a clean layout signals that the result is real and considered. This is where a design tool beats any writing surface, because page design is its whole job, and it is worth the extra hours for the stories that carry your pitch.

So the workflow that actually works is: structure the story and gather the proof where you can see it all at once (a canvas like Storyflow, where the beats, quotes, metrics, and screenshots sit together and the AI reads everything), then write and design the final case study in the surface where it will live. Storyflow is honest about this boundary: it is where the case study is structured and its evidence organized, not where the final page is styled or the PDF is laid out. Match the finish to where the buyer meets it, and never let the format outrun the story.

Common Case Study Mistakes

• Writing about the company, not the customer. Opening with "we are a leading platform" gives the reader no one to identify with. Open with the customer and the problem they were living with.
• No clear before and after. Praise without a starting state is not a story. Establish where the customer began so the result has something to stand against.
• No real numbers. "Significant improvement" reads as an admission the result was not big enough to name. Get a specific figure, even a modest one, and print it.
• Confusing a testimonial with a case study. A sentence of praise is not a narrative. Show the path from problem to result with enough detail that a stranger could picture the same journey.
• Skipping the interview. A case study written from a survey response or a sales note has no real quotes and no texture. Talk to the customer and record it.
• Burying the result. If the headline metric is on paragraph five, the skimming buyer never reaches it. Lead with the outcome and let the story explain it.
• A feature list instead of a rollout. Listing what your product does is not the same as telling how this customer used it. Tell the story of the change, friction and all, so it reads as real.
• Ignoring approval until the end. Building the whole case study around a number the customer's legal team will not clear means rewriting it from scratch. Confirm what you can name, quote, and show up front.
• Designing before it is structured. A gorgeous PDF wrapped around a story with no arc is style covering for a thin idea. Structure and prove it first, then design the finish.

The Bottom Line

A case study is not a brochure about your company. It is a story about a customer, written to make the next buyer see themselves in it and believe they will get the same result. Choose a customer whose result is specific and provable, interview them until you have the numbers and the quotes, gather every piece of proof, structure the six beats before you write, and write it tight enough that a fifteen-second skim still lands the story. Show the customer as the hero and your product as the thing that helped, let the numbers and the real quotes do the persuading, and you will have proof a competitor cannot fake.

The honest boundary holds. Structure the story and organize the evidence where you can see it all at once, the beats beside the quotes beside the metrics, with AI that reads the whole board, and then write and design the final case study in the surface where the buyer meets it: a page on your site, a designed PDF for sales, or a video for the stories worth it. The tool where you structure it and the surface where you finish it are two different choices, and the team that ships case studies that convert makes both on purpose.

If your customer's great result is still a pile of notes and quotes rather than a story a buyer can follow, structure the case study on one canvas in Storyflow and write the story, not the brochure.

Author

By Justkay, Documentary Filmmaker and Founder of Storyflow. I interview real people for a living, and a case study is the same craft aimed at a customer: find the story, earn the true quote, prove the result, and shape it so a stranger will read to the end. This guide is the working method, including the honest place where the structuring tool stops and the final page or PDF takes over.