Resources

Consulting workflows

Consulting meeting follow-up templates (recap + next steps)

Copy-paste follow-up templates for consulting calls: recap, decision summary, and scope confirmation. Keep the next step clear so projects do not drift.

Mar 31, 20268 min read

Why a meeting recap is a consulting superpower

A good recap turns a conversation into a shared plan. It reduces misalignment, prevents scope drift, and makes it easy for the client to say "yes" to the next step.

Your follow-up should not be long. It should be clear: what we agreed, what happens next, and who owns what.

A simple recap structure (keep it short)

  • Context: the goal we discussed (one sentence).
  • Decisions: what we agreed (2-4 bullets).
  • Open questions: what we still need to confirm.
  • Next steps: who does what by when.

Copy-paste templates

Template 1: Standard recap + next steps

Subject: Recap + next steps

Hi {{first_name}} - thanks again for today.

Goal:
- {{one_sentence_goal}}

What we agreed:
- {{decision_1}}
- {{decision_2}}

Open questions:
- {{open_question_1}}

Next steps:
- {{your_name}}: {{your_next_step}} (by {{date}})
- {{client_name}}: {{client_next_step}} (by {{date}})

If I missed anything, reply here and I will update the plan.

Best,
{{your_name}}

Template 2: Decision summary (for stakeholders)

Subject: Summary of decisions

Hi {{first_name}} - sharing a short summary you can forward internally.

Decisions:
- {{decision_1}}
- {{decision_2}}

Why this approach:
- {{reason_1}}

Next step to move forward:
- {{single_next_step}} ({{date}})

Thanks,
{{your_name}}

Template 3: Confirm scope (prevent drift)

Subject: Confirming scope for {{project_name}}

Hi {{first_name}} - quick scope confirmation so we stay aligned.

In scope:
- {{in_scope_1}}
- {{in_scope_2}}

Out of scope (for now):
- {{out_scope_1}}

Next step:
- {{next_step}} (by {{date}})

If you want to adjust scope, reply with what you want to add and what we should remove.

Best,
{{your_name}}

Turn the recap into a system (thread -> next step)

A recap email is only half the system. The other half is capturing the next step so it does not get lost in your inbox.

After you send the recap, create one next-step task for yourself and one follow-up date if you are waiting on the client.

Common mistakes

  • Writing a long recap that no one reads.
  • No clear due dates, so the plan feels optional.
  • Avoiding scope language, then being surprised by scope creep later.
  • Not capturing the next step, so the recap becomes a dead document.

Weekly review: spot projects that are drifting

In your weekly review, scan for consulting projects with no next step. If the thread is quiet and there is no task, the project is drifting.

One short close-the-loop email is usually enough to restore momentum.

Want this workflow inside Gmail?

Donna CRM runs inside Gmail as a Chrome extension. Use these workflows with real contact context, pipeline stages, and follow-up tasks - without leaving your inbox.

FAQs

Common questions about consulting meeting follow-ups.

How soon should I send a meeting follow-up?
Same day is ideal. Next morning is fine. The longer you wait, the more the recap turns into a memory test instead of a plan.
Should I include pricing or budget in the recap?
Only if it was discussed and it helps prevent confusion. If budget is sensitive, reference it briefly and offer to confirm details on a short call.
What if the client never replies to recaps?
That is common. The recap still reduces misunderstandings and gives you a clean thread to follow up from later. Treat silence as "not blocked" unless a client action is required.

Related reading

Keep exploring: these pages go deeper on the feature set and the core Gmail CRM workflow.