Nousu Collective
    Book a 30-minute call
    All sales email templates

    Follow-up

    Follow-up email after a meeting or demo

    After a good meeting the deal belongs to whoever writes the clearest summary. Buyers forward recaps to colleagues who were not in the room, so the email often does more selling than the meeting did.

    Jump to the templatesBrowse the library

    Quick answer

    Send the recap the same day, in three parts: what they told you, what you agreed would happen next and who does what by when. The templates below cover the recap, the proposal email and a version written to be forwarded internally.

    Write it for the person who wasn't there. If a finance lead reading it cold could not tell why the meeting happened, it is too vague.

    How to use these templates

    Every {{placeholder}} marks something you must research or write yourself. Replace all of them before you send, and if you cannot fill one with something true and specific, pick a different template.

    The names mean the same thing on every page: {{first_name}} and {{company}} are always the prospect and their business, {{your_name}}, {{your_company}} and {{your_phone}} are always you, and {{their_phone}} is the number you called them on.

    Each email ends with {{signature}} and {{opt_out}}. {{signature}} is your full name, role, company, website and phone number. {{opt_out}} is one plain line. On a cold email: If this isn't relevant, reply "no thanks" and I won't contact you again. In an ongoing conversation it can be quieter: Prefer not to hear from me? Reply "unsubscribe". Keep both in every commercial email, including short follow-ups.

    The structure of a recap that moves deals

    Lead with their situation, not your product. Two or three bullet points in the language they used, then the agreed next step with a date, then anything you owe them. Keep features out unless they asked about a specific one.

    A dated next step is the line that matters. 'Let's touch base soon' is not a next step. 'You'll share the current process with {{colleague}} by Thursday and we'll meet again on the 14th' is. If no next step was agreed, the recap should propose one.

    • What we heard: their problem, its cost and why now.
    • What we agreed: the next meeting, the next document or the next person to involve.
    • Who does what by when, including you.

    The templates

    Each template has subject lines, the body with placeholders, when to use it, why it works, three variants, common mistakes and a compliance note.

    The recap and next steps email

    Subject line options

    • recap: {{company}} and {{your_company}}
    • notes and next steps from today
    • {{meeting_topic}}: what we agreed

    Email

    Hi {{first_name}}, Thanks for the time today. A quick recap so we're on the same page. What we heard: - {{problem_in_their_words}} - {{impact_or_cost}} - {{why_now}} What we agreed: - {{next_step_1}} by {{date_1}} ({{owner_1}}) - {{next_step_2}} by {{date_2}} ({{owner_2}}) I've sent an invite for {{next_meeting_date}}. If I've got anything wrong, reply and I'll fix it. {{signature}} {{opt_out}}

    When to use it

    The same day as a discovery call or demo, to everyone who attended.

    Why it works

    It proves you listened, gives the buyer a document they can forward and turns a good conversation into dated commitments on both sides. Errors get corrected early, before they cost you a stage.

    Variants

    Short

    Hi {{first_name}}, Thanks for today. You're dealing with {{problem_in_their_words}}. Next: {{next_step_1}} by {{date_1}}, then we meet {{next_meeting_date}}. {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, Thank you for your time today. To summarise our discussion: {{problem_in_their_words}}, with {{impact_or_cost}}, and a need to address it because {{why_now}}. We agreed that {{owner_1}} will {{next_step_1}} by {{date_1}}, and that we will reconvene on {{next_meeting_date}}. Please let me know if I have misrepresented anything. Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, Cheers for the time today. Here's what I took away: - {{problem_in_their_words}} - {{why_now}} Next up: {{next_step_1}} by {{date_1}}, and we're back together on {{next_meeting_date}}. Shout if I've got any of that wrong. Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Writing a feature list instead of their problem.
    • Leaving the next step undated.
    • Sending it two days later, after they have forgotten the detail.

    Compliance note

    Post-meeting emails are part of an existing conversation, but keep accurate sender details and honour any request to stop.

    The proposal email

    Subject line options

    • proposal for {{company}}: {{project_name}}
    • {{company}} proposal, as discussed
    • your proposal and the {{date}} decision

    Email

    Hi {{first_name}}, As promised, here's the proposal: {{link}}. It's built around what you told us: {{problem_in_their_words}}. The short version: - Scope: {{scope_summary}} - Investment: {{price_summary}} - Start: {{start_date}}, if signed by {{sign_by_date}} Can we take 20 minutes on {{day}} to walk through it with {{other_stakeholder}}? Questions are easier on a call than in an email chain. {{signature}} {{opt_out}}

    When to use it

    When you send a proposal or quote after a meeting where the buyer asked for one.

    Why it works

    The summary answers the three questions every approver asks: what, how much and when. Proposing a walkthrough with the other stakeholder stops the proposal sitting unread in someone's inbox.

    Variants

    Short

    Hi {{first_name}}, Proposal here: {{link}}. Scope {{scope_summary}}, {{price_summary}}, start {{start_date}}. Walk through it {{day}}? {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, Please find our proposal at {{link}}. It addresses the priorities you outlined, in particular {{problem_in_their_words}}. In summary, the proposed scope is {{scope_summary}} at {{price_summary}}, commencing {{start_date}}. Would {{day}} suit for a short walkthrough with {{other_stakeholder}}? Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, Here's the proposal: {{link}} Short version: {{scope_summary}}, {{price_summary}}, kicking off {{start_date}}. Easier to talk it through than email back and forth, so can we grab 20 minutes {{day}} with {{other_stakeholder}}? Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Sending the proposal with no summary, so the reader has to open it to learn anything.
    • Burying the price on page nine.

    Compliance note

    If your proposal email goes to new stakeholders for the first time, introduce yourself properly and keep your full contact details in the signature.

    The forwardable stakeholder recap

    Subject line options

    • for {{other_stakeholder_role}}: {{project_name}} summary
    • summary for the team: {{topic}}
    • {{company}}: one-page summary of {{topic}}

    Email

    Hi {{first_name}}, You mentioned you'd need to run this past {{other_stakeholder_role}}. Here's a version written to forward as is. {{company}} is looking at {{topic}} because {{why_now}}. Today the team {{current_process}}, which {{impact_or_cost}}. {{your_company}} would {{proposed_change}}. Expected outcome: {{expected_outcome}}. The decision needed is {{decision_needed}} by {{date}}. Happy to join a 15-minute call with {{other_stakeholder_role}} if that's easier. {{signature}} {{opt_out}}

    When to use it

    When your contact has to sell the idea internally to someone you have not met, such as finance, IT or a founder.

    Why it works

    It does your champion's work for them in plain language, with no jargon and no attachments. It also opens the door to the multi-threading email by offering a call with the other stakeholder.

    Variants

    Short

    Hi {{first_name}}, Forwardable version: {{company}} is fixing {{topic}} because {{why_now}}. We'd {{proposed_change}}. Decision needed by {{date}}. {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, As requested, a summary suitable for {{other_stakeholder_role}}: {{company}} is assessing {{topic}} due to {{why_now}}. The current approach, {{current_process}}, results in {{impact_or_cost}}. {{your_company}} proposes to {{proposed_change}}, with an expected outcome of {{expected_outcome}}. A decision is required by {{date}}. Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, Here's one you can forward straight on to {{other_stakeholder_role}}: We're looking at {{topic}} because {{why_now}}. Right now {{current_process}}, and it's costing us {{impact_or_cost}}. The fix is {{proposed_change}}. Decision needed by {{date}}. Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Writing it in your sales language rather than theirs.
    • Adding claims you could not back up if the other stakeholder asked.

    Compliance note

    You are writing for your contact to forward. Do not email the other stakeholder directly until you have a published work address or an introduction, and a message relevant to their role.

    Spam Act checklist for every template

    Australian B2B email is legal and regulated by the Spam Act 2003. Before you send any template on this page, check these four things.

    Australian cold calling and Spam Act rules
    • Consent. You need express consent (they agreed) or inferred consent. For B2B, consent can be inferred where a work address is conspicuously published, the message is relevant to the person's role, and there is no statement that they do not want unsolicited messages.
    • Identification. Every message clearly identifies you and your business, with contact details that stay accurate for at least 30 days after you send it.
    • Unsubscribe. Every commercial message includes a working opt-out, which must be actioned within 5 working days and keep working for at least 30 days after sending.
    • No harvested lists. Do not use address-harvesting software or lists built with it. A bought list does not come with consent.

    Calls in the same cadence follow different rules: wash Australian numbers against the Do Not Call Register and call within permitted hours. New Zealand and Singapore recipients are covered by their own laws, summarised on the template library hub. This is general information, not legal advice. AU, NZ and Singapore rules

    FAQ

    Follow-up after a meeting or demo: questions

    Practical answers from SDR managers who run outbound every day.

    Still have questions?

    Book a 30-minute call

    The same day. A recap sent within a few hours is accurate, and it lands while the buyer is still thinking about the problem.

    Their problem in their words, the agreed next step with a date, and anything you owe them. Skip the feature recap unless they asked about a specific feature.

    Everyone who attended. Then offer your main contact a forwardable version for anyone who needs to approve it but was not there.

    Propose one in the recap: a specific meeting, a document or a person to involve, with a date. A recap without a next step usually ends up as a stalled deal.

    A link to a shared document is usually easier to track and less likely to be filtered. Either way, put the summary in the email itself.

    Ask a specific question about the decision, such as whether the {{date}} timeline still stands. If it stays quiet, use the re-engagement templates.

    Related templates and guides

    Discovery call questions

    What to confirm before the recap

    Multi-threading emails

    Reach the second stakeholder

    Qualification frameworks

    BANT, MEDDIC and SPIN compared

    Appointment setting

    Qualified meetings booked into your calendar

    All sales email templates

    The full template library

    Want Australian SDRs to run your outreach?

    Book a 30-minute call. We will map your market and buyers and show you what a phone-first campaign would book.

    Book a 30-minute callSee pricing

    Starting at $7,000 a month. Exact fee quoted after a 30-minute call.