The structure (and why it is in this order)
A case study is not an essay. It is four blocks, read in the order a prospect thinks in: was this me? → what did they do? → did it work? → can I trust this?
- Challenge — the situation before, in the client's terms. This is the block that makes a reader recognise themselves. Skipping it is the most common mistake.
- Solution — what you did, in plain language, plus the one decision that changed the outcome.
- Results — a number, a timeframe, or an observable change. One honest, specific outcome beats three vague ones.
- Customer quote — left in their voice, typos and all. Polished quotes read as invented.
Blank template
Paste it into a doc and fill the brackets.
[Client name] — [result in one line] CHALLENGE Before working together, [client] was [specific situation]. It mattered because [cost of the problem: time, money, missed opportunity]. SOLUTION We [what you actually did, in plain language]. The part that made the difference was [the decision or step that changed the outcome]. RESULTS [Number, timeframe or observable change]. [A second, softer outcome — confidence, time back, fewer fires.] IN THEIR WORDS "[One or two sentences, unedited, in the client's voice.]" — [Name], [Role], [Company]
The same template, filled in
Everything below came from four short answers from the client — nothing was invented, only rewritten.
Worked example
Notice how each block traces back to one client answer.
Northlane Studio — stopped improvising every launch CHALLENGE Every product launch at Northlane was improvised. Two people held the process in their heads, and each launch cost roughly a week of scrambling. Nothing was repeatable, so nothing got faster. SOLUTION We mapped their last three launches, kept what worked and dropped the rest into a single checklist the whole team follows. The part that made the difference was assigning one owner per stage — not more process, just a clear name next to each step. RESULTS Launch prep went from about a week to two days. The first launch after the change shipped on the planned date, which had not happened in a year. IN THEIR WORDS "Every launch used to be improvised. Now there is one clear plan the whole team follows — it paid for itself in about two weeks." — Ana Duarte, Head of Product, Northlane Studio
The four answers that produce it
You do not need an interview. These four questions give you one block each:
- What was going on before we worked together? → Challenge
- What changed, and what made the difference? → Solution
- Is there a number, a timeframe or something you can now do? → Results
- What would you say to someone hesitating? → Quote
Three things that quietly ruin a case study
- No before. Results with no starting point are unreadable. "Doubled leads" means nothing without "from what".
- Your voice everywhere. If the quote sounds like your marketing copy, readers discount the whole page.
- Waiting for a perfect number. "Paid for itself in about two weeks" is specific enough. Do not hold a case study for six months waiting for a dashboard screenshot.
Approval, in one message
Send the draft to the client before publishing. It takes one line and almost always comes back approved.
Approval message
Hi [name] — I wrote up how the project went, using your own words for the quote. Draft below. Happy to change anything, or cut the numbers if you would rather not share them. If it looks right, I will publish it as is.