The Post-Call Recap Email That Actually Moves the Deal (Write It in Six Minutes)

The recap email nobody forwards

Here is the email almost every rep I have watched sends after a good discovery call.

Hi Dana,

Great speaking with you today! Really enjoyed learning about your operation. I have attached our overview deck and a case study I think you'll find relevant. Let me know if you have any questions and I'll follow up next week.

Best, Rep

That email is not wrong. It is just inert. It gets opened once, on a phone, in a hallway, and then it sits in an inbox until it scrolls off the screen. Nobody forwards it, because there is nothing in it worth forwarding. It contains no information the buyer did not already have. It is a receipt.

The recap email is the only artifact of your call that other people will ever see. You had thirty minutes with one person. The decision is going to get made by three or four people, and at least two of them were not on the call and never will be. Everything they learn about you, they learn through your champion's retelling — or through your email, forwarded, with two words of commentary at the top: "thoughts?"

So write the email for the person who wasn't there.

The forwarding test

Before you hit send, read your draft as if you are the operations director who did not attend, who has forty unread emails, and who has been pitched by four vendors this quarter. Ask one question: after reading this, do I know what problem we are solving and what happens next?

If the answer is no, you wrote a thank-you note.

A good sales follow up email after a discovery call passes that test cold, with no verbal context from your champion. It survives being forwarded because it is mostly the buyer's own material, organized. You are not selling in this email. You are handing your champion a document they can put in front of their boss without having to translate it.

That is the whole idea. Everything below is mechanics.

The five parts

1. Their words for the problem

Open with the problem, in the buyer's language, in quotation marks, attributed to them.

Not: "We discussed challenges around your maintenance workflow."

But: "You said the issue is that nobody knows a line is going down until it's already down — 'we're running maintenance on a calendar, not on the equipment.'"

The quotation marks are doing real work here, and they are the part reps skip. When you paraphrase, you translate the buyer's problem into vendor vocabulary. "Reactive maintenance posture." "Visibility gaps." "Alignment challenges." The moment you do that, the email becomes yours instead of theirs, and the person reading the forward can smell it. Vendor language triggers the same reflex in a reader that a cold call opener does — this is a pitch, I will deal with it later.

Quoted language does the opposite. When the operations director reads a sentence her plant manager actually said, in the phrasing he actually used, she is not reading a vendor email anymore. She is reading her own organization's problem, written down. That is a different genre of document. People forward that one.

The practical consequence is that you have to write down what they say during the call, verbatim, not in summary. I keep a running column on my notepad for exact phrases. Anything vivid, anything with a number attached, anything they say twice — that goes down in their words, not mine. If you take notes in summary form you will find at 4pm that you have nothing to quote and you will end up paraphrasing, which is where the whole thing dies.

2. The numbers they gave you

Every number in the recap should be a number the buyer said out loud. Not one of yours. Not an industry figure. Not a benchmark from your marketing team.

"You mentioned four unplanned stoppages last quarter and roughly two hours to get the line back up each time."

That sentence is powerful for a reason that has nothing to do with the arithmetic. It proves you listened, and more importantly, it puts the buyer's own quantification into a document that will be read by the person who controls the budget. When the operations director sees a number her plant manager supplied, she can't dismiss it as vendor math. She has to engage with it. Sometimes she engages by correcting it — "it was five, not four" — and that is a wonderful outcome, because now she is in the thread.

If they did not give you a number, do not supply one. Write "you weren't sure of the exact figure and are going to check with Marcus." That is honest, and it creates a task for them, which is its own kind of engagement. An invented number in a recap email is the fastest way I know to lose a deal you were winning, because the one person you don't want reading it is the person who knows the real figure.

Getting quotable language and real numbers out of a call is mostly a function of how you ran the call in the first place. If your discovery is a series of qualification checkboxes you will get one-word answers and nothing worth quoting. The 25-minute discovery playbook I use with plant managers and maintenance leaders is built around questions that produce sentences rather than yes-or-no, and the recap email is the reason why.

3. What you agreed to do

