.svg)
When to send — and what the email must accomplish
Send this note within 24 hours of verbal close or contract signature on a partner-sourced deal. Your goals are simple: acknowledge the partner’s role, confirm the outcome the customer expects, introduce your delivery owner, and lock a kickoff time. Resist the urge to sell again — the sale is done. Now you’re building trust and smoothing the handoff.
Use one CTA to reduce friction — a booking link or two time windows. If your partner will remain engaged post-sale, make that explicit and give them a role in the first meeting.
Anatomy of a clean partner-sourced introduction email
- Who you are — name, role, and why you’re the right contact.
- Gratitude and context — thank the partner and summarize what the customer purchased in a single line.
- Next step — the exact meeting you’re proposing and what will be decided there.
- Owners — who leads what on your side and the partner’s side.
- Practical details — data access, timelines, shared channel.
- One clear CTA — a calendar link or two options to choose from.
Aim for 90–130 words. You’re signaling control and clarity — not writing a novel.
Subject lines that work
- Welcome to [Product] — kickoff details inside
- Great to meet you via [Partner] — next steps
- [Partner] × [Your Company] — quick kickoff invite
- Your [Product] setup — 30-minute plan
Common mistakes to avoid
- Multiple CTAs. Ask for one thing — usually the kickoff time.
- Ignoring the partner after close. Keep them cc’d if they’ll be involved.
- Vague agendas. State decisions the kickoff will make — timeline, owners, success criteria.
- Overloading attachments. One link to a booking page or shared doc is enough.
Follow-up mini-snippets
Paste these as replies if there’s no response.
Nudge — 2 days
“Following up on kickoff times above. If next week’s better, I can send a one-page plan and hold two slots that fit your team.”
Value add — 5 days
“Sharing a one-pager your team can skim before kickoff — goals, timeline, and roles. Still good to connect [day/time]?”
Last call — 9 days
“Happy to pause if timing shifted. If you’d like, I can re-propose dates next month and keep [Partner] looped for updates.”
Pro tips for smoother partner-sourced handoffs
- Confirm the agreed success metric in writing — the one the partner and buyer used in evaluation.
- Assign one owner per milestone. Shared ownership often means no ownership.
- Create the shared channel before the kickoff and include the partner if they’ll support post-sale.
- Keep the partner visible through early wins — they helped land the deal; let them help cement adoption.
If you use Introw, you can drop this template into a shared partner sequence, trigger it automatically at stage Closed-Won for partner-sourced opportunities, and track replies and booked meetings in your CRM — no separate portal required. Introw can also generate the mutual action plan from your opportunity data and keep the partner cc’d via Slack or email so everyone stays aligned.
Download free version
Should I always cc the partner on the intro?
Yes, if they’ll stay involved in enablement, change management, or ongoing services. If their role ends at close, thank them in the first line, then move them to bcc after kickoff is booked.
What if procurement isn’t finished?
Acknowledge it and propose a planning call anyway. Make clear you’ll avoid any configuration that implies use until paperwork is complete.
How long should the kickoff be?
Thirty minutes is enough for smaller scopes. If you expect security or data access topics, schedule 45–60 minutes and invite the right technical owner from both sides.
