How to Write a Follow-Up Email That Gets Answered
Most follow-up emails retell the call in the order it happened: here's what we discussed, here's what you mentioned, here's what I mentioned. The next step, if there is one, shows up in the last line, after the prospect has already decided whether they're still reading. A rep who spends thirty minutes on a genuinely good discovery call can undo a lot of that momentum with a follow-up that makes the prospect scroll through four paragraphs of recap before finding out what happens next.
Warning
A recap tells the prospect what already happened. It's the next step that gets a reply, and burying it at the end means a lot of readers never see it.
A follow-up isn't a transcript. It's the one thing you need the prospect to do next.
Why chronological order works against you
Writing in the order the call happened is the easiest way to write a follow-up, but it's optimized for how you experienced the call, not for what the prospect needs to do with the email. By the time the next step shows up, you've already spent their attention on the recap. A prospect skimming their inbox between meetings gives an email a few seconds before deciding whether it's worth a full read, and a chronological recap has nothing in those first few seconds that tells them why this one matters.
Take a thirty-minute discovery call where a prospect clearly cared most about one thing, integration with their existing data warehouse, mentioned partway through the conversation. A chronological follow-up opens with pleasantries, works through the agenda in order, and finally gets to the data warehouse point and a proposed next step in the last two lines. A prospect who skims the first few lines and doesn't see their actual priority reflected back may not read far enough to reach the part that was written specifically for them.
Before: open your notes, write down what was discussed in order, end with "let me know if you have any questions."
After: give Claude the raw notes and ask for a follow-up that opens with the prospect's own stated priority and closes with one specific next step and date.
A process for a follow-up that leads with the next step
- 1
Give Claude the raw notes, not a cleaned-up version
Paste what you actually wrote during or right after the call. The messy version has the prospect's own phrasing in it, which reads as more genuine than your paraphrase of it.
- 2
Name the prospect's stated priority explicitly
Tell Claude which point in your notes was the thing they clearly cared about most. That's what the email should open with, not whichever point happened first in the conversation.
- 3
Give an actual word limit and a specific next step
State the real constraint, not "keep it short." A word limit forces the recap to compress, and a specific next step with a date is what actually gets a reply instead of silence.
- 4
Check the next step is the last thing they read
Confirm the draft ends on the ask, not on a courtesy line after it. The last sentence a prospect reads is the one most likely to get acted on.
Here are my notes from a 30-minute discovery call with a prospect evaluating our tool against two competitors. Their clearest priority was integration with their existing data warehouse. Draft a follow-up email under 120 words that opens with that priority and proposes a next step by Friday.
”When a call includes a specific technical question you didn't have a firm answer to on the spot, it's worth telling Claude to include a proactive answer in the follow-up, since resolving an open question unprompted is a stronger signal than waiting for the prospect to ask again.
They also asked whether our data warehouse integration supports incremental syncs, which I wasn't fully sure of on the call. I've since confirmed it does. Add that answer to the follow-up proactively, since it directly supports their stated priority.
”
Inside Claude Tutorial
Leading with the point that matters most is transferable.
Opening with what the reader actually cares about, instead of the order events happened in, applies to more than sales follow-ups. The app has a full lesson on it, with practice that carries over to any message where you need a reply.
When there isn't a clean next step yet
Sometimes a call ends without an obvious next action, maybe the prospect needs to check with a colleague first. That's still worth naming specifically instead of defaulting to a vague "let me know." A follow-up with no real ask puts the entire burden of moving the deal forward on the prospect, and most prospects, even genuinely interested ones, won't take that initiative on their own.
Tip
If the call didn't produce a clear next step, ask Claude to draft one that moves things forward anyway, like proposing a specific date to check back in. A vague close gets a vague reply, or none at all.
This call didn't end with a clear next step, the prospect said they need to loop in their IT lead first. Draft a follow-up that acknowledges that and proposes checking back in exactly one week from today.
”It's also worth including something the prospect can use in that internal conversation with their IT lead, since a follow-up that only proposes a date to check back in gives them nothing to actually move the conversation forward on their end in the meantime.
Since they need to loop in an IT lead, add a short, technical one-line summary of our integration approach they could forward along, so they have something concrete to share internally while we wait.
”Continue reading
- Sharpening a Cold Email Before You Hit Send: the same "test it, don't just trust it" approach, applied before the call this follow-up is responding to.
- Turning a Messy Call Transcript Into CRM-Ready Notes: the internal version of this same call, structured for your CRM instead of the prospect's inbox.
- Turning a Discovery Call Into a One-Page Proposal: what a strong follow-up eventually builds toward.