Template
Expansion — email follow-up #1 (value)
When to use
Day 2 follow-up; artifact offer.
Expansion — email follow-up #1 (value)
Email
expansion
email
followup
value
Subject: One-page expansion execution checklist
Hi {{name}} — sharing a quick artifact.
I can send a one-page “expansion execution” checklist that covers:
- what signals to watch on target accounts (so timing stays real)
- how to prioritize daily during expansion
- how to keep messaging consistent (tokenized drafts) as segments change
- a simple “don’t send” rule when context is missing
If {{company}} is focusing on {{initiative}} while expanding into {{region_or_segment}}, it should help.
If you want it, I can send it here — or if you’re open to a quick 12-minute call, I’ll tailor it to how you’re measuring {{metric}} across segments. 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. |
| {{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). |
| {{region_or_segment}} | Expansion target | Region or segment they’re expanding into. |