The case study structure that works in email puts the facts first: who the client was, what was going wrong, what changed, and what happened next, each in a plain sentence that makes sense on its own. The story and the process come after. Built that way, one client story can be cut into the follow-up emails you send after someone enquires, sit on your website as a full page, and still read clearly when a reader skims it or an AI answer quotes a single paragraph.
Most coaches and consultants write a case study once, for the website, as a narrative that only lands if you read every word. Then it sits there. The people who most need it are the ones who filled in your form last week and went quiet, and they never see it because it was never shaped to travel. This post is about giving it that shape.
Key takeaways
- A case study works in email when its key facts sit at the top as short, standalone sentences, before any narrative.
- The best home for a client story is the follow-up after an enquiry, when the reader is asking whether this works for someone like them.
- One structured story can become three or four follow-up emails, each built around a single section.
- Writing each section so it names who and what, instead of leaning on "they" and "this", helps skimming readers and AI answers alike.
- Get the client's written permission for the exact details and the level of naming before a story goes into any email or page.
Why don't most case studies get used in follow-up?
Because they're written as one long piece. The usual format opens with a few paragraphs about the client's industry, spends the middle on the process and how well everyone worked together, and saves the result for a closing line. On a page, a patient reader might get there. In an email, nobody does.
The research on how people read online backs this up. Nielsen Norman Group's work on web reading found that people scan, picking out headings, the start of paragraphs and anything that looks specific. Their advice for writing to be scanned is the inverted pyramid: the conclusion first, then the supporting detail, then the background. A case study written the other way round is fighting the reader.
There's a timing problem too. The moment someone is most open to a client story is right after they've enquired. They've raised a hand, and the question in their head is some version of "has this person helped someone like me?" If your follow-up emails don't answer that, the silence fills with doubt. That's the gap we look at when we build enquiry follow-up, and a well-shaped client story is one of the most useful things to put in it.
What structure should a case study follow?
Here's the structure I'd use. Each part stands alone, so you can quote any one of them in an email without the rest.
- A plain headline. Who it was and what changed, in words the client would recognize. "A leadership coach whose enquiries kept going quiet after the first call" tells the right reader this story is about them.
- The facts block. Directly under the headline, before any story: the type of client, the problem in one sentence, what was built in one sentence, the timeframe, and what happened next. If you have numbers, give the before, the after and when it was measured. If you don't, describe the change honestly in words.
- What was going wrong? One short section in the client's own words where you can get them, describing the situation the way your new enquirer would describe theirs.
- What did we change? The two or three decisions that mattered, written so a reader could picture them. Skip the meetings and the process diagram.
- What happened next? The result, stated plainly, with any limits on it. "This worked because the list was already there" earns more trust than a result with no edges.
- A line from the client. One quote, attributed as fully as they're comfortable with.
Repeat the subject in each section. A paragraph that says "this cut their reply time in half" means nothing quoted alone, because "this" and "their" point back to something the reader didn't see. "The coach's reply time to new enquiries dropped" survives being lifted out.
How do you turn one case study into follow-up emails?
Once the story is in sections, the emails mostly write themselves. A short follow-up sequence after an enquiry might use it like this:
- The first reply. Answer their question, confirm the next step, and keep the story out of it. They wrote to you; this email is about them.
- A day or two later. The "what was going wrong" section, rewritten as a short note: "Someone I worked with described the same thing you did." Link the full case study for anyone who wants it.
- A few days after that. The "what we changed" section. This is where the reader starts to see what working with you looks like, which is often the real question behind "how does this work?"
- Before you'd normally give up. The result and the client's line, with a simple ask: reply, or book a time.
Each email carries one idea and one link. That keeps them short, and it means a reader who only opens the third one still gets a complete thought. If you're building the automated version of this in HubSpot, ActiveCampaign or Kit, proposal follow-up automation for service businesses covers the timing and the exit rules once a proposal is out. For smaller pieces of proof, like a one-line testimonial or a reply from a reader, how to use social proof in email copy covers where they fit. This post is about the full story, the one you only have a handful of.
Does the same structure help with AI search?
Yes, and you don't need a separate version for it. Google's own guidance on AI features says there's nothing special to add for AI Overviews or AI Mode beyond the usual: pages that can be crawled, content written for people, and text that makes sense. A case study with its facts at the top and self-contained sections is already doing that, and it's the kind of passage an AI answer can quote without dragging in the paragraphs around it.
Two practical points. Keep the full case study on an open page rather than behind a form, because a gated page can't be found, quoted or linked. And link it from your service pages and your follow-up emails, so the people and the crawlers who need it can reach it. Our own case studies sit on open pages for that reason.
What I wouldn't do is write case studies for machines first. The person reading your third follow-up email is the one who books the call. If the story works for them, it'll work for an AI answer too.
When isn't a case study the answer?
If you don't have permission, you don't have a case study. Get the client's written OK for the specific details and how they're named, whether that's full name and company or "a leadership coach in Calgary". Most clients agree to more than you'd expect when they see the draft, but the ask comes first.
And if enquiries are going quiet because nobody replies for three days, a better story won't fix it. The follow-up itself has to exist before there's anywhere to put the proof. In that case I'd start with the reply and the sequence, then add the story in.
FAQ
What should be at the top of a case study?
A plain headline that names the type of client and what changed, then a short facts block: who the client was, the problem in one sentence, what was built, the timeframe, and the result. Put the narrative after that. A reader skimming the page, or reading a single excerpt in an email, gets the whole point in a few seconds, and anyone who wants the full story can keep reading.
How many case studies do I need?
Fewer than most people think. One strong, well-structured story for each kind of client you most want to hear from is plenty to start with, and for most coaches and consultants that's two or three. A follow-up sequence only needs one story that matches the enquirer's situation. Three that are specific and permitted will do more than ten vague ones that blur together.
Can I use a client story without naming the client?
Yes, if the client agrees to that level of detail. Describe them the way your next enquirer would describe themselves, such as "a creator with a list that had gone quiet", and keep the situation specific. What makes a story believable is the detail of the problem and the change. Anonymity is fine; vagueness is what makes readers skip it.
Should case studies be gated behind a form?
I wouldn't. A gated case study can't be found by search, quoted in an AI answer or linked easily from an email. Keep the full story on an open page, link it from your follow-up emails and service pages, and if you want something to capture an address, offer a separate checklist or worksheet instead. The story's job is to build trust, so put it where people can reach it.
How long should a case study email be?
Short enough to read on a phone in under a minute. One section of the story, one idea, one link to the full case study, and a simple next step like replying or booking a time. If you find yourself pasting the whole case study into one email, split it across the sequence instead. The follow-up works because each email gives the reader one more reason to say yes.
Read next
- How to Use Social Proof in Email Copy to Build Trust
- Proposal Follow-Up Automation for Service Businesses
- Email Storytelling Framework for Deeper Reader Engagement
Put your best story where it gets read
If people enquire and then go quiet, the follow-up is usually where the gap is, and it's often where your best client story should have been. Our enquiry follow-up build covers the path from the enquiry to a person picking it up, including what gets sent when there's no reply. If you'd rather talk it through first, get in touch.