An AE on a client team I work with came to a pipeline review last quarter with what she called her cleanest deal of the year. $180K ACV, mid-market SaaS, champion who replied within an hour, three discovery calls done, demo locked, security review scheduled. The forecast call: 95% commit, expected close in 11 days.
The deal died on day 14. The champion got pulled into a reorg, his manager inherited the eval, and the new owner had never spoken to us. She did not even know our company name when our AE finally got her on the phone.
This is the most expensive failure mode in B2B sales right now, and almost every team I audit has the same problem. They build their forecast on a single relationship per account, and then act surprised when 40% of their late-stage pipeline evaporates.
This post is the playbook I use with my clients to fix it. The data, the role taxonomy, the actual HubSpot setup, and the rep behavior that gets coached.
What single-threading actually costs you
The numbers on this are not subtle.
Gartner research puts the average B2B buying group at 6 to 10 stakeholders. Some enterprise deals now run 11 to 15. If you are talking to one person, you are talking to between 10% and 17% of the people who actually decide.
A study from Aviso found that engaging multiple contacts on a deal increases the win rate by 42%. For deals over $50K ACV the lift is 130%. That is not a marginal tactical improvement. That is the difference between hitting the year and missing it.
And then the kicker. 40% of stalled deals die because the primary contact changed roles, left the company, or got reassigned. If your AE only knows one person at the account, every internal change at the customer is a coin flip on the deal.
Median B2B win rates dropped from 23% in 2022 to 19% in 2024. Buying groups got bigger, deal cycles got longer, and the rep behavior did not change. Most AEs still run one-relationship-per-account because that is what they were coached to do, and because building a second relationship feels like extra work for the same commission.
It is not extra work. It is the work.
Why reps single-thread (the real reasons)
I have sat in enough deal reviews to know the excuses. None of them are good, but they are predictable.
The champion is great. They love us. They have all the info. Why would I go around them? This is the most common one, and it is fundamentally a misreading of the buyer side. A great champion is not the deal. A great champion is your translator inside the company. You still have to meet the people they are translating to.
I do not want to annoy the prospect by going over their head. Translation: the AE is afraid of damaging the one relationship they have. The fix is to never go around the champion. You go with them. Asking your champion to introduce you to their VP of Operations is not a betrayal, it is the entire point of having a champion.
The deal is too small to warrant 4 stakeholder calls. Sometimes true. If your ACV is $8K and the buying committee is the founder plus maybe a junior on the team, you are fine. But for any deal above $25K in mid-market and especially anything Series A/B and up, the buying group is bigger than your rep is acting like it is.
The champion said they would handle internal alignment. They will not. Nobody handles internal alignment for you. Buyers are not paid to sell your product internally. They have a day job.
The role taxonomy your CRM should track
If you do not have an explicit framework for who is who on a deal, your reps invent their own and it falls apart. Here is the taxonomy I deploy. Six roles, drawn from Challenger and MEDDIC, refined by what actually closes.
A few notes from running this in practice.
The champion and the mobilizer are not always the same person. Your champion can love you and still be politically incapable of moving a decision. CEB research on the Challenger Customer was explicit about this: mobilizers are 31% more likely to drive a buying group to a yes. Most reps are too busy enjoying the warmth of the champion to test whether the champion can actually push the deal forward.
The economic buyer is often two levels removed from the champion. On a $150K deal with a Director of Sales as champion, the economic buyer is usually the CRO or the CFO. Reps avoid going up because it feels uncomfortable. The discomfort is the job.
Procurement is treated like a final speed bump. It is not. If you engage procurement at week 3 instead of week 9, you find out about the standard MSA, the security questionnaire, and the budget cycle while you still have time to adjust. Most reps treat procurement like a tollbooth at the end of the journey, and then act surprised when the deal slips a quarter.
How to actually multithread (without being weird about it)
I am going to be specific here, because most multithreading advice is "talk to more people," which is useless.
The setup is a conversation with the champion, ideally in the first or second discovery call.
You: "To make sure we get this through your procurement and security process without surprises, who else should be involved as we move forward? Usually for a deal like this we end up working with someone on the IT side, the budget owner, and a few end users. Who fits those roles at your company?"
That is it. You are not asking permission. You are not going around them. You are stating that this is how it works for deals like this, and asking them to map their org for you. Champions who are real champions will give you names. Champions who are not real will deflect, and that is itself a signal.
From there, your sequence is straightforward.
The 15-minute economic buyer call is the highest-impact thing in this whole list, and the one most reps skip. The pitch to your champion is: "Before we send pricing, I want to spend 15 minutes with [exec] to confirm the success metrics they care about, so the proposal speaks directly to that. Would you join the call and make the intro?" Almost every champion says yes to this when framed as making their work easier.
If your champion blocks the exec intro, you do not have a real champion. You have a contact who likes you. Different thing.
The HubSpot setup that makes this enforceable
You can run multithreading on instinct, but it falls apart the moment the rep gets busy. The structural fix is in the CRM. Here is what I deploy.
Association labels on the contact-to-deal relationship. HubSpot supports this natively, no custom object needed. Create labels for: Champion, Economic Buyer, Technical Buyer, End User, Mobilizer, Procurement, Blocker. Make them required for any deal past discovery stage.
A required count check. Build a property on the deal called "Stakeholders engaged" that counts the number of contacts with association labels on the deal. Any deal moving past discovery without at least 3 labeled stakeholders gets flagged in pipeline review.
A Champion + EB rule. Any deal moving to proposal stage must have a Champion AND an Economic Buyer labeled, with at least one logged meeting or call against the EB contact. Build this as a deal stage entry criterion. If the EB has no meeting logged, the rep cannot move the stage. This is not bureaucracy. It is the most reliable single fix I deploy for late-stage slip rates.
A 14-day no-contact alert. If any labeled stakeholder on an active deal has had no email, call, or meeting in 14 days, the deal gets a "single-thread risk" flag. Reps see it on their dashboard. Managers see it in pipeline review.
Pipeline review cadence is where this comes together. The first question on every deal review I sit in on is no longer "what is the next step." It is "who is in the buying group, and when did you last talk to each of them." If the rep cannot answer this in 30 seconds, the deal is downgraded.
The deal is not the next step. The deal is the map of people moving toward yes.
Most pipeline reviews start with "what is the next step on this deal." That is the wrong opening question. Ask who is in the buying group, when each was last contacted, and what role they play. The next step falls out of that automatically.
A small case study
A client of ours, a Series B fintech with a 7-person AE team, ran with a 16% close rate on opportunities above $40K. We pulled the deal-loss data and found that 71% of the lost deals had only one stakeholder contact logged. The wins averaged 3.4 stakeholders per deal.
We deployed the role taxonomy in HubSpot, made Champion plus Economic Buyer required for proposal stage, and rebuilt the pipeline review template around the stakeholder map. We also did a half-day workshop on the exec intro ask, because that was the specific behavior reps avoided most.
Six months later the close rate on the same segment was 24%. The slip rate on late-stage deals dropped from 38% to 22%. The reps reported the work felt less anxious, because they were not building a forecast on a single thread that could snap at any moment.
The whole thing cost less than one quarter of one rep's quota miss.
Where multithreading goes wrong
A few failure patterns I see often, all of them fixable.
Bulk-adding fake stakeholders to clear the pipeline gate. Reps figure out the rule and start associating every contact at the company to the deal to clear the count. This is why I require a logged meeting against the Economic Buyer, not just an association. Activity-gated, not count-gated.
Champion-led intros that never happen. Champion agrees in the call to introduce you to the IT lead and then ghosts on it. The fix is to draft the intro email for the champion and ask them to forward it. Lowers their cognitive load. Conversion goes from about 30% to 80% in my experience.
Going too wide too fast. Some reps overcorrect and try to engage 6 stakeholders in the first 10 days. The buyer side sees this as desperation. The right pacing is one or two new stakeholders per call, with each connection rooted in a real reason ("for the security review," "for the rollout plan").
Multithreading and not synthesizing. You meet 4 people and now you have 4 different views of priorities. If you do not write up a single shared view ("here is what we heard, here is what we are proposing") and circulate it to all of them, the deal can stall on internal disagreement about what is being bought. A short mutual action plan in a shared doc is the fix.
Single-thread deals slipping through your pipeline?
We help B2B teams rebuild their HubSpot setup, deal stage gates, and rep coaching around how buyers actually buy. Book a 30-minute audit and we will show you the three changes that have the biggest impact on your specific pipeline.
Book an audit →What to do this week
If you read this and want to act on it before the quarter ends, here is the order I would do it in.
Pull your closed-lost deals from the last two quarters. Count the number of distinct contacts that had logged activity on each one. If the median is below 3, that is your problem. Now check your closed-won deals, do the same count. The gap between those two numbers is the size of your multithreading opportunity.
Set up the six association labels in HubSpot. Spend the 30 minutes doing it properly. Disposition them across your existing open pipeline. You will find some uncomfortable truths.
Add the Champion plus Economic Buyer requirement at the proposal stage. Even if you cannot enforce it with a hard gate, make it a manual question in every deal review.
Coach one specific behavior. The exec intro ask. Role play it with each rep. The single sentence: "Before we send pricing, I want to spend 15 minutes with [exec] to confirm the success metrics they care about." Reps practice that until it sounds natural.
That gets you 60% of the value. The rest is iteration. The rep team that builds this habit will outperform the team that does not, by margins that compound every quarter.
For a deeper look at how we set up the CRM and RevOps stack end to end, or how we automate the pipeline hygiene workflows that keep stakeholder data accurate, those pages cover the broader system this fits into. If you are mid-flight on a migration or a stack rebuild, the CRM implementation work and the go-to-market design pages are also useful.
FAQ
How many stakeholders should I have engaged on a typical B2B deal?
For deals under $25K, two is usually enough: a champion and an economic buyer. For deals between $25K and $100K, plan for four: champion, EB, technical buyer, and one end user. Above $100K, you should be tracking five to seven roles, including procurement. The Gartner buying group average is 6 to 10 people across the company, but you do not need to talk to every single one. You need to talk to the ones who can say no.
What if my champion refuses to introduce me to other people?
Then you do not have a champion. You have someone who likes you, which is different. A real champion benefits from the deal closing and will help you build the case internally. If they will not make warm intros, the deal is single-threaded by default, and you should weight it lower in your forecast. The most useful question to ask: "What would make it easier for you to introduce me to your VP of Operations?" If the answer is no useful answer, you have your signal.
Does multithreading work for transactional or SMB deals?
Less. For deals under $10K where the buyer is the founder or a single department head, the buying committee is small enough that one or two contacts is fine. Multithreading is most valuable in mid-market and enterprise, where buying groups are 5+ people and deal cycles are 60+ days. Below that, you spend more time managing the map than closing the deal.
How do I track multithreading in HubSpot without a custom object?
Use association labels on the contact-to-deal relationship. HubSpot supports this natively as of 2023 and it works on every Sales Hub tier. Create labels for Champion, Economic Buyer, Technical Buyer, End User, Mobilizer, and Procurement. Add a calculated property on the deal that counts the number of associations with any of these labels. Use that property in your pipeline reports.
How do I get my AEs to actually multithread instead of just adding contacts?
Two things. First, gate the deal stages on activity, not associations. Require a logged meeting or call against the Economic Buyer contact before the deal can move to proposal. Second, change the first question in your pipeline review from "what is the next step" to "who is in the buying group, when did you last speak to each of them, and what is each one waiting on." This changes the reps' attention from task completion to relationship maintenance, and that is the actual behavior change you want.