B2B Case Study Page Best Practices: Structure and Proof

The short answer

Write each case study for one kind of buyer, around one problem. Agree the facts and the wording with the client before you start, keep the evidence for every number, and lay the page out so a skimming reader gets the client, the problem, the result and the period from the first screen. Then link it from every service page it proves.

What a case study page is for

Logos say who you have worked with. Testimonials say someone was pleased. A case study does a different job: it lets a buyer judge whether you can solve their problem, by showing the situation, the work and the outcome for a client they recognise as similar. For a lean B2B team it is often the most useful proof on the site, because it is the one a sales conversation can point to.

That also means a case study is read sceptically. In Nielsen Norman Group's 2019 research on About Us content, users still read testimonials but "remained leery as to whether the company had curated the reviews to show only the most favorable ones", and many checked third-party review sites as well¹. The authors recommend "honest and balanced testimonials"¹. The same applies to case studies: detail, context and admitted limits make them more believable, not less.

This guide covers the case study page itself. For where proof sits on other pages, see B2B landing page best practices and the proof section of B2B value proposition examples.

Before you write: agree it with the client

Most case studies stall at sign-off, not at writing. Settle these points with the client contact at the start, in writing:

Named or anonymised. Can you use the company name, logo and the contact's name, role and photo? If not, what description is acceptable (sector, size, region)?
Which numbers can be published. Some clients are happy to share a percentage change but not absolute figures, or a result but not the baseline.
Who approves the final text, and how long they need.
How long it can stay up, and who to ask if the contact leaves the company.

Keep the evidence behind every claim: the data export, the email confirming the quote, the signed approval. In the UK, the CAP Code requires marketers to hold documentary evidence that a testimonial or endorsement is genuine, and contact details for the person or organisation that gives it (rule 3.47), and to hold evidence for objective claims before publishing them (rule 3.7)². A results figure in a case study is likely to be read as an objective claim, so treat it as one.

The structure that works for most case studies

Order the page by the questions a buyer asks, and put a summary at the top for the many readers who will not read the rest.

Section	What it contains	Why it matters
Headline	The client (or client type), the outcome and the service	A skimming buyer learns the relevance in one line
Summary box	Client, sector, size, region, service, period, headline result	Lets the buyer check fit before reading on
The situation	What was wrong or needed, in the client's words, and what it was costing them	Buyers recognise their own problem
Why they chose you	The alternatives they considered, including doing nothing	Answers the buyer's own comparison question
What you did	Scope, approach, team, timeline and what the client had to do	Shows the work is real and repeatable
Results	Before and after, the period, how it was measured, what else changed	Makes the outcome checkable
The quote	A named person, role and company, saying something specific	A human voice the buyer can trust
Next step	A link to the service page and one call to action	Turns proof into a conversation

Write the headline around the result and the client type

A title like "Case study: Northfield Ltd" tells a newcomer nothing. A headline in the form "[What changed] for [type of client] with [service]" works on the page, in a list of case studies and in search results. Use the client's name in the headline only if buyers would recognise it; otherwise lead with the sector.

Put a summary box at the top

Many readers decide from the first screen whether a case study is relevant. A short block of facts (client, sector, employees or revenue band, region, service, project period and the main result) answers that quickly and makes the page easy to quote in a sales email.

Say what the client had to do

Buyers want to know the effort involved on their side: how many hours of their team's time, what access you needed, how long before anything changed. Many case studies leave this out, and it is one of the most useful things a buyer can learn from one.

Report results that hold up

The results section is where case studies most often lose credibility. A number without a baseline, a period or a method invites doubt, and a buyer who doubts one number will discount the whole page.

Give the starting point. A line such as "from 12 to 31 qualified enquiries a month" is checkable; "158% more enquiries" on its own is not.
State the period before and after, and when the work finished.
Say how it was measured: which system, which definition of a lead or a sale.
Name other things that changed in the same period, such as a price change, a new salesperson or a campaign. Saying so makes the rest more credible. A website change log makes this easy to reconstruct.
Avoid "up to". Report the actual result for this client, not the best figure across several.
Use non-numeric results honestly when there is no clean number: a process that now takes one person instead of three, a supplier audit passed, a launch date met.

If you measured the outcome of a website change yourself, our guide to measuring the impact of a website change sets out the method, including when the honest answer is that you cannot tell.

Quotes from named people

Anonymous praise reads as invented. Use the person's full name, role and company where the client allows it, and a photo if they agree. Ask the client questions that produce specific answers, such as "What were you doing before?", "What made you choose us?" and "What would you tell a peer considering this?", then quote their words rather than polishing them into marketing copy. Send the final wording back for approval and keep that approval.

When the client cannot be named

