How to Write the Recap Email That Keeps the Deal Moving (and the Version That Kills It)

The call ends and the room empties. The email is what's left.

Here is the thing almost nobody internalises early enough in their career: the people who decide whether you win were not on your call.

You spoke to a champion. Maybe a champion and a manager. The person who signs, the person in finance who kills things for sport, the peer team whose sign-off you need — none of them heard your discovery, none of them saw your demo, and none of them will. What they will see is a forwarded email. Your champion will drop it into a Slack thread or paste it into a slide, and that block of text has to do the selling in a room you are not in.

So the recap is not admin. It is the artifact. Treat it as the deliverable of the call rather than the receipt for it.

Most reps do not. Almost every recap I have read from a rep who is struggling reads like a thank-you note with a features paragraph stapled to the bottom. It is polite, it is enthusiastic, and it is completely useless to anyone who was not in the meeting.

The version that kills the deal

Here is the email. You have sent this. I have sent this.

Subject: Great speaking today!

Hi Dana,

Thanks so much for your time this afternoon — really enjoyed learning more about you and the team!

As discussed, [Product] is a leading platform that helps companies like yours streamline finance workflows, increase efficiency and drive better decision-making. Our unified platform brings reconciliation, reporting and controls into a single pane of glass, and customers love how quickly they get to value.

I've attached our overview deck, the integrations one-pager, two case studies and our security whitepaper for your review.

Let me know if you have any questions and I'll follow up next week to see where you've landed. Looking forward to next steps!

Count what is actually in there. Not one thing the prospect said. Not one number from their business. No decision, no scope, no owner, no date. Four attachments, none of which were requested. A closing line that hands the entire next step to a person who has thirty other emails.

Now imagine Dana forwards it to her CFO with "thoughts?" on top. The CFO reads a vendor describing itself, sees four attachments he will not open, and learns nothing about his own company. Best case he ignores it. Worst case he concludes Dana is being sold to, which is the exact impression you cannot afford, because the moment a champion looks like a mark internally, they stop championing.

The features paragraph is the tell. If a stranger can read your recap and not work out what business problem is being solved, you have written a brochure.

What a forwardable recap has to do

Five jobs. In this order.

1. The problem, in their words and their numbers

Not your framing. Theirs. If they said "close takes fourteen days and the board wants eight," you write fourteen and eight. If they said the audit finding "would be a bad look going into the round," you use that phrase, in quotes if it was vivid.

This does two things. It proves you listened, which is worth more than any proof point you own. And it gives the executive reader something recognisable — their own language coming back at them — instead of vendor abstraction.

You cannot do this from memory two days later. You write the recap during the call, in the prospect's words, while they are talking. My notes doc during discovery is mostly verbatim fragments and numbers, because those are the only two things I will need afterwards.

2. What you agreed is worth solving

The word is agreed. Not "here's what we can do." A short list of the specific things you both decided are worth spending time on, with the value they attached to each — again, their estimate, not yours.

This is where the recap starts doing work you cannot do in person. A champion who has to defend a project internally needs a sentence that begins "we agreed" rather than "the vendor says."

3. What is explicitly out of scope

This is the section nobody writes and it is the one that changes deals.

Write down what you are not doing. The module they do not need. The region they are leaving out. The integration they told you is contracted elsewhere until March. Put it in a labelled block.

Three reasons. First, it is the fastest credibility move in a first email — a vendor who names what they are not selling reads as someone with judgement. Second, it pre-empts the finance question, because the smallest, cleanest version of the deal is right there in writing and nobody has to imagine a bloated one. Third, and most practically, it stops the scope creep that arrives at week six when someone in the forwarded thread says "can it also do payroll?" You already said no in writing, on day one, and everyone read it.

I have never regretted narrowing scope in a recap. I have regretted the opposite plenty.

4. The next step, with a date and an owner

"I'll follow up next week" is not a next step. It is a way of saying the call did not produce one, dressed up so nobody has to admit it.

A real next step has a date, a time, a duration, a list of humans, and a stated purpose. It also has the small tasks either side of it, each with a name against it. If the prospect owes you something — a system version, an org chart, a sample file — write it down as theirs. People honour written commitments in a way they do not honour verbal ones, particularly when a third party might read the email.

5. One line the champion can copy and paste

This is the part that separates a good recap from a great one.

Your champion is busy and is not a professional communicator about your product. When their boss asks what the meeting was about, they will paraphrase you, badly, in a hurry. So write the paraphrase for them. Three or four sentences at the bottom, written in their voice, not yours, framed as if it's useful for [boss's name].

Do not be coy about it. Label it. Champions are grateful for it, because you have just saved them a job and made them sound sharp to their manager.

The rewrite

Same call, same information. Fictional company and made-up figures, purely to show the shape.

Subject: Close cycle 14 → 8 days — notes, scope, next step 12 Aug

Hi Dana,

Notes from today so you have them in writing. Correct anything I got wrong — I would much rather be corrected now than build a plan on a bad number.

What you told me

• Month-end close takes 14 days. The board has asked for 8 by the start of Q4.
• Three of your five entities still reconcile in spreadsheets. FX revaluation for the German entity is done by hand, by Marek, who you described as "a single point of failure."
• Last year's audit produced two management letter points, both on manual journal entries. A third one would be, in your words, "a bad look going into the round."

What we agreed is worth solving

