Customer case studies: what they are, the structure, and the one-week timeline

A customer case study is a long-form story about a specific customer, with their situation, the action they took, the result they got, and their own voice throughout. It is the highest-conversion testimonial format and the highest-effort to produce. The work flows from one interview and one week of editing, and the output is reusable across sales decks, proposals, the website, and nurture sequences.

The case study is the third of the four customer advocacy outputs (testimonials, reviews, referrals, case studies). The case study is the one that drives sales. The testimonial is the one that lives on the homepage. The referral is the one that brings a new lead. The case study is the one that closes a deal.

This page covers what a case study is, the structure, the customer interview, the writing, the design and placement, and the failure modes. The end of the page is a realistic timeline for one customer, one week of effort.

Why the case study is the highest-conversion format

The case study converts because it does what a short testimonial cannot. The short testimonial says “we use the product and it works.” The case study shows how a specific customer got from a specific situation to a specific result. The prospect reads the case study and evaluates fit.

The three evaluation questions a case study answers for the prospect: “Is this customer like me?” “Did they have the same problem I have?” “Did they get the result I want?” The short testimonial answers the first one. The case study answers all three. That is why the case study is the highest-conversion format.

The tradeoff is effort. A testimonial takes 5 minutes to ask for and 5 minutes to publish. A case study takes one customer interview and one week of editing. The conversion is higher. The production is higher. The math works for customers who are likely to be referenced in sales, and does not work for everyone.

What a customer case study is

A customer case study is a published story about how a specific customer solved a specific problem, with their situation, the action they took, the result, and their own voice. It is the long-form version of a testimonial, with the structure that a prospect can use to evaluate fit.

A case study is not a customer success story in the abstract. A case study is a specific customer, a specific situation, a specific result, and the customer’s own words. The structure is what makes it different from a blog post, a press release, or a sales pitch. The structure is what makes it useful for evaluation.

The case study is also not a white paper. A white paper is an educational document. A case study is a story with a customer as the protagonist. The two formats are different in purpose, in structure, and in conversion. A case study converts a qualified lead. A white paper generates one.

The case study structure

The working structure for a case study has four parts: situation, action, result, and customer voice. The parts are not equally weighted. The result is the largest section, because that is the part the prospect cares about. The situation is short, because the prospect is already in a similar one.

The action is medium, because it shows fit. The customer voice is woven through, not siloed.

Situation. One paragraph. Who the customer is, what they do, what their situation was before the product. The reader should see themselves in this paragraph. The reader should be able to identify with the situation.

Action. Two to three paragraphs. What the customer did, why they did it, how the product fit in. The reader should see the decision-making process. The reader should understand the evaluation criteria.

Result. The largest section. Three to five paragraphs. What changed, with metrics. The reader should see the outcome. The reader should be able to verify the claim.

Customer voice. Three to five direct quotes, woven into the action and result sections. The reader should hear the customer. The reader should trust the outcome because the customer is talking.

The customer interview

The interview is the source of the case study. The interview is 45-60 minutes. The interview is recorded with the customer’s consent. The recording is the document. The transcript is what you write from.

The five questions that produce the best material: (1) Tell me about your situation before you were using the product. (2) What was the decision-making process? (3) What changed once you started using it? (4) What surprised you about the product? (5) What would you tell someone in a similar situation today?

The first three questions produce the situation, action, and result. The fourth question produces the most quotable material (the surprise is the part the customer did not expect, which is the part the prospect also does not expect). The fifth question produces the customer voice that lives at the bottom of the case study.

The interview is the part you cannot fake. A case study written without an interview reads like a blog post. A case study written from an interview reads like a customer talking. The recording is what makes the difference.

The writing

The writing flow has four steps. First, the transcript produces 4,000-6,000 words of raw material. Second, the situation, action, and result are extracted into a 1,000-1,500 word skeleton. Third, the customer’s best quotes are selected from the transcript and woven into the skeleton. Fourth, the skeleton is edited into the case study.

