Template · 9 min read
Case study template: turn a client win into proof that sells
Somewhere in your last year of work is a result that would close your next three deals — if it existed anywhere outside a Slack thread and your memory. That's the case study problem: the wins are real, but unwritten proof is worth nothing in a buying decision. This template turns one client win into a one-page document a prospect reads in a minute and believes. The structure is below with the reasoning, plus the client-approval playbook and a prompt that makes AI draft the whole thing from your raw facts.
What a case study is actually for
A case study has exactly one job: let a buyer borrow someone else's experience of hiring you. Your proposal says what you'll do; your case study proves you've done it — for someone who had the buyer's problem, at the buyer's scale. It's read at the most skeptical moment in the funnel, usually side by side with your pricing, by someone actively looking for reasons to say no.
That context dictates the form. This is not brand storytelling and not a portfolio piece — it's evidence, and evidence has rules: specific numbers, a named or precisely-described client, a timeframe, and the client's own voice. The moment a case study starts reading like your marketing wrote it, it stops working, because the reader's whole reason for being there is that they don't trust your marketing.
And the hero matters: the client, not you. The story arc is theirs — their problem, their stakes, their result. You appear as the instrument. Case studies that star the vendor ("we leveraged our proprietary framework") read as ads; case studies that star the client read as references. The buyer is casting themselves in the client's role, so give them a protagonist worth identifying with.
The template, section by section
Seven sections, one page. The result leads; the story exists to make it credible.
- Headline result. The strongest number, with its timeframe, as the title: "34% fewer support tickets in 90 days." Not "Case Study: Acme Corp." The reader decides whether to read at all based on this line, so spend the best fact here rather than saving it for the ending.
- Client context. One line: who they are, what size, what world they operate in. Enough for the reader to answer "is this like me?" — that's all this section is for.
- The problem. Two or three sentences with the stakes attached: what was happening, what it cost, why the obvious fixes hadn't worked. The result in the headline is only as impressive as the problem was real.
- What we did. The approach in three to five bullets — including why this approach over the alternative the reader is probably imagining, and the wrinkle: the first thing that didn't work, the constraint you worked around. That one honest detail does more for credibility than every adjective you could add.
- Results. A before/after table with timeframes. Numbers the client signed off on, defined the same way in "before" as in "after". If a result can't be quantified, name the concrete change instead — "the founder stopped doing support on weekends" is a result; "improved efficiency" is fog.
- The quote. The client's real voice, saying something specific. "They found the problem two audits had missed" outsells "great to work with" by a mile. Drafting a quote for the client to edit and approve is normal practice — inventing one is not.
- What this means for you. Two sentences bridging to the reader: who this result is repeatable for, and what the first step looks like. Without this, the case study is a trophy; with it, it's a sales document.
One rule over all seven: specificity beats adjectives, everywhere. A precise number implies a measurement; a vague superlative implies its absence. Cut every "significantly", "dramatically" and "seamlessly" and let the table do the talking.
Getting the client to say yes
Ask at the moment of the win. The right time to request a case study is the week the result lands — goodwill peaks, the numbers are fresh, and the person who'd approve it is the one celebrating. Six months later the champion has changed jobs and the ask needs a meeting.
Make it cost them nothing. You draft everything — the story, the numbers, even a proposed quote — and they edit and approve. Final sign-off on every word and figure is theirs, in writing. That's not just courtesy; approved numbers are the difference between proof and a future awkward phone call.
Have an anonymity fallback ready. Plenty of clients can't be named — competitive reasons, procurement policy, legal caution. Take the deal: "a 40-person logistics company" with real numbers beats a named logo with the numbers lawyered out. Precision is what persuades; the name is a bonus. And when a client says no entirely, respect it and move to the next win — one strong case study you can actually publish outworks three you can't.
One page per win — and know when a prospect reads it
results grow ↻ the proof stays current
- Tue 11:20
Sent with the proposal
- Tue 15:47
Prospect opened · 3m 05s
- Wed 10:02
Opened again — new viewer, same company
- Wed 10:30
It's being passed around. Good sign — follow up
Publish each case study as its own page at a permanent link, and it stops being a static asset. When the six-month numbers beat the ninety-day numbers, you update the page in place — every proposal you've ever sent now points at the stronger version. A PDF case study is frozen at its weakest moment; a living page compounds with the result.
The read signal earns its keep in proposal week. You send the proposal with two case studies linked; the tracked pages show whether the prospect opened them, for how long, and — the interesting one — whether new viewers from their side show up. A case study being passed around a buying committee is one of the strongest signals a deal gives off before the yes. The usual honesty applies: opens aren't identities, forwarded links and mail scanners count, and time-on-page is approximate. It's a signal for when to follow up, not evidence to quote at anyone.
Draft it with AI (prompt included)
The facts already exist — in the final report, the before/after metrics, the client's thank-you email. What kills case studies is the blank page, and that part an AI does well. The prompt below encodes the structure, the specificity rule, and the two hard constraints: never invent a number, never invent the quote.
Copy, fill in the brackets with the win's real facts, paste into Claude or ChatGPT:
You are producing a one-page client case study as a single, self-contained HTML file. CONTEXT — replace everything in brackets: - Client: [name, or an anonymized descriptor like "a 40-person logistics company"] - My company / role: [who did the work] - The problem they had, and what it was costing them: [the situation + the stakes] - What we did: [the approach in 3-5 bullets, including WHY this approach over the obvious alternative] - One thing that didn't work first, or a constraint we had to work around: [the honest wrinkle] - Results, each with a number and a timeframe: [metric — before — after — timeframe, one per line] - Client quote: [their words, verbatim — or "draft one for approval" and mark it clearly as a draft] - Who should read this: [the kind of buyer this proof is aimed at] - Brand: [primary hex color] + [logo URL, or "text wordmark"] REQUIREMENTS: - The headline states the strongest result with its number and timeframe — not the client name, not "Case Study". - Section order: Headline result · Client context (one line) · The problem · What we did · Results (as a before/after table) · Client quote · What this means for you. - Keep every number exactly as I gave it. If something is missing, leave a clearly marked [TBD] — never invent data, and never invent or embellish the quote. - Include the wrinkle — the thing that didn't work first belongs in "What we did". It makes the rest credible. - Self-contained HTML: inline CSS, no external scripts, readable on a phone, printable. 300-600 words. - Tone: testimony, not advertising. No superlatives, no "delighted to", no adjective where a number will do.
- 1 Paste the prompt (with your details filled in) into Claude or ChatGPT. You get a finished, self-contained HTML document — review it, correct anything, iterate until it's right.
- 2 Publish it as a permanent tracked link: with the Pagelive connector in Claude, say "publish this page" and the link comes back in chat — next cycle, "update it" replaces the content at the same URL. Or paste the HTML at app.pagelive.io.
Then the human steps that can't be skipped: check every number against the source, replace or get approval on the drafted quote, and send the finished page to the client for sign-off before it goes anywhere near a prospect. AI drafts the testimony; the client certifies it. A case study that skipped approval isn't an asset — it's a liability with formatting.
Frequently asked
Seven sections, in order: a headline that states the result; one line of client context; the problem with its stakes; what you actually did and why that approach; results with numbers and a timeframe; a client quote in the client's real voice; and a bridge that tells the reader what this means for them. The result leads — the story exists to make the number credible.
One page — 300 to 600 words. A case study is proof, not a memoir: the buyer reads it mid-decision, usually next to your proposal, and gives it about a minute. If the engagement genuinely needs more, layer it: the one-pager up top, detail linked below for the reader who digs.
Anonymize with precision: replace the name with industry plus size — 'a 40-person logistics company', 'a Series B fintech' — and keep every number real. Specific and unnamed reads far stronger than named and vague. Say why it's anonymous if asked; buyers understand confidentiality, they don't forgive fog.
Ask at the moment of the win, not months later — right after the result lands, when goodwill peaks. Make it effortless: you draft everything, they approve or edit, and they get final sign-off on every word and number. Offer anonymity as the fallback. Timing and low effort convert far more case studies than incentives do.
Specificity. '34% fewer support tickets in 90 days' beats 'dramatically improved efficiency' every time, because a precise number implies a measurement and a vague adjective implies its absence. Add the messy detail a marketer would cut — the first approach that didn't work, the constraint you worked around — and the whole document starts reading as testimony instead of advertising.
Related: consultant proposal template · consulting report template · how to make a one-pager
One page per win. Updated as the results grow, tracked when prospects read it.
Draft the case study with AI, publish it as a permanent link you can update in place, and see when a buying committee starts passing it around. Free for 5 pages, no card.