Specific, dated, and short. "I'll send over the two-page summary of how the Bakersfield site handled the same rollout, by Thursday."

Not "I'll follow up with some information." That is not a commitment, it is a mood.

Two or three items maximum. If you promised eight things on the call you over-promised on the call, and the recap is not the place to fix it. Pick the two that matter and drop the rest.

4. What they agreed to do

This is the part reps are afraid to write, and it is the part that makes the email a working document instead of a courtesy.

"You're going to pull the downtime log for Q3 and check with Marcus on whether the PLCs on lines 2 and 4 are the same generation."

Writing down the buyer's commitment feels pushy the first few times you do it. It is not. You are not assigning homework; you are recording something they said in a conversation you both had. If they did not commit to anything on the call, that is the real signal — you had a pleasant chat, not a discovery call, and the email cannot rescue it.

There is a second function here. When the email gets forwarded, the internal reader sees that their colleague has already agreed to do work. That is social proof of a kind nothing you write about your product can match. Deals feel real when both sides have tasks.

5. The date

One line. Named day, named time, named attendees.

"We're back on the calendar Tuesday the 14th at 10am Pacific, 30 minutes, and you said you'd try to get Ravi from IT on the call."

No "let me know what works." No "I'll reach out next week to find time." If you left the call without a date, say so plainly and propose two slots. But you should not have left the call without a date, and the discomfort of writing that sentence is a useful reminder for next time.

Why the attachment goes last, or not at all

The deck is the enemy of the forward.

An email with an attachment reads as a vendor email before a single word is processed. The paperclip icon is a genre signal. It says: this is marketing, this will take twenty minutes, later. And the person you most want to reach — the one who wasn't on the call — is precisely the person with the least tolerance for a twenty-minute PDF from a company they have never heard of.

So my default is no attachment in the recap. Everything that matters goes in the body, in text, readable on a phone in under ninety seconds. If there is genuinely a document the buyer asked for, it goes at the bottom, after the date, with one sentence explaining what it is and why they should open it — "the Bakersfield summary you asked about is attached, page 2 is the part relevant to your PLC question." Tell them where to look. Nobody reads a fourteen-page PDF, but a lot of people read page 2 if you tell them page 2 is the point.

And never lead with it. The moment the first line of your email is "attached please find," you have written a receipt again.

The one line that lets your champion sell

Somewhere in the recap — I usually put it right after the numbers — I write one sentence that is designed to be lifted out and pasted into an internal message.

It looks like this: "The short version for anyone who wasn't on the call: four stoppages last quarter, two hours each, and no way to see them coming. We think that's a sensor and alerting problem, not a staffing problem, and we can test that assumption in about three weeks without touching the existing PLC setup."

Problem, in their numbers. Diagnosis, in a sentence. Proposed test, with a time frame and a reassurance about the thing they are worried about. That is the shape.

Your champion is not a professional salesperson. When their boss asks "what did that vendor call turn into?", they will improvise something vague and the deal will lose a week. Give them a sentence. Almost every good champion I have worked with used it nearly word for word, because it was easier than composing their own.

The reassurance clause at the end matters more than people think, especially with buyers who have been through a failed implementation before. If someone has already been burned, their internal objection is not "will this work" but "how much of my time and credibility does this cost me if it doesn't." I go into that dynamic at length in the demo script for operations leaders who have already been burned once, and the recap email is where you either address it in writing or leave it to fester.

Example one: after a plant manager discovery call

This is invented, but it is the shape of what I send. Names and figures here are illustrative.

Subject: Line 2 downtime — recap and the Q3 log

Dana,

Recapping so you have it in writing and can forward it.

The problem, in your words: "We're running maintenance on a calendar, not on the equipment." You said nobody knows line 2 is going down until it's already down, and the crew ends up doing a two-hour recovery instead of a twenty-minute planned swap.

What you told me: four unplanned stoppages last quarter on line 2. Roughly two hours to recover each one. You weren't sure of the exact cost per hour and you're going to check that with finance.

