Template
Product launch — email #3 (breakup)
When to use
Use as a final touch when there is no response.
Product launch — email #3 (breakup)
Email
product_launch
email
breakup
Subject: Close the loop for {{company}}?
Hi {{name}} — closing the loop.
I reached out because immediately after a launch, teams often rework {{initiative}} and outbound messaging. The timing window is short, and the risk is sending generic “congrats” notes that don’t convert.
The teams that do well post-launch usually align on three things quickly:
- what counts as a real “why now” signal
- which accounts to prioritize first
- one message pattern that stays consistent across reps
If this isn’t a priority at {{company}} in the next {{timeframe}}, no problem — I can close this out.
If it is, would you prefer I send the one-page checklist + examples, or are you open to a quick 12-minute call with the owner for {{metric}}?Token glossary (this template)
| Token | Meaning | How to fill |
|---|---|---|
| {{company}} | Target account | Company name (or domain if you prefer). |
| {{name}} | Contact first name | First name only. |
| {{initiative}} | Likely priority | One initiative tied to the trigger (pipeline, enablement, reporting, security, expansion). |
| {{timeframe}} | Decision window | “30 days”, “this quarter”, “next 60 days”. |
| {{metric}} | Target metric | One metric that matters (reply rate, meetings, cycle time, ramp time, pipeline coverage). |