A case study is not a long testimonial. It is a record of a decision: what the customer faced, what options existed, what was done, and what changed. When it is written well, the reader finishes it with a picture of how you work, not a list of how great you are.

Most case studies fail in the same way. The customer appears for two paragraphs, the company takes over for six, and the result is a percentage with no explanation of how it was measured.

Decide what the reader should take away

Before drafting, write one sentence: after reading this, a reader considering a similar purchase should understand ___. Usually it is a trade-off, not a triumph. That the migration took longer but avoided downtime. That the cheaper option was rejected for a reason.

This sentence governs everything. It tells you which facts to keep, which quotes to chase, and where to stop.

Set the scene with constraints

Open with the situation as the customer experienced it: the size of the team, the systems in place, the deadline, the thing that could not be broken. Constraints make the story credible, because every real project has them.

Include the context a stranger needs. Industry, scale, location, and the trigger for the project. Two short paragraphs is plenty. Resist the urge to begin with the history of the client's company.

Let the customer describe the problem

Use their words. If they said the reporting was held together with sticky tape, keep that phrase and attribute it. A direct quote early in the piece signals that the rest is not entirely your narration.

Then add the part they could not see from inside: the cost of the problem, the workaround that had become normal, the risk nobody had quantified. Say plainly which of these you observed and which the customer told you.

Explain the decisions, including the ones you rejected

This is the section that separates a case study from an advert. Describe two or three options you considered and why one was chosen. If you recommended against the obvious solution, say so and explain the reasoning.

A reader learns more from your judgement under constraint than from a list of features delivered. Keep the sequence clear: what you found, what you proposed, what changed after the first week.

The rejected option is often the most persuasive paragraph in the whole document.

Report results you can defend

One primary number, agreed with the customer, with its baseline and its measurement window. Two supporting numbers at most. If the primary result is qualitative, such as a reduction in complaints, describe how it was tracked.

Where a number is uncertain, say so. The figure was estimated from the support inbox, not from the billing system. That sentence protects the whole document, and readers notice the honesty.

Include what went wrong

A short paragraph on the difficult part: a delay, a system that did not behave, a decision that was reversed. Explain what you did about it. This is not a confession, it is evidence of how you operate when the plan meets reality.

Customers reading a case study where nothing went wrong assume the document is marketing. Customers reading one where something did go wrong, and was handled, assume the supplier is honest.

Close with a quote that adds something. The final quote should not repeat the results. It should say something the numbers cannot: what the working relationship felt like, or what the customer would tell a peer. One quote. Two at most.

Then a short summary box: the client, the service, the timeframe, the headline result. Readers who skim will read that box instead of the article, so make it accurate on its own.

Keep the process repeatable

Build a template with fixed sections and a fixed interview. Six questions to the customer, a review of the project file, one approval round. The constraint makes each case study faster to produce and easier to compare.

  • Takeaway sentence written first
  • Constraints and context in the opening
  • Customer quote describing the problem
  • Two rejected options explained
  • One primary metric with baseline and window
  • One paragraph on what went wrong
  • Final quote that adds new information
  • Summary box readable on its own
  • Written approval from the customer

Leave out the superlatives, the agency voice, and the paragraph about your culture. The work should be impressive enough without them, and if it is not, the case study is the wrong place to fix that.