• Automating FX revaluation and intercompany eliminations. Your estimate: roughly six of the fourteen days.
• Putting manual journal entries behind an approval workflow with an audit trail, so the management letter points do not repeat.

What is not in scope

• Payroll. Contracted until March, and you do not want it reopened.
• The Brazil entity. Excluded until the acquisition closes.

Open question

• Which NetSuite version you are on. Marek will know. It is the difference between a two-week and a six-week implementation, and I do not want to give you a go-live date before we know which.

Next step

• Tuesday 12 August, 2pm your time, 45 minutes. You, Marek, me, and Priya from our solutions team. We run the FX revaluation against your actual entity structure rather than a demo dataset. Invite sent; agenda by Friday.
• Before then: I send you the two-page implementation outline for a five-entity close (Thursday). You confirm the NetSuite version with Marek.

If it's useful for Ravi: "We looked at getting month-end close from 14 days to 8 before Q4. The two things they would automate — FX revaluation and intercompany eliminations — are about six of those days, and it also closes the two audit points from last year. Payroll and Brazil stay out of it. Next session is 12 August, testing it against our real entity structure."

Nothing in that email describes the product in marketing terms. A CFO who has never heard of you can read it in forty seconds and know exactly what is being proposed, what it excludes, and what happens next.

Also notice the second line: correct anything I got wrong. That is the highest-response sentence I put in recap emails. It is easier for a prospect to correct a number than to compose a reply, and a correction is a written endorsement of everything they did not correct.

The rule on attachments

One, and only if it was asked for.

Attachments do not survive forwarding reliably. They get stripped by mail gateways, they trip security filters at exactly the kind of buttoned-up enterprise you want to sell to, and they turn your recap from a summary of a business conversation into a vendor packet. Nobody has ever forwarded a security whitepaper to a CFO and improved a deal.

Everything that matters goes in the body of the email as text. Text is what forwards. Text is what gets pasted into Slack. If you genuinely need to send a document, send it as a separate email later in the week, with its own subject line, which also gives you a legitimate second touch instead of a needy check-in.

And never attach the deck you presented. If the deck was self-explanatory you did not need to be on the call, and if it was not self-explanatory it will confuse anyone reading it cold.

Two versions: one for the champion, a shorter one for the exec

If a senior person was on the call, they do not get the same email.

The champion's version is the full one above — it is a working document they will refer back to. The executive version is five lines and it is a subset, never a different story. Something like: here is the problem you described, here is the piece we agreed is worth solving and roughly what it is worth to you, here is what we are deliberately leaving out, here is the date of the next session and who from your team needs to be in it, here is the one thing I need from you.

Copy the champion on it. Two reasons: they need to know what their boss received, and being visibly copied on a note to the exec is good for them internally.

What you must not do is write an exec version that is warmer, more certain, or more expansive than the champion version. If the two ever get compared — and they will, because people forward things — any gap between them reads as manipulation. Shorter, yes. Different, never.

If no exec was on the call, do not email one. Write the copy-paste line and let the champion carry it. Going around your champion to their boss after a first call is a good way to lose the champion.

Timing, and the subject line

Send it the same day, ideally within an hour or two, before their next three meetings overwrite yours. Speed is also a signal — a recap that lands before the prospect has finished their coffee tells them what working with you will be like.

The subject line carries substance. "Great speaking today" is invisible in a mailbox and worse than useless when forwarded, because the CFO's first impression is a pleasantry. Put the problem and the date in it. Something like Close cycle 14 → 8 days — notes and next step 12 Aug. When the champion searches their inbox in three weeks, that is the line that finds it.

The recap is only as good as the call underneath it

Here is the uncomfortable part. If you cannot write the "what you told me" section, it is not a writing problem. You did not run discovery. You ran a conversation.

Every block in that rewrite maps back to something you were supposed to extract live. The numbers, the named single point of failure, the deadline with a board attached, the explicit exclusions — those come out of deliberate questioning, which is the whole subject of our 25-minute diagnostic playbook for SaaS discovery calls, and of the cybersecurity version for diagnosing a SOC before you pitch it, where the numbers you are chasing are alert volumes and analyst hours rather than close cycles. The scope and out-of-scope lines usually come out of the demo rather than discovery, which is why the manufacturing demo script for plant managers who interrupt spends so much time on getting the buyer to tell you which part they actually care about.

A useful habit: before the call, open a blank recap template with the five headings in it. During the call, fill it in. Whatever is still empty at the thirty-minute mark is what you ask about in the last five. I have caught myself with no date and no owner more than once and only noticed because the template was staring at me.

Write the email, then say it out loud

One last test, and it is the one that catches the most damage. Read the recap aloud as though you were the CFO who has never met you. If any sentence makes you cringe, delete it. Adjectives about your own product will be the first to go, followed by every instance of "as discussed" attached to something that was not discussed, and then all the exclamation marks.

If you want to get properly good at this, the fastest route is to practise the call that produces it. Run a discovery rep, then immediately write the recap from your notes, without replaying anything — that gap between what you thought you heard and what you can actually evidence in writing is where the skill lives. It is what I would build reps around, and it is why we made DrillCall let you run the same call again and again against an AI buyer until the notes come out complete. Do a call, write the recap, look at the empty headings, go again.

The reps who win the deals you are not invited to are not better talkers. They are the ones whose emails survive being forwarded.