How to follow up after a sales meeting, with 3 email templates

You have had a good meeting. The client spoke openly, you both agreed there was something worth exploring, and you said you would send something over. What you send next, and when, decides whether that meeting turns into a deal or a pleasant memory.

This guide covers the timing, a five-minute debrief to do before you write, what the email should contain, and three templates you can adapt.

How soon should you follow up after a sales meeting?

Send your follow-up the same day if you can, and no later than the next working day. The client still remembers the conversation, and so do you.

Speed matters for a second reason. Chapter 6 of The Pharaoh's Pitch lists meeting expectations as the first of three things that make a salesperson trustworthy. Its example is simple: don't be late for the first meeting, because if you can't meet a small expectation, the client has reason to doubt the larger ones that come after the sale.

A follow-up you promised "by Friday" is exactly that kind of small, visible test. So promise a date you can beat. Say Thursday, send it Wednesday.

Two sensible exceptions:

• The meeting ended late on a Friday. Monday morning is fine. Nobody is reading your recap at the weekend.
• You are waiting on your own team. Send a two-line note the same day: "Thanks again for this morning. I'm getting the implementation costs confirmed with our delivery team and will have them to you by Wednesday."

Before you write: debrief yourself first

Spend five minutes writing down what happened before you write a word to the client. Without this step, the email describes your presentation instead of their problem.

The book closes on this habit. As Ivan Yong puts it in the epilogue:

Make this into a habit whereby you would debrief yourself right after a sales meeting, even one that has ended not in your favour.

He suggests noting what happened objectively, without emotion. Chapter 5 adds a related practice it calls self-monitoring: reflect on your own behaviour in the meeting and on how the client reacted, then decide what to change. For a follow-up email, five questions are enough:

1. What is their problem, in the words they used? Not your category name for it. If the CFO said "we can't close the books on time", write that, not "finance process optimisation".
2. What do they want personally? The book calls this a buyer's personal win: what an individual decision maker hopes to gain for themselves, beyond what the company needs. A finance director may want the board to stop asking why the numbers are late.
3. Who else has a say, and what does each of them care about?
4. What did you promise, and by when?
5. What is the one next step, and did they seem ready for it?

Chapter 4 shows what happens when this step is skipped. It describes a two-hour meeting, with the author observing, in which a vendor team kept presenting data and case studies to a university dean while a question he raised again and again went unanswered.

The team never asked what the dean wanted for himself, and lost the account six months later. A follow-up written without a debrief repeats that mistake in writing.

What a post-meeting follow-up email should include

A good follow-up email has five parts: a specific thank you, a recap in the client's words, the agreed actions, one next step with a date, and only the attachments you promised. Everything else can go.

• A subject line they can find later. Name the meeting and the topic: "Tuesday's conversation: month-end close". Not "Following up!"
• One line of thanks, made specific. "Thank you for walking me through how month-end works today" beats "Thanks for your time."
• A two or three line recap. Restate their situation and what matters to them. If you have misunderstood something, this is where they will correct you, which is exactly what you want.
• What each side agreed to do. Yours first, with dates. Then theirs, phrased as a reminder rather than a demand.
• One next step. A proposed date and time, with an easy way to move it.

What to leave out: a re-pitch of the product, the full deck "for reference", three different calls to action, and the phrase "just checking in". Keep it short enough to read on a phone. If you are writing a sixth paragraph, you are probably selling again.

Three follow-up email templates

Adapt these rather than paste them. The recap only works if it uses the client's actual words.

Template 1: the recap after a first meeting

For a software seller writing to a finance director after a discovery call.

Subject: Tuesday's conversation: month-end close

Hi [Name],

Thank you for walking me through how month-end works today, and for being so candid about the pressure from the board.

To check I've understood: your team reconciles across three systems, which means the board doesn't see final numbers until the second week of the month. You'd like to shorten that before the next financial year, without adding headcount.

As promised, I'll send a short outline of how we'd approach the reconciliation by Thursday. You mentioned you'd check with [IT lead's name] about access to the ERP.

Could we take 30 minutes on [date] at 10am to go through the outline with [IT lead's name]? Happy to move it if another time works better.

Best regards, [Your name]

Template 2: the email your contact will forward

For a consultant whose contact at a regional bank needs to sell the idea upward. Assume every follow-up after a group meeting will be forwarded, and write it so your contact looks good when it is.

Subject: Branch onboarding review: summary for your team

Hi [Name],

Thank you for bringing your operations and compliance colleagues together on Wednesday. Your framing of the problem, that onboarding delays are costing branches their best new customers, gave the discussion real focus.

The three priorities the group agreed on were: cutting the number of handoffs, keeping compliance sign-off inside the agreed turnaround, and measuring time from application to first transaction.

I've attached the one-page scope we discussed, written so it can be shared with [senior stakeholder] as it is.

Would it help if I joined the first ten minutes of your meeting with [senior stakeholder] to answer questions? If not, I'm happy to follow your lead on timing.

Kind regards, [Your name]

Note what this email leaves out: anything the contact told you privately, such as their budget or their frustration with a colleague. Chapter 6 treats confidential information, with budget as its example, as something a trustworthy seller never uses against the client.

Keeping it out of an email that will travel round their office is part of the same discipline.

Template 3: the nudge when they haven't replied

For an insurance broker who sent a recap to an SME owner a week ago and heard nothing.

Subject: One more thought on your group medical renewal

Hi [Name],

I know renewal season is busy, so I'll keep this short.

One thing I didn't cover when we met: [a specific, useful item, for example how the outpatient limit would work for the staff you mentioned]. It speaks directly to the concern you raised about cost per head.

If it's easier to talk it through, I'm free for 15 minutes on Thursday or Friday morning. And if the timing has changed, just tell me and I'll check back closer to your renewal date.

Best, [Your name]

The nudge works because it brings something new and offers an easy way out. "Just checking in" asks the client to do work. This gives them a reason to reply.

Call or email, and how many follow-ups

Email the first recap, because a written summary can be checked, corrected and forwarded. After that, use whatever channel the client actually answers.

Some buyers reply to a phone call or a message within minutes and leave email for days. With relationship-first buyers in Kuala Lumpur or Singapore, a call can do more than a third email; there is more on that in our guide to selling to Malaysian and Singapore buyers.

There is no right number of follow-ups. The rule is that each one must add something. Follow up on the date you agreed; if nothing was agreed, send one or two useful nudges, then a short note closing the loop:

"I haven't heard back, so I'll assume the timing isn't right and won't keep filling your inbox. If things change, I'd be glad to pick this up again."

If the meeting ended with "let me think about it", the approach is a little different; see our guide to what to say when a prospect needs to think it over. If you have already sent a proposal and it has gone quiet, read following up on a proposal.

When the answer is no, follow up once more anyway, to ask why. The book's author describes still meeting prospects who had bought from someone else, because conversations about lost deals hold some of the best lessons in selling:

"Thank you for letting me know, and for telling me directly. If you're open to it, I'd value fifteen minutes to hear what tipped the decision. No pitch. It would genuinely help me improve."

The Pharaoh's Pitch lens: the pitch continues after the meeting

The book treats the follow-up as part of the pitch, not an afterthought to it. In chapter 6, the end of the pitch is described as the start of the closing stage. As Ivan Yong puts it:

You may be lulled into complacency the moment you have finished your pitching, thinking that you have done what's necessary to win over the client. That is far from the truth.

The same passage makes two practical suggestions.

First, pitch with the expectation of managing things after the meeting, which can mean holding some information back so you have something to bring later. Second, make each follow-up continue from the original conversation rather than starting a new one. That is why Template 3 introduces a single new point that links back to a concern the client raised.

Chapter 6 also asks for a consistent message throughout the engagement, because consistency signals that you are authentic and stick to your commitments. In practice, the problem statement in your recap should be the same one in your proposal and in your last follow-up. If it keeps shifting, the client will wonder whether you understood it at all.

Chapter 4's idea of giving face shapes Template 2. The book describes seeing a client as an "individual-in-relation": someone whose standing with colleagues you protect, even when those colleagues are not in the room.

An email that credits your contact's thinking in front of their boss does that. One that exposes a private remark does the opposite.

There is a quieter lesson in chapter 4 too. The author recalls a shared taxi in Singapore that ended with a businessman giving him his card and inviting him to visit.

He never followed up, and writes that he still wonders what would have come of it. Most missed follow-ups are like that: nothing dramatic, just a door that was open and then wasn't.

Niles has a post-meeting debrief and an email-draft tool if you would like a second opinion before you press send. For the groundwork that makes the recap easy to write, see how to prepare for a first sales meeting.