Agency Case Study Template: How to Write One Clients Actually Read

An agency case study template needs five parts: client context, the specific problem, your approach, the measurable result, and a client quote or review — in that order, written specifically enough that a prospect in a similar situation can picture their own project. Getting client approval before publishing, especially for numbers and quotes, matters as much as the structure itself. A case study is one of the few sales assets that works passively, influencing a prospect while your team is busy with client delivery rather than actively selling. Agencies that turn client reviews into case studies systematically, rather than scrambling to produce one when a pitch suddenly needs it, tend to have a deeper, more current library to draw from when it matters. The case study template Start with client context: industry, size, and anything relevant to why this client's situation matters to the prospect reading it — two or three sentences, not a full company history. Then state the specific problem as the client experienced it, in their language where possible, since a problem description that sounds like internal agency jargon doesn't resonate the way a client's own framing does. Your approach section should describe what you actually did, specifically enough to be credible but without giving away proprietary methodology you'd rather keep for paying clients. The result section needs real numbers wherever the client has approved sharing them — a percentage change, a specific metric, a timeframe — since vague claims like "significant improvement" convince nobody who's seen enough marketing copy to be skeptical of unquantified claims. Close with a client quote, ideally pulled from an actual review rather than written and attributed to them after the fact, since a review the client actually wrote and stood behind carries more credibility than copy your team drafted on their behalf. A sixth element worth including when you have it: a brief note on what changed in the relationship after the initial result — did the engagement expand into a larger retainer, did the client refer another business, is the relationship still active years later. This signals something a one-time result can't: that the relationship held up over time, which matters to a prospect who's less worried about a single good project than about whether an ongoing engagement with your agency actually sustains itself. Keep the whole document to roughly 400-600 words for a standard written case study — long enough to be specific, short enough that a busy prospect actually reads the whole thing. A one-page PDF or a dedicated page on your site both work; what matters more than the format is that it's easy to find and share, ideally with its own URL you can link directly in a proposal or follow-up email rather than burying it in a longer portfolio page. Getting client sign-off and handling NDAs Build case study approval into your project close-out process rather than asking for it separately months later, when the client has moved on mentally and the ask feels like an imposition. At the point a project wraps successfully, ask directly: would they be comfortable with a case study, and if so, what level of detail and what numbers are they willing to have shared publicly? Some clients will approve everything; others will approve the story but not specific numbers, or will want to be referenced anonymously by industry and size rather than by name. For clients under an NDA or confidentiality clause, check the actual agreement rather than assuming what's allowed — some NDAs permit case studies with client approval despite a general confidentiality clause, others don't, and the safest path is a specific written approval for the case study itself rather than relying on a general sense that "they seemed fine with it" in conversation. Keep a record of what was approved — which numbers, which quotes, named or anonymous — so a case study doesn't drift beyond what was actually signed off on as it gets reused across different sales materials over time. Put the case study permission language directly into your standard contract template, as a simple opt-in or opt-out clause, rather than treating it as a one-off conversation that happens or doesn't depending on who remembers to raise it. A client who's already said yes in writing during onboarding is an easier conversation to revisit for specific details later than a client who's never been asked at all and now has to make a cold decision about something they haven't thought about before. Using only real, client-approved numbers Never round a client's actual result up to make a case study more impressive, and never publish a number the client hasn't specifically confirmed as accurate and shareable. Beyond the honesty issue, an inflated or unconfirmed number creates real risk if a prospect later asks the client directly during a reference call and hears a different figure — that gap damages trust far more than a modest, accurate number would have in the first place. If a client's result genuinely wasn't dramatic, a case study can still work by focusing on the specificity of the approach and the relationship rather than manufacturing a bigger number than what actually happened. A fictional example of this done well: a fictional agency, Copperfield Studio, ran a website redesign for a regional furniture retailer that produced a modest, honest result — a 12% increase in online form submissions over three months, not a dramatic transformation. Rather than inflating that figure or skipping the case study entirely for being unimpressive, Copperfield built it around the specific redesign decisions that drove the improvement and included the client's own detailed Clutch review describing why the process itself felt collaborative and low-friction. That case study closed more deals for Copperfield than a flashier, higher-percentage case study from a different client, because prospects reading it recognized their own modest, realistic expectations in the story rather than a number that felt too good to apply to their own situation. FTC endorsement guides and disclosure If a case study includes a client testimonial or quote, standard advertising-disclosure practice applies the same way it would to any other endorsement: don't imply the client received anything — a discount, free work, a referral fee — in exchange for appearing in the case study, unless that's disclosed clearly. Most agency case studies involve a client who genuinely isn't being compensated for appearing, which is the simplest and safest position to be in; if your agency does offer something in exchange for a client's participation in a case study, disclosure requirements likely apply and are worth confirming with counsel rather than assumed away. Turning an existing review into a case study starting point A detailed Clutch or G2 review, written by a client describing a specific project, is often most of a case study already written in the client's own voice — reusing that language, with permission, saves time and keeps the story grounded in what the client actually said rather than what your team wishes they'd said. This is one more reason a steady review-collection habit pays off beyond the review platform itself: a library of detailed, specific client reviews becomes raw material for case studies, social posts and sales decks, not just a profile metric. Our review card generator turns a strong review into a shareable visual quickly, which works well alongside a longer-form written case study rather than replacing it. How many case studies does an agency need? There's no fixed number, but having at least one strong, specific case study per major service line or niche you sell into matters more than having many generic ones. A handful of detailed, client-approved case studies that each speak clearly to a specific type of prospect outperforms a dozen thin ones that all read the same. It's worth revisiting this library at least annually, retiring case studies that no longer reflect your current services or team, and prioritizing production of new ones for any niche or service line where your current examples are thin or outdated. A sales team pitching a service your library doesn't yet have a strong case study for is working at a real disadvantage compared to one pitching a service with two or three current, specific examples ready to send. Can we publish a case study if the client won't let us use their name? Yes — an anonymized case study ("a 40-person SaaS company in the logistics space") still works, as long as the details shared are accurate and approved, and as long as the anonymization is genuine enough that the client can't be easily identified from the specifics included. Should case studies be updated once published? Revisit older case studies periodically, especially if the relationship with that client has continued and newer results are available, or if the client's circumstances have changed enough that the original framing no longer reflects reality accurately. A stale case study with outdated numbers can undercut credibility if a sharp prospect notices the dates don't add up. Who should write the case study — the account team or a dedicated writer? Either can work, but whoever writes it needs direct input from the people who actually ran the project, since a case study drafted entirely from secondhand notes tends to miss the specific details that make it credible. A common workable setup is the account lead providing the raw facts and client quote, with a dedicated writer or marketer shaping it into the final template, rather than expecting either role to do the whole thing alone. Every review from Clutch, G2, Google and UpCity in one inbox → Try Tailwind free.