Outreach9 min read

Sales follow-up emails: six templates for after the call, the demo and the proposal

The follow-up email after a sales call gets forwarded to someone who was not on it. Six templates written for that reader, with timing for every stage.

By

A sales follow-up is read by the person it gets forwarded toWho reads the recap?YouContactSigner“Thanks so much for your time!”skipped“most of Friday” · next step ThursdayreadWrite it for the one who was not on the call

The follow-up email after a sales call often has one reader who matters more than the person you spoke to: whoever they forward it to. That might be the boss who signs, the colleague who'll use the thing, or the finance person who asks what it costs. Write the email for that reader, and send it the same day.

In practice that means four things: their problem in their own words, what you agreed, one next step with a date, and anything you promised to send. Thanking them for their time is optional. The date isn't.

Who actually reads a sales follow-up email

Your contact already knows what was said, because they were there. The recap isn't really for them.

In most B2B deals the person on the call isn't the only one who decides, so the email gets forwarded with a line on top like "see below, thoughts?" From then on it has to make sense to someone who's never heard of you and is probably reading on a phone between other things.

Where a sales follow-up email goes after you send it Three people left to right: you, your contact who was on the call, and whoever signs, who was not. Below, the recap email as that third reader sees it. The thank-you line and the product description are skipped. The problem quoted in a colleague's words, what was agreed, and the dated next step are read. You send the recap Your contact was on the call Whoever signs was not on the call same day “thoughts?” THE RECAP, AS WHOEVER SIGNS READS IT Thank you so much for your time today! skipped Our platform automates financial operations end to end. skipped You said reconciliation takes Priya most of Friday. read Agreed: a test on your own March data before Marcus sees it. read Next: Thursday at 2pm. The invite is already in your calendar. read
The recap is written for the person it gets forwarded to. They skip the thanks and the product description. What they read is the part in their own colleague's words, and the date.

That reader skims past the thanks, your company description and the feature list. What gets through is the part written in their colleague's words, because it's the only part that sounds like their own company talking. "You said the weekly reconciliation takes Priya most of Friday" gets read. "Our platform automates financial operations" doesn't.

So the practical rule is short: quote them, not yourself.

The four parts of a good follow-up email after a sales call

Each template below uses the same four parts, in this order.

  1. Their problem, in their words. A sentence or two, using the phrases they used and any numbers they gave you. If they said "most of Friday", write "most of Friday", not "significant time".
  2. What you agreed. Not what you discussed, but what you both said yes to, even if it was small: "you'd like to see it on your own data before involving Marcus."
  3. One next step, with a date. A meeting, a trial or a document. Just one, with a day attached, and ideally already in their calendar.
  4. What you owe them. Anything you promised to send, attached or linked, so nobody has to chase it.

Leave out the pitch. They've heard it, and repeating it in writing turns a recap into a brochure. Brochures don't get forwarded.

Six sales follow-up email templates

The brackets are for real details from the conversation. If you can't fill one in, the call didn't produce it, and it's better to notice that now than six weeks into the deal.

1. After a discovery call. Send it within a few hours.

Subject: notes from today + [the next step]

Hi [name],

A quick recap so it's all in one place, and so it makes sense if you pass it on.

Where things are: [their problem in their words, with their number]. Right now it's handled by [what they do today], which works until [the limit they described].

What we agreed: [the smallest thing you both said yes to].

Next: [the step] on [day and date]. I've sent an invite for [time], so move it if it clashes.

The [thing you promised] is attached.

[your name]

2. After a demo. Send it the same day, and write it for the colleague who wasn't in the room, since they're often who decides what happens next.

Subject: what you saw today, for [the colleague they mentioned]

Hi [name],

You mentioned [colleague] would want to see this before anything moves, so here's the short version for them.

The problem: [their problem in their words].

What the demo showed: [the one workflow that mattered to them, in a line], using [their data or their example, if it was].

What it didn't cover: [the question you couldn't answer, and when you will].

Next step: [step] on [date].

The "what it didn't cover" line is worth keeping even though it feels like admitting a weakness. It shows you were listening for the gap, and it stops the colleague finding it first and wondering why you left it out.

3. After sending a proposal or quote. This one works best as two messages. The first goes out the same day:

Subject: proposal for [project], and the two lines that matter

Hi [name], the proposal's attached. The two things worth reading first are [the price line] and [the timeline line]; the rest is detail.

I've kept [date] free for a 20-minute call to go through questions. If it's easier to reply here, that's fine too.

Then, if nothing comes back, a short follow-up on day four:

Subject: re: proposal for [project]

Hi [name], just checking the proposal reached the right people. Is there anything in it that needs to change before [decision-maker] sees it?

That second question invites an edit rather than a verdict, and an edit is much easier for a busy person to send.

4. After "send me some information". This is sometimes a polite way of ending a call, so treat it as something you still need to earn.

Subject: the one page you asked for

Hi [name], you asked for something to read. Rather than the full deck, here's the one page that covers [their specific problem]: [link].

If it still looks relevant once you've read it, the next step would be [step]. If not, no reply needed.

Send one page about their problem, not the deck. The deck is the version with everything in it, which is exactly why nobody reads it.

5. After the deal goes quiet. Silence in the middle of a deal is different from cold silence. They know you, and something's changed on their side that they haven't mentioned.

Subject: re: [original thread]

Hi [name], it's been [time] since [the last step]. When a project goes quiet it's usually one of three things: priorities moved, someone new got involved, or the numbers didn't work. Is it any of those?

Happy to pause this until [month] if that's easier.

Naming the likely reasons makes the honest answer easy to give, and the offer to pause is a real offer. A paused deal is still a deal. If they never replied at all, that's a different situation with a different sequence.

6. After "not now". Send this when the reason they gave has run out, not on a fixed ninety-day timer.

Subject: [the thing they were waiting for]

Hi [name], back in [month] you said the timing was wrong until [the thing, like a new hire starting]. [Evidence it happened, like "I saw Dana joined in August."]

Is [the problem] back on the list, or has it been solved another way?

This only works if you wrote the reason down at the time. It's worth making your CRM's "closed lost" notes specific enough to use later: "waiting for new ops lead, starts August" rather than "timing".

When to send each one

Moment When to send What it has to include
After a discovery call Within a few hours Their problem in their words, and the next step with a date
After a demo The same day A version the absent colleague can take in quickly
After a proposal The same day, then day 4 The two lines worth reading first, then a question that invites an edit
After "send me information" Within a day One page about their problem, not the deck
After the deal goes quiet 7 to 10 days after the missed step The likely reasons, and an offer to pause
After "not now" When their stated reason runs out Evidence that it has
When each sales follow-up email should go out A timeline of five moments in a deal. After a discovery call the recap goes within three hours and carries their words and the next step with a date. After a demo it goes the same day, written for the absent colleague. After a proposal it goes on day zero and day four, inviting an edit rather than a verdict. When the deal goes quiet it goes after seven to ten days, naming the likely reasons and offering to pause. After a not now, it goes when the stated reason expires. WHEN EACH FOLLOW-UP GOES Discovery call within 3 hours their words, next step + date Demo same day a version for the absent colleague Proposal day 0 and day 4 invite an edit, not a verdict Goes quiet 7 to 10 days name the reasons, offer to pause “Not now” reason expires show that it really expired
Every meeting gets its recap the same day. The only follow-up with no fixed date is the one after “not now”, which waits for the reason they gave to expire rather than for a ninety-day timer.

Sending on the same day after any meeting isn't about politeness. The recap is most accurate while you still remember their exact words, and most useful while they're still deciding what to tell their boss about the call.

Subject lines for sales follow-ups

Keep follow-ups in the original email thread wherever you can. A reply in the same thread carries its own context, and the subject line takes care of itself.

When you do start a new thread, say what's inside rather than how you feel. "notes from today + next steps" tells the reader what they're opening; "Great speaking with you!" doesn't, and is easy to leave unread. There's more on sales email subject lines here.

Mistakes that slow a deal down

Opening with thanks. "Thank you so much for your time today" is how a huge number of follow-up emails start, which is exactly why readers skip it. Put their problem first.

Recapping your pitch instead of their problem. If the recap is mostly about your product, it reads as marketing, and the one person you needed to reach may never get past it.

Ending with "let me know if you have any questions". It sounds open but asks nothing. Swap it for the date of the next step.

Asking for three things at once. A call, a referral and a look at the case study. The reader picks the easiest option, which is often none of them.

Attaching everything. The deck, the case study, the security document and the price sheet, just in case. One attachment that answers what they actually asked for is worth more than five they have to dig through.

When an email isn't the right follow-up

If the deal is stuck on something only a conversation can settle, like a pricing objection or internal politics, email rarely fixes it. Ask for fifteen minutes instead of writing a longer message.

If your contact has to sell it internally, what they need is less an email than a document: a one-page business case, in their words, that they can present. Offer to write the first draft. It's one of the most useful things you can do for someone championing you inside their company.

And if you're on your fourth unanswered message, stop. Send a close that leaves them with something useful, and put your time into accounts that are active right now.

Doing this by hand is the slow way

Revtive runs a team of agents that find the venues, read their rules, qualify leads on real evidence and draft the outreach for you to approve. Free to start, no card.

Start free

Keep reading