Multithreading means running cold outreach to more than one contact at the same target company at the same time, instead of emailing a single champion and hoping they carry the deal internally. It's a response to a simple fact about B2B buying: most deals aren't decided by one person, and a single-threaded email that goes unanswered has no fallback path.
In practice, multithreading looks like identifying two to four relevant contacts at a target account — usually spanning different roles or seniority levels — and sequencing outreach to each of them, timed so the messages don't collide or look coordinated in a way that reads as impersonal. It's distinct from just emailing a bigger list at the same company with the same template; the point is deliberate coverage of the actual buying group, with each contact getting a message relevant to their specific stake in the decision.
According to research from Instantly analyzing enterprise buying patterns, the median B2B buying committee for deals above $50K includes 11.2 people, and the broader average across B2B purchases is around 13 stakeholders. Committee size scales with both deal size and company size:
| Deal value | Typical stakeholder count |
|---|---|
| Under $25K | 3-5 |
| $25K-$100K | 5-9 |
| $100K-$250K | 6-10 |
| $250K+ | 10+ |
The same data breaks it down by company size: organizations with 50-200 employees typically involve 5-7 stakeholders in a purchase decision, 200-1,000 employee companies involve 6-10, and companies above 1,000 employees involve 11-15. Technology purchases tend to pull in the largest committees of any category, sometimes around 25 people, while financial services deals typically involve 8-15 and manufacturing or healthcare purchases run smaller, around 6-10. Emailing one person at any of these accounts and treating silence as "no interest" ignores that the non-response might just mean the wrong person got the email, or the right person forwarded it to someone who never replied.
A reasonable starting split for most B2B accounts is one likely end-user or day-to-day owner of the problem, one manager or director-level person who would need to approve budget, and — for larger accounts — one more senior stakeholder (VP or above) who'd need to sign off on anything with real spend attached. Add the second and third contacts either from the start for accounts above a size threshold your ICP defines, or after the first contact goes quiet for a full sequence without a reply. Adding every contact simultaneously on day one at a smaller account can look excessive; staggering by a few days per contact tends to read as more natural.
The mistake that makes multithreading look like spam is sending the identical email to three people at the same company. Each contact should get a message angled to what they'd actually care about in the decision — an end-user cares about day-to-day friction the current approach creates, a director cares about the team-level or budget impact, and a VP cares about how it rolls up to a larger initiative or number they're accountable for. The underlying offer stays the same; the framing of why it matters to that specific person changes. If two contacts do compare notes internally, distinct framing reads as a company that understood their org rather than one blasting a list.
A workable pattern: start with the most likely champion (usually the end-user or a manager-level contact), and if there's no reply by the second touch in that sequence, bring in the second contact with a fresh angle rather than a forwarded thread. If a reply does come from either contact, pause outreach to the others at that account rather than continuing to cold-email people at a company you're now in an active conversation with — that's the point where multithreading should hand off to normal sales process. Tools that support account-level sequencing (pausing all other contacts at a company once one replies) make this easier to enforce than doing it manually across separate campaigns.
Running cold outreach to more than one relevant contact at the same target company at the same time, each with a message angled to their specific role in the buying decision, instead of relying on a single contact to carry the deal internally.
Two to four is a reasonable range for most B2B accounts — typically one end-user or day-to-day owner, one manager or director, and for larger accounts one more senior stakeholder who'd need to approve spend.
Only if every contact gets the identical email. Differentiating the framing per role — what an end-user cares about versus what a VP cares about — while keeping the underlying offer the same avoids that.
Pause outreach to the other contacts at that account and move into normal sales process with whoever replied first — continuing to cold-email people at a company you're already in conversation with undermines the multithreading approach.
Related guides
Written by
Scott Holmes
AI systems consultant based in Barrie, Ontario. Founder of Pinnacle Tech Projects. Has run multithreaded outreach campaigns reaching multiple stakeholders per account.
Answer four quick questions and get a tool recommendation for your setup.