How to Write a Case Study

You just wrapped a customer call where your champion rattled off three specific results, two timelines, and an unscripted quote about how your product changed the way her team operates. Fifteen minutes later, you're in another meeting. By the time you sit down to write that case study, you can barely remember the gist.  

Many case studies fall apart before they're written because the raw material, the actual words your customer used, gets lost between the conversation and the document. Learning how to write a case study means learning how to capture and organize a customer's story effectively so that prospects can see themselves in it. 

The Short on Time Version

• Start with a sales objective, not a customer. 
• Choose a relatable protagonist and secure buy-in carefully.
• Use open-ended questions, push past vague answers to get specific numbers.
• Structure for scanning and distributing beyond your website.
• Capture the call with tools like Otter.ai, so the exact phrasing carries over into the draft.

Start With the Sales Objective

Decide what the case study needs to accomplish. Are you trying to break into a new vertical or move upmarket? Do you have collateral to overcome a specific objection your reps hear on every discovery call?

When a case study is mapped to a sales scenario, it becomes a targeted sales tool. Before you reach out to any customer, align with your sales team on which story would move the most pipeline right now.

Choose a Customer Your Prospects Can See Themselves In

The most effective case study subject is often the most relatable one for your target buyer. The strongest candidate is the customer your target buyer recognizes as similar to them, even if another customer has a bigger logo.

The strongest case studies usually need a recognizable protagonist and a clear before-and-after story that shows how the customer solved the problem using your solution. Prioritize customers with specific, measurable results, a company profile your prospects identify with, and permission to be named and quoted publicly. Using the customer's name, especially when the customer has significant brand recognition, makes the story more credible and more useful to prospects.

Secure Buy-In Without Triggering a Legal Review

This step is often where case studies slow down. Internal approvals and legal review can keep a large share of in-progress case studies from ever being published, with one interview estimate putting that number at roughly half.

Two techniques can reduce friction. First, avoid the phrase "case study" in your outreach. It can trigger formal review cycles. Use language like "share your successes" or "highlight what you've accomplished" instead. Second, interview the most senior people available, since they often have the authority to approve participation without routing through additional chains.

It also helps to provide case study samples and a document describing the writing and editing process and how the finished piece will be used. Give customers the opportunity to review and revise the case study before publication and have a say in how it gets distributed. Building both assurances into your initial pitch removes the two most common objections before they surface.

Prepare Interview Questions That Map to Each Section

Structure your questions so answers flow naturally into specific sections of the finished case study. Avoid yes/no questions entirely. Use open prompts like "Can you describe..." or "Tell me about a time when..."

Here is a practical starting framework:

• Background: "Walk me through your responsibilities and how your team is structured."
• Challenge: "What was going on at your company that sent you looking for a solution like ours?"
• Previous attempts: "Before you landed on our solution, how did you try to solve the problem?"
• Selection: "Why did you choose our solution over competitors or the option of doing nothing?"
• Results: "How are you benefiting from our product? Can you share specific results or metrics?"

This set of questions gives you enough structure to cover the story while leaving room for specifics and follow-up. A small set of questions sent in advance can help your customer prepare while still leaving room for spontaneity. Before the call, review the customer's website and any internal usage data you have so you spend the interview on details only the customer can provide.

Run the Interview to Capture Tension and Proof

The interview is the case study. Walk away with specific stories and at least one quotable number, and the writing is straightforward. Walk away with vague praise, and no amount of craft will save it.

Avoid collecting generic positive sentiment. B2B stories need friction. If everything goes right, readers have no reason to care about the answer.

Push past the first response. When a customer says "we had inefficiencies," ask: What did that actually cost you, in time, money, or missed opportunities? When they offer a directional answer like "our efficiency improved," follow immediately with: By what percentage? What did that translate to in dollars or hours?

Tell customers that estimates are acceptable. Customers frequently hesitate to give numbers because they lack exact data. Telling them that approximations are useful removes that hesitation and keeps the conversation moving.

After the interview, organize your material by section before drafting. Use a framework built around the problem, attempted solutions, why they chose you, implementation, and results. Recording makes that organization easier and more accurate.

That record also determines how much of the customer's real language survives into the final draft.

Why Recording the Interview Changes the Output

Recording the interview helps you preserve accurate quotes and statements throughout the case study. Exact phrasing matters. A customer's natural language carries a credibility that paraphrased marketing copy cannot replicate. Most interview subjects ramble, repeat, and over-explain, so editing often means trimming and stitching quotes for readability as long as the intended meaning is preserved.

Memory and shorthand notes force you to reconstruct what the customer said. A full transcript with speaker labels lets you select from what they actually said.

Write Each Section With the Reader's Situation in Mind

Keep the reader’s situation in mind and write each section using the given template:

• Title: Use a two-part structure: a main headline with a subheadline that includes a specific metric and timeframe. Lead with a clear, measurable result. For example: "How [Company] Reduced Churn by 40% in 90 Days."
• Executive summary: Write two to four sentences summarizing the entire story, followed by bullet points with key success metrics.
• The challenge: Give this section a sense of scale. Use dollars, complexity, difficulty, or size to make the reader feel the weight of the problem. The bigger and more complex the problem appears, the more impressive the solution becomes.
• The solution: Describe what operationally changed for the customer. A useful target is 120 to 160 words covering what was deployed, how it integrated into existing systems, who used it, and what changed day to day. Avoid feature lists.
• The results: Share results, with ROI as the ideal. When ROI cannot be firmly established, improved workflows, time saved, money saved, increased performance metrics, and increased conversions are all legitimate. Present results as bullet points showing each KPI, the change as a percentage or dollar amount, and the timeframe.
• Customer quote: Always include at least one. Quotes humanize the data and provide third-party validation that your own marketing copy cannot replicate.

