Template
Expansion — email #3 (breakup)
When to use
Use when expansion execution isn’t active.
Expansion — email #3 (breakup)
Email
expansion
email
breakup
Subject: Close the loop for {{company}}?
Hi {{name}} — quick close-the-loop.
I reached out because expansion into {{region_or_segment}} usually forces a decision on {{initiative}} and the messaging standard.
The common failure mode is predictable: teams keep the same targeting + copy while segments change, so reps either over-personalize (slow) or go generic (low conversion).
If that’s not a priority for {{company}} in the next {{timeframe}}, no problem — I can close this out.
If it is a priority, 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}} to align on what “good” looks like during expansion?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). |
| {{region_or_segment}} | Expansion target | Region or segment they’re expanding into. |