Template
Expansion — email #1 (short)
When to use
Best when expansion implies new processes, segmentation, and messaging changes.
Expansion — email #1 (short)
Email
expansion
email
cold
why_now
Subject: Quick question on expansion into {{region_or_segment}}
Hi {{name}} — congrats on expanding into {{region_or_segment}}.
Expansion usually breaks one thing first: consistent execution. New reps/segments mean routing changes, messaging drift, and a growing backlog of “accounts we should contact.”
If {{initiative}} is a focus for {{company}} in the next {{timeframe}}, I can share a playbook: the signals to watch for your watchlist, a daily shortlist tied to {{metric}}, and tokenized drafts so reps can move fast without inventing context.
Worth a 12-minute call, or should I ask {{alt_owner}}?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). |
| {{alt_owner}} | Alternate owner | Likely owner: RevOps, Enablement, SDR leader, VP Sales, Partnerships, Product. |
| {{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). |
| {{region_or_segment}} | Expansion target | Region or segment they’re expanding into. |