# One contact is not a deal: how to multithread an enterprise account URL: https://www.coltasa.com/insights/sales-multithreading Author: Colin Constantine Published: 2026-11-03 Category: Pipeline > Multithreading in sales means building relationships with several people in a buying group. How to map the group, earn introductions and cover every role. Photo: [Kindel Media](https://www.pexels.com/photo/overhead-shot-of-people-in-a-meeting-7688360) on Pexels Multithreading in sales means building working relationships with several people in a buying organisation, not just one, so the deal does not depend on a single contact. To do it well, map the buying group early, earn each introduction by giving your contact something useful to share, and give every person a reason to talk to you that is about their job, not your product. Start in the first two meetings, not when the deal stalls. Most enterprise deals that die late were single-threaded. One enthusiastic contact carried the evaluation, then went on leave, changed role, or simply lost the argument in a meeting you were never invited to. Multithreading is the insurance against that, and it is also how you find out what the organisation actually needs. ## What is multithreading in sales? Multithreading is the practice of engaging multiple stakeholders in a target account at the same time, each with a relationship and a reason to stay involved. A single-threaded deal runs through one person. A multithreaded deal has several independent lines into the account: your champion, the economic buyer, the people who will use the product, and the functions that can say no, such as IT, security, finance and procurement. The reason it matters is simple arithmetic about who decides. Forrester's research on business buying found that "[on average, 13 people within an organization are involved in the buying decision](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024)", and that 89 percent of purchases involve two or more departments. If you are talking to one of them, you are guessing about the other twelve. Forrester describes the buying group as people from different parts of the organisation with different needs and roles, "[including decision-maker, champion, influencer, ratifier, and user](https://www.forrester.com/blogs/the-verdict-is-in-its-buying-groups-for-the-win/)". Those role names are a useful starting map. Each one needs a different conversation from you. ## Why is a single-threaded deal so risky? A single-threaded deal is risky because every piece of information and every internal argument passes through one person, and that person has a day job, a manager and a career that do not revolve around your deal. Three things go wrong. - You lose the deal when you lose the person. Reorganisations, resignations and parental leave are normal. If your only contact disappears, so does your deal. - You only see one version of the problem. Your contact describes the pain from their seat. Finance, IT and the end users often see a different problem, a different priority or a different deadline. - You cannot forecast honestly. If one person tells you the deal is on track, you have an opinion, not evidence. A [forecast built on evidence](https://www.coltasa.com/insights/forecast-evidence) needs confirmation from more than one seat at the table. A friendly contact who discourages you from talking to anyone else is a warning sign, not a relationship to protect. Sometimes it means they lack the standing to get you further. Sometimes it means they are worried about what others will say. Either way, you need to know. ## How do you map the buying group in an enterprise account? You map the buying group by asking your first contact how decisions like this get made, then writing down every role involved and who fills it. Do this in the first or second meeting. People are more open about process early, before the politics of a live evaluation set in. Questions that work well in a [discovery call](https://www.coltasa.com/insights/discovery-call): - The last time you bought something of this size, who was involved from start to finish? - Who has to agree that this problem is worth solving this year? - Who controls the budget this would come from? - Who will be using this every day, and who looks after the systems it connects to? - Which teams have a formal sign-off: security, legal, procurement, finance? - Who would be most sceptical, and why? Turn the answers into a simple map: one row per person, with their role in the decision, what they care about, whether you have met them, and who can introduce you. A spreadsheet is fine. The point is to make the gaps visible, so the team can see that you have three users and no one from finance. ## How do you get introduced to more stakeholders without going around your contact? The cleanest way is to ask your contact for help, and to make the introduction easy and safe for them. People resist introductions when they fear losing control of the project or looking foolish in front of senior colleagues. Remove both fears and most will help. A sequence that works: - Explain why, in their interest. "Finance will need to sign this off later. If we understand their criteria now, we avoid a surprise that delays your project." - Give them something to forward. A two-paragraph summary of the problem, the proposed outcome and the question for the new person. Write it so they can send it under their own name. - Offer to include them. Invite your contact to the first conversation with the new stakeholder, so they stay at the centre of the project. - Report back. After each new meeting, tell your contact what you learnt. This builds trust and shows that more threads make their case stronger, not weaker. If your contact still refuses, test whether they are a coach rather than a [real champion in the deal](https://www.coltasa.com/insights/enterprise-sales-champion). A champion wants the deal to happen and will open doors. A contact who blocks every introduction is telling you something about their influence. Two other routes are legitimate when used with care. Peer-to-peer outreach (your CEO to their CEO, your security lead to their security lead) works because it carries its own credibility. Direct outreach to a new stakeholder works when you have a specific, relevant reason and you tell your main contact you are doing it. ## What should you say to each person in the buying group? Talk to each person about their own problem and their own risk, not about your product in general. A finance director and a team lead can both want the same purchase for completely different reasons, and a generic pitch to either one wastes their time. - Economic buyer: the business outcome, the cost of doing nothing, and how this fits the year's priorities. - Champion: what they need to win the internal argument, and what is in it for them if the project succeeds. - Users: how their daily work changes, and what the first month looks like. - IT and security: integration, data handling and the documentation they will ask for, provided early. - Finance and procurement: commercial structure, payment terms and how value will be measured. A [mutual success plan](https://www.coltasa.com/insights/mutual-success-plans) pulls these threads together. When each stakeholder's step appears in a shared plan with names and dates, the buying group can see its own process, and you can see who has gone quiet. ## How many contacts do you need in an enterprise deal? There is no universal number, but a working rule is to have a relationship with someone in every role that can stop the deal. For most mid-market and enterprise deals that means at least the champion, the economic buyer, a representative user and whoever owns technical sign-off. Count roles covered, not names in the CRM. A useful illustration: say a deal needs approval from five roles and you have strong contact with two. You do not have 40 percent of a deal. You have two people who think it is a good idea and three who have not been asked. Treat the uncovered roles as open risks in your deal review, each with an owner and a next step. Multithreading also applies inside your own team. Pair your executives, your solutions engineers and your customer success lead with their counterparts. Several people on each side, talking about the parts they know best, produce a far sturdier deal than one seller trying to be everything to everyone. This week, pick your three largest open deals and draw the buying group for each. Mark every role that can stop the deal and whether you have spoken to that person in the last month. For each gap, write the introduction request you will send to your contact, and send it. ## Sources and further reading - [Forrester (2024): To Master B2B Buying Mayhem, Providers Must Prioritize Buyers' Needs](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024) - [Forrester (2025): The Verdict Is In: It's Buying Groups For The Win](https://www.forrester.com/blogs/the-verdict-is-in-its-buying-groups-for-the-win/) ## Frequently asked questions ### What is the difference between multithreading and having a champion? A champion is one person inside the buyer's organisation who actively sells your solution internally. Multithreading is the wider practice of building relationships with several people across the buying group, including the champion. You need both: the champion drives the decision, and the other threads protect the deal if the champion leaves and confirm that the rest of the organisation agrees. ### When should you start multithreading a deal? Start in the first or second meeting, while you are still in discovery. Ask how similar decisions have been made, who is involved and who signs off. Early on, contacts share this freely and introductions feel natural. If you wait until the deal stalls, asking for more contacts looks like a sign of trouble and is much harder to get. ### What if my main contact will not introduce me to anyone else? Explain why the introduction helps them, offer a short summary they can forward under their own name, and invite them to join the first meeting. If they still refuse, treat it as a signal about their influence and commitment. Consider peer-to-peer outreach from your own leadership, and lower your confidence in the deal until you have a second thread. ### Does multithreading only apply to large enterprise deals? It matters most in large deals because more people are involved, but it applies whenever more than one person can say no. Even a mid-sized purchase usually involves a user, a budget holder and someone responsible for security or procurement. Scale the effort to the deal: map the roles, then make sure each one that can stop the deal has heard from you.