The follow-up email is where most deals quietly slow down. The call went well, everyone agreed on a next step, and then the email that confirms it goes out two days later, says "great speaking with you", and asks nothing.
A good follow-up does three jobs: it shows you listened, it puts the agreed next step in writing, and it makes replying easy. Below are the rules, then six templates for the situations that come up most.
Four rules for a follow-up that gets a reply
- Send it the same day. The buyer still remembers the call and can correct anything you got wrong.
- Recap in their words, not yours. If they said "our reps spend Friday afternoons updating Zoho", write that, not "you have CRM hygiene challenges".
- One next step, with an owner and a date. Not three options. Not "let me know".
- Keep it short enough to read on a phone. If it needs scrolling, it needs cutting.
1. After a discovery call
Subject: Notes from today, and next steps
Hi [Name],
Thanks for the time today. What I took away:
- [Problem, in their words]
- [What it costs them: time, money, a missed target]
- [What a good outcome looks like for them, and by when]
As agreed, I'll [your action] by [date], and you'll [their action] by [date].
Did I miss anything important?
[Your name]
The closing question is deliberate. It invites a reply, and a correction now is worth far more than one after the proposal.
2. After a demo
Subject: [Their company] + [your product]: what we showed and what's next
Hi [Name],
Thanks to you and [colleague] for today. The parts that seemed most relevant to you:
- [Feature] for [their use case]
- [Feature] for [their use case]
You asked about [question]. [Answer, or when you'll have it.]
Next step: [specific step, e.g. a 2-week pilot with 5 reps], starting [date]. Shall I send the setup details?
[Your name]
3. After sending a proposal, when there's no reply
Wait three to four working days, then:
Subject: Re: Proposal for [their company]
Hi [Name],
Checking in on the proposal. Is there anything in it that needs changing before you can take it to [decision maker]?
If the timing has moved, that's fine. Just tell me and I'll follow up when it suits you.
[Your name]
Giving them an easy way to say "not now" gets more honest replies than a second "just checking in".
4. When the deal has stalled ("dekhte hain")
"Dekhte hain" and "let me check internally" usually mean there is an objection nobody has said out loud. Name the likely one:
Subject: A quick question about [project]
Hi [Name],
When we spoke, it sounded like [timing / budget / getting approval from X] might be the real hurdle. Is that right?
If it is, here's how other teams handled it: [one sentence: a smaller pilot, a different start date, a call with the decision maker].
Happy to adjust, or to close this out for now if it isn't a priority.
[Your name]
5. After a no-show
Subject: Missed you today
Hi [Name],
Looks like today didn't work out. No problem. Here are two times that work for me: [option 1], [option 2]. Or pick any slot here: [booking link].
[Your name]
No guilt, no "as per my last email". Make rescheduling one click.
6. After a "yes, let's pilot"
Subject: Pilot plan: [their company], starting [date]
Hi [Name],
Great to have this agreed. The plan:
- Who: [names / number of users]
- Starts: [date]. Review call: [date]
- What success looks like: [the measure you agreed, in their words]
Before then: I'll [your action] by [date]; could you [their action] by [date]?
[Your name]
Writing down what success looks like is what makes the review call a decision instead of another demo.
Let the call write the email
These templates are only as good as your notes from the call. That is why EchoBrief drafts the follow-up for you: after a call on Google Meet, Zoom or Teams, click Draft follow-up on the meeting page and you get an email built from what was actually said, with the thank-you, the recap of what each side committed to, the buyer's own words for what they asked for, and the agreed next step. It only uses facts from the call, so nothing is invented, and it works on calls in Hindi and Hinglish too.
EchoBrief is in invite-only beta: request access to try it on your next call.