How to Turn Your Work Into Proof: The B2B Case Study Page

Every B2B company has done work it’s proud of. Far fewer have turned that work into something a prospective buyer can read.

This matters more in B2B than almost anywhere else. A buyer choosing a supplier is making a decision they’ll have to defend internally, often to people who never visited your site. What they need isn’t a claim that you’re good. It’s evidence, in a form they can forward to a colleague.

That’s what a case study is for. Not a portfolio entry, and not a press release. A short, specific account of a problem you solved for someone like them.

Why most B2B case studies don’t work

Look at a dozen and the same failures repeat.

• There’s no problem. They open with the solution, which removes the only part a reader recognizes themselves in.
  
  
• The results are vague. “Improved efficiency” tells nobody anything. Buyers assume the worst when numbers are missing.
  
  
• They’re anonymous by default. Every client is “a leading manufacturer,” which reads as though you’re not sure it happened.
  
  
• They read like a press release. Adjectives instead of specifics, and quotes that sound written by committee, because they were.
  
  
• They’re buried. A PDF behind a form, or a portfolio page with a logo and no story.

The underlying issue is that most case studies are written to look impressive rather than to be useful, and buyers can tell the difference immediately.

Why Most Case Studies Fail

There’s no problem, only a solution

Results are vague or missing

Every client is anonymous

They read like a press release

They’re buried behind a form

The structure that works

A good case study answers six questions in roughly this order.

1. Who is this about? Name, industry, size, and enough context so that a reader can decide whether this is someone like them.
   
   
2. What was the problem? Ideally, you’ll want to state this in the client’s words. Be concrete about what wasn’t working and what it was costing them.
   
   
3. Why was it hard? State the project’s constraint. A deadline, a technical limitation, a merger, a regulatory requirement. This is what separates a real story from a brochure.
   
   
4. What did you do? Enough that a reader understands the approach, without turning into a methodology lecture.
   
   
5. What happened? Provide results, as specific as you’re permitted to be.
   
   
6. What did they say? A quote from a named person with a real title, ideally saying something a marketing department wouldn’t have written.

The third question is the one most companies skip and the one that does the most work. Anyone can describe a project that went smoothly. Describing a genuine constraint and how you handled it is what makes a buyer trust the rest.

The Six Questions to Answer

1. 1
   Who is this about? Enough context that a reader can decide whether this is someone like them.
2. 2
   What was the problem? In the client’s words, and concrete about what it was costing.
3. 3
   Why was it hard? The constraint. This is the part most companies skip.
4. 4
   What did you do? Enough to understand the approach, without a methodology lecture.
5. 5
   What happened? Results, as specific as you are permitted to be.
6. 6
   What did they say? A named person with a real title.

Write it while it’s fresh

The best moment to write a case study is the week the project finishes. Everyone remembers the constraint, the client is pleased, and the numbers are still to hand.

The worst moment is eighteen months later, when the team has moved on, the baseline figures have been overwritten, and your contact has changed jobs. Most companies have a drawer full of projects in exactly that state.

A simple habit fixes it. When a project closes well, book thirty minutes to answer the six questions below while the details are still in someone’s head. It doesn’t have to be publishable that day. It just has to exist before your memory of the project fades.

Getting numbers you can actually use

The most common blocker is that nobody measured anything, or the client won’t let you publish what was measured.

Some options, in descending order of preference.

Ask for the numbers before the project ends, ideally at kickoff. Baselines are easy to capture at the start and nearly impossible to reconstruct two years later.

Use relative figures if absolutes are sensitive. “Enquiries up 40%” is publishable when “from 12 to 17 per month” is not.

Use the client’s own operational measures. Time saved, error rates, onboarding speed, or fewer support calls are often less commercially sensitive than revenue and just as persuasive.

Use a qualitative result honestly. If you have no numbers, say what changed in plain terms rather than inventing a percentage. A specific description beats a fabricated statistic, and inventing one is the fastest way to lose a reader who checks.

When you can’t name the client

Procurement rules, competitive sensitivity, or a client who simply says no are some of the reasons why you can’t genuinely include the name of the client in the case study.

Anonymize carefully rather than vaguely. “A Southern Ontario food processing company with four plants” gives a reader far more than “a leading manufacturer.” Keep the industry, the scale, and the shape of the problem. Remove only what identifies them.

It’s also worth asking properly rather than assuming the answer is no. Approach the person you worked with, not their legal department, and make it easy. Offer to write it and send it for approval, tell them exactly where it will appear, and let them edit. Most people say yes when the work went well and the request arrives shortly afterward.

Where case studies live on your site

A case study nobody finds isn’t proof of anything.

Give each one its own page with a descriptive URL rather than collecting them all in one document. Separate pages can rank for the problem they describe, which is how buyers in the research stage tend to find them.

Then link them from where decisions happen. On the relevant service page, near the point where you ask someone to get in touch, and from the homepage if the story is strong. A buyer comparing vendors is the person most likely to read one all the way through, so put them within reach of that moment.

Don’t put them behind a form. The gated PDF made sense when contact details were scarce. Today it mostly ensures your best proof is read by nobody, at the exact point in the journey where a buyer is deciding whether to shortlist you.

What a good one reads like

The difference between a case study that works and one that doesn’t is usually visible in the opening two sentences.

The version most companies publish:

Lakeshore Filtration is a leading provider of industrial air filtration solutions. We partnered with a major food processing client to deliver a comprehensive system upgrade, leveraging our expertise to achieve outstanding results.

The version a buyer reads to the end:

A four-plant food processor in southwestern Ontario was failing internal air quality audits at one site, and a failed external audit would have paused production. Their existing system was fifteen years old, and the plant could not shut down for more than a single weekend.

We designed a replacement that could be installed in stages across three consecutive weekends, with each stage leaving the line operational. The plant passed its next audit with no production days lost.

“The part that mattered was that they planned around our shutdown window instead of asking us to plan around theirs.” — Operations Director

The second version is barely longer. What it has is a real problem, a genuine constraint, a specific outcome, and a quote that sounds like a person rather than a marketing department.

It also contains something the first version can’t: a reason for a similar buyer to recognize themselves. Any plant manager with an ageing system and no shutdown window has just read their own situation described accurately by someone who has solved it before.

Weak

• “A leading manufacturer”
• “Improved efficiency”
• No constraint mentioned
• A quote from “the team”

Strong

• Named, or specifically described
• A number, or an honest description
• The constraint that made it hard
• A named person with a title

Start with three

Companies stall on this because they imagine documenting everything. You don’t need everything.

Pick three projects. One that shows the work you most want more of, one from your strongest vertical, and one where something went genuinely wrong and you fixed it. That third one is often the most persuasive thing on your site, because it’s the only kind of story your competitors won’t tell.

Write those, publish them properly, and you’ll have more usable proof than most of the companies you’re bidding against.

Show the work

Case studies are the closest thing a B2B website has to a salesperson who never sleeps. They answer the question every buyer is really asking, which is whether you’ve solved this before for someone like them, and they answer it without you being in the room.

Most companies have the raw material sitting in finished projects and completed invoices. The only thing missing is somebody writing it down while the details are still fresh. If you’d like help turning your work into case studies that earn their place, book a discovery call and we’ll talk through which projects to start with – no pitch, and no pressure.