The recap is part of the sale
Most agencies treat the discovery call recap as an afterthought. The call ends, you write a quick email, you send it later in the day or the next morning.
That is a mistake. The recap is part of the sale.
A great recap email does three things:
Confirms you listened — the client sees their own words and priorities reflected back
Locks in commitments — what was decided and who is doing what is now in writing
Creates urgency — the next step is clearly named with a date
If you wait until tomorrow to send it, you have lost the urgency. If your recap is a generic "thanks for the call!" you have wasted the opportunity to close.
The template
Here is the structure that works for discovery call recaps:
Subject line: [Project name] — discovery call recap & next steps
Opening (1 sentence): Reference the conversation in human terms.
"Great speaking with you today, Sarah — really appreciated your candor on the timeline pressure."
Confirmed scope (3-5 bullets): Restate what was agreed, in their language.
Owners and next steps (3-4 bullets, with names and dates):
Open items (1-3 bullets): Things you noted that aren't blockers but need answers.
Sign-off: Plain, direct, with the next anchor.
"I'll send the SOW Monday morning. Looking forward to kickoff May 6."
That's it. Six blocks, around 200 words. It reads like you put thought into it because you did.
Why most recaps fail
The two failure modes:
Failure 1: Generic and templated. "Hi {{name}}, thanks for the call! It was great to learn about your business..." Nobody reads past the first line. The client knows you sent the same template to four other prospects this week.
Failure 2: Too long. Three-paragraph essays summarizing every twist of the conversation. The client skims it for the action items, doesn't find them clearly listed, and shelves the email.
The structure above avoids both. It is specific to the call (because it references real decisions from your notes) and it is scannable (because every section is a few bullets, with owners and dates highlighted).
How to write it in 60 seconds, not 20 minutes
The math on writing a discovery recap manually: 20 minutes per call, 5 discovery calls a week → 100 minutes / week of recap writing. 80+ hours a year. That's two full work weeks.
The fix: don't write it manually. While the call is happening, jot down decisions, owners, and dates as bullets — fragments are fine. After the call, paste those bullets into MeetingFlash and you get a complete Execution Pack including a draft follow-up email that already follows this structure. Edit it, send it, done.
We've actually built a discovery call template into the templates dropdown — so you have a starting structure for your notes too.
A working example
Here is what the bullet input might look like:
Sarah, Acme Corp. Wants Shopify Plus rebuild. Mentioned competitor launched migration last quarter, feels behind. Budget $48k, OK with milestone billing. Timeline 12 weeks, hard launch by Aug 1. Brand assets exist but scattered. Wants weekly status calls. Unsure about migrating 3 yrs of customer data. We recommended GA4 + Hotjar. Kickoff May 6. Tom on her side is decision-maker on technical stuff.
Pasted into MeetingFlash, that becomes a structured recap with the decisions, actions, owners, deadlines, follow-up email, Slack message for your team, and a next agenda — in 20 seconds.
Send it before they finish their coffee
The single most underrated agency superpower: sending the recap email before the client has finished the coffee they grabbed after the call. It signals competence at a level no pricing tier can match.
Try it on your last discovery call →
For more on follow-ups that actually convert, see How to Write a Professional Follow-Up Email After a Meeting.