Single-Threaded Deal

A single-threaded deal has one living relationship holding up the entire opportunity. The CRM record might list four contacts, a decision-maker, an influencer, and a procurement liaison — but if only one of them has replied to an email or joined a call in the last 45 days, the deal is single-threaded, and it will die the moment that one person stops responding. This is the single most common reason a deal marked "90% probability, closing this quarter" evaporates in the last week: the champion took a new job, got reorged, or simply lost the political capital to push the deal through, and the rep never had a second relationship to fall back on.

How Single-Threaded Deals Are Identified

Multithreading is measured by engaged contacts, not logged contacts. RevOps teams flag a deal as single-threaded when only one stakeholder has taken an action — replied, attended a meeting, opened a proposal — within a defined recency window, typically 30 to 60 days. Some CRMs surface this with an engagement-decay metric per contact; without that tooling, the check is manual: open the opportunity, look at the activity timeline, and ask how many of the listed contacts have actually said or done anything recently.

Worked Example

An opportunity shows four contacts: a VP sponsor, a director, an IT lead, and a procurement contact, all added during discovery. Ninety days later, only the director has responded to anything — the VP hasn't opened an email in six weeks, IT was looped in once and never again, and procurement is waiting on the director to initiate. On paper this looks like a four-contact, multi-threaded enterprise deal. In reality it's single-threaded through the director, and if the director gets pulled onto another project, the deal has no path forward. Forecast accuracy on this opportunity should reflect one relationship, not four contacts.

When Sales Teams Flag Single-Threaded Deals

Sales managers use the check in deal review to downgrade forecast confidence before finance does it for them. RevOps builds it into pipeline scoring so a $200,000 opportunity sitting at "commit" gets automatically flagged if engagement data shows only one live contact. VPs of Sales watch for it at the portfolio level — a pipeline that's heavily single-threaded is a pipeline where a single round of layoffs or reorgs at target accounts can wipe out a quarter, which is a very different risk profile than the same dollar amount spread across well-threaded deals.

Common Single-Threaded Deal Gaming Patterns

Reps pad the contact list to fake multithreading without doing the work: CC three extra names on an email so the CRM shows engagement across a buying committee, when none of those names have ever spoken on a call or replied. It reads as multithreaded in a pipeline report and completely different in reality once someone checks who's actually responding. The other common failure mode is organizational, not individual — a rep does try to multithread, but the champion actively blocks it, wanting to control the narrative internally and protect their own credit for the deal, which keeps the rep boxed into one relationship whether they like it or not. Neither pattern shows up in a stage or dollar-amount view of the pipeline; both only surface when someone actually counts who in the account has said anything to the vendor in the last month.