Short version for anyone who wasn't on the call: four stoppages, two hours each, no early warning. We think that's a sensing and alerting problem rather than a staffing problem, and there's a way to test that on one line in about three weeks without changing the existing PLC setup.

I'm doing: sending you the two-page Bakersfield summary by Thursday, and confirming with our engineer whether the retrofit works on the older Allen-Bradley units.

You're doing: pulling the Q3 downtime log, and checking with Marcus on the PLC generations for lines 2 and 4.

We're back on: Tuesday the 14th, 10am Pacific, 30 minutes. You said you'd try to get Ravi from IT on it.

Timothy

No attachment. No adjectives about how great the call was. Every fact in it came out of Dana's mouth. Dana can forward that to her director with "see below" and nothing is lost in translation.

Example two: after a demo

Demo recaps are different. By the demo, the problem is established. What is unresolved is whether the thing actually works in their environment, and who has to agree.

Subject: Demo recap — the scheduling conflict question and next step

Ben,

Recap from this morning, written so you can forward it.

What you were checking for: you said the last system "looked great in the demo and fell apart the first week the crews were on it." So the test today was whether ours holds up when two foremen edit the same day's schedule at the same time.

What we showed: the conflict case, live, on the second attempt — the first one I fumbled, and you saw the actual error state, which I'd rather you see now than in week one. Second pass, the edits merged and both foremen got the notification.

Still open: whether it works on the tablets your crews actually carry. You said they're on the older Samsungs. I don't know the answer yet and I'm not going to guess at it.

I'm doing: getting a definitive answer on the Samsung models from our engineering team by Monday, and sending the two-week pilot outline.

You're doing: talking to Alicia about whether her yard would take the pilot, and getting me the crew count.

We're back on: Thursday the 23rd, 8am Mountain, 45 minutes, with Alicia if she can make it.

Timothy

Note the admission that the first attempt failed and the flat "I don't know the answer yet." Both go in the email deliberately. A recap that says everything went perfectly is not credible to someone who was not in the room, and a buyer who has been burned before is scanning for exactly the moment you paper over a gap. Writing down the thing you do not know is the cheapest credibility you will ever buy.

The six-minute sequence

Run this before you dial the next account, not at the end of the day. At the end of the day you will not remember the phrasing, and the phrasing is the whole thing.

Minute one. Read your notes and mark the two or three verbatim phrases. Circle every number.

Minute two. Write the subject line. Their problem, their words, no company names. "Line 2 downtime — recap and the Q3 log." A subject line that names their problem gets opened by the person it gets forwarded to; "Great connecting today!" does not.

Minute three. Write the problem paragraph with the quote in it. Do not rewrite their sentence to be more grammatical.

Minute four. Write the numbers line and the forward-me line underneath it.

Minute five. Write the three commitments — yours, theirs, the date.

Minute six. Delete every adjective. "Great," "excited," "really enjoyed," "robust," "seamless." Then read it as the person who wasn't on the call, and if you cannot tell what happens next, fix that one line and send.

Six minutes, and it is six minutes because you are working from a call that generated quotable material. If it takes you twenty, the problem is upstream. You did not get the buyer talking, or you took notes in summary. That is a call problem, and the fix is in how you open and what you ask — the energy and utilities discovery playbook is built the same way, on questions that produce quotable sentences rather than yes-or-no confirmations.

What I would do next

Pick your last five discovery calls and open the recap emails you sent. Count how many contained a direct quote from the buyer, a number the buyer supplied, a written commitment on their side, and a named date. My guess is very few of them contain all four, and I include my own past self in that.

Then fix the calls, not just the emails. If you want reps producing recaps like the ones above, they need to come off calls with real language and real numbers in their notes, which means they need reps at asking the follow-up question instead of accepting the first vague answer. That is what we built DrillCall for — live practice against buyers who deflect, so that by the time it is a real plant manager on the line, the rep has already heard "we're fine, we've got a system" fifty times and knows what to ask next. The recap email is easy to write when the call gave you something to write about.

The email is not the deal. But it is the only piece of the deal that travels, and it travels to the people you never get to talk to. Write it for them.