How to Write a B2B Case Study: Structure, Template and Tips

To write a B2B case study that buyers actually read, tell it as the client's story rather than yours: start with their situation, make the problem specific, explain what you did and why in plain language, report the result honestly, and finish with who this kind of work suits. That five-part structure works for almost any B2B service or product.

Most case studies fail because they read like press releases. The vendor is excited, the client is "thrilled", and the result is "transformational". Buyers skim straight past it. What they're looking for is simpler: did someone with my problem get a believable result?

Why B2B case studies matter in the sales process

A case study is proof in a format a buyer can forward. Your prospect probably isn't the only person deciding; they have to convince a manager, a finance lead or a sceptical colleague. A good case study gives them something to send that does the convincing for them.

That changes how you should write it. You're not writing to impress the reader. You're writing so the reader can retell the story in a meeting you're not in.

How to write a B2B case study: the five-part structure

1. The situation

Open with the client's world before the work started: their industry, size, goal, and what was in the way. One or two short paragraphs. If a prospect reads this and thinks "that's us", they'll keep going.

Weak: "Acme is a leading provider of innovative logistics solutions." Better: "Acme runs same-day deliveries for 40 restaurants in Manchester. In early 2026 their booking page was getting traffic but almost no completed bookings." (Acme is an illustrative example.)

2. The problem

"The client needed better marketing" isn't a problem. "Demo requests dropped after a redesign, and nobody could explain why" is. Specific problems make the solution feel earned. Include what they'd already tried, because it shows the problem was real and not trivial.

3. The approach

Walk through what you actually did, in order, and why. Buyers use this section to judge how you think, so name decisions and trade-offs: "We kept the pricing table but rewrote the plan names, because the call recordings showed buyers didn't understand them." That's far more persuasive than "we followed best practices".

4. The result

Real numbers are best when you have them and the client agrees. Give context so the number means something: "from 12 to 31 demo requests a month" beats "a 158% increase".

5. The fit and next step

Close by saying what kind of company this approach suits and how to start a similar project. This turns a nice story into a sales asset.

How do you write a case study without numbers?

This comes up constantly. Clients often won't share revenue, or the project's impact is hard to measure. You still have plenty to work with:

• Observable change: "The sales team now sends the new deck before every first call."
• Time saved: "Onboarding questions to support dropped noticeably in the first month."
• Before and after: show the old headline next to the new one and let readers judge.
• The client's own words: a specific quote about what changed is proof in itself.
• Scope and speed: "Five landing pages, rewritten and live in three weeks."

What you mustn't do is invent or round up numbers. One exaggerated claim that a prospect later checks undoes the trust the whole page was built to create.

What questions should you ask in a case study interview?

The best material comes from a 30-minute call with the client, ideally the person who felt the problem most, not just the person who signed the contract. Questions I use:

1. What was going on before you started looking for help?
2. What had you already tried?
3. What nearly stopped you from working with us?
4. What was the first moment you noticed things were different?
5. What would you tell a peer who's in the position you were in?
6. Is there anything we could have done better?

Question 3 is gold. The objections your client had are the objections your next prospect has, and the case study can answer them in the client's voice. Record the call (with permission) so you can quote accurately.

Common case study mistakes

• Making yourself the hero. The client is the hero. You're the guide.
• Burying the result. Put a one-line summary at the top: who, what, result.
• Too long. Most B2B case studies work best at 600 to 1,000 words, with a scannable summary box.
• No approval process. Always send the draft to the client for sign-off before publishing, and agree in advance what can be named.
• One format only. Turn each case study into a one-page PDF, a slide for sales decks and a short LinkedIn post.

A B2B case study template you can fill in

Copy this into a document and replace each prompt with your own material. The word counts are a guide for a page of about 800 words.

Headline: [Client type] + [what changed]. For example, "How a Manchester delivery firm tripled bookings", if those are the real numbers.

Summary box (4 lines):

• Client: [name, or "a UK fintech company" if anonymised]
• Industry and size: [sector, team size or market]
• What we did: [service, in a few words]
• Result: [the one result a busy reader should remember]

The situation (about 100 words): Before the project, [client] was [goal or growth stage]. They were [what was working]. But [what was in the way].

The problem (about 120 words): The specific issue was [problem, in the client's terms]. They had already tried [previous attempt], which didn't work because [reason]. If nothing changed, [cost of doing nothing].

The approach (about 250 words): We started by [first step, such as interviews or an audit]. That showed [key finding]. So we [decision], rather than [the obvious alternative], because [reason]. Then [next steps, in order].

The result (about 120 words): Within [timeframe], [result with context, such as "from X to Y a month"]. If you can't share numbers, describe the observable change: what the team does differently now.

Client quote (1 to 3 sentences): A specific line from the interview about what changed, attributed with name and role if they agree.

Who this suits (about 60 words): This approach works well for [type of company] facing [similar problem]. To talk about a similar project, [next step].

Before you publish, check that every number has the client's approval and that the client, not your company, is the main character.

Frequently asked questions

How long should a B2B case study be?

Usually 600 to 1,000 words for a web page, with a summary at the top for skimmers. Complex technical projects can run longer if the extra detail helps buyers evaluate you.

Do I need the client's permission to publish a case study?

Yes. Get written approval for the final text and agree on whether you can use the company name, logo and quotes. If they won't be named, an anonymised case study ("a UK fintech company") can still work well.

What's the difference between a case study and a testimonial?

A testimonial is a short endorsement. A case study tells the full story of the problem, the work and the result, so it can answer a buyer's questions in far more depth.

Where should case studies go on a website?

On a dedicated case studies page, and linked from the relevant service pages and sales pages, where buyers are making decisions.

Getting your case studies written

If you've got happy clients but no written proof, my case study writing service handles the interview, structure and writing. You can see the approach in this SaaS case study sample. To put that proof to work on a sales page, see B2B sales page copywriting.