Many B2B clients will not allow their name to be used. An anonymised case study can still work if it is precise:

Describe the client exactly enough to judge fit: "a UK logistics company with about 400 employees and three depots" rather than "a leading logistics firm".
Say plainly that the client is anonymised at their request.
Keep the same evidence on file as for a named case study. Anonymising the page does not make the claims any less yours.
Pair anonymised studies with at least some named ones, if you can, so the set as a whole is credible.

Publish it as a web page, not a gated PDF

Case studies are often published as PDFs behind a form. That hides the proof from the people who need it and from search engines. Nielsen Norman Group's advice is direct: "Do not use PDFs to present digital content that could and should otherwise be a web page"³. The UK Government Digital Service gave its reasons for preferring HTML in 2018: PDFs are harder to find, use and maintain, do not adapt to phone screens, are often bad for accessibility and are harder to keep up to date⁴.

Publish the full case study as an HTML page that anyone can read.
Offer a PDF only as an extra, for people who want to forward or print it.
If you use video, add captions and a text summary on the page. WCAG 2.2 makes captions for prerecorded video with audio a level A requirement (success criterion 1.2.2)⁵.

Make case studies easy to find

A case study nobody finds does no work. Most buyers will reach it from another page, not from the case study index.

Link each case study from the service pages it proves, next to the claim it supports. Our services page optimisation checklist covers where proof sits on those pages.
Make the index filterable by sector, service and company size, with each card showing the client type and the result, not just a logo.
Give each case study its own URL and a descriptive page title, so it can rank for searches such as a service plus a sector.
Link to it from your homepage proof section, as described in our guide to B2B homepage best practices.
Review dates. Add the project date to each case study, and retire or refresh studies about services you no longer offer.

A template to copy

Use this outline as the brief for each case study. Fill in every line, or decide on purpose to leave one out.

Headline:      [What changed] for [type of client] with [service]
Summary box:   Client | Sector | Size | Region | Service | Period | Main result
Situation:     What was wrong or needed, in the client's words (2 to 4 sentences)
Alternatives:  What they considered instead, including doing nothing
What we did:   Scope, approach, team, timeline
Client effort: Hours of their time, access needed, decisions they made
Results:       Before, after, period, how measured, what else changed
Quote:         Full name, role, company; approved wording on file
Next step:     Link to [service page]; one call to action
Evidence file: Data export, quote approval, publication approval, review date

The checklist

Check	Pass if
Permission	Written approval of the final text, names, logo and figures
Evidence	Every number and quote has its evidence on file
Headline	States the result, the client type and the service
Summary	Client, sector, size, period and result visible in the first screen
Results	Baseline, period, method and other changes stated
Quote	Named person, role and company, saying something specific
Format	A readable web page; any PDF is optional, not gated
Video	Captions and a text summary on the page
Links	Linked from each service page it proves, and the reverse
Date	Project date shown; a review date set

Common mistakes

Writing about your process in general instead of this client's problem.
Percentages without a baseline, or results with no period.
Quotes that sound like your own marketing copy.
One case study page per logo, with no result in the headline or the index card.
Gating the only copy behind a form.
Case studies that nobody links to from the pages where buyers make decisions.
Leaving old studies up for services or sectors you have left behind.

A case study is rarely the page where a buyer gets in touch, so judge it by whether service pages link to it and buyers move on from it. Our B2B CRO guide shows where it sits among the other pages buyers read.

Where Artiweave fits

Artiweave does not write results or quotes for you; those have to come from your client, as this guide describes. Where it helps is placement: from crawl, Search Console and performance evidence it can flag proof that is missing or hard to find, such as a service page with no link to a relevant case study, and propose a specific change for your team to approve, edit or reject.

Frequently asked questions

How long should a B2B case study be?

Long enough to show the situation, the work and a checkable result, and no longer. Most need a summary box and a few hundred words; a complex project may need more. Put the client, the problem, the result and the period in the first screen, so a reader who stops there still gets the point.

Should case studies be gated behind a form?

Usually not. A case study is proof, and gating it hides that proof from the buyers and search engines who need it. Publish the full case study as a web page and, if you want, offer a PDF copy as an extra.

Can I publish a case study without naming the client?

Yes, if the client asks for that. Describe them precisely (sector, size, region), say the case study is anonymised at their request, and keep the same evidence on file as for a named one.

How many case studies does a B2B website need?

There is no fixed number. Aim for at least one relevant case study for each main service or each main sector you sell to, so every service page can link to proof that matches its buyers.

Sources

All sources accessed 3 November 2026.

Put your proof where buyers decide, with every change approved and measured.

Artiweave proposes specific changes from evidence, your team decides what is published, and outcomes are reported honestly. It is in private beta.

Join the waitlist