Multithreading · Multi-Contact Selling
Multithreading in Sales
What is multithreading?
- Build relationships with several roles inside the client at once
- Each role has different concerns, so the message differs too
- A deal with only one contact is a warning sign
What multithreading really changes is where your information comes from. With a single contact, sales can only piece together the client's internal picture from what that one person says, and statements like 'leadership is on board' or 'the budget is secured' end up in reports unverified. With just three contacts, the same question gets answers from different angles, and where those answers diverge is where the deal's real risk sits. The essence is deal ownership shifting from one individual contact to the client organization, which is why forecast accuracy improves before your win rate does.
In practice, you count role coverage rather than the number of people met. The more accurate view is how many of five seats are still empty: users, working-level reviewers, technical and security validators, the approver who holds the budget, and procurement and legal. Meeting three contacts on the same team is not three contacts; it is effectively one. Horizontal expansion across departments and vertical expansion up the ranks are different in nature, and as deal size grows, vertical expansion is what decides the outcome. That is why many companies automatically lower the win probability in the pipeline review for deals of KRW 100 million (≈ US$74,800) or more with fewer than three contacts or three roles. The purpose of broadening is not to gain more allies but to find the opponents first.
The most common misconception is treating this as 'going over your contact’s head.' If you email an executive without telling your contact, that email almost always gets forwarded straight back down to them, and the person who was helping you turns against you. The principle is to go past your contact, but always through your contact. The second pitfall is changing your story by role until it stops adding up. If you tell Finance 'cost savings' and tell the business team 'full feature expansion,' the moment the two sit across from each other in an internal meeting, trust in the whole proposal collapses. Write the message differently for each role, but keep the facts the same.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Jaehyuk ParkHands-on instructor in B2B technical sales and AI-driven sales strategyResearchers have consistently found that several people take part in corporate purchasing decisions, starting with Webster and Wind’s (1972) buying center research. Later studies of complex B2B purchases report a growing number of participants, which is why securing multiple contacts has become a basic principle of sales practice.
Consider a hypothetical case: a KRW 300 million (≈ US$224,500) deal to sell a production management system to Company A, an industrial parts maker with 900 employees and KRW 240 billion (≈ US$179,560,100) in revenue. Six months in, the proposal had been revised three times, but no approval request had gone up, and all the sales rep knew was the 'under review' message passed along by Manager Kim of the Smart Factory TF.
- When the sales rep went back through six months of emails and meeting notes, the only person they had actually talked to was Manager Kim, and the approver, finance, security, and business-unit seats were all empty.
- We told Manager Kim, 'When the approval request goes up, the cost team will surely ask about the payback period, so I’ll prepare that answer for you in advance.' That earned us a meeting with the cost team’s deputy general manager.
- In the 30-minute slot with the head of production, we dropped the feature walkthrough entirely and showed only 15 slides of three same-industry cases that cut defect rates from 1.8% to 1.1%.
- For the information security team lead, we prepared a separate air-gapped network proposal and a list of 12 data items to be taken outside, and got the answer 'In this form, we can put it up for security review.'
- For the pilot, four foremen on Assembly Line 2 ran it for two weeks, and we responded by putting 7 of the 9 pain points they logged into the next version’s schedule.
- Contacts grew from 1 to 6 and role coverage from 1 to 5. Even after Manager Kim moved to another division in a February reorganization, the deal survived and closed at KRW 320 million (≈ US$239,400), 7 weeks after the original 6-month review.