Keep Your Company Out of the Hero Role

A strong case study works best when the customer is the protagonist, the challenge creates tension, and your solution helps produce the resolution. Make the customer the protagonist and your company the support behind the resolution. When your company takes the hero role, the customer disappears from the story, and prospects cannot see themselves in a narrative where they are absent.

Format for Scanning

A finished case study should not be a wall of text. Use headings and subheadings to guide readers through the structure. Present results as bullet points or a table. Pull strong customer quotes out of the body text and display them prominently. Include the customer's logo for immediate credibility. Add a clear call to action at the end. Most B2B SaaS case studies work well at 800 to 1,500 words.

Distribute It Where Deals Actually Happen

A case study should do more than live on a single website page. Equip reps with it as a leave-behind for late-stage prospects. Organize your website library by industry, use case, or company size. Match specific case studies to prospect segments in email nurture sequences, and extract key stats and customer quotes as standalone social posts.

One operational detail to cover early: distribution rights and intended channels must be discussed and agreed upon during the buy-in conversation.

The Interview Record Is the Bottleneck Worth Fixing

Every step in this guide depends on one thing: the quality of what you capture during the customer conversation. The tension, the specifics, the unscripted quote with real numbers in it. 

Otter.ai is an AI meeting assistant that can help address this bottleneck by recording, transcribing, and summarizing conversations. It turns every interview into a searchable transcript with speaker labels, an automated summary, and conversation intelligence your whole team can reference. 

Whether you're producing your first case study or building a repeatable program across your org, the difference between a generic success story and one that moves the pipeline is the raw material you walk away with.

How Otter Helps Take Interviews for Case Studies

Otter captures and organizes what's said in your meetings. For case study interviews specifically, Otter can join your Zoom, Google Meet,  Microsoft Teams calls, or in-person meetings to transcribe conversations in real time, which include automated summaries when the meeting ends. After an interview, you can search the full transcript for the exact quote you need, with the speaker labeled and the timestamp attached. Otter AI Chat takes this further: ask "What did the customer say about ROI?" and it returns the relevant passage from the transcript. You can also have it draft the full case study from the interview, and upload a few of your published case studies to the chat so it matches your usual voice, tone, and length.

Glacier Media, an integrated media company with an editorial team of roughly 150 staff operating across multiple newsrooms, offers a useful parallel for anyone writing case studies. Their reporters faced the same core problem case study writers face: capturing accurate quotes from interviews without losing the thread of the conversation, and doing it under a deadline. Manually recording and transcribing interviews was slow and pulled reporters away from the story itself. 

After adopting Otter, reporters began using it for phone interviews, field interviews at events, and press conferences. They now save 30 minutes to an hour per interview. For recordings they upload after the fact, a one-hour file is transcribed in roughly 10 minutes, and live calls are transcribed in real time as the conversation happens. The shift let them focus fully on the source during the conversation and quickly skim past transcripts for quotes when writing under a deadline. That same shift separates a case study built on real customer language from one stitched together from memory.

For in-person interviews, Otter's mobile app on iOS and Android handles the recording directly, and pre-recorded files can be uploaded for transcription. Teams producing multiple case studies can organize all interviews for a single project in a shared workspace, so the writer and the sales rep who sourced the story have access to the same record. That turns a single interview into searchable team knowledge instead of one person's notes.

Try Otter free on your next customer interview.

Frequently Asked Questions About "How to Write a Case Study"

What Is the First Step in Writing a Case Study?

The first step is defining the sales or marketing objective the case study needs to accomplish. Decide whether you're trying to break into a new vertical, move upmarket, or overcome a specific objection. This decision guides every choice that follows, from which customer you select to which questions you ask in the interview.

How Do You Write a Case Study in a Clear Style, and How Long Should It Be?

Start with a logical structure: outline your main points before writing, assign one idea per paragraph, and lead each paragraph with a clear topic sentence. Use headings and subheadings to guide readers through the story, present results as bullet points or a table, and pull strong customer quotes out of the body text so they stand out. Most B2B SaaS case studies work well at 800 to 1,500 words, especially when they are written for scanning with headings, bullets, and highlighted metrics.

How Many Interview Questions Should I Send in Advance?

Send a small set of five to seven open-ended questions in advance so the customer can prepare, then use the live conversation for follow-up questions and specifics. Avoid yes/no questions and lean on prompts like "Can you describe..." or "Tell me about a time when..."

Why Should I Record a Case Study Interview, and How Does Otter Help?

Recording helps you preserve exact quotes, numbers, and phrasing, and gives you a searchable transcript you can reference later instead of relying on memory or partial notes. That is the difference between selecting from a customer's real words and reconstructing what you think they said. Otter records interviews, creates transcripts with speaker labels, generates summaries, and makes it easier to find exact quotes and outcomes after the call. Writers end up with a stronger conversation record to work from when drafting the story.

What Makes a Case Study Persuasive?

Relatability, tension, specificity, and measurable results. Prospects need to see a customer like them, a real problem worth solving, and proof that something materially improved.