The best sales follow-up email templates do one job each. They confirm what the buyer needs, deliver what you promised, and end with one question the buyer can answer in a line. Below are seven, one for each stage of a B2B deal after the first meeting, each with what makes it work and a template you can copy.

"Let me know if you have any questions" leaves all of that work with the buyer. So does "just checking in". A deal rarely dies on one email, but it slips on them: in Ebsta and Pavilion's 2025 benchmark, 36% of deals slipped past their close date.

All seven templates follow one fictional deal, a team evaluating a shared sales forecast, so you can see how each email builds on the last. Highlighted text is a placeholder. Replace it with the names, dates and words from your own deal.

Which sales follow-up email template should you use?

Pick the template by what the buyer has to do next, not by how many emails you have sent.

Where the deal isTemplateWhat the buyer has to do
Buyer explained the problem1. Discovery recapConfirm you understood it
Buyer saw the product2. Demo follow-upTest what is still open
Someone else must approve3. Forwardable summaryForward it to the approver
You promised an answer4. Promised answerCheck the answer covers it
Buyer has your proposal5. Proposal follow-upName what blocks a decision
Buyer said "not now"6. Milestone follow-upAgree when to talk again
An agreed step was missed7. Stalled dealSay whether it is still on

These follow-up email templates for sales are for a buyer you have already met. For outreach to someone who has never replied, see the cold email reply rate benchmarks instead. For the one five-line recap every meeting needs, and when to send it, see the follow-up email template and timing guide. The templates below pick up where that recap leaves off.

What makes a sales follow-up email get a reply?

A follow-up gets a reply when the buyer can answer it without opening anything else. Five rules run through every template below.

  • One ask, at the end. A question the buyer can answer in a line: yes or no, a date, a name.
  • The buyer's words, not yours. Quote the problem as they said it. "We rebuild the forecast every Friday" beats "better visibility".
  • Bullets for anything with more than one part. Open items, owners and dates are easier to check as a list than as a paragraph.
  • Bold the decision and the date; italicize the buyer's quote. The templates are plain text so they paste cleanly. Add the bold and italics in your mail client, and use them on one or two things per email, or nothing stands out.
  • A subject line that says what is inside. "Demo recap: export still to check" is easy to find again before the buyer's internal meeting. "Following up" is not.

How to write a discovery call follow-up email that gets a reply

A discovery call follow-up email plays the buyer's problem back to them, in their words, with the next step you agreed. Its job is to get a correction now rather than a surprise at proposal stage.

What works

  • Name the task and the person stuck with it, not a category like "visibility".
  • Keep the consequence the buyer described. Don't add a revenue loss they never mentioned.
  • End by asking whether you got it right. A correction is a reply, and it is cheaper now than after the proposal.
Discovery recap
Subject: @[Forecast review]: did I get this right? Hi @[First name], Thanks for walking me through @[how the forecast works today]. Here is what I heard: • The problem: @["managers rebuild the forecast from spreadsheets every Friday"] • Why it matters now: @[you need a forecast the team trusts before the November budget review] • Who else cares: @[your sales operations lead, who owns the Friday report] Next steps: • I send @[a sample report] by @[Wednesday] • We go through it with @[your sales operations lead] on @[Thursday at 10:00] Have I got the problem right, or is there something I missed? @[Your name]

How to write a demo follow-up email that moves the deal forward

A demo follow-up email separates what the demo proved from what the buyer still has to check. Interest in a feature and confirmation that it meets a requirement are different facts.

What works

  • Split the email into "shown" and "still open". The open list is the deal.
  • Give each open item an owner, so nobody has to ask who is checking it.
  • Offer a focused next step on the open item. A second general demo only helps if another team still needs to see it.
Demo follow-up
Subject: Demo recap: @[export] still to check Hi @[First name], Thanks for today. Where we landed: Shown in the demo: • @[Managers can review the forecast by region] • @[Deal changes since last week are flagged automatically] Still open: • @[Does the export include every column finance needs?] Owner: @[Maya in finance] • @[Can regional managers be limited to their own region?] Owner: me, answer by @[Friday] I'll send @[a sample export] by @[tomorrow]. Could you forward it to @[Maya] and ask her to mark any missing columns? @[Your name]

How to write a forwardable summary for internal approval

A forwardable summary is written for the person who missed the meeting. Your contact forwards it to finance, IT or their manager without rewriting a word.

What works

  • Label every part: problem, proposal, cost, what is still open, decision needed. The approver scans; they don't read.
  • Lead with the decision you need from the approver, not with your company.
  • Don't write as if they have already chosen you. Your contact may still be comparing options.
Forwardable summary
Subject: @[Forecast project]: summary for @[finance] Hi @[First name], Here is the summary for @[your finance review]. It is written so you can forward it as is. Decision needed: @[Whether finance joins a 30-day evaluation starting this month.] • Problem: @[Regional managers rebuild the forecast each Friday from separate spreadsheets.] • Proposal: @[One shared forecast for the regional sales team, evaluated for 30 days.] • Cost: @[See the attached proposal; the evaluation itself is free.] • Still open: @[Required export columns and the annual budget.] Is anything missing before you send it to @[Maya]? @[Your name]

How to follow up on a question you promised to answer

A promised-answer follow-up delivers the answer you said you would find. It is the easiest follow-up to get right, and the one most often replaced with a brochure.

What works

  • Put the answer in the first line. Conditions and attachments come after.
  • Say what the answer means for the buyer's workflow, not just for your product.
  • If you don't have the answer yet, send the date you will have it, and keep that date.
Promised answer
Subject: Answer: @[regional access] Hi @[First name], You asked whether @[regional managers can be restricted to their own region]. Short answer: @[yes]. What it takes: • @[An administrator assigns each manager a region before they log in.] • @[It takes about ten minutes for a team of your size.] I've attached @[the permissions guide] for @[Alex and your IT team]. Does that cover the requirement @[Alex] raised? @[Your name]

Only send a yes you have checked for your product. If the check is unfinished, write: "I'm confirming the regional permissions with our technical team. You'll have the answer by Thursday."

How to write proposal follow-ups that get replies

A proposal follow-up email finds out what stands between the buyer and a decision. Sending a proposal does not mean the buyer has agreed on budget, scope or who signs.

What works

  • Tie it to the review date you agreed, not to the day you sent the proposal.
  • Name the decisions still open and ask which one is blocking. A buyer can answer "budget" in one word.
  • Don't ask for a signature while the buyer is still checking whether the setup works.
Proposal follow-up
Subject: @[Forecast proposal]: what's left after @[Tuesday's finance review]? Hi @[First name], We planned to pick the proposal back up after @[your finance review on Tuesday]. Two decisions are still open on my side: • @[Budget: has finance approved the annual cost?] • @[Implementation: is Alex happy with the setup plan?] Which of these is holding things up, or is it something else? If @[the budget is approved], I can book @[the implementation review with Alex] for @[next week]. @[Your name]

If no review date was agreed, ask when the team expects to look at the proposal, then follow up on that date.

How to follow up when a buyer says "not now"

A milestone follow-up answers "come back later" by tying the next conversation to an event the buyer named, such as a budget review, a reorganization or a hire.

What works

  • Anchor to their milestone, not to "next quarter". If they only said "later", ask what would have to happen first.
  • Send anything they asked for now, so the project is easy to restart.
  • Respect the pause. A postponed project is not permission for weekly reminders. Log the date in the CRM so whoever has the account next sees it too.
Milestone follow-up
Subject: After @[the November budget review] Hi @[First name], You said @[the forecast project] depends on @[the November budget review], so I'll leave it until then. In the meantime: • I'm sending @[the evaluation checklist] you asked for, so it's ready for planning • I've noted @[the week of 23 November] to reconnect Does that week work, or should I wait until @[the new budget is signed off]? @[Your name]

How to follow up on a deal that has gone quiet

A stalled deal follow-up goes out when an agreed step has passed without a word. Its job is to find out whether the project is still on, not to make the buyer feel chased.

What works

  • Refer to the missed step factually. "I've emailed you three times" makes the email about your effort.
  • Offer two easy answers: still on, or paused. Either one tells you what to do next.
  • Offer to take work off the buyer's plate if the project is still on.
Stalled deal
Subject: Is the @[forecast evaluation] still on? Hi @[First name], We had planned to @[review finance's export requirements] @[last Thursday]. Is the evaluation: • still on, just later than planned, or • paused for now? If it's still on, I can @[check the sample export with Alex] so it's ready when you are. If it's paused, tell me when to check back and I'll leave it until then. @[Your name]

The reply tells you whether to book the review, move the reminder or close the opportunity. Silence alone doesn't tell you why a project stopped. For where deals usually stall, see where sales deals go cold.

Frequently asked questions

One job per email. A good template confirms one thing, delivers what you promised, and ends with one question the buyer can answer in a line. Keep the structure and replace every placeholder with the buyer's own words, names and dates; a template sent with generic phrasing reads like one.
Yes, for anything with more than one part. Bullets make open items, owners and dates easy to check, and bolding the decision or the date makes the ask stand out. Use bold and italics on one or two things per email; formatting everything formats nothing.
Reuse the structure, not the content. Pick the template by the buyer's next task rather than by how many emails you have sent, and respect a request to stop or pause. The familiar claim that 80% of sales need five follow-ups has no retrievable primary source; see the sales statistics fact-check.
Yes. A draft can use the meeting conversation and the deal history, but check the recipients, facts, commitments and tone before you send it. Spiich drafts one follow-up per recorded meeting and never sends it for you; see how follow-up drafts work.

Agree the next step before the meeting ends

Every template above is easier to write when the meeting ended with a clear next step. Before you end your next call, ask: "What needs to happen next, who will do it, and by when?" Then write the follow-up around the answer.

When the follow-up is drafted from the conversation, the buyer's words are already in it. At Hedda, the CEO credits better emails and follow-ups drafted in Spiich with a significant rise in conversion. Whichever template you use, the rep still reads it, edits it and presses Send.