The editing step is where the case study becomes publishable. The editing does three things: tightens the sentences, removes the parts that are not useful for evaluation, and adds the sections that are (a customer photo, a logo, a metric visualization, a call to action at the end).

The customer reviews the case study before it publishes. The review is for accuracy, not for marketing tone. The customer is the source of the facts. The customer is not the source of the writing style. Get the facts right. Write the case study in the company’s voice, not the customer’s.

The case study skeleton, in detail

A working skeleton for the situation paragraph has four sentences. The first sentence is the customer name, the company, and the role. The second sentence is the industry and the size of the company. The third sentence is the situation before the product. The fourth sentence is the specific problem the customer was trying to solve.

A working skeleton for the action section has three paragraphs. The first paragraph is the evaluation process. The second paragraph is the decision to choose the product. The third paragraph is the first 90 days. The paragraphs each have a single point. The reader can scan them and still get the story.

A working skeleton for the result section has three parts: the metric, the change, and the meaning. The metric is the number. The change is the before/after. The meaning is what the customer can now do that they could not do before. The result section is the part that closes the deal. The result section is the longest section of the case study.

The design and placement

The case study design is a one-time decision. There are two paths: a long-form web page with a hero image, a customer logo, a subhead, and the body text, or a one-page PDF with the same structure. The web page is more searchable and more shareable. The PDF is more useful inside a sales deck.

The placement is where the case study pays off. The web page lives at /customers/{name}/ or /case-studies/{name}/. The PDF lives in the sales team’s shared drive. Both should be referenced from the homepage, the pricing page, the relevant feature pages, and the relevant industry pages.

The case study that sits in the shared drive and is not linked to is wasted. The case study that is linked from the pricing page, the homepage, and the sales deck is a working asset. The placement is what makes the difference between an asset and a piece of content.

The case study that is buried in the shared drive is the case study that did not get read. The case study that is linked from the homepage, the pricing page, the feature page, and the industry page is the case study that closed three deals last quarter. The placement is what determines the return on the production effort, week after week.

The most common failure modes

The case study fails on one or more of the four parts. The four failure modes are predictable.

First, missing the situation. The reader does not see themselves in the customer. The case study opens with a company name and a quote, not with a situation. The reader scrolls past.

Second, weak action. The reader does not see the decision-making process. The case study jumps from the situation to the result. The reader does not understand the fit. The reader cannot evaluate.

Third, generic result. The case study ends with “the team loves the product” instead of a number. The reader cannot verify the claim. The reader does not trust the outcome.

Fourth, missing customer voice. The case study reads like a press release, not a customer talking. The reader does not hear a real person. The reader assumes the case study is fabricated.

The realistic timeline

One customer, one case study, one week. Day 1: schedule and run the interview. Day 2-3: write the skeleton. Day 4: weave in the quotes, edit. Day 5: send to the customer for review. Day 6: design the page. Day 7: publish and link from the relevant pages. The timeline is tight. The timeline is realistic for a focused writer with one customer in mind.

The journey after this page

If you have just read this page and want the broader advocacy system that case studies are part of, the customer advocacy pillar is the parent reference. The other advocacy outputs are at the customer referrals page (the second output), the word of mouth marketing page (the fourth output), and the customer testimonials pillar (the first output).

For the source material that the case study is built from, the how to collect testimonials page covers the four-stage workflow that also produces case study customers. For the placement of the case study once it is written, the displaying testimonials page covers the seven placement patterns that also apply to case studies.

For teams that want the case study wired up alongside the other advocacy outputs, Testivo is one tool that supports the case study workflow. The case study is the long-form output. The testimonial is the short-form output. Both come from the same customer success upstream.

The case study is the long-form capture that often accompanies the testimonial moment. The testimonial to referral workflow page is the workflow that connects the testimonial to a referral opportunity.