post_discovery_follow_up_email
Recap key points from a discovery call and set the next step to keep momentum toward a proposal. Choose from three routes: warm, interested but not ready, or send a proposal.
Instructions
Write the follow-up email sent after a productive discovery or intro call with a prospect — the email most freelancers either skip or fumble. Its job: confirm you listened, recap the key points so nothing gets lost, set the next step clearly, and keep the momentum toward a proposal. Distinct from discovery_call_no_show_email (for when they don't show) and client_followup (for chasing a sent proposal). Three routes: warm (engaged prospect, moving forward — default), interested_but_not_ready (good conversation but they need more time or internal buy-in — play the long game), send_proposal (they asked for one on the call — confirm it's coming and when). Required: contact_name, what_discussed (2-4 bullet points or a brief paragraph of what you covered on the call). Optional: next_steps (what you agreed to do next — e.g. 'send a proposal by Friday', 'schedule a follow-up in two weeks'; defaults to a warm but open close), your_service (what you do — helps personalise the recap line), timeline (their stated timeline or urgency — e.g. 'looking to start in July', 'hoping to launch before Q3'), route, your_name. Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contact_name | Yes | The prospect's first name | |
| what_discussed | Yes | The key points from the call — 2-4 bullets or a brief paragraph (e.g. 'their rebrand timeline, budget range of $5-8k, need for brand guidelines and logo, internal stakeholder review required before sign-off'). This becomes the recap section. | |
| next_steps | No | Optional: what was agreed as the next step (e.g. 'I'll send a proposal by Friday', 'you'll come back to me once you have internal sign-off', 'we'll speak again in two weeks'). If omitted, the email closes warmly without a hard next step. | |
| your_service | No | Optional: a short description of what you do — helps personalise the recap line (e.g. 'brand identity and packaging design', 'React development for SaaS products', 'copywriting for B2B tech companies'). If omitted, the email stays generic. | |
| timeline | No | Optional: the prospect's stated timeline or urgency (e.g. 'looking to start in July', 'hoping to launch before Q3', 'no fixed deadline yet'). If provided, the email acknowledges it. | |
| route | No | warm: engaged prospect, ready to move forward — default for most calls. interested_but_not_ready: good conversation but they need more time, budget approval, or internal buy-in. send_proposal: they asked for a proposal on the call — confirm it's on its way and when they'll have it. | |
| your_name | No | Optional: your name for the sign-off |