multithreadinglisted

# Multithreading ## Purpose Turn a single-threaded deal into a multi-threaded one: map the full buying committee, see which roles you've actually reached, find warm intro paths from your existing contacts, and equip each persona with the value angle they care about — so the deal survives your champion going quiet. ## Inputs - The deal and its current contact roster (who you've met, their roles) - The deal stage, size, and what you're trying to advance - The buying motion (who signs, who blocks, who uses the product) ## Method 1. **Coverage analysis against the buying committee.** List the roles a deal this size needs, then mark each as *engaged*, *known-not-engaged*, or *missing*: - **Economic buyer** — controls budget, signs the contract. - **Champion** — sells internally for you when you're not in the room. - **Technical / security evaluator** — vets feasibility, integration, compliance. - **End users** — live with the product daily; their adoption is the proof. - **Blocker / detractor** — has reason to say no (incumbent owner, rival initiative). - **Procurement / legal** — gates the paperwork late in the cycle. Score coverage. A deal with only one or two roles engaged is at risk regardless of how good those relationships feel. 2. **Identify intro paths from current contacts.** You rarely cold-reach the committee — you get introduced. For each missing role, find the shortest warm path: who among your engaged contacts reports to, works wi