How To Write A Case Study People Believe

A case study is read by someone who suspects it is marketing, because it usually is. The genre has been degraded by two decades of testimonials dressed as evidence: a happy quote, a percentage with no baseline, and a logo.

The good version is a different document. It is closer to a short incident report than to a brochure, and its distinguishing feature is that a sceptical reader can check whether the claim is plausible.

Give The Baseline Or Do Not Give The Number

“Reduced response times by 60%” is not a fact. Sixty per cent of what, measured how, over what period, compared to what?

Before:

After implementing our solution, the client saw a dramatic improvement in team productivity and a significant reduction in time spent on routine communication tasks.

After:

Before: 14 support agents, each spending roughly 90 minutes a day writing and rewriting customer replies, measured over two weeks in March using their helpdesk timestamps. After: about 55 minutes a day over the equivalent two weeks in June. Ticket volume was 8% higher in June, and two agents were new in that period.

The second version includes an inconvenient detail, which is precisely why it is believable. It also survives being quoted, because the number travels with its method.

The density is not a problem here. Nielsen Norman Group’s work on when website reading actually happens found that people do read closely when the page is directly relevant to a decision they are making, and a case study is read by nobody else.

If you cannot get a baseline, do not manufacture a percentage. Describe what changed qualitatively and say the measurement was not instrumented. That is less impressive and considerably more credible.

Structure It As A Decision, Not A Journey

The template most case studies follow is challenge, solution, results. It is fine, and it produces a document that reads like a story about your product.

The version buyers actually use follows their own decision instead.

The situation, with specifics. Company size, team, constraints, what they were using before.

What they tried first, and why it failed. This section is almost always missing, and it is the most valuable one. A buyer in the same situation has tried the same thing.

What made them hesitate. The objection. Name it and say how it resolved, including where it did not.

What happened, with method. Numbers plus how they were obtained.

What is still not solved. One paragraph. This is where you win the sceptic.

The Unimpressive Result Problem

Sometimes the outcome is modest, and the reflex is to inflate it into a percentage that sounds better or to quietly not publish.

There is a third option that works well: publish it as a bounded claim. “Saved each agent about half an hour a day, which paid for the licences in the second month and did nothing for our escalation backlog” is a sentence a buyer can act on. A modest, precise result outperforms an impressive vague one with the audience that has budget authority.

Getting Approval Without Losing The Content

The usual damage happens in the customer’s legal review, which strips the numbers, the names, and the failure. What comes back is unusable.

Two moves help. Ask for approval on specific sentences rather than on a full draft, since a reviewer editing a whole document will smooth everything. And offer anonymisation of the company before you offer removal of the figures: “a 40-person logistics company in the Netherlands” preserves the evidence and usually clears review faster than a named logo with vague numbers.

A Wrivio Context for the approval draft could say:

Rewrite this case study to remove identifying details while preserving every figure, measurement method, date range, and stated limitation exactly as written. Replace the company name with the description provided, and remove named individuals. Do not add outcomes, benefits, or quotes that are not in the original, and do not round or restate any number.

Press Ctrl+Shift+Space, paste the section, and check the diff line by line. The instruction not to round is deliberate: a rewrite tidying “about 55 minutes” into “under an hour” has softened the evidence, and the anonymisation pass is exactly where that kind of quiet loss happens.

Publish The Quote Last

The customer quote is the least load-bearing element and the one teams get first. Get it, use it, and do not let it carry any claim that is not established elsewhere in the document.

A quote saying “it transformed how our team works” supports nothing. A quote saying “we stopped doing the Friday afternoon rewrite session entirely” describes an observable change, and those are the ones worth chasing during the interview.

Where It Sits In The Funnel

Case studies belong in the group of pages that still earn a click, because a summary of one is worthless to the reader: they came for the detail. That puts them alongside comparison pages in the priority list, for the reasons set out in zero-click search and what to do about it, and they benefit from the same specificity discipline as comparison pages.

Common Questions

How long should a case study be?

600 to 1,200 words. Longer usually means narrative padding, and the sections that matter are the constraint, the method, and the limitation.

What if the customer will not be named?

Anonymise the company and keep the figures. A described company with real numbers is more useful to a buyer than a named logo with vague claims.

Should I include a customer quote?

Yes, but only for describing an observable behaviour change. A quote asserting a benefit that the data does not show weakens the document.

What if the results were modest?

Publish them precisely. A small, credible, method-backed result convinces sceptical buyers more reliably than a large unexplained percentage.

Download Wrivio for Windows to prepare an anonymised case study draft locally, with a rewrite that leaves every measured figure exactly as you wrote it.