How to write a B2B case study, including the ones your customer will not put their name to

Most B2B case studies are all outcome and no obstacle. A logo, a percentage, a manicured quote, and nothing that tells a buyer what it is actually like to work with you. They read like press releases because that is structurally what they are: a document the customer had to approve.

The better ones show the friction. And the best source of those is the story your customer will never let you put their name to.

What a B2B case study is for

A B2B case study is all about insight and converting buyer interest.

It’s not a trophy or a tome, it’s an exercise in showing the buyer what life could be like as your customer.

The buyer is shopping around, doing their homework; you need to clearly illustrate the gains you can bring to businesses like theirs, while convincing them not to go anywhere else.

It’s simple enough, in theory.

The structure that works

Good overcoming evil. Journeys from darkness to light. These are the stories that stay with us.

Except in the realm of B2B, ‘evil’ is ‘missed business targets’ and ‘ailing sales figures’ (existential threats to any organization, and more real than any Blofeld or Dr Octopus).

Telling a B2B success story should start with the problem and work towards the solution. Here’s a simple structure you can follow:

1. Set up the real starting position, and the scale of the problem: what’s broken and needs fixing?
2. Show your workings – we’re talking trials and tribulations (ideally not too many tribulations). Where did you try and fail, what didn’t work?
3. Capture the masterstroke, the strategic decision that reversed course and changed your client’s fortunes.
4. Give us the results: baseline facts and figures
5. Take a look back, reflect – is there anything the client would’ve done differently?

Why public references all sound the same

There are tacit rules to public references that dictate the stories we tell (and the way we tell them).

No customer is going to attach their logo to a case study that reflects badly on them. That’s just the reality of the transaction.

And that means public references all start to sound the same:

• They diminish the initial conditions that created the need
• They make everyone involved sound omniscient
• They smooth out any friction that doesn’t fit the positive narrative

In other words, they tell a story with all the depth and insight of a press release.

But what if you did something braver—by becoming an advocate for the buying decision your prospects are wrestling with?

Anonymity buys you honesty

What if by writing business case studies, you exposed what it’s really like to be a customer—good and bad?

There’s a universe of customer stories we’re not telling because we’re constraining ourselves to public, positive stories.

But anonymity grants marketers permission to explore the juiciest parts of customer stories they’d never normally touch.

B2B buying decisions are too long, multi-faceted and nonlinear to be effectively served by two-dimensional Good News stories. Getting insanely honest about the obstacles and friction along the way to the results you deliver signals confidence and builds trust in a way that most public references never achieve.

Let’s take a look at why, when you’re not constrained by someone else’s approval, there’s an infinite horizon of problems, solutions and benefits you’re suddenly free to explore.

Questions that get you a usable anonymous story

A good anonymous case study isn’t just a public reference with the names taken out. You need to fill the customer vacuum with a different kind of social proof: vulnerability.

Acknowledged hardship is the necessary source of conflict that both provides value for prospects (because they get to see what you’re like under pressure) and bypasses the question of believability.

The tacit agreement with a public reference is with the customer: we’ll make you look good.

With an anonymous case study, it’s with the reader: we’re confident enough to tell the truth.

So how do you expose the right kind of vulnerability? By asking bigger—potentially uncomfortable—questions that uncover what’s usually left unsaid.

Here are some business case study writing tips to get you started:

What was the reality of the problem you solved?

You don’t need to sand the edges from the pain of the old world. Get specific about the inefficiency holding them back, or the weak spot in their customer experience. Write something brutally honest (but compassionate) that prospects recognize from their own reality.

Once we worked with a brilliant software provider with a chronic blind spot in their cloud spend. They had a brilliant product, happy customers and a totally unnecessary cash flow haemorrhage jeopardizing everything.

Where was the friction in the sales process?

Did you help the customer better understand the business problem they’re trying to solve? Or conversely, were you doing something you’d never done before? Maybe you accepted aggressive pricing terms because there was a bigger upside for you? This is a chance to show your comfort with curveballs.

We love working with companies as ambitious as we are. Which is why when one manufacturer asked about refactoring our process optimization software for the sensors in their delivery trucks, we had to say yes. The whole thing was a leap of faith—and one that paid off for both of us.

What happened during implementation?

Were you handholding way more than you expected? Did you need to bring all hands on deck to handle sudden obstacles? Did the scope explode or focus pivot halfway through? Successful companies are always learning from the past—show your prospects the gnarly problems you’ve already solved.

We were two months into designing new network infrastructure for a chain of retail stores when news of the acquisition hit. The new owner brought in a whole new list of technology integrations we had to support. We had to develop emergency processes from the ground-up to get the project back on track. And now we’re ready for anything.

How did the results stack up?

Did the customer need to change some expectations or behaviours in order to achieve their goals? Were there any unexpected benefits or side effects? Did the project hit a road bump that you’ve since recovered from? Prove that you only win when your customers win.

We helped one construction company rationalize and consolidate over a decade of customer data, dispersed across countless legacy systems, into a single view. This created a different problem: they were overwhelmed with business development opportunities.

What does the future (actually) hold?

When you get to the good news, go beyond traditional financial and performance metrics and use anonymity as a license to get personal. Whose life is easier now? How are their customers impacted? Did someone impress their boss? Do you have exciting plans to keep them improving?

This story has a bittersweet ending. Three months after we finished deployment, we got an email from the IT director saying they were leaving the project team…to start as CIO. We’re sad not to speak every week anymore—but now we’re focused on getting the next person promoted.

In summary

How do you write a good B2B case study?

Start with the real problem including what was broken, say what you tried that did not work, then the decision that changed things, then the result against a baseline. Buyers use case studies as due diligence, not as reassurance, so the friction is the part that carries the value.

Are anonymous case studies worth publishing?

Yes, and they are often better than named ones. Anonymity removes the customer's approval constraint, which is what flattens most case studies into press releases. What you lose in social proof you can recover through specificity and honesty about what went wrong.

How long should a B2B case study be?

Long enough to contain a real obstacle. In practice 600 to 1,200 words for a written study. The one-page summary version is a different asset for a different moment and should be produced from it, not instead of it.

How many customer references does a B2B company need?

At least two per priority segment, region and use case, so no single customer's availability can stall a deal. Map your existing library against your target account list and the gaps usually become obvious in under an hour.