A case study is genuinely persuasive proof — but most cold emails built around one make the mistake of treating the case study itself as the whole email, rather than compressing it down to the two or three sentences that actually carry the persuasive weight.
The typical version links to a full case study PDF or attaches it outright, on the assumption that more proof is better. In practice, almost no cold email recipient clicks through to a multi-page PDF from a stranger, so the email ends up saying, in effect, "trust me, the details are elsewhere" — which asks for more effort than most first-touch recipients are willing to give. The proof needs to live inside the email itself, compressed to the point that it reads at a glance.
A three-part structure fits a case study into two or three sentences: the starting problem (specific, not generic), the change made, and a specific, believable outcome. Example: "A team at [Company], similar size to yours, was losing about a day a week to manual reporting. We helped them automate the parts that didn't need a human, and that day came back within a month." Note what makes this work: a specific relatable comparison ("similar size to yours"), a concrete before-state, and an outcome stated plainly rather than dressed up with adjectives.
What to avoid in the compressed version: percentages or numbers precise enough to look invented ("increased efficiency by 47.3%") unless they're genuinely sourced and verifiable — a rounder, more conversational outcome ("cut their turnaround time roughly in half") often reads as more credible than a suspiciously exact figure, even when the exact figure is real, simply because overly precise numbers in a cold outreach context have become associated with fabricated claims.
A compressed case study earns its place in the second or third touch of a sequence more than the first — the opening email's job is to establish relevance quickly, and proof works better once the recipient has some context for why it might apply to them. It also works well as the content of a PS line (see our guide on PS lines) when the rest of the email is making a different point, letting the proof point add credibility without taking over the whole message.
Skip the client's full name and title unless you have explicit permission to use them — "a team at [Company]" or an anonymized description ("a mid-size logistics company") is usually enough and avoids a permissions problem. Skip the methodology section entirely; a cold email recipient doesn't need to know how the result was measured, only that it's specific enough to sound real. And skip stacking more than one case study in a single email — one specific, well-told example outperforms three vague ones.
Generally not as the primary proof point — most recipients won't click through, so the persuasive detail needs to live inside the email itself, compressed to two or three sentences.
Usually the second or third touch rather than the first — proof lands better once the recipient has some context for why it applies to them, which the opening email is still establishing.
Rounder, conversational figures ('cut turnaround roughly in half') often read as more credible than suspiciously exact percentages, since overly precise uncited numbers have become associated with fabricated claims in cold outreach.
Only with explicit permission. Without it, an anonymized description ('a mid-size logistics company') avoids a permissions problem while still giving the recipient enough specificity to find it credible.
Related guides
Written by
Scott Holmes
AI systems consultant based in Barrie, Ontario. Founder of Pinnacle Tech Projects. Has compressed full case studies into cold-email-length proof points for client campaigns.
Answer four quick questions and get a tool recommendation for your setup.