How to Write an Agency Case Study That Wins Deals

Why Most Agency Case Studies Don't Close Anything

The default agency case study is written for the wrong reader. It's written for the design community, for the award jury, for the founder's own portfolio. That's why it opens with a mood shot, explains the creative process, and ends with a lovingly cropped view of the final deliverable. Nothing in it is written for a buyer.

A prospect reading a case study is not admiring the work. They are running a silent simulation: could this agency do the thing I need done, for a company that looks like mine, with a result I could defend in front of my CFO? If the page doesn't let them answer that, they close the tab. The work might have been brilliant. The case study did nothing.

I treat case studies as a sales asset, not a portfolio piece. That reframe changes almost every decision — what goes in, what gets cut, how it's structured, where it lives, and who it's aimed at.

What a Prospect Is Actually Reading a Case Study For

Before I write a single line, I write down what the reader needs to answer. Not what I want to show — what they need to decide. Four questions, every time.

• Is this agency working on the same problem I have? Pattern-match on situation, not industry. The closer the before state reads to their own, the more the rest of the case study lands.
• Did they actually do something, or did they just show up? A prospect is trying to separate agencies that make calls from agencies that take orders. The case study has to show a specific decision the agency made that the client couldn't have made alone.
• Did it work in a way that matters? "Matters" is defined by the buyer's vocabulary, not the agency's. Revenue, pipeline, cost, time, retention — not impressions, engagement, or creative awards.
• Would I hire them for the same thing? This is the question the case study has to leave them holding. If the page ends and they don't know what to hire the agency for, the page failed.

Almost every decision after this is in service of making those four questions easy to answer. Any paragraph that doesn't advance one of them gets cut.

The Five-Part Structure I'd Use

I'd keep the shape deliberately simple. Five sections. Same order every time. The discipline of the format is what makes the page readable in ninety seconds, which is all the time a real prospect is going to spend on it.

1. The client in one paragraph. Not a bio. Just enough to let the reader pattern-match. Who they are, what stage they're at, what the commercial reality looked like. Two or three sentences is plenty.

2. The before state. The specific situation that led them to bring you in. Not "they wanted to grow" — the actual friction. The thing that wasn't working, in the detail they would have described it to their own board.

3. The decision the agency made. The one call that mattered. This is the section most case studies fumble, because it's where the work is supposed to live. But a prospect doesn't need the process; they need the judgment. What did you see that the client didn't? What did you choose to do differently from what they'd asked for? This is the only section that demonstrates that the agency is a thinking partner, not a vendor.

4. The result. Outcome in the client's language. If there's a number, use the number. If there isn't, use the change — what the client could now do that they couldn't do before, or what stopped happening that had been a problem. Specificity beats scale. "Closed three enterprise deals inside a quarter" is worth more than "dramatically improved pipeline."

5. The line back to the service. A short closing section that names the capability being sold — not the project, the service. A sentence about who else this type of engagement is a fit for, and a single, clean call to action. No hero image. No masthead. Just the offer.

The whole page should be readable in under two minutes. If it's longer, it's probably describing process. Process is what agencies want to talk about; it's rarely what buyers need to see.

How to Write the Before State Without Making It a Puff Piece

The before section is the one most agencies skip or soften, because it feels impolite to describe a client's situation too sharply. I'd argue the opposite — the less flinching the before section is, the more the reader believes the after.

The test I run on a before section is simple: does a prospect in a similar position read it and feel understood? Would the client themselves recognise it as an honest description of where they were? If the answer is yes on both, it's landed. If it reads like a generic "the client wanted to scale," it needs rewriting.

I'd include the friction. The internal debate the client was having. The thing they had tried that hadn't worked. The stakes — not dramatised, just named. A prospect who is sitting in the same situation reads a crisp before section and moves from "maybe" to "this is the agency for me" without the agency having to make the argument. The before does the selling.

Always clear the framing with the client before publishing. "Honest" doesn't mean unflattering — it means specific. The version that lands is the one the client would be comfortable reading aloud in a room of their peers.

How to Write the Result Section Without Numbers You Don't Have

The most common reason agencies put off writing case studies is that the numbers aren't in yet. Or the client doesn't want them shared. Or the engagement didn't produce the kind of result that fits in a bar chart. So the case study never gets written, and the pipeline runs drier than it needs to.

I'd stop waiting for perfect numbers. A result section doesn't require a percentage to be useful. It requires a change the reader can picture.

• Change in capability. What can the client now do that they couldn't do before? "The team now runs a weekly outbound cycle without agency involvement" is a result.
• Change in posture. What internal debate stopped happening? "The founder no longer sources every new client personally" is a result.
• Change in rhythm. What used to take weeks that now takes hours? What used to happen once a quarter that now happens every week? Operational cadence is a result.
• Commercial direction. If the hard number is protected, the direction usually isn't. "Pipeline coverage doubled in the first quarter" is often shareable even when the underlying revenue figures are not.

A well-written qualitative result, credited to the named client, outperforms a vague percentage from an anonymous "Fortune 500 retailer" almost every time. The credibility is in the specificity and the attribution, not the decimal places.

The Line Back to the Service (the Part Most Agencies Skip)

A case study without a line back to the service is a magazine article. It may be good reading. It does not generate meetings.

The final section of the page needs to tell the reader two things very clearly. First, this is the kind of engagement this agency sells. Name the service. Not the project title — the repeatable service offer the agency is in business to deliver. Second, this is who it's a fit for. A one-sentence description of the situation that would make another company a good candidate for the same engagement.

Then the CTA. One button, one action. "Book a call" is the default, and the default is fine. What I'd avoid is the common ending — a wall of three CTAs, a newsletter signup, and a link to related projects. Every additional option is a reason the reader doesn't take the first one. Pick one. Make it the clear move.

How to Build Case Studies Without Waiting for a Perfect Outcome

The other reason agencies have thin case study libraries is that they're treating each one like a year-end project. Set aside a week. Hire a writer. Do a full interview. Shoot new photography. By the time the thing is live, the engagement is old, the enthusiasm has faded, and the page lands with less force than it deserved.

I'd write the first draft from live engagements as soon as there's a decision worth writing about. That could be month three of a retainer, not month twelve. Draft the before state and the decision section while the context is fresh. Leave the result section as a placeholder, and come back to it when the outcome has matured. A case study in two passes, written close to the work, reads sharper than one written from memory a year later.

The same logic applies to who's writing it. The person who made the call on the engagement should draft the decision section, not a marketer rewriting a brief. The voice of the person who did the work is almost always more credible than the voice of the person who's polishing it.

A rolling case study library built this way compounds. After a year of the habit, an agency has six to ten living assets across the service lines, each sharp enough to send into a sales conversation without caveating. That's worth more than one beautifully produced flagship case study that takes a quarter to ship.

Where a Case Study Actually Earns Its Keep

A case study that's only lived on the website is underused. The page is the artefact. The real job is what the artefact enables in conversations.

I'd use them in three specific places. First, as the second message in an outbound sequence, after a prospect has engaged but before they've taken a call — a short, pattern-matched link that does the work of proof before the meeting happens. Second, as a pre-meeting send, when a qualified lead has booked a call and the agency wants to shape the conversation. A relevant case study sent the day before a discovery call changes what the prospect walks in expecting. Third, inside proposals, stitched directly into the section where the agency's approach is being explained, so that the recommendation lands on top of prior evidence rather than floating alone.

A case study used this way stops being a marketing asset and starts being a sales one. That's the shift that makes the time spent writing them pay back. The page is the same. The role it plays is different. And the agencies that treat their case studies as sales tools — not portfolio entries — are almost always the ones whose pipelines feel less like weather and more like a system.