Skip to content
Guides6 min read

Send a Post-Discovery Call Recap Email With AI the Same Day

After a sales or discovery call, send a same-day recap that confirms decisions, surfaces open questions, and sets a mutual action plan—using ChatGPT, Google Docs, and Gmail.

By DoAIWork · November 13, 2026

Send a Post-Discovery Call Recap Email With AI the Same Day

Freelancers and micro-agencies often nail the pre-client call brief and still lose momentum after the discovery call. You hang up, switch to delivery work, and three days later the prospect asks, “So… what were we doing again?”

A post-discovery call recap is not a proposal and not a full scope document. It is a short email you send the same day (or within 24 hours) that:

  • Restates what you heard in their words
  • Lists explicit decisions and assumptions
  • Surfaces open questions that block pricing
  • Ends with a mutual action plan (who does what by when)

That email is your paper trail before you invest hours in a scope doc clients approve. It also filters polite tire-kickers early: if they will not confirm basics in writing, the full scope chase may not be worth it.

This playbook uses ChatGPT, Google Docs, and Gmail — no browser RPA, no fake “AI closes deals” promises. You send the email.

What belongs in the recap (and what does not)

Keep the recap to one screen on mobile. Include:

  1. Thanks + context (one sentence)
  2. Problem & success criteria (2–4 bullets, their language)
  3. In scope / out of scope for now (high level only)
  4. Constraints (budget band, deadline, stakeholders, tools they already pay for)
  5. Open questions (numbered — these drive your next message)
  6. Mutual action plan (table: owner, task, due date)

Do not attach pricing, legal terms, or a 12-page SOW. Those come after they confirm the recap is directionally right.

Step 1: Capture notes during the call (low friction)

Use the simplest capture that survives tab-switching:

  • A running Google Doc titled CALL-YYYY-MM-DD ClientName — raw
  • Or bullets in your pre-call brief doc — add a section LIVE NOTES before you dial

Rules while live:

  • Tag lines with [D] decision, [Q] question, [R] risk, [$$] budget hint
  • When they say “must have,” write it verbatim in quotes
  • Do not polish live; polish once, after you hang up

If you use Zoom or Meet recording, treat the transcript as optional input later, not a substitute for decisions you wrote down.

Step 2: Paste into ChatGPT with a structured prompt

Within 30 minutes of the call, paste raw notes only (plus your brief if you had one). Use this template:

You are an assistant to a freelance consultant writing a POST-DISCOVERY recap email.

Audience: the prospect who was on the call.
Tone: clear, warm, professional, no hype. Short paragraphs.

Input notes:
---
[paste raw notes]
---

Output:
1) Subject line (≤60 chars)
2) Email body in Markdown with sections:
   - What we heard
   - Decisions so far
   - Assumptions (label as assumptions)
   - Open questions (numbered)
   - Mutual action plan (Markdown table: Owner | Task | Due)
3) One sentence I should add if their budget was vague.

Rules:
- Never invent features they did not mention.
- Flag anything unclear as an open question instead of guessing.
- Due dates: propose business-day dates starting tomorrow unless notes say otherwise.

Review the draft for hallucinated integrations. ChatGPT loves to add “we will also set up SSO” when nobody said SSO.

Triage discovery call notes into decisions, questions, and next steps
Triage discovery call notes into decisions, questions, and next steps

Step 3: Polish in Google Docs (human gate)

Copy the Markdown into a Google Doc. This is your quality gate:

  • Fix names, product names, and numbers
  • Shorten adjectives; keep their phrasing for goals
  • Highlight assumptions in yellow — they should jump off the page
  • Add a single line: “Reply to confirm or correct by [date].”

Save as ClientName — Discovery recap — YYYY-MM-DD. Link this doc in your CRM or client folder.

Step 4: Send via Gmail (you press send)

Paste into Gmail. Subject from ChatGPT is usually fine; prefer concrete over clever:

  • Good: Recap: onboarding automation scope — next steps
  • Weak: Following up on our amazing chat!

In the first paragraph, say you are confirming understanding, not selling. End with the mutual action plan table copied cleanly (Gmail handles simple tables; if it breaks, use a bullet list with Owner / Task / Due).

Same-day send beats perfect send. A recap at 6 p.m. still beats silence until Friday.

Mutual action plan: keep it embarrassingly small

Prospects stall when the “next step” is vague. Three rows is enough:

OwnerTaskDue
ClientAnswer open questions 1–32 business days
YouDraft scope outline (not full SOW)3 business days after their reply
Both20-min alignment call if answers conflictwithin 1 week

Adjust dates to your real capacity. Under-promise the due column.

Step 5: What happens after the recap

When they confirm (even partially):

  1. Feed confirmed bullets into your scope-doc workflow
  2. If they ghost after two nudges, stop scope work — the recap already documented what was discussed
  3. If they disagree materially, schedule a short call only for the disputed rows, not a full re-discovery

Browse more guides for freelancers and SMBs when you are ready to productize this into templates.

End-to-end workflow

Loading diagram…

Copy-paste recap skeleton (if ChatGPT is down)

Subject: Recap — [project nickname] — next steps

Hi [Name],

Thanks for the time today. Here is my understanding so we stay aligned before I draft a detailed scope.

What we heard

  • …
  • …

Decisions so far

  • …

Assumptions (please correct anything wrong)

  • …

Open questions

  1. …
  2. …

Mutual action plan

OwnerTaskDue
You……
Me……

Reply by [date] to confirm or edit. Once aligned, I will send a scope outline for approval.

Best, [You]

Common mistakes

  • Recap = proposal. Pricing belongs after they confirm direction.
  • Waiting for the “perfect” transcript. Send bullets you trust.
  • No due dates. Without dates, mutual action plans are wish lists.
  • Skipping assumptions. Hidden assumptions cause scope fights later.

Quick checklist

  • Raw notes tagged D/Q/R during call
  • ChatGPT draft within 30 minutes
  • You verified facts in Google Docs
  • Gmail sent same day
  • Scope work scheduled only after explicit recap confirmation

You do not need a CRM to start. A folder, a doc, and a sent recap email beat another discovery call that repeats the same conversation.

Related guides