Template
Product launch — email follow-up #1 (value)
When to use
Day 2 follow-up; sends an artifact.
Product launch — email follow-up #1 (value)
Email
product_launch
email
followup
value
Subject: One-page post-launch outreach checklist
Hi {{name}} — following up with a quick artifact.
I can send a one-page “post-launch outreach” checklist that includes:
- how to write a truthful why-now tied to {{trigger_event}}
- how to pick accounts to contact (daily shortlist)
- 2 message patterns that improve {{metric}} without over-personalizing
- a simple “don’t send” rule so reps don’t invent context
If {{initiative}} is a priority for {{company}} this quarter, it should be useful.
If you want it, I can send it here — or if you’re open to a quick 12-minute call, I’ll tailor the checklist to the messaging standards you want post-launch. Which is easier?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. |
| {{trigger_event}} | Why now trigger | Funding, hiring spike, partnership, product launch, displacement, expansion. |
| {{initiative}} | Likely priority | One initiative tied to the trigger (pipeline, enablement, reporting, security, expansion). |
| {{metric}} | Target metric | One metric that matters (reply rate, meetings, cycle time, ramp time, pipeline coverage). |