Lorixen.
EN

Case study pages for B2B service firms: a worked outline

Short answer: A good B2B case study page tells one client's problem, what you did and what changed, in the client's language, with their written approval. Agree permission and the level of detail before you write, use only results the client confirms (or describe outcomes without numbers), and offer an anonymised version when the client can't be named. Then link each case study to the service it proves, and let visitors filter by industry.

For consultancies, accountants, engineering firms and agencies, case studies often do more selling than the services page. Prospects want to see a business like theirs with a problem like theirs. The hard part is rarely the writing; it's getting permission, getting the facts right and keeping the client comfortable.

Why case studies carry so much weight

Nielsen Norman Group's article on what B2B sites can learn from B2C lists case studies and use cases among the ways to prove a service works, noting they're especially helpful when customers come from different industries and that variety addresses a wider range of concerns. In B2B, the person reading often has to persuade a colleague or a boss, so a case study is also something they forward.

Google's guidance on helpful, people-first content asks whether content shows first-hand expertise, provides original information, and makes it clear who created it. A real case study is exactly that kind of page, provided it contains real detail rather than marketing filler.

Step 1: Permission before writing

Before drafting a word, agree with the client contact:

  • Can we name you? Full name and logo, industry only, or not at all.
  • What can we say about results? Specific figures, ranges, or qualitative outcomes only.
  • Who approves the final text? One named person, ideally with authority to say yes.
  • Can we quote you? The quote is written or approved by them, word for word.
  • Visuals: can you show screenshots, documents, photos of their premises or team?
  • Duration: is there a date after which they'd like it reviewed or removed?

Get the approval in writing, even if it's a short email. Have a lawyer check any standard permission wording you use across clients.

Step 2: A worked outline (hypothetical)

The example below is entirely hypothetical, to show the structure. There's no real client, and the result placeholders show where approved facts would go.

Title: How a regional logistics company replaced spreadsheet scheduling with a shared planning tool

Summary box (top of page):

  • Client: a family-owned logistics firm in the Midlands (named, if approved)
  • Service: operations consulting and workflow software
  • Duration: [agreed timeframe]
  • Outcome in one line: [result the client confirmed, or a qualitative summary]

The situation: Dispatchers planned routes in shared spreadsheets. Version conflicts meant drivers sometimes got outdated plans. The managing director wanted one source of truth without forcing drivers onto complex software.

What we did:

  1. Shadowed dispatch for two days to map how plans were made and changed.
  2. Ran a workshop to agree which decisions the tool should support and which stay human.
  3. Configured a shared planning board, with a simple driver view on phones.
  4. Ran old and new systems in parallel for [agreed period], then switched.

What changed: [Approved result, for example "fewer last-minute plan changes reached drivers", stated in the client's words, with a figure only if the client provides and confirms it.]

In their words: "[Quote approved in writing by the named contact.]"

What we'd do differently: One honest sentence about something you learned. It's often the most convincing part of the page.

Related service: link to your operations consulting page.

Results without invented numbers

Numbers persuade, but only if they're real. Rules worth adopting:

  • Only publish figures the client gave you or confirmed, and say what they measure and over what period.
  • If figures aren't available or can't be shared, describe the change: what used to happen, what happens now, who noticed.
  • Never round up, extrapolate or calculate a percentage the client didn't sign off.
  • If several factors contributed to a result, say so.

Anonymised versions

Many clients can't be named: confidentiality, competitive reasons, or simple caution. An anonymised case study still works if it keeps the specifics that matter to a reader:

  • Industry, size band and region ("a mid-sized engineering firm in Munster")
  • The problem in concrete terms
  • Your approach, step by step
  • Outcomes described qualitatively

Check that the combination of details doesn't make the client obvious anyway, and get the client to approve the anonymised text too.

Page layout that works on the web

  • Summary box at the top for skimmers
  • Short sections with plain headings: situation, approach, outcome
  • One or two visuals: a before-and-after screenshot, a process diagram, a photo of the work
  • The approved quote, attributed
  • A link to the related service and to similar case studies
  • A clear next step: "Talk to us about a similar project"

Making the collection useful

Once you have five or more, add an index page with filters by industry and service. Each card shows the client (or description), the problem in one line, and the service. Prospects scanning for "someone like me" should find them in seconds.

Field checklist for each case study

Field Required? Notes
Client name or anonymised description Yes As approved
Industry and size band Yes Used for filtering
Service(s) provided Yes Links to service pages
Problem statement Yes In the client's terms
Approach (steps) Yes What you actually did
Outcome Yes Approved figures or qualitative
Quote Optional Approved word for word
Visuals Optional Approved, no confidential data
Approval record Internal Who approved and when
Review date Internal When to re-check with the client

FAQ

How long should a case study page be?

Long enough to explain the problem, approach and outcome clearly, often 600 to 1,000 words. A summary box lets busy readers get the point in seconds.

Should case studies be PDFs or web pages?

Web pages first: they can be found in search, linked from service pages and read on a phone. Offer a PDF version for prospects who want to forward it.

What if a client relationship ends?

Check with them whether the case study can stay up. A review date in your records makes this a routine question rather than an awkward one.

Can we write a case study from an internal project?

Yes, as long as it's described as such. An internal or pilot project shows method, just not client results.

Turning finished projects into case study pages clients are happy to approve is something we can help you set up as a repeatable process.

Sources

WhatsAppLet’s talk