Every B2B company wants case studies. Most of them have three months of data, a client who agreed to participate "in principle," and no one who knows how to turn a 45-minute Zoom call into a story that closes deals.
That is where you come in.
Being a case study copywriter means more than knowing the five-part structure. The structure is the easy part. The hard work is everything that happens before you write it: the client interview, the result extraction from a contact who says "things got better," and the approval process that can strip the life out of the document if you let it.
This guide covers the full job, not just the format.
What a B2B Case Study Actually Is
A B2B case study is not a testimonial. A testimonial is a quote. A case study is a story.
It has a main character (the customer), a problem that character faced, a decision they made, and a result they got. The reader's job is to read that story and ask: "Is this my situation?"
If the answer is yes, the case study does what it is supposed to do: it removes the risk of buying. It shows that someone like the reader, in a situation like theirs, got the outcome they're looking for.
That is the job the document must do for the sales team. Not impress the CMO. Not live on the website. Close deals by making skeptical prospects feel less alone.
Who Hires Case Study Copywriters
The clients are almost always B2B: SaaS companies, consulting firms, agencies, professional services businesses, and technology vendors.
The person who hires you is usually a content marketing manager, a demand generation lead, or a solo founder who knows they need the content but doesn't have time to do the interviews and write the documents themselves.
What they actually need, though they often don't say it this way: a case study that can be forwarded by a sales rep to a prospect on a Thursday afternoon, and get a reply by Friday. That is the real job. Not "published on our website." Used in a sales conversation.
Keep that in mind when you're deciding what to emphasize in the draft. The headline is the one sentence a sales rep can forward without context.
Before the Interview: What to Gather
Before the client interview, collect the following from the company you're writing for:
- The before and after metrics, even rough ones. You will validate and sharpen them in the interview.
- The timeline from first contact to implementation to result.
- The moment the client decided something had to change. This is often the best story hook.
- The product or service delivered and the key features or steps that produced the result.
Also read anything publicly available about the customer company: their LinkedIn, their website, recent press. The more you know going in, the more you can follow up on specifics instead of asking for everything from scratch.
It also helps to know what language the target buyer uses before you write your questions. Real buyer conversations in forums and Reddit communities tell you which objections are most common and which phrases resonate. PhraseMine organizes these conversations by theme, so your interview guide is built around the language buyers actually respond to.
The best case study interviews feel like a conversation between two people who already know the basics. The interviewee spends their time adding detail, not explaining context.
The Client Interview: Questions That Produce a Story
Most case study interviews fail not because the interviewee has nothing to say, but because the questions produce summaries instead of stories.
Before
“Can you describe the results you saw after using [product]?”
After
Walk me through what a typical week looked like before you started. And then what it looked like three months in.
The second question puts the interviewee back into the experience. They stop summarizing and start describing. That description is your raw material.
Five questions that consistently produce story material:
-
What was the situation that made you realize something had to change? This gets to the "status quo broken" moment: the emotional hook in every strong case study.
-
What did you try before this? Failed previous attempts create contrast and validate the decision to switch.
-
Who else was involved in the decision, and what were their concerns? Buying committee context makes the story more realistic and more useful to sales reps navigating the same committees.
-
Walk me through the first 90 days. Specifics about what actually happened are more persuasive than retrospective summaries.
-
What would you tell someone in your exact situation a year ago? This often produces the best direct quote in the entire document.
For the research behind what customers care about before they even get to a buying decision, customer research questions for copywriters covers the interview framework that surfaces copy-ready language.
When the interview is over, you should have more material than you can use. That is the right problem to have.
Extracting Results When Numbers Are Unavailable
The hardest part of writing a case study is often the results section. Legal teams restrict specific numbers. Clients are reluctant to disclose revenue figures. The marketing contact who agreed to participate can't get a sign-off on the numbers from their finance team.
You still have options.
Proxy metrics work when primary metrics aren't available. If the revenue number is off the table, ask about time savings. "Our team saves eight hours a week on reporting" is a real result. "We were able to reallocate two headcount to higher-value work" is a real result. "The sales cycle shortened from six weeks to three" is a real result.
Qualitative results carry weight when framed correctly. "Our sales team stopped getting 'we need to think about it' objections in demo calls" is a claim that any sales director reading that case study will understand immediately. It does not need a percentage attached to it.
Before and after comparisons are often available when absolute numbers are not. "Before: manual spreadsheet process. After: automated reporting with same-day visibility." The contrast is the result. The reader fills in the value.
When a client genuinely has no results to share (they're at early stage, the engagement is new, or the outcome is qualitative), be transparent with the company hiring you. Either delay the case study until there is something to report, or position it explicitly as a process story rather than a results story. Process stories ("how we implemented X across five teams in 60 days") can work in industries where implementation complexity is the buying concern.
The 5-Part Structure That Works in B2B
The Client sets the scene in two to three sentences. Industry, company size, the specific role of the person you interviewed, and the context that makes the story relevant.
The Challenge names the problem in the client's own language. Not "the company needed to improve operational efficiency." What did it actually feel like? What was breaking? What made action urgent? This section is where the interviewee's own words do the most work.
The Approach explains what was done clearly and without jargon. Readers skim this section. They are looking for the part that answers "could we actually do this?" Keep it specific enough to be credible and plain enough to be readable.
The Results is the section readers skip to first. Put the best number in the first sentence. If you have three metrics, lead with the most impressive and then support it with the other two.
The Takeaway is one paragraph at the end that does what the reader came for: connects this story to their situation. "If your team is dealing with [same challenge], here is what the client would tell you." This is where the direct quote from question five of the interview usually goes.
Know what your client's buyers care about before you write the interview questions
PhraseMine surfaces real conversations from B2B buyer communities on Reddit, organized by theme. Use it to understand what objections and desires your client's target audience has before you build the interview guide.
Try PhraseMine freeGetting the Case Study Approved
The approval process is where most case study drafts go to die by committee.
A legal team will remove specific claims. A marketing VP will want to add product features the story doesn't naturally support. The interviewee's manager will soften the language until the urgency is gone.
Two techniques that protect the document:
Lock the headline before you write anything else. Get the company to agree on the single-sentence summary of the result before the full draft goes into review. "Software company cuts reporting time by 12 hours per week and reallocates team to pipeline work." If that sentence is approved, it is much harder to strip the specifics out of the body copy later.
Run two separate reviews, not one. Send the first draft to the interviewee and their direct team for accuracy. Only send it to legal and the VP after the story is stable. When legal reviews a finished document, their edits are usually minor. When they review an early draft, they often rewrite sections wholesale.
The interviewee who gave you the best quotes is your ally. If the internal review is killing the story, go back to them. "The result section originally said X. Legal wants to remove it. Do you have a way to say the same thing that would pass?" They often do.
Voice-of-customer research helps you understand what language the target buyer is already using, so the terminology in the case study matches what prospects actually search for and respond to. When the document uses the reader's own vocabulary, it survives the approval process better because it sounds authentic rather than marketing-crafted.
Format Options for Your Deliverable
Most case study copywriting engagements produce a web page. Some produce a PDF download. Some produce both, plus a condensed version for a sales deck.
Set the format expectation before you start the interview. The web page version needs headers and scannable subheads. The PDF needs page breaks and a design handoff. The sales deck insert needs to fit on two slides. They are three different writing tasks even if the content is the same.
When scoping the engagement, be specific about what you are delivering. "One B2B case study, web format, 800 words, with a short-form PDF adaptation" is a deliverable. "A case study" is an invitation for scope creep.
Case study writing often pairs with white paper copywriting as a B2B long-form service. If a client hires you for case studies, they often need white papers for the earlier stages of the buying journey. Positioning both services together is a natural expansion of the same engagement.
Pricing and Positioning Case Study Writing
Case study writing typically runs between $500 and $2,500 per document, depending on the research required, the number of interviews, and the format deliverables. Clients with complex products, long sales cycles, or multiple reviewers should expect the higher end.
The recurring element is the pitch. B2B companies don't need one case study. They need a library: by industry, by use case, by company size, by region. Once you've written one document for a client and they know what a finished case study looks like coming from you, the next engagement is easier to close than the first.
Position the service as a program, not a project: "I write two case studies per quarter, each with a full interview, two drafts, and a PDF and web version included." That framing turns a one-time deliverable into a retainer conversation.
The structure is straightforward. The interview is where the real work happens. A case study that closes deals starts with questions that produce stories, not summaries. Get those questions right and everything else follows. Knowing what language the target buyer already uses, before you walk into the interview, is what separates a good interview guide from a great one. PhraseMine is built for that research step.