How do you coach reps on multithreading into target accounts?

Why This Happens — Diagnose Before You Coach

A rep who stays single-threaded is almost never lazy. Before you coach, figure out the root cause, because the fix differs completely:

• Skill — the rep doesn't know *how* to ask a champion for an intro, or how to write outreach to a CFO they've never met. This is the easiest to fix with scripts and reps.
• Will — the rep is afraid of "going around" their contact, scared of annoying the champion, or worried a senior stakeholder will expose a weak business case. This is the most common and needs confidence work, not just tactics.
• Knowledge — the rep genuinely doesn't know the org chart, the buying process, or who signs. They can't multithread into people they can't name.
• System / territory — your CRM, MEDDIC fields, and deal stages never *force* the question. If "number of contacts" is invisible in the pipeline review, reps optimize to the one relationship that feels safe.

Use this decision tree in the 1:1 to route from symptom to cause:

The Coaching Conversation

Run this as a GROW conversation (Goal, Reality, Options, Will) in your deal review or 1:1. Do not solve it for the rep — make them own the plan. Here are the verbatim questions.

Goal. Set the frame so multithreading is the rep's idea: > "Walk me through who has to say yes for this to close. If your one contact got promoted and left next week, would this deal survive?"

That last question does more work than any lecture. When they admit "no," you have buy-in.

Reality. Surface how thin the deal really is: > "Show me the buying committee. Who's the economic buyer, who's the champion, who could kill this, and who have we actually *talked* to versus *assumed*?"

Make them point at real names in the CRM. Anyone they can't name is a gap, not a contact.

Options. Generate the plays — don't hand them over: > "If you wanted to earn one more relationship before our next meeting, what are three different ways you could do it? Which feels lowest-risk to your champion?"

Then coach the champion-led intro, which is almost always the safest path. The verbatim ask to the champion: > "Sarah, you know this better than I do — to make sure we build something the whole team will defend in the budget review, who else should be in the room? Would you be comfortable introducing me, or would it land better coming from you first?"

That language frames multithreading as protecting the champion's win, not going around them. Reframe the fear directly: > "Going multithreaded isn't disloyal to your champion — it's the thing that makes *them* look good when they bring you a deal that's already aligned."

For a cold-to-warm exec, coach Command of the Message-style outreach tied to a business outcome, not a feature: > "Hi Mark — I work with Sarah's team on [outcome]. Before we get to a recommendation, I want to make sure it ladders up to what *you* care about this year. Worth 15 minutes so I don't waste the committee's time?"

Will. Lock commitment and a date: > "So by Thursday, you'll have asked Sarah for the intro to Mark and sent the outcome email to finance. What might get in the way, and what do you need from me?"

End every coaching conversation with a named person, a named play, and a date. Vague intent dies in the pipeline.

The Coaching Plan / Cadence

Multithreading is a habit, so coach it on a loop, not in a one-time talk. A simple 30/60/90 for a rep you're leveling up:

• Days 1–30: Every deal in the review must have a buying-committee map. You coach the *missing* stakeholder each week. Goal: every open opp names an economic buyer.
• Days 31–60: Rep runs the champion-intro script live in role-play, then on two real deals. You listen to the call in Gong or Chorus and coach the actual ask.
• Days 61–90: Rep self-diagnoses single-threaded deals before the review and brings the plan. You shift from directing to inspecting. Goal: contacts-per-opp trends up across the territory.

Drills & Role-Play

• Org-map drill (10 min). Give the rep a live deal and 5 minutes to draw the buying committee on a whiteboard — names, titles, role (champion / EB / blocker), and "talked to vs. assumed." Anything assumed becomes this week's action.
• The intro-ask role-play. You play the nervous champion who says "Why do you need to talk to my boss?" The rep must reframe it as protecting the champion. Run it three times until the language is smooth.
• Cold-exec outreach scorecard. Rep drafts the email to the economic buyer; score it on outcome-led opening, brevity, and a clear ask. Reject any opener that leads with the product.
• Call review. Pull a recent single-threaded call in Gong and ask: "Where could you have asked for one more name?" Mark the exact timestamp.
• Win/loss replay. Have the rep compare a won multithreaded deal to a lost single-threaded one. Let the pattern teach the lesson.

What to Measure

Coach to leading indicators, because win rate tells you too late:

• Contacts per opportunity (the headline metric — target 4+ on enterprise deals).
• Percentage of deals with a named economic buyer engaged, not just identified.
• Stakeholders added per week on active deals.
• Champion-intro requests made (the behavior you're actually coaching).
• Multithreaded vs. single-threaded win rate — Gong Labs research consistently shows deals with more engaged contacts close at materially higher rates and slip less.
• Behavior change over time: is the rep diagnosing single-threaded deals *before* you have to?

If contacts-per-opp climbs but win rate doesn't, your reps may be adding the *wrong* contacts — coach quality (economic buyer, blockers) over volume.

Common Mistakes Managers Make

• Coaching the deal, not the skill. "Go email the CFO" wins one deal. Teaching the rep *how to earn any second relationship* wins the next twenty.
• Rescuing the rep. Sending the exec email yourself, or jumping on every call, builds a rep who can't multithread without you. Make them run the play.
• No follow-through. You set an action, never inspect it, and the rep learns the plan was optional. Inspect every committed action by name and date.
• Treating fear as laziness. A rep who won't go multithreaded is usually scared, not lazy. Coaching tactics at a will problem doesn't work.
• One-size-fits-all coaching. Your top rep needs the org-map drill; a new SDR needs the verbatim script. Diagnose first.
• Letting the CRM stay silent. If your pipeline review never asks "how many contacts?", you've made single-threading invisible — and invisible behavior never changes.

The Multithreading Playbook: Three Specific Entry Points

Once you’ve diagnosed the root cause, give reps a concrete playbook with three reliable entry points into any target account. Coach them to pick the one that fits their champion’s personality and their own comfort level:

• The “Help Me Help You” Intro – Rep asks their champion: “To make sure I build the strongest case for your team, could you introduce me to [Title] so I can understand their priorities?” This frames the ask as protecting the champion’s project, not bypassing them.
• The “Parallel Path” Outreach – Rep sends a cold, value-first email to a different stakeholder (e.g., a technical buyer if the champion is economic) referencing a shared challenge but not mentioning the champion. This avoids putting the champion in an awkward spot while building a separate relationship.
• The “Event or Content Trigger” – Rep uses a recent trigger (a webinar, a competitor move, a product update) to reach a new stakeholder with a specific insight. For example: “Saw your team is expanding in APAC—here’s how we helped [similar company] reduce onboarding time by 30% there.”

Role-play all three in your next coaching session. Most reps only know one approach; giving them three dramatically increases their confidence to act.

How to Measure Multithreading Progress (Without Making It a “Gotcha”)

Avoid just asking “How many contacts do you have?”—that encourages reps to add low-value names. Instead, track three simple leading indicators in your CRM or coaching tool:

Coach reps to review these metrics weekly, not just at deal review. If a rep has 5 contacts but all are in the same department, coach them on how to cross into IT, finance, or operations. If the second contact takes 6 weeks, role-play the “parallel path” approach to accelerate it. This turns multithreading from a vague goal into a measurable habit.

FAQ

How many stakeholders should a rep multithread into? On transactional deals, two is often enough. On enterprise deals with a buying committee, coach for at least four engaged contacts — minimum the economic buyer, champion, technical evaluator, and one likely blocker. Quality beats raw count; an engaged economic buyer outweighs three junior users.

What if the champion blocks the rep from talking to anyone else? That's a yellow flag, not a green light to obey. Coach the rep to reframe: "To protect *your* recommendation in the budget review, who else should weigh in?" If the champion still gatekeeps hard, the deal is riskier than it looks — and that's a deal-qualification conversation, not just a multithreading one.

Is multithreading just for big enterprise deals? No. Even mid-market deals slip when the one contact goes quiet, gets reorged, or leaves. The rule scales down: any deal that can't survive losing its single contact is single-threaded and coachable.

How do I coach a rep who's afraid of annoying their contact? Address the will, not the tactic. Use the reframe that multithreading makes the champion look good, role-play the nervous-champion objection until the language is natural, and start them on a low-risk ask (a champion-led intro) before a cold exec reach. Confidence comes from reps, not pep talks.

Can AI tools help coach multithreading in 2027? Yes. Gong, Chorus, and Clari now flag single-threaded deals automatically and surface which stakeholders are missing from the conversation. Use those alerts to target your coaching, but the actual reframe and role-play still have to come from you — the tool finds the gap, the manager coaches the close.

When is multithreading not the real problem? When the deal lacks a business case entirely, when it's a wrong-fit account, or when the rep has a deeper qualification or activity issue. Adding contacts to a dead deal doesn't revive it. Diagnose with MEDDIC first; if there's no metric and no economic buyer who cares, that's a qualification fix, not a multithreading one.

Bottom Line

Make every rep show you the buying-committee map in every deal review, diagnose whether the gap is skill, will, or knowledge, and coach the verbatim champion-intro ask until it's a habit — then measure contacts per opportunity as your leading indicator. Single-threaded deals are the most predictable way to lose a quarter, and multithreading is the most coachable fix you own.

Related on PULSE

• [How do you coach an account manager to grow existing accounts?](/knowledge/cg0204)
• [How do you coach a BDR to research accounts before reaching out?](/knowledge/cg0202)
• [How do you coach a rep to research accounts before reaching out?](/knowledge/cg0028)
• [What coaching question would you use to challenge a rep who is stuck in a comfort zone with easy, low-value accounts?](/knowledge/cg0888)
• [Top 10 Coaching Techniques for Building Champions Inside Accounts](/knowledge/cg0793)
• [How do you coach reps across multiple time zones?](/knowledge/cg0186)

Sources

• Gong Labs — What separates winning deals from losing ones
• HBR — The New Sales Imperative (buying committees)
• Gartner — The B2B Buying Journey
• RAIN Group — Sales Coaching Research and Best Practices
• MEDDIC Academy — Mapping the Buying Committee
• Force Management — Command of the Message
• Sales Hacker — How to Multithread Enterprise Deals
• Winning by Design — The SaaS Sales Method

*Sales coaching for multithreading into target accounts — how to coach reps on multithreading, sales manager coaching guide, buying committee coaching framework, and a rep multithreading playbook for 2027.*

People also search for: coach reps on multithreading into target accounts · how to coach reps on multithreading into target accounts · coach reps on multithreading into target accounts guide