Follow-Up After the Demo
12 sales follow-up email templates for after the demo
By Justin HamptonLast updated Reviewed by Justin HamptonHow we write these
Short answer
Key takeaways
- Send a recap within a few hours of the demo, and the proposal a day or two later.
- From the third email on, every follow-up should give the buyer something useful, such as an answer or a business case.
- When a buyer pushes back on price, ask what they are comparing it to before offering any discount.
- Use proposal open signals to time your follow-up, but never tell the buyer you saw them open it.
- Send a polite breakup email when nothing has worked; it often gets the most honest answer.
A sales follow-up email after the demo has one job: move the deal one step forward. Below are 12 templates for the moments that actually happen after a demo, from the same-day recap to the email you send after a no. Each one says when to use it. Copy them, then rewrite the brackets in your own words.
I've written versions of all of these for my own deals. The pattern that works is always the same: short, about the buyer, and one clear ask. If the deal has already gone quiet, the guide to what to send when a prospect goes silent after your proposal goes deeper on that one situation.
A simple follow-up rhythm
You don't need a 14-step cadence. You need a reason for every email. Here's the rhythm I use after a demo:
| When | What to send |
|---|---|
| Same day | Recap (template 1) |
| Day 1-2 | The proposal (template 2) |
| Day 3-4 after the proposal | Short check-in (template 3) |
| As things come up | Pricing, champion, stakeholder and answer emails (templates 4-7) |
| Before the decision date | Decision-week nudge (template 8) |
| About 2 weeks of silence | Gone-quiet email (template 9) |
| After that | Breakup email (template 10) |
1. The same-day recap
When to use it: within a few hours of the demo. Write down their words while you remember them.
Subject: Recap from today, and what happens next
Hi [Name],
Thanks for the time today. Here's what I heard, so you can tell me if I got anything wrong:
- [Problem 1, in their words]
- [Problem 2, in their words]
- [What a good result looks like to them]
Next step: I'll send a proposal by [day] that shows how we'd handle each of these, with pricing. You mentioned [person or team] will want to see it too.
Does [day and time] work to walk through it together?
[Your name]
2. Sending the proposal
When to use it: when the proposal is ready. Lead with their problems, not your product.
Subject: Your proposal for [their goal]
Hi [Name],
Here's the proposal we talked about: [link]
It starts with the problems you described, then shows how we'd solve each one. Pricing is at the end with [one, two and three-year] options so you can compare.
If [approver or colleague] needs to see it, you can forward the link. Happy to answer anything before our call on [day].
[Your name]
3. No reply after 3 days
When to use it: three or four days after sending the proposal with no answer. Keep it light and give them an easy reply.
Subject: Re: Your proposal for [their goal]
Hi [Name],
Just checking the proposal reached you. One question that usually comes up at this point: is [the main problem] still the priority for [this quarter], or has something else jumped ahead of it?
Either answer is useful to me.
[Your name]
4. After the buyer reacts to pricing
When to use it: when they say the price is higher than they expected. Don't discount in the first reply. Understand first.
Subject: About the pricing
Hi [Name],
Thanks for being straight with me about the price. Before I suggest anything, can I check what you're comparing it to? Is it a budget number, another quote, or what you pay today?
A few things we can look at together:
- A longer term, which lowers the yearly price
- Starting with [fewer users or one team] and adding more later
- What it costs you to keep [the problem] for another year
If you can share the number you need to hit, I'll tell you honestly whether we can get there.
[Your name]
5. Your champion needs to sell it internally
When to use it: when your contact likes it but has to convince someone who wasn't on the call. Do the work for them.
Subject: Something to make the internal conversation easier
Hi [Name],
You mentioned you'll need to get [approver] on board. To save you time, I put together a one-page summary you can forward or copy into your own words: [link]
It covers the problem, what it costs today, the options, the price and the payback. Change anything that doesn't sound like you.
Is there a question you expect [approver] to ask that I can help you answer?
[Your name]
A one-page business case is the most useful thing you can send here. Use the business case template to draft it.
6. Bringing in a new stakeholder
When to use it: when someone new joins the decision, like finance, IT or the owner. Write to them directly, briefly, and give them what they care about.
Subject: [Their company] and [your company]: a short summary for you
Hi [New stakeholder name],
[Champion name] asked me to share where things are. In short:
- The problem: [one line, in the team's words]
- What we'd do: [one line]
- Cost: [price and term]
- What you'll probably want to check: [security, contract terms, budget timing]
The full proposal is here: [link]. I'm glad to send anything specific you need, or set up 20 minutes.
[Your name]
7. Answering a question you couldn't answer on the call
When to use it: when you said "I'll find out." Close the loop fast. It builds more trust than the demo did.
Subject: Answer to your question about [topic]
Hi [Name],
On the call you asked [their question]. The answer: [clear, direct answer].
[One or two lines of detail, or a link to the documentation.]
Does that settle it, or does it raise anything else I should check?
[Your name]
8. Before the decision date
When to use it: a few days before the date they gave you. Make deciding easy and surface any last blocker.
Subject: Anything you need before [decision date]?
Hi [Name],
You mentioned you're aiming to decide by [date]. Is there anything still open that I can help close before then? Common ones at this stage are contract review, a security question, or the start date.
If everything's in place, the next step is [accept the proposal / sign the order form], and we'd [first step after yes] on [date].
[Your name]
9. Gone quiet for two weeks
When to use it: about two weeks of silence after the check-ins. Bring something new, not "just following up."
Subject: A thought on [their problem]
Hi [Name],
I haven't heard back, so I'm guessing things got busy or the priority moved. No problem either way.
One thing I meant to share: [a useful idea, a short example, or an answer to a question they had]. It might help even if you don't go with us.
Should I check back in [next month], or close this out for now?
[Your name]
10. The breakup email
When to use it: when nothing has worked. Be polite, be final, and make it easy to reply. It often gets the most honest answer of the whole thread.
Subject: Should I close your file?
Hi [Name],
I've reached out a few times and haven't heard back, so I'll assume the timing isn't right and stop emailing.
If [the problem] comes back up, just reply to this and we'll pick up where we left off. The proposal stays as it is until [date].
Thanks for the time you gave this.
[Your name]
11. After a no
When to use it: when they choose someone else or do nothing. Ask why, keep the door open, and mean it.
Subject: Thanks for letting me know
Hi [Name],
Thanks for telling me. I'd rather know than wonder.
If you have two minutes, I'd value one honest line on why: price, fit, timing, or something we missed. It helps me get better.
I hope [their project] goes well. If anything changes, you know where I am.
[Your name]
12. After a yes
When to use it: the moment they accept. Confirm the next steps so the deal doesn't stall between "yes" and "live."
Subject: Thank you, here's what happens next
Hi [Name],
Thank you. I'm glad we're doing this together.
Here's what happens next:
- [Paperwork or invoice step] by [date]
- Kickoff call on [date] with [who should attend]
- [First milestone] by [date]
If anyone else on your side should be on the kickoff, send me their name and I'll add them.
[Your name]
How to make these work
- Use their words. The recap only works if it sounds like what they said. Write it from your notes, not from memory a week later.
- One ask per email. A question they can answer in one line gets more replies than three questions.
- Give before you ask. From the third email on, every message should carry something useful: an answer, a summary, a business case.
- Keep it phone-sized. Most follow-ups are read on a phone between meetings. If it needs scrolling, cut it.
- Agree the plan early. Follow-ups are easier when you both agreed the steps and dates on the call. A mutual action plan gives every email a reason to exist.
Common mistakes
- "Just checking in." It gives the buyer nothing and asks them to do work. Replace it with a question or something useful.
- Mentioning that you saw them open the proposal. Use the signal for timing. Don't say it.
- Discounting before you understand the objection. You'll lower the price and still lose if price wasn't the real problem.
- Writing to the champion only. Once others are involved, write to them directly, with their own short summary.
- Never sending the breakup email. Leaving a dead deal open makes your pipeline look better than it is.
Write them faster
Templates get you started. The fastest version is one written from what was actually said on the call. The follow-up email preview shows how that works for each deal stage. Inside AfterDemo, the AI drafts follow-ups in your own writing style from the call, and nothing goes to the buyer until you approve it.
Free toolFollow-up Email GeneratorQuestions people ask
How soon should you send a follow-up email after a demo?
The same day, ideally within a few hours, while the call is fresh for both of you. Send a short recap of what you heard and the agreed next step. The proposal can follow a day or two later if you need time to build it properly.
How many follow-up emails should you send before giving up?
There's no magic number. A sensible pattern is a check-in after three days, another after a week, a value-add a week later, then a polite breakup email. Every email should give the buyer something new, not just ask if they've had a chance to look.
What should a follow-up email after a sales call include?
What you heard, in the buyer's words; what you agreed to do next and by when; anything you promised to send; and one clear question or ask. Keep it short enough to read on a phone.
Should you mention that you saw the buyer open your proposal?
No. Use the signal to time your follow-up and decide what to say, but don't tell the buyer you watched them read it. It feels like surveillance and makes people stop opening your emails.