B2B buying decisions involve five to eleven people, depending on deal size, and the number has been rising for a decade.
Single-threaded outbound ignores this. You find one plausible contact, work them, and the deal lives or dies on whether that person champions it internally, leaves, or turns out not to have the influence you assumed. A large share of stalled pipeline is a single-threading failure discovered late.
Multi-threading is the fix, and done carelessly it gets you blocked at the account level.
Who is actually in the room
Roles rather than titles, because titles vary wildly.
The economic buyer. Signs, or approves the budget. Frequently a level above whoever you first contacted.
The champion. Wants the problem solved and will argue for you internally. Usually feels the pain directly.
The user. Lives with the consequences daily. Their objection kills deals late and quietly.
The technical evaluator. Security, IT, data. Can veto without ever being in a sales conversation.
The blocker. Someone with a reason to prefer the status quo — they chose the incumbent, or they own the process you would replace.
Procurement. Enters late, cares about terms and precedent.
You are not contacting all six. You are identifying which two or three you need and which one you must not surprise.
The order that works
Sequencing matters more than coverage. Contacting everyone simultaneously is the mistake that gets accounts blocking your domain.
Start one level below the economic buyer. Senior enough to have a view, close enough to the problem to feel it. Usually a director or head of function. They can bring the problem upward, which is far more effective than you bringing it downward.
Add the user or technical evaluator second, once the first contact has engaged or gone quiet after a few touches. A different message, aimed at what they specifically care about.
Go up to the economic buyer third, ideally with something to reference — a conversation with their team, a specific finding, a question their director raised.
Never open with procurement. They will route you to a process, and the process will be a form.
Two to three contacts per account is usually right. Past four you look like a scattergun, and the account starts comparing notes.
The rule that prevents the damage
Different message per person, genuinely different.
The failure mode is sending near-identical outreach to four people at one company. They talk. Somebody forwards it to somebody else. The account concludes it is being processed rather than approached, and now all four ignore you.
What differentiates a message properly:
| Role | What they care about | Opening angle |
|---|---|---|
| Economic buyer | Cost, risk, strategic fit | Outcome and comparable companies |
| Champion / director | Solving the problem, looking good | The specific problem and how others solved it |
| User | Daily friction | What changes in their week |
| Technical evaluator | Security, integration, maintenance | Architecture and what you will not break |
If you cannot write a genuinely different message for the second person, you do not need to contact them.
Referencing other contacts, carefully
There is a right and wrong way to acknowledge that you are speaking to their colleague.
Wrong: “I’ve also reached out to [name] and [name].” Reads as a campaign.
Right, once there has been a conversation: “I spoke with [name] last week about [topic] — they suggested you’d have a view on [specific thing].”
Right, when there has not: say nothing. Contact them independently with a message that stands on its own.
The dividing line is whether a real conversation happened. Referencing a conversation is normal business behaviour. Referencing the fact that you emailed someone else is admitting to a sequence.
Channel allocation
Multi-threading multiplies touches at one company, so total-touch discipline matters more here than anywhere.
Email for the primary contact and anyone senior. Least intrusive, easiest to ignore, which is appropriate.
LinkedIn for the second and third contacts. Lower commitment than email from a stranger, and visible enough that it reads as professional interest rather than a campaign.
Phone only for the champion or economic buyer, and only after some engagement. Calling four people at one company in a week is how you become a story in their team channel.
WhatsApp rarely, and only with someone who has already engaged — except in markets where it is normal business communication.
Set a total-touch ceiling per account, not per contact. Three contacts at four touches each is twelve touches at one company, which is plenty.
Suppression across the account
Non-obvious and important.
When one person at the account replies positively, the others should stop receiving automated sequences. The conversation has started; continuing to prospect their colleagues undermines it, and the champion will hear about it.
Equally, if one person says no on behalf of the company, that should suppress the account rather than just the contact. Contacting three more people after a clear rejection is what generates complaints.
This requires account-level rather than contact-level suppression, which many setups do not do by default. Worth checking.
Measuring it
Track at the account level, not the contact level.
- Accounts touched versus accounts engaged
- Contacts per engaged account — if it is consistently one, you are not really multi-threading
- Which role first replies, which tells you where to start next time
- Whether deals with three engaged contacts close at a higher rate than those with one
That last number is usually the one that settles internal argument about whether multi-threading is worth the effort. It generally is, and by a wide margin.
The short version
Buying committees have five to eleven people and single-threading is why good deals stall quietly.
Contact two to three people per account, starting one level below the economic buyer, adding the user or technical evaluator second and going upward third. Write genuinely different messages per role, or do not contact the second person.
Reference conversations that happened, never the fact that you emailed a colleague. Cap total touches at the account level, and suppress the whole account when one person replies or refuses.
Then measure at the account level, because contact-level metrics will not show you whether any of this worked.
Next: defining an ICP, or automating prospecting across four channels.
Frequently asked questions
What is multi-threading in sales?
Building relationships with several people inside one target account rather than relying on a single contact, so a deal does not depend on one person’s influence, priorities or continued employment.
How many people should you contact at a target account?
Two to three for most deals. Past four you look like a scattergun and the account starts comparing messages, which is how domains get blocked.
Who should you contact first at a target account?
One level below the economic buyer — usually a director or head of function. They feel the problem directly and can raise it upward, which works far better than approaching the top first.
How do you multi-thread without annoying the account?
Genuinely different messages per role, staggered rather than simultaneous, a total-touch ceiling at account level, and suppression that stops the others once one person replies.