A single-threaded deal is one where every meaningful conversation, discovery through pricing, routes through the same one or two people at the buying company, regardless of how many contacts are logged in the CRM.
A CRM's Contact Roles field can list five names on an opportunity and still describe one relationship. A VP who got cc'd on a recap email and never spoke on a call counts as a logged contact. So does a champion's direct report who sat silently through a demo because they were told to attend. Both inflate the count. Neither adds an independent thread, and if the champion leaves or goes cold, every one of those relationships goes with them, because none of the other names ever had a conversation that didn't route through the champion first.
Pull the calendar invites for a deal's discovery call, its technical or demo call, and its pricing call, and look at who showed up to each one. If the same one or two names sit in every meeting, the deal is single-threaded, no matter how many contacts are sitting in the CRM. A deal that's actually multithreaded looks different on the calendar itself: a technical evaluator shows up for the demo who was never in discovery, because discovery wasn't their job, and someone from finance shows up for pricing who never sat in on the technical review, because pricing wasn't theirs to weigh in on until the deal got real.
This matters more than a hygiene issue. Matthew Dixon and Ted McKenna's research, published in Harvard Business Review in June 2022 and based on more than 2.5 million recorded sales conversations, found that 40 to 60 percent of deals that looked like they were moving forward were lost to customer indecision rather than to a competitor. A single-threaded deal is structurally the shape that indecision hides in: there's no one else in the room with enough standing to push a stalled decision forward, so it just sits, and the rep reads the silence as a good sign until it isn't.
Run a calendar-invite audit at each stage gate, not once at deal creation: pull every meeting logged against the opportunity, tag each by type (discovery, technical, pricing, executive, legal), and build a grid of who attended which. A healthy grid shows new names appearing in the meeting types that are theirs. A red-flag grid shows the same one or two names repeating across every column.
Managers use "five contacts logged" as proof a deal is safe, when that number measures something different from what it's supposed to measure. It's evidence one person is good at getting names into a CRM field, not evidence the deal would survive that person leaving.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us