Joshua Franklin Wiedeman

Multithreading Sequences

Multithreading means running coordinated outreach to several people in one account: the economic buyer, the technical evaluator, the day-to-day user, and the executive sponsor. The goal is to build agreement across the buying group instead of relying on one champion to sell for you internally.

How it works

B2B purchases usually involve several stakeholders. If your whole relationship runs through one person, the deal is at risk when that person changes roles, loses influence, or gets busy. Multithreading removes that single point of failure. Each role gets a message that fits its concerns: the CFO gets ROI, the engineering lead gets architecture, users get workflow improvements.

How to do it

  1. Map the buying committee. For each account, identify 4-6 contacts: economic buyer, technical evaluator, user champion, executive sponsor, and procurement or legal. Use LinkedIn Sales Navigator, org charts, and your champion’s input.
  2. Write role-specific sequences. Economic buyer: ROI, cost, and competitive position. Technical evaluator: architecture, integration, and security. Users: ease of use and workflow.
  3. Stagger the outreach. Do not contact everyone on the same day. Start with the champion. Contact the technical evaluator a few days later and reference the existing conversation. Reach the economic buyer the following week with a business case.
  4. Ask for warm introductions. Once you have rapport, ask your champion to introduce you to others. If that is not possible, reference the existing conversation: “I have been speaking with [Name] about [topic].”
  5. Track contacts per deal. Add a CRM field for the number of engaged contacts per opportunity. Set a minimum, for example three engaged contacts, before a deal can move to the proposal stage.

What to measure

  • Engaged contacts per opportunity: unique contacts with a meeting, reply, or content engagement, per open deal.
  • Win rate by thread count: close rate for deals with 3+ engaged contacts versus deals with 1-2.
  • Cycle length by thread count: average days to close, grouped by number of engaged contacts.

Best practices

  • Give each contact a different reason to talk to you. Same product, different story.
  • Share engagement across threads. If the technical evaluator reads the security whitepaper, the rep contacting the CISO should know.
  • Use LinkedIn as a parallel channel. People who ignore cold email often accept a request from someone already working with a colleague.
  • Build a mutual action plan that lists every stakeholder by name. This makes the multithread visible to everyone.

Common pitfalls

  • Sending the same generic email to everyone. It looks like spray-and-pray and undermines credibility.
  • Going over the champion’s head without telling them. Always let your champion know before you contact their leadership.
  • Starting too late. Adding stakeholders in the final stage looks desperate. Begin during discovery.