What makes a multithreading email worth sending?
There's one phrase I won't send to a buyer: "just checking in." An email like that takes a minute of someone's day and gives them nothing back, and after a few of them, people learn to skip your name in their inbox.
A multithreading email has it even harder, because you're often writing to someone who never asked to hear from you. A VP your champion mentioned once. A skeptic who sat quiet through the demo. A legal team that doesn't know your deal exists yet. So every email below is built for one moment in the deal, and for something that reader wants to know.
If you're after the strategy (who belongs in the buying group, when to bring each person in, and how to keep your champion on your side), start with how to multithread and navigate dysfunctional buying groups. Which leaves this page for the emails themselves, grouped by when you'd send them. Most of them open on the reader's priority and keep your champion in the loop, and the ask at the end is usually for feedback, the way an internal email would ask (there's more on that in how to write forwardable emails).
Champion emails
Two emails for when your champion is engaged, and you need them to carry the deal to someone you can't reach yet.
1. The "Forwardable" Follow-Up. Send it after a strong champion call, when they need to loop in a decision-maker or budget holder. It opens with a company-wide initiative, uses a trigger phrase they already know, stirs up emotion with visual language, creates tension through a challenge, and matches the ask to the decider's job. The forwardable email guide breaks this one down line by line.
Subject: [Internal Project Name]
[Prospect], you mentioned your team (especially [Key Contact]) is working on [big initiative].
The goal is "[internal trigger phrase]", ideally [measurable outcome].
To make that happen, though, you need to [remove this problem / specific roadblock].
So we built out a shortlist of ways [your company] can help, attached here.
Guessing [Key Contact] might want to weigh in?
2. The "Idea" Follow-Up. For the quiet stretch mid-cycle. Recall a topic from your last conversation, tie it to a tool or idea, confirm it's still a priority, and offer proof the idea helps. It's the email that helps them do their job today, whether or not they ever buy.
Executive emails
Six emails for executives, from the first cold outreach to a concern you need to raise mid-funnel, each one written so the exec can forward it to their own team.
3. Executive: Outbound. Cold outreach when you've spotted a strategic shift in their business. Name the shift first, then the two approaches their team is probably weighing.
Subject: [2-3 words on their internal priority]
[Executive], with [significant shift or change in their business] happening right now:
I'm guessing [what the prospect needs to do, to avoid a negative outcome] is a focus.
Typically, [related business unit] is considering either [first approach], or [second approach].
So we let teams like [customer reference] [unlock a positive outcome].
Worth exploring with your team?
4. Executive: Inbound. A lead came in through someone lower in the org. Loop the exec in early, and let them know you're already working with their team.
5. Executive: Expand the Thread. A reply to your first exec email, bringing in another business unit hit by the same shift: "Which often means [how an executive-level priority impacts other business units]. Is this a focus for them? If so, I'll loop them in for feedback, too."
6. Executive: Post-Discovery Update. After your first real discovery call, share one surprising finding, link your exec summary, and pull them toward the next milestone.
Subject: Update, [Deal Focus]
[Executive], we're making good progress exploring [priority area].
Surprisingly, [nonobvious, interesting finding or discovery you've made with their team].
Summary here [link to your exec summary].
We have [activity] planned for next week, is that something you'd want to weigh in on?
7. Executive: Exec Match, Mid-Funnel. Use a shared interest or concern to put your leadership in front of theirs.
8. Executive: Troubleshooting, Mid-Funnel. Something feels off, so take it straight to the exec, framed as a concern about the project: "I'm a little concerned we're [not taking account of x / not aligned on y / missing other areas]. Let me know your availability for us to discuss?"
Those last two ask for time on purpose, by the way. Getting your leadership in front of theirs, or raising a concern before it costs the deal, is worth a meeting.
Skeptics and new contacts
Four emails for the people who aren't in the deal yet, and the ones who are in it and quietly against it. Tough crowd, but skeptics always hold more power than advocates, so they're worth the extra email.
9. The "Soft Loop." Someone should be in the deal, and you have no relationship yet. The easy out at the end is what makes a yes more likely.
Subject: [Internal Priority]
[New Contact], I was hoping to invite you into a conversation about [internal priority] with the [business unit] team next week.
Here's the [agenda]:
Would it make sense for you to weigh in on this?
If this doesn't sound relevant for you now, all good ([their business unit] just tends to be closest to this topic at first).
10. Engaging the Skeptic. Someone has expressed doubt, or is quietly blocking. Go direct, and make the whole email about their concern.
Subject: [Priority Area], feedback
[Skeptic Name]: [Champion Name]'s team is evaluating [your approach] for [initiative].
Sounds like you might have a different take on [specific concern or competing priority]:
Would you be open to sharing that?
Hoping to understand more what you're seeing, that I've missed.
Either way, very much appreciate the callout,
11. The "Your Name Came Up" Warm Intro. Your champion mentioned someone, so use the champion's name to open the door.
12. Cross-Department Expansion. You've landed in one department and see the same problem in another. Lead with the work you're already doing there, which is all the proof you need.
When a thread goes quiet
Two emails for when someone who should be in the deal has gone dark, or never really showed up.
13. Single-Threaded Follow-Up After a Group Demo. You ran a group demo, and you only have one real contact. Use the attendee list before the deal goes dark.
Subject: Resource, [Demo Topic]
[Attendee Name], great to meet you in [Champion Name]'s session on [topic] yesterday.
You asked about [specific question or comment they made], which comes up a lot with our teams working on [related challenge].
I pulled together [a resource / a quick take / a short example] that might help: [link].
Happy to dig in more if relevant to what your team's working on?
14. Re-Engaging a Stalled Thread. A contact you'd engaged has gone dark, so lead with something new: "Since last we spoke, we've been working with [Champion] on [initiative]. One thing that came up: [surprising insight or finding relevant to this contact's role]."
Emails your champion sends
Three emails you write for your champion to send to procurement, legal, and security, with the context already baked in so they don't have to rewrite your work.
15. Procurement, Pricing Review. Your champion needs procurement to review your pricing options. It recaps the partnership in a line, ties it to the executive's project, lays out the options, and names the date you're working to finalize by.
16. Legal, MSA Review. Gives your champion a reason to nudge legal, the internal priority plus the deadline, in a tone legal won't mind getting.
Subject: [Your Company], MSA Review: Timeline Update
Hi [Legal Contact],
Checking on our timing to finalize our review of [document type: MSA / SOW / etc.] from [Your Company], attached.
We're working to finalize our partnership by [target date], to keep on track with [internal priority], and move from [core issue] to [outcome].
Could you send over an update with any redlines, or questions on terms by [deadline]?
Thanks so much,
[Champion's name]
17. Security / IT, Review Status. Security is the bottleneck, so your champion sends the status request with the contacts, services, and milestones pre-loaded.
Won't these read like templates?
They will, if you fill the brackets with things that didn't happen. But every bracket should hold something the buyer actually said, shared, or worried about, and if you can't fill one honestly yet, you're writing too early.
So before any of these goes out, I run it through the same test I use for every follow-up:
- Am I introducing new information? If it's only a check-in, and they didn't ask for a reminder, it doesn't go.
- Would it be weird for another prospect to read it? It should be. If it could go to anyone, the only excuse is a sales cycle under 30 days, and these deals aren't that.
- Am I asking for feedback, in whatever way's easiest for them? Or am I trying to force 30 minutes onto their calendar? (Emails #7 and #8 are the exceptions above.)
- Did I keep it short? Re-read it, and cut the fluff.
Your move this week
Pick your biggest open deal and look at who's on the CRM record but has never replied to you. Choose the moment above that matches where each person is, write that one email, and give your champion a heads-up before you send it.