Multi-threading a deal means building working relationships with several people at the buyer, each with their own reason to want the project. The account executive does it, with the manager checking it in the weekly deal review. Done early, it adds a few conversations over two or three weeks. Done late, it is usually a rescue.
A single-threaded deal depends on one person staying in the job, staying interested and winning every internal argument on the seller's behalf. That is a lot to ask of anyone, and it is a common reason a late-stage deal goes quiet. This is one of the gaps covered in our guide to deal coaching.
What multi-threading a deal means
A thread is a person at the buyer who has described the problem in their own words and has a reason to want it solved. A name on a meeting invite is a contact. Five contacts and one thread is still a single-threaded deal.
- Owns the problemDay to day
- Signs
- Will use what you sell
- Budget or team affected
- GatekeepersIT, security, procurement, legal
- Owns the problemDay to day
- Signs
- Will use what you sell
- Budget or team affected
- GatekeepersIT, security, procurement, legal
The test matters because a CRM contact count looks healthy long before the deal is. The person most likely to stop a deal is often one the seller has never met, such as a department head who rarely appears on the stakeholder map. The cure is finding those people and hearing the problem from each of them.
How to multi-thread a deal in seven steps
Step 1. Map who you know, by what they said
Do: list every person at the buyer you have spoken to. For each one, write their role, the last thing they said about the problem (a quote), and what they lose if the project stalls.
Good looks like: each row has a quote. A row with no quote is a contact, and the rep should mark it that way.
Step 2. Find the missing seats
Do: check the map against the seats most deals need: the person who owns the problem day to day, the person who signs, the people who will use what you sell, anyone whose budget or team is affected, and the gatekeepers who can slow it (IT, security, procurement, legal).
Good looks like: a short list of seats with no thread, ranked by which one could stop the deal soonest. Usually that is the signer or the person who loses something.
Step 3. Ask the champion for help
Say: "Who else on your side will be asked to defend this, and how can we prepare them together?" Or: "If this went to your CFO tomorrow, what would they ask first, and who would they ask?"
Do: make the champion the person who opens the doors. Ask for introductions they are comfortable making, and offer to prepare material they can use.
Good looks like: the champion names people and offers introductions. If they refuse every one, that is evidence about the champion and goes into the deal review.
Step 4. Give each new person a reason to meet
Do: for each name, write one sentence on what that person cares about, in their terms. The finance lead cares about the cost of the problem and the cost of the fix. The operations lead cares about disruption. IT cares about what it touches.
Say (in the intro request): "Casey mentioned you'll be asked about the rollout. Could we take 20 minutes so you can hear the plan and tell us what would worry you?"
Good looks like: an invitation about their concern. A request to "show you a demo" gives most people no reason to come.
Step 5. Run the first conversation as discovery
Do: ask each new person to describe the problem from where they sit and what it costs them. Listen for differences from the champion's version.
Good looks like: a quote from that person, in their words, and one thing they need to see before they would support the project. Now they are a thread.
Step 6. Connect the threads in one plan
Do: put what each person said into the shared plan for the deal. If there is a mutual action plan, add their steps with their names. Our guide to building a mutual action plan covers the format.
Good looks like: people at the buyer own steps in the plan, and the champion can see that others are now carrying part of the case.
Step 7. Check the threads every week
Do: in the weekly deal review, ask the rep to name each thread and the last thing that person said. A thread that has gone quiet for three weeks gets a conversation planned.
Good looks like: the rep can answer from memory, with dates.
A worked example (illustrative)
The account, people and figures are fictional.
The deal. Riley is selling to Brisley Manufacturing, 1,100 employees. Riley's contact is Casey, Plant Operations Manager. CRM stage: Solution agreed. Casey has been on four calls.
Step 1. Riley's map has three names: Casey (quote: "unplanned downtime is killing our output, about nine hours a month per line"), Avery from IT (on one call, said nothing about the problem) and a procurement email address. That is one thread, plus a contact and an inbox.
Step 2. Missing seats: the person who signs (Casey says it is the COO, Quinn), the maintenance lead whose team will use the system, and IT, who was present but never engaged.
Step 3. Riley asks Casey: "When this reaches Quinn, what will Quinn ask first?" Casey: "Whether maintenance will use it at all. They killed the last tool." That is new and important. Riley asks if Casey would make an introduction to the maintenance lead, Rowan. Casey agrees.
Step 4. Intro request to Rowan: "Casey mentioned your team had a rough time with the last system. Could we take 20 minutes so you can tell us what went wrong and what would have to be different?"
Step 5. Rowan says the last tool needed data entry the technicians never had time for. Rowan wants alerts on a phone. Riley writes the words down. Rowan is now a thread, and the reason the last deal died is on the table.
Step 6. The mutual action plan gets a new step: Rowan's team trials alerts on one line for two weeks, owned by Rowan. Casey forwards the plan to Quinn with Rowan's step in it.
Step 7. Next deal review, Riley names three threads with quotes: Casey, Rowan and, after Casey's forward, a one-line reply from Quinn asking about the trial results.
Where it goes wrong
Going around the champion. The rep emails the CFO directly without telling the champion. The champion feels undermined, and the rep loses the one thread they had. Fix: ask the champion first, every time, and make them the person who opens the door.
Counting contacts. The rep reports "six stakeholders engaged" because six people were on a calendar invite. Fix: use the thread test. A thread has a quote.
The same pitch to everyone. Every new person gets the champion's demo. Finance hears features; maintenance hears ROI. Fix: step 4, one reason per person, in their terms.
Threading too late. The rep tries to add people once the deal is in procurement. By then the new people are reviewers, and reviewers look for reasons to say no. Fix: start step 2 as soon as the problem has a number on it.
Executive outreach without a reason. A cold email to the COO "to introduce myself" is ignored or forwarded back to the champion. Fix: reach the executive through the champion, with a question the executive cares about.
Checking every deal's threads every week
Step 7 is the step that slips. A manager running weekly reviews can check threads on the one or two deals they review per rep. The rest of the book goes unchecked until a deal goes quiet, and by then the champion may be the one person left to call.
Our AI sales experts run that check as a call. The rep brings the deal to Caty and talks it through; she asks who the rep has heard from and what each person said, flags a deal with one thread, and plans the conversation with the champion that opens the next door, in the team's methodology. Typing works as a fallback. The manager gets the read across the team from Bryce, who coaches the managers.
If the deal you are worried about already has one thread and a quiet champion, it is a stalled deal as much as a thin one: how to coach a stalled deal picks it up from there. To work through a single-threaded deal of your own, talk to us.
FAQ
What does multi-threading mean in sales?
Multi-threading means having working relationships with several people at the buyer, each of whom has described the problem in their own words and has a reason to want it solved. It reduces the risk that one person leaving, changing priorities or losing an internal argument ends the deal.
How many people should you be talking to in a deal?
Enough to cover the seats that can stop the deal: the problem owner, the signer, the main users, anyone whose budget or team is affected and the gatekeepers. The number depends on the deal. Count threads with a quote, and ignore names on an invite.
How do you multi-thread without going around your champion?
Ask the champion for help first. Ask who else will be asked to defend the project and how you can prepare them together. Make the champion the person who opens each door, offer material they can use, and keep them informed of every new conversation.
When should you start multi-threading a deal?
As soon as the buyer has put a number on the problem, usually during discovery. People added early help shape the plan. People added in procurement arrive as reviewers and tend to look for reasons to say no, which is why late multi-threading is mostly a rescue.
What is a single-threaded deal?
A single-threaded deal is one where the seller has a working relationship with only one person at the buyer. Every message and every decision runs through that person. It is fragile because the deal depends on one person's job, attention and influence.
Can AI help with multi-threading?
Yes, AI can map the contacts on a deal and flag deals where too few people at the buyer are involved. With our AI sales experts, the rep talks the deal through on a call and the expert checks who has said what about the problem, flags single-threaded deals and plans the next conversation with the champion. The manager sees the read across the team.