TL;DR: A case study that converts does three things in order: makes a stranger see themselves in the client, shows what changed not what was made, and makes the next step obvious. The structure that works: client one-liner, the problem in their words, the constraint, what we shipped, the measurable change, the client quote, the offer to talk. Keep it under 800 words. Lead with outcome, not process. Name the buyer, the timeline, and the dollar impact. Most agency case studies fail because they describe craft instead of change. Buyers do not hire craft. They hire outcomes they can picture themselves getting.
Most agency case studies are written by the agency's marketing person trying to make the agency look smart. The right way to write a case study is from the buyer's perspective: what did the client need, what did the work change, what did it cost. The case study works if the next reader can see themselves in it.
Here is the format that converts, the parts most studios get wrong, and a starter template you can use today.
What a case study has to do
Three things, in this order:
- Make a stranger see themselves in the client. The reader has to think "this is my situation."
- Show what changed. Not what was made. What changed.
- Make the next step obvious. If the case study reads like the work is for "people like this," the reader's next move is the contact form.
If the case study describes craft without naming the buyer or the change, it's a portfolio piece, not a sales tool.
The structure that works
Six sections, in this order. Each does one job.
1. The problem (1–2 sentences)
The first sentence names the client's specific situation in business terms. Not "they needed a website." Specific:
- "SupplyDivo outfits military units and command shops, and most sites in the category force a phone call to get a straight answer."
- "Reapify is a lead-gen product for agencies who have seen every SaaS pattern and stopped trusting most of them."
The reader recognizes a peer. That's the entire job of the first paragraph.
2. The shape of the project (1 paragraph)
What the engagement was. Scope, timeline, key decisions. No fluff, no "we collaborated closely" language. Just the project shape.
- Scope: "5 page redesign, custom theme, Klaviyo and Loop integration."
- Timeline: "4 weeks from kickoff to launch."
- Key decision: "We decided to ship without the bundle builder, then add it in a v2 once we saw which products buyers were actually configuring."
3. Outcomes (3–5 short bullets)
The most important section. Each bullet describes one observable change to the business — not a deliverable, not a feature.
Bad outcome bullet: "Built a new homepage." Good outcome bullet: "Single-CTA homepage replaces a buried demo form."
If you have hard numbers, use them. "Booking conversion up 38%" beats "improved conversions." If you don't have numbers, describe the observable behavior change. Don't fabricate metrics.
4. The thinking (2–4 short sections)
This is where craft shows up. Each section is one decision the project hinged on, written as the question and the answer.
Examples:
- "Why we built the homepage around a single CTA, not three."
- "Why the quote button carries product context, not just a generic form."
- "Why the booking flow doesn't appear in the navigation."
These sections show how the project thought, not what it shipped. They're what makes a case study feel like the team behind it has taste, not just a stack.
5. A client quote (1–3 sentences)
A real human's name. A real role. A specific sentence about something that changed for the client.
What works:
"Our reps used to chase artwork and quantities over three follow-up emails. Now the spec is on the request before they open it." — Sam, ops lead at SupplyDivo.
What doesn't:
"Webdimonia was great to work with! Highly recommend!" — Anonymous, satisfied client.
If you don't have a real quote yet, leave the slot empty. Anonymous testimonials are worse than none.
6. A soft CTA (1 sentence)
The case study ends with a one-sentence path: "If your team is in a similar situation, [next step]." Not a sales pitch. Just the obvious next move.
What most case studies get wrong
Five patterns that show up constantly.
1. The intro paragraph is about the agency, not the client. "We were thrilled to partner with..." Cut this. The intro is about the client's situation.
2. The "process" section dominates. Discovery → wireframes → design → development → launch. Buyers don't care about the process. They care about the outcome.
3. Visuals show pretty screenshots, not behavior change. Three full-bleed screenshots of the homepage tell the buyer nothing about whether the site works. A before/after, an annotated screenshot, or a 3-second clip of the working flow tells them everything.
4. The list of deliverables is buried at the end as a sidebar. If the deliverables are interesting (custom hero scene, automation pipeline), surface them. If they're standard (homepage, services page, contact form), don't bother listing them.
5. The case study is locked behind a "request the case study" form. If a case study is gated, nobody reads it. The buyer was trying to qualify your work and got asked to give up an email address. They left.
A starter template
Copy this. Fill in the blanks.
# [Client Name] — [one-line blurb]
## The problem
[Client] is [what they do]. They were [the specific situation]. Most companies in their position [what the obvious-but-wrong path is], and that wasn't going to work for them.
## The project
- Scope: [what we built]
- Timeline: [how long]
- Key decision: [the one tradeoff that defined the project]
## Outcomes
- [One observable change to the business]
- [Another observable change]
- [A third one]
- [Optional fourth]
## The thinking
### [Decision 1, framed as a question]
[The decision and why. 2–4 sentences.]
### [Decision 2]
[Same.]
### [Decision 3]
[Same.]
## In their words
"[A real quote from a real person.]" — [Name, role at Client]
---
If you're in a similar situation, [the obvious next step].
That's the template. It's what we use on our own case studies, and it works because every section earns its place.
What we ship for clients
When we work with a studio or service business on case studies, the typical engagement is:
- Three case studies rebuilt to this structure: $1.5–$3k.
- Original photography, screenshots, or motion per case: $300–$1k each.
- Schema markup (
Articleper case): included. - Internal linking from blog posts to cases: included.
Three real case studies done right outperform twelve weak ones. Quality over volume, every time.
Three questions to fix your case studies this week
- Does the first paragraph name the client's specific situation, not your service? If no, rewrite.
- Are there 3+ outcome bullets that describe behavior change, not deliverables? If no, ask the client what changed and rewrite.
- Is there a real client quote with a real name? If no, ask. Drafts are easier than they sound.
If you want a 10-minute review of one of your existing case studies (structure, outcomes, voice), send us the URL. We reply within a day.