Template

Product launch — email #2 (medium)

When to use

Use when you want to describe the week-1 workflow in practical steps.

Product launch — email #2 (medium)

product_launch

cold

enablement

Subject: A simple post-launch workflow to improve {{metric}}

Hi {{name}} — after a launch, outbound usually becomes a “do more with less time” problem.

Teams that win the first 30 days post-launch do three things consistently:
1) decide what triggers count as “why now” (launch, partnerships, hiring, displacement)
2) prioritize accounts daily instead of running a backlog
3) standardize first-touch messaging so the team doesn’t drift

If {{company}} is pushing {{initiative}} right now, I can share the exact checklist + copy pattern we use: a one-line why-now, one concrete next step, and tokens ({{company}}, {{trigger_event}}, {{initiative}}) so it stays truthful.

Open to a quick 15-minute walkthrough this week?

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).