What to Do After a Sales Meeting: The Complete Post-Meeting Playbook

Capture Raw Notes

Within 5 minutes

The first 5 minutes after a meeting are the most valuable and the most wasted. Your memory of the conversation is at its peak. Every minute you wait, details disappear.

Don't write polished notes. Write raw capture: the buyer's exact words on their biggest problem, the objections that came up, the names they mentioned, the timeline they referenced, the competitors they're evaluating.

What to capture:

• Their #1 priority. What was the thing they kept coming back to? Not what you wanted to talk about - what they wanted to talk about.
• Specific numbers. Budget range, team size, timeline ("We need this by Q3"), current spend on the problem.
• Objections or concerns. What made them hesitate? Technical concerns, pricing, internal politics, competing priorities.
• Decision process. Who else is involved? What's the approval path? Committee, boss, procurement step?
• Competitors mentioned. Who else are they talking to? What do they like about the alternatives?
• Exact quotes. The buyer's own words are gold for follow-ups. "We're drowning in CRM updates" is 10x more powerful in your follow-up than "you mentioned data management challenges."

The 5-Minute Rule

If you don't capture these details within 5 minutes, half of them will blur by tomorrow. Open your notes app, your CRM, or a voice memo. The format doesn't matter. Getting it down does.

If you record your meetings (and you should), the recording is your safety net - but don't rely on it as your primary capture method. You'll never go back and re-watch a 45-minute call. Capture the highlights while they're fresh, then use the recording to fill gaps later.

Update Your CRM

Within 15 minutes

This is the step most reps skip. And it's the step that causes the most damage over time.

A CRM that's 3 days out of date is a CRM that lies to you. The deal stage is wrong. The next step is missing. The close date is a guess. Multiply that across 20 deals, and your pipeline forecast is fiction.

What to update:

• Deal stage. Did the meeting move the deal forward? Update the stage. If the buyer agreed to a proposal review, that's a different stage than "discovery." Be precise.
• Close date. Did the buyer mention a timeline? Update the projected close date to match what they actually said, not what you hope.
• Next step. One sentence: what happens next and when. "Send proposal by Friday" or "Demo with technical team on March 20."
• Deal amount. If budget was discussed, update the amount. If it wasn't, leave it. Don't guess.
• Contact roles. Did new stakeholders appear in the meeting? Add them. Note their role in the decision.
• Meeting notes. Paste your raw capture from Step 1 into the deal record. Future you will thank you.

The 15-Minute Rule

CRM updates should happen while the conversation is still in your head. Not at the end of the day. Not during your Friday pipeline review. Now.

If updating your CRM takes more than 5 minutes per deal, your CRM setup is too complicated. Simplify the required fields. The goal is fast, accurate logging - not a data entry exercise.

The Follow-Up Email

Within 4 hours

Send it the same day. Not because speed is magic — because specificity fades. A follow-up written 2 hours after the meeting references what the buyer actually said. A follow-up written 2 days later defaults to generic filler.

This is the single highest-leverage action in the entire post-meeting process.

The formula: Specific reference from the conversation + one clear next action + easy reply.

Hi Sarah,

Good call earlier. When you mentioned that getting budget approval requires a business case showing 12-month ROI, that was really helpful context.

I've put together a one-pager with the ROI numbers based on what you shared about your current team size and deal volume. See attached.

Would Thursday at 10am work to walk through it together and discuss what to include in the internal business case?

Cheers,
[Your name]

This email works because "getting budget approval requires a business case showing 12-month ROI" is something Sarah actually said. It proves you were listening and shows you've already started working on her problem.

For a complete library of follow-up templates covering every scenario - first call, demo, budget discussion, gone quiet, multi-stakeholder, and more - see our Follow-Up Email Templates guide.

What Goes in the Email

Five things, in this order. Anything else is padding.

1. One thing they actually said. Not the topic. The sentence. "Budget sign-off needs a business case showing twelve-month ROI" is theirs. "Great to discuss your goals" is yours, and it proves you were in the room, nothing more.
2. What you agreed, as a list. Two or three lines. This is the bit that gets forwarded to someone who wasn't on the call, so write it for them.
3. Anything you promised, with a date on it. If you said you'd check something, say when you'll be back. If you've already got it, attach it.
4. One next step, with a time. "Thursday at 10?" beats "let me know what works" because it costs them one word to answer.
5. Sign off. No paragraph about your company. No mission statement. Your name.

Under 150 words. If it's longer than the meeting agenda, it won't get read.

Subject Lines After a Call

One job: make it obvious this is the thread from the conversation they just had. Being clever works against you here.

• Their words, plus the next step. "Business case for the board + Thursday"
• Recap: what we agreed. Boring, and it survives being forwarded.
• The thing you promised. "The ROI one-pager, as promised"

Not "Great speaking today". It's the most common follow-up subject line in existence, which means their eye has learned to skip it.

When There Were Four People on the Call

Reply to all of them, and write for the one who said the least. In most rooms the quiet one is the one who has to live with the decision, and they're the one who'll actually read the recap.

Two adjustments. Spell out anything that was shorthand in the room — the acronyms, the system names, the thing everyone nodded at. And if someone pushed back, answer it in the email. An objection doesn't disappear because the call ended. It gets repeated in a meeting you're not in.

How Fast Is Fast Enough

Same day, and four hours is the number I give people. Not because there's a study — because your memory of what they actually said goes quicker than you think. Write it while you can still hear the sentence.

If four hours isn't happening, here's the order: a specific email tomorrow morning, then a generic one this afternoon. The specific bit is doing the work. A same-day email that could've gone to anyone buys you nothing.

The one that doesn't work is the compromise everyone reaches for: two lines now, "detail to follow". It gets a nod, starts a thread that goes quiet, and now the real follow-up has to fight the feeling that you already sent one.

The "Here's What We Agreed" Email

Use when: the call produced decisions, not just interest, and you want them written down before anyone's memory drifts.

Hi [Name],

Writing this down so we're working from the same list.

— You're taking [item] to [person] before [date]
— I'm sending [thing] by [day]
— We're both assuming [assumption]. Tell me if that's wrong.

Thursday at 10?

[Your name]

Why it works: the third line. Saying the assumption out loud is the cheapest way to find out it's wrong while it's still cheap to be wrong.

Speed vs. quality

Don't sacrifice specificity for speed. A specific email sent at 4pm beats a generic email sent at 2pm. But a specific email sent at 2pm beats both. If you can't achieve both manually, this is where AI meeting tools earn their keep - pulling the specific details from your recording and drafting the email before you've even thought about it.

Create Action Items

Within 30 minutes

Meetings generate commitments. Commitments without tasks are just good intentions.

After every meeting, extract every action item, assign an owner, set a due date, and log it in a system you actually check. This sounds obvious. Almost nobody does it consistently.

What counts as an action item:

• Anything you promised to send ("I'll send you the case study")
• Anything the buyer promised to do ("I'll loop in our CTO")
• Internal tasks triggered by the meeting ("Build a custom demo for their integration use case")
• Calendar tasks ("Follow up if no response by Thursday")

Where to log them: In your CRM as tasks attached to the deal. Not in your personal to-do list. Not in a notebook. Not in your head. Tasks in the CRM are visible to your team, tied to the deal, and create accountability.

The Missed Action Item Problem

The most common way deals stall is not a "no." It's a forgotten promise. You said you'd send a case study. You forgot. The buyer notices. Trust erodes quietly. Capturing every action item within 30 minutes of the meeting ending is insurance against this.

Brief Your Team

Within 1 hour

Your colleagues shouldn't have to ask "how did the meeting go?" The relevant people should receive a brief before they think to ask.

Who needs to know:

• Your manager. A 3-line summary: what happened, what's next, any blockers. Managers hate being surprised. Give them the headline.
• The technical team. If a demo, integration, or technical review was discussed, brief the people who'll deliver it. Include the specific requirements the buyer mentioned.
• Other reps on the account. If multiple people in your org interact with this buyer, share context so nobody contradicts what was discussed.
• Support or onboarding. For deals nearing close, loop in the team that will own the relationship post-sale. Early context prevents painful handoffs later.

How to brief: A short Slack message or email to the relevant channel. Not a meeting about the meeting. 5-7 sentences covering: what was discussed, what was agreed, what's needed from the team, and the timeline.

Meeting with Acme Corp (Sarah Chen, VP Sales)

Went well. They're evaluating 3 tools for post-meeting automation. Main concern is integration with their existing HubSpot setup. Asked for a custom demo showing the HubSpot sync.

Next step: Technical demo on March 20. @james can you prep a HubSpot integration walkthrough by March 18?

Budget: confirmed £5K-8K range. Decision by end of Q1.

That took 60 seconds to write and saves 3 people from having to chase you for updates.

Schedule & Cadence

Schedule the Next Meeting

Same day

A deal without a next meeting is a deal without momentum. Before the day ends, send a calendar invite for whatever was agreed as the next step. Don't say "I'll send some times." Send the invite. Include:

• A clear purpose ("Proposal walkthrough" or "Technical demo: HubSpot integration")
• The right people invited (including anyone new who was mentioned in the meeting)
• A brief note in the description referencing what was agreed

If a specific date wasn't agreed, propose one in your follow-up email. Give two options. Make it easy to say yes. Every day between the meeting and the next booking is a day where priorities shift, competitors advance, and urgency fades.

Set the Follow-Up Cadence

Same day

One follow-up email is not a process. It's a hope. After the first follow-up, plan the sequence.

The "Just Checking In" Ban

If your follow-up starts with "just checking in" or "bumping this up", you've failed. Every touchpoint must add value - a useful resource, a relevant insight, a question that advances the conversation. If you can't think of something to add, wait until you can.

Building a personalised cadence manually takes 10-15 minutes after every meeting. Tools like 60 detect what was discussed, what the buyer cares about, and what the agreed next steps are, then suggest a cadence with specific content for each touchpoint. Total time: a couple of minutes instead of 15.

Review & Checklist

Review and Prep for Next Time

The final step happens before the next meeting, not after the current one - but you set it up now. Create a "pre-meeting review" task for the day before the next scheduled meeting. When it fires, review:

• Your notes from the last meeting (captured in Step 1, logged in Step 2)
• The action items you committed to (tracked in Step 4)
• Whether the buyer completed their actions (visible from your follow-up cadence in Step 7)
• Any new information since the last meeting - company news, stakeholder changes, competitor moves

This review takes 5 minutes when your records are clean. It takes 30 minutes of panicked scrambling when they're not.

The Compound Effect

Each meeting builds on the last. Clean notes make the next prep faster. Tracked action items make the next meeting start with accountability. A maintained cadence means the buyer shows up already re-engaged. The first time you do this, it feels slow. By the fifth deal, it's muscle memory.

Manual vs. Automated Comparison

For a rep doing 5 meetings per week, that's 3–5 hours reclaimed every week.

The Post-Meeting Checklist

Run through this after every meeting.

• Raw notes captured (within 5 min)
• CRM updated: stage, close date, next step, notes (within 15 min)
• Follow-up email sent with specific reference + next action (within 4 hours)
• Action items created with owners and due dates (within 30 min)
• Team briefed via Slack or email (within 1 hour)
• Next meeting scheduled or proposed (same day)
• Follow-up cadence planned and logged (same day)
• Pre-meeting review task set for next meeting

Automate the whole system

60 connects to your meeting recordings, extracts key details, drafts follow-up emails, updates CRM records, creates action items, and posts team briefs to Slack. You review and approve. Post-meeting admin goes from 40–70 minutes to under 10 - after every meeting, every time.