Template
Partnership — email #1 (short)
When to use
Best when a partnership announcement implies new handoffs, routing, or enablement changes.
Partnership — email #1 (short)
Email
partnership
email
cold
rollout
Subject: Quick question on the {{partner}} rollout
Hi {{name}} — congrats on the {{partner}} announcement.
Partnership rollouts usually get stuck in one place: handoffs. The work is less about the press release and more about “who owns what,” “what gets reported,” and “how reps message it.”
If the rollout touches {{handoff}} between {{system_a}} and {{system_b}} for {{company}}, I can share a short rollout checklist and a tokenized draft that ties the rollout to a clear “why now” next step.
Worth a 12-minute call to compare notes, 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. |
| {{alt_owner}} | Alternate owner | Likely owner: RevOps, Enablement, SDR leader, VP Sales, Partnerships, Product. |
| {{partner}} | Partner name | The partner from the announcement. |
| {{handoff}} | Concrete handoff | Routing, reporting, onboarding, enablement, data sync. |
| {{system_a}} | System/process A | One side of the handoff. |
| {{system_b}} | System/process B | The other side of the handoff. |