Multithreading

Most reps know they should multithread. Ask why a deal is still single-threaded and the answer is almost never that they could not find the other stakeholders. It is that their champion asked them not to.

Definition

Multithreading is the practice of building and maintaining active relationships with several members of a buying group in parallel, rather than routing a deal through one contact. It is not the same thing as knowing who those people are. Buying committee mapping tells you the seats and who fills them. Multithreading is what you do about it over the following weeks, while the deal is live, the politics are real, and somebody has an interest in you not doing it.

The distinction matters because teams routinely declare victory at the mapping stage. A complete org chart with one active conversation on it is still a single-threaded deal.

Why it matters

Gartner puts the modern buying group at five to 11 stakeholders, drawn from an average of five business functions. The same research finds that buyers spend roughly 17 percent of the purchase journey with suppliers at all, and that 17 percent is split across every vendor in the evaluation. Meet three vendors and any one of them gets about 5 percent of the buyer's total attention.

Read those two numbers together and the case makes itself. You have a very small amount of access, and it has to be spread across a lot of people who will decide without you in the room. A rep who spends all of it on one enthusiastic contact has not built a relationship with the account. They have built a relationship with a person who will be outvoted.

The effect is measurable. In Litera's deployment, accounts with six or more buying group members engaged showed a 38 percent lift in win rate against accounts without that coverage, alongside 2.4 times more coverage than CRM-managed contact lists were producing and 73 percent of stale contacts surfaced as no longer valid.

The champion problem

This is the real blocker, and most advice skips it. Your champion says some version of "let me handle the internal side." The rep hears cooperation and stops. What the champion actually means is one of four things, and each one needs a different response.

They are protecting their credit. They found you, they want the internal win. This is the easiest case and the most common. The answer is to make the threading visibly theirs: every new conversation is introduced by them, positioned as them bringing in the right people, and you say so out loud in front of their leadership.

They are protecting you from a known skeptic. Somebody senior has already pushed back and your champion does not want you walking into it unprepared. This is genuinely useful information being withheld. Do not ask whether you can talk to more people. Ask who has concerns and what they are, then ask to address them directly. Framed that way, most champions hand over the name.

They do not have the access they implied. They cannot get you to the economic buyer because they cannot get to the economic buyer either. This is the case worth finding out about fastest, because every week you spend waiting is a week the deal is not really progressing. Test it with a small, specific ask rather than a general one.

They are not your champion. They like talking to you, they are not spending capital for you. The tell is that they will discuss the product indefinitely and will not introduce you to anyone. A champion who cannot name what they personally get from this purchase is a coach at best.

The ask that works across all four is narrow and gives them control:

"You know this better than I do. Who else is going to have an opinion on this, and which of them would you want in the room before we go further? Happy for you to set it up however makes sense."

It asks about people, not permission. It concedes that they run the process. And it is very hard to answer with "nobody", which is the answer you are really testing for.

The order you thread in

Threading everyone at once reads as panic and puts your champion on the defensive. Sequence it by political cost, lowest first.

1. The user or technical evaluator. Cheapest conversation to ask for and the easiest to justify, because it is framed as making the evaluation accurate rather than as selling. It also gives you ground truth on whether the problem is as your champion described it.

2. The economic buyer. The highest-value thread and the one most deals never open. It needs a reason that is worth their time, which is almost never a demo. A business case they are already arguing for internally is the reason. Go too early with nothing to say and you spend the one meeting you get.

3. Security, legal and procurement. Timing-driven rather than value-driven. These threads should open ahead of when they are needed, because they are the ones that eat weeks at the end of a quarter. A deal that clears security review in parallel rather than in sequence closes materially sooner.

4. The skeptic. Deliberately, and earlier than is comfortable. Gartner's finding that 74 percent of buying teams show unhealthy conflict during the decision is the argument for this: the disagreement is happening whether or not you are there for it. A skeptic you have met can be answered. A skeptic you have never met just wins the room when you leave it.

Getting the order wrong is expensive in a specific way. Going to the economic buyer first, without the champion, converts a supportive contact into an obstacle, and you rarely get them back.

When your champion will not help

Sometimes the answer really is no. There is an escalation ladder, and the rule that governs all of it is that you never go around someone silently. Tell them you are doing it, and why, before you do.

Lateral first. A peer of your champion in an adjacent function, reached on a pretext that has nothing to do with the deal: a shared user group, a webinar, a question about how their team handles the same problem.

Executive to executive. Your VP or CEO to theirs. This is not a rep motion and should not be attempted as one. It works because it is peer-level, and it fails when it reads as a rep's escalation wearing a borrowed title.

A warm path from outside the deal entirely. Someone in your network who already knows the person you cannot reach: a customer, an investor, a board member, a partner, a former colleague. This is the only route on the ladder that does not spend any of your champion's capital, because it does not touch them at all.

Warm expansion beats cold expansion

Most threading advice quietly assumes you will cold email the rest of the committee. Consider what that actually looks like from the other side: an unsolicited note from a vendor currently in evaluation, to a senior executive who has never heard of you, about a purchase they have not been briefed on. It is the weakest move available and it can damage the thread you already have, because it gets forwarded to your champion.

The alternative is to reach each seat through someone who already has the relationship. Executive relationship management covers the senior end of this, and customer-sourced pipeline covers the case where the route runs through an existing customer. The practical version: before sending anything cold to a committee member, check whether anyone across your team, customers, investors or partners can reach them. On enterprise accounts the answer is yes more often than reps assume, because nobody has ever looked.

Threads decay

A thread is not a contact record. It is an active relationship, and it goes cold on a predictable schedule if nothing feeds it.

Users and evaluators need a reason to talk every two to three weeks, and the reason has to be theirs rather than yours. Economic buyers need far less contact but each touch has to carry something they can use internally. Security and procurement threads go dormant by design and should be reopened on a date, not on a feeling.

The bigger decay problem is people leaving. Litera surfaced 73 percent of their CRM contacts as stale. On a committee of eight, tracked over a nine-month enterprise cycle, assume at least one seat changes hands. A thread you have not touched since the person moved is not a thread, and the CRM will not tell you, because the CRM believes whatever it was told last.

What to measure

Counting contacts on the opportunity measures data entry, not coverage. Four numbers are worth tracking, and they belong alongside the rest of your deal health signals.

Coverage. Seats with an active thread, against seats the deal needs. Expressed as a fraction, so three of seven reads honestly and seven contacts does not.

Reciprocity. How many of those threads have replied without being chased in the last thirty days. This is the single most predictive of the four and the one most teams do not look at.

Recency. Days since the last inbound from each seat. Inbound, specifically. Outbound measures your activity, not their interest.

Level. The most senior seat with a live thread. A deal with six threads that all sit below director level is broad and shallow, which fails in a different way from single-threaded but fails just the same.

What fails

The same email to everyone. Committee members talk. Identical outreach signals that you have not understood what any of them individually care about.

Threading only downward. Adding users is easy, which is exactly why it is where reps stop. Downward threads rarely change an outcome that is decided above them.

Counting CRM contacts as threads. Someone who attended one demo eight weeks ago is a name. Coverage reporting built on contact counts will tell you a deal is healthy right up until it is lost.

Threading after the deal stalls. The moment a deal goes quiet is the worst possible moment to introduce yourself to five new people. It reads as exactly what it is. Threads opened while things are going well are the ones available to you when they are not.

The short version

Mapping a committee is a research task and it takes an afternoon. Multithreading is a political task and it runs the length of the deal. The constraint is almost never information about who the stakeholders are. It is access, and the willingness to ask your champion a question whose answer you may not like.