Why one contact is not enough
A single-threaded deal is one where all your information and influence run through one person. It feels efficient. They are responsive, they understand the problem, and the conversation is easy. Then they take a new job, or their priorities shift, or they walk into a room with four colleagues and cannot make the case alone.
The scale of the problem is easy to underestimate, because you only ever see your side of it.
Read those two together and the picture is clear. You are usually talking to one member of a group that is larger than you think, and that group is probably arguing. Your champion is not just relaying your message, they are fighting for it in a room where three other people have their own research and their own priorities.
The rule this article follows
Your champion cannot win an argument you have not equipped them for, in a room you are not in, against objections you have never heard. Multi-threading is how you find out what those objections are.
Who you actually need
Not everybody. Three roles cover most of the risk.
| Role | What they care about | What happens if you skip them |
|---|---|---|
| The person with the problem | Whether it actually gets solved | Nothing. This is usually your champion |
| The person who signs | Cost, risk, and what else it competes with | Deal stalls at proposal with no explanation |
| The person who has to use it | Disruption, effort, whether it makes their week worse | Quiet resistance that surfaces after purchase |
| The gatekeeper, if there is one | Security, legal, procurement, compliance | A four week delay nobody warned you about |
The third row is the one small teams most often miss. A deal can be approved by a budget holder and then die because the people expected to change how they work were never consulted and have no reason to cooperate.
How to widen a deal without going around anyone
Openness is the whole technique. Done transparently it is ordinary; done secretly it ends deals.
Ask on the first call who else is affected
Not "who is the decision maker", which sounds like you are trying to route around them. Ask who else will feel this, and who has to agree before something like this goes ahead.
Ask it early, when it is a neutral question about their organisation rather than a manoeuvre late in a deal.
Call oneAsk about impact, not authorityRequest the introduction with a reason for them
"Would it help if I walked your ops lead through how the migration works, so you are not the one fielding those questions?" gives your champion a benefit rather than a favour to grant.
People introduce you when the introduction makes their own life easier, not when you want it.
Frame it as helpGive each person something for their own role
The finance contact needs the commercial shape. The person who will use it needs to know what changes on a Tuesday. Sending everyone the same deck wastes the access you just earned.
One page each, aimed at their concern, does more than a shared document nobody reads.
Different page per personKeep the champion informed, always
Copy them, or tell them afterwards. "I sent Priya the security summary, here it is for you too."
The moment a champion feels worked around, you have converted your strongest advocate into an obstacle. This rule is not optional.
Never a surpriseRecord who you have actually spoken to
On the deal record, with their role. Not "met the team" but named people and what each one cares about.
This is what makes single-threading visible in a [weekly pipeline review](/blog/weekly-pipeline-review) rather than a surprise in month three.
Names on the record
Arming the champion for the room you are not in
Most B2B deals are decided in a meeting you do not attend. What survives that meeting is not your pitch, it is whatever your champion can remember and repeat.
Give them a one page summary in their language: the problem in their words, what changes, the cost, and the answer to the two objections you know are coming. Short enough to forward without editing.
Then ask the question most salespeople skip: "When you take this internally, what is the hardest question you will get?" Their answer tells you exactly what the internal argument is, and it is usually not what you would have guessed. Handle that objection in the document.
Where price is the recurring objection, our guide to handling price objections without discounting covers what is usually underneath it, which is frequently a value framing problem rather than a number problem.
Signs a deal is still single-threaded
Worth checking against every open deal above a threshold you set:
- You have one email address for the whole account
- You have never heard a second person's opinion, only your champion's report of it
- You do not know who signs, or you are guessing
- Meetings are always one to one
- You cannot name a single objection anyone raised internally
- Your champion says "leave it with me" and nothing visible happens
Any three of those together and the deal is one resignation away from disappearing. That is also the most common story behind a deal that goes silent after a strong start: the champion took it internally, it did not survive the room, and nobody wanted to deliver the news.
Multi-threading is not a technique for large enterprise deals only. In a five person company buying software, there are still usually three opinions that matter, and knowing all three is the difference between a deal you can forecast and one you are hoping about. Keeping those contacts and what each of them said on the same record, as covered in CRM data hygiene, is what makes the difference visible to everyone rather than living in one salesperson's head.
Frequently asked questions
- How many people should you know inside a deal?
- Three at minimum for anything above a small transaction: the person who feels the problem, the person who signs, and one person who has to live with the result. Gartner puts B2B buying groups at five to sixteen people, so three contacts is a floor rather than a target.
- Is multi-threading going behind your champion's back?
- Only if you hide it. Asking your champion who else should be involved, and telling them when you contact someone, is normal practice. Contacting people secretly is what damages trust and usually costs the deal.
- What if the champion refuses to introduce anyone?
- That is information. It can mean they lack internal standing, that the project is not real, or that they are protecting their position. Ask directly what is making the introduction difficult, and treat continued refusal as a risk to record on the deal.
- How do you multi-thread a small deal without being heavy-handed?
- Ask one question on the first call: who else will be affected by this. Then copy that person on the summary email with your champion's agreement. That is enough for most deals under a few thousand.
- What happens when your champion leaves?
- If they were your only contact, the deal usually restarts from zero or dies quietly. If two other people know what you are doing and why, it survives. Champion departure is the single most common cause of a well-qualified deal collapsing.