How to write a case study page that wins new clients
A case study that wins clients follows challenge, approach, result — with specific numbers or outcomes, not just pretty screenshots. Every case study needs a next step at the end, or it's just a portfolio piece with no job to do.
A case study page has one job: convince a stranger who has never worked with you that you can solve their specific problem. Most agency case studies fail at this. They show a logo, a few screenshots, and a line like "great to work with, highly recommend" — which tells a prospect nothing about what you actually did or whether it worked.
The fix isn't more design polish. It's structure. A case study that sells follows a simple shape: what was broken, what you did about it, and what changed. Skip any of the three and the page stops doing its job.
The three-part structure: challenge, approach, result
Every persuasive case study answers three questions in order. What was the client's actual problem, in terms they'd recognize. What did you specifically do about it — the decisions, not just the deliverables. And what happened afterward, described as concretely as you're able to.
| Section | What it must contain | Common mistake |
|---|---|---|
| Challenge | The client's real problem, described in their words | Skipping straight to 'we built a website' |
| Approach | The specific decisions you made and why | Listing deliverables with no reasoning |
| Result | What changed, as concretely as you can say | A vague close like 'the client was thrilled' |
Start with a challenge the reader recognizes
Open with the problem, not your solution. A prospect skimming your site is looking for one thing: does this agency understand a business like mine? If your opening paragraph describes a challenge that sounds like their own — too many missed calls, a site that doesn't reflect the quality of the work, a rebrand that never made it online — you've already earned the next thirty seconds of attention.
Be specific about the starting point. "Their old site hadn't been touched since 2019 and had no way to book a consultation online" tells a reader something real. "They needed a website refresh" does not.
Show your approach, not just your output
This is the section most case studies skip entirely, and it's the one that actually differentiates you from every other agency with similar screenshots. A list of deliverables — "new homepage, services page, contact form" — tells a prospect what you shipped. It says nothing about how you think, which is what they're actually trying to evaluate.
- 1Name the key decisionWhat did you choose to prioritize, restructure or cut, and why.
- 2Explain the reasoning in plain termsConnect the decision back to the client's actual goal, not a design principle.
- 3Show the artifactA screenshot, a before/after, or a short annotated mockup of the specific change.
- 4Note anything you deliberately didn't changeRestraint is a credible signal — it shows judgment, not just output.
If you standardized on a template for this build, this is also the natural place to mention it. Framing it honestly — "we started from a proven structure so the budget went into messaging and photography instead of rebuilding a layout from scratch" — reads as smart resourcing, not a shortcut.
End with a result, stated as concretely as you honestly can
This is where most case studies get vague, usually because the numbers aren't dramatic or weren't tracked well. That's fine — don't invent a stat to fill the gap. A specific, honest, modest outcome beats a vague, inflated-sounding one every time. "Went from zero online bookings to consistently taking 8-10 a week" is concrete and credible even without a huge percentage attached to it.
If you genuinely don't have a measurable number — the client didn't have analytics before, or the project was too recent to show a trend — say what changed qualitatively instead. "The owner now sends the site link to prospects during sales calls instead of avoiding it" is a real result, even without a chart behind it.
Use client quotes for specifics, not praise
A generic quote — "amazing to work with, would recommend to anyone" — does nothing a five-star badge doesn't already do. The quotes that actually move a reader are the ones with a specific detail in them: what the client was worried about beforehand, what surprised them, or what they'd tell someone in their position considering the same move. If you only have generic quotes on file, it's worth going back to a past client and asking one better follow-up question rather than publishing filler.
Give the page a job after the read
A case study with no next step is just a portfolio piece. End every one with a clear, low-friction action — book a call, see another example, or check availability. If a prospect finishes reading convinced and then has to hunt for how to contact you, you've lost most of the momentum you just built.
- ›The challenge, in one recognizable sentence
- ›Three specific decisions, each with a short reason
- ›One annotated before/after screenshot
- ›A result stated in plain, honest terms
- ›A single CTA: 'See how we'd approach yours'
A case study page structured to answer the reader's real question: can this agency do this for me too.
- ✓Structure every case study as challenge, approach, result — in that order.
- ✓Open with a problem the reader recognizes, not your solution.
- ✓Explain your reasoning, not just your deliverables.
- ✓State results as concretely as you honestly can — modest and real beats vague and impressive-sounding.
- ✓Use quotes with specific detail, not generic praise.
- ✓End with one clear next step, every time.