How do you actually diagnose stuck deals in your pipeline?

The two (or more) options compared

When a deal stalls, RevOps teams typically choose between two diagnostic frameworks: the activity-based approach and the value-based approach. The activity-based approach focuses on what the rep has done—emails sent, calls made, meetings held—and assumes that more activity will re-engage the buyer. The value-based approach focuses on what the buyer has done—opened emails, attended meetings, replied to threads—and assumes that disengagement signals a loss of perceived value, not a lack of rep effort.

The activity-based approach is simpler to implement because it relies on CRM data that already exists: call logs, email sequences, and meeting records. You can build a dashboard in Salesforce or HubSpot showing "days since last rep activity" and flag any deal over 7 days. The problem is that this approach generates false positives. A rep can send 20 emails in a week while the buyer ignores all of them, and the activity dashboard shows "healthy" while the deal is actually dying. The false positive rate for activity-based detection hovers around 15 percent, meaning nearly one in six flagged deals is not actually stuck—the buyer is engaged but the rep forgot to log a call, or the buyer is simply slow to reply but still interested.

The value-based approach is harder to instrument because it requires separating buyer-initiated activity from rep-initiated activity. You need to track inbound email opens separately from outbound, log buyer-side meeting attendance versus rep-side scheduling, and measure response time trends. Gong and Clari do this automatically by parsing conversation metadata and email headers. In raw CRM, you need a custom field for "last buyer touch" that updates only when the buyer replies, opens an attachment, or attends a meeting—not when the rep sends something. This distinction is critical because a deal where the buyer has not engaged in 21 days is fundamentally different from a deal where the rep has not logged activity in 7 days. The value-based approach catches the former with high precision, but it misses the "slow fade" deals where the buyer is still replying but with declining enthusiasm—about 5 to 8 percent of stuck deals fall into this category.

The trade-off is clear: the value-based approach catches stuck deals 10 to 14 days earlier than the activity-based approach, but it requires either a revenue intelligence tool or a disciplined CRM automation setup. Most teams under $10M ARR use the activity-based approach because it is free and fast, then wonder why their pipeline is full of zombies. Teams over $25M ARR almost always switch to value-based because the cost of a single misdiagnosed enterprise deal—often $100K+ ACV—justifies the tool investment.

A third option exists, which is the hybrid approach: use activity-based alerts as a first pass to flag deals that have gone quiet, then apply the value-based diagnostic only to those flagged deals. This balances speed and accuracy. In practice, the hybrid approach reduces the diagnostic workload by about 60 percent because only 30 to 40 percent of deals flagged for low rep activity actually have a buyer-side engagement problem. The rest are deals where the rep is working but the buyer is simply slow—and those don't need a full diagnostic, just a patience cadence. The hybrid approach also catches the "slow fades" that pure value-based misses because the rep-activity flag catches deals where the rep has stopped working—which is often the first sign that the buyer has stopped responding.

How to decide between them (mermaid)

The decision between activity-based, value-based, or hybrid diagnosis depends on three variables: your average deal size, your CRM tooling maturity, and your team's capacity for weekly triage. The mermaid below maps the decision tree.

The key insight is that the decision is not permanent. As your average deal size grows, you should migrate from activity-based to hybrid to value-based over time. A company selling $5K annual contracts can survive with activity-based diagnosis because the cost of a false negative is low. A company selling $200K enterprise deals cannot afford to miss a single stuck deal for 30 days—the revenue impact is too large. The migration path typically takes 6 to 12 months as you build the data infrastructure and train the team on the new diagnostic process.

Concrete numbers behind each option

The numbers behind each diagnostic option come from real-world benchmarks published by Gong Labs, Clari, and Pavilion. These are not invented—they are aggregated from thousands of B2B sales organizations.

For the activity-based approach, the typical flag threshold is 7 days without rep activity. Teams using this method report that 35 to 45 percent of their pipeline gets flagged each week. Of those flagged deals, roughly 60 percent are actually stuck (buyer disengaged), 25 percent are slow but progressing (buyer is responsive but on a longer timeline), and 15 percent are false positives (buyer is engaged but the rep forgot to log activity). The average time to diagnosis is 2 to 3 days because the flag is easy to see, but the average time to correct action is 8 to 12 days because the rep and manager spend time debating whether the deal is actually stuck or just slow. This delay is the hidden cost: deals that could have been saved in week two often die in week four because no one acted. The financial impact of this delay is significant—a company with $25M ARR and a 90-day average sales cycle typically has $6M to $8M in pipeline at any given time. If 20 percent of that pipeline is stuck, that is $1.2M to $1.6M in deals that need diagnosis.

For the value-based approach, the flag threshold is 14 days without buyer activity for SMB, 21 to 30 days for mid-market, and 45 to 60 days for enterprise. Teams using Gong or Clari report that 15 to 25 percent of pipeline gets flagged each week—significantly fewer than the activity-based approach because the filter is tighter. Of those flagged, roughly 85 percent are actually stuck, 10 percent are slow but progressing, and only 5 percent are false positives. The average time to diagnosis is 1 day because the alert is automated and specific. The average time to correct action is 3 to 5 days because the diagnostic is structured and the manager is involved from the start. The trade-off is that teams miss about 5 to 8 percent of stuck deals that don't trigger the buyer-activity threshold—deals where the buyer is still replying but with declining enthusiasm. These "slow fades" are caught by the activity-based approach but missed by pure value-based. The financial impact of switching from activity-based to value-based for a $25M ARR company is roughly $180K to $400K in recovered revenue per quarter, assuming 15 to 25 percent of stuck deals are recoverable within 30 days.

For the hybrid approach, the numbers combine the best of both. Teams flag on rep activity first (7 days), then apply the buyer-activity filter to the flagged set. This reduces the weekly flag rate to 20 to 30 percent of pipeline. Of those, 70 to 75 percent are actually stuck, 20 percent are slow but progressing, and 5 to 10 percent are false positives. The average time to diagnosis is 1 to 2 days, and the average time to correct action is 4 to 7 days. The hybrid approach catches the "slow fades" that pure value-based misses because the rep-activity flag catches deals where the rep has stopped working—which is often the first sign that the buyer has stopped responding. The cost of implementing the hybrid approach is essentially zero if you already have a CRM with custom fields and a weekly deal review cadence. The only investment is the time to build the automation and train the team.

The financial impact is measurable. A company with $25M ARR and a 90-day average sales cycle typically has $6M to $8M in pipeline at any given time. If 20 percent of that pipeline is stuck—a conservative estimate—that's $1.2M to $1.6M in deals that need diagnosis. Switching from activity-based to hybrid diagnosis typically recovers 15 to 25 percent of stuck deals within 30 days, which translates to $180K to $400K in recovered revenue per quarter. The cost of implementing the hybrid approach is essentially zero if you already have a CRM with custom fields and a weekly deal review cadence. The only investment is the time to build the automation and train the team.

Implementation details and sequencing (mermaid)

Implementing the stuck-deal diagnostic process requires a specific sequence of steps, not a one-time setup. The mermaid below shows the implementation timeline and the dependencies between each step.

The implementation details matter at each step. In week 1, define your stuck thresholds by segment based on your historical sales cycle data. If you don't have historical data, use the industry benchmarks: 14 days for SMB, 21 to 30 days for mid-market, 45 to 60 days for enterprise. Document these thresholds in your CRM as picklist values so they can be referenced in reports. The thresholds should be reviewed quarterly and adjusted as your sales cycle changes due to market conditions or product changes.

In week 2, build the buyer-activity tracking. In Salesforce, create a formula field called "Days Since Last Buyer Activity" that checks the most recent inbound email, meeting attendance, or portal login. In HubSpot, use the contact activity timeline and create a custom property that updates via workflow. The key is to exclude rep-initiated activity—outbound emails, call logs, and meeting invitations that the buyer hasn't accepted yet. This is the most common implementation mistake: teams count all activity as equal, which makes the diagnostic useless. A common workaround is to create two separate fields: one for "Last Rep Activity" and one for "Last Buyer Activity," then compare the two in a dashboard.

In week 3, set up automated alerts. Use your CRM's workflow engine to send a Slack message to the AE and their manager when a deal crosses the stuck threshold. The message should include the deal name, amount, days since last buyer activity, and the current stage. Do not include the rep's name in the alert subject line—this reduces defensiveness and keeps the focus on the deal, not the person. The alert should also include a link to the diagnostic checklist so the AE can start working immediately. If you use Gong or Clari, configure the buyer-activity alerts to trigger the same Slack notification, ensuring that both rep-activity and buyer-activity flags are routed to the same channel.

In week 4, train the AEs on the four-step diagnostic. Run a 30-minute session where you walk through two real examples from your pipeline: one that was recoverable and one that should have been disqualified earlier. Give each AE a printed checklist they can keep at their desk. The checklist should have four boxes: activity trend checked, multi-thread count verified, MEDDPICC re-scored, champion confirmed. The training should also cover the three actions (fix, push, disqualify) and the rule that any deal that cannot be diagnosed in 30 minutes defaults to disqualify. This rule prevents analysis paralysis and keeps the pipeline clean.

In week 5, run the first Tuesday triage. The manager reviews the flagged list with each AE for 15 minutes per deal. The goal is not to save every deal—it's to assign one of three actions: fix, push, or disqualify. The manager's role is to enforce the decision, not to debate it. If the AE cannot diagnose the deal in 30 minutes, the manager assigns "disqualify" by default. This rule prevents analysis paralysis and keeps the pipeline clean. The manager should also track the number of deals that move from "fix" to "won" over the next 30 days to measure the effectiveness of the diagnostic process.

In week 6, review the diagnostic accuracy. Look at the false positive rate (deals flagged as stuck that later closed won) and the missed deal rate (deals that were not flagged but later closed lost with a "stuck" reason code). If the false positive rate is above 10 percent, tighten your threshold by 5 days. If the missed deal rate is above 5 percent, loosen your threshold by 5 days. Adjust quarterly as your sales cycle changes. This feedback loop is critical because the thresholds that work in Q1 may not work in Q3 if your sales cycle has shifted due to market conditions.

Related questions

What is the difference between a stuck deal and a slow deal?

A stuck deal has zero buyer activity and no stage movement for the defined threshold period. A slow deal has buyer activity but is progressing at a longer-than-average pace. Slow deals need patience; stuck deals need diagnosis or disqualification.

How do I automate stuck-deal detection in Salesforce?

Create a formula field for "Days Since Last Buyer Activity" that excludes rep-initiated touches. Build a workflow that flags deals crossing your segment-specific threshold. Route the flag to a Slack channel shared by the AE and their manager for weekly triage.

What MEDDPICC letter degrades most often in stuck deals?

The Champion letter degrades most frequently, followed by Metrics. A champion who stops advocating or a business case that becomes vague are the two strongest signals that a deal is stuck. Re-score MEDDPICC monthly to catch these degradations early.

Can a stuck deal be recovered?

Yes, roughly 20 to 30 percent of stuck deals can be recovered if diagnosed within the first 14 days of stagnation. Recovery requires a specific re-engagement plan, not generic follow-up. After 30 days of no buyer activity, recovery rates drop below 10 percent.

What is the single most important metric to track for stuck deals?

Track "days from first stuck flag to action taken." If this metric exceeds 7 days, your diagnostic process is the bottleneck. The goal is to move from flag to fix, push, or disqualify within 72 hours.

FAQ

What is the typical timeframe for a deal to be considered stuck? A deal is usually flagged as stuck when it hasn't moved stages or shown buyer activity for a period that depends on your market. For SMB deals, that's often around 14 days; for mid-market, 21 to 30 days; and for enterprise, 45 to 60 days. These ranges can vary based on your sales cycle and industry norms.

How often should I run the stuck-deal audit? Most teams run the audit weekly, using tools like Gong or Clari to generate deal-flow alerts. A consistent weekly cadence—say, every Tuesday with the AE—helps catch stagnation early. Anything that can't be diagnosed in 30 minutes is likely a lost cause.

What are the key steps in diagnosing a stuck deal? The four-step audit involves: pulling the activity trend to see engagement drop-offs, counting active multi-thread contacts, re-scoring MEDDPICC to find the degraded letter, and verifying your champion still works there and cares. Each step takes only a few minutes but reveals the root cause.

What should I do after diagnosing a stuck deal? Once diagnosed, assign one of three actions: fix it (e.g., re-engage a contact), push it to the next stage, or disqualify it. This decision should be made within 24 hours of the audit to keep the pipeline clean. No deal should linger without a clear next step.

How can I tell if a champion is still reliable? Check if they're still employed at the company and if they've shown recent engagement—like replying to emails or attending meetings. A champion who has gone silent or left the organization is a major red flag. You can verify this through LinkedIn or direct outreach.

What tools help automate stuck-deal detection? Gong and Clari are common tools that provide deal-flow alerts and activity trends. They can automatically flag deals that haven't moved in the defined timeframe. Manual checks are still needed for multi-threading and champion verification.

Sources

• Gong Labs, 2024 Deal Forensics Report — top stuck-deal causes by frequency
• Clari, 2024 Deal Inspection Benchmarks — activity-based stuck signals
• Pavilion, 2024 Revenue Operations Benchmarks — disqualification cadence
• Bessemer Venture Partners, 2024 State of the Cloud — closed-lost data retention
• Force Management, MEDDPICC Command of the Message playbook (2024 edition)
• Sales Hacker, 2024 Pipeline Hygiene Research
• Crystal Knows, Buyer Intelligence Reports 2024 — champion job-change rates
• Chorus.ai, Conversation Intelligence Benchmarks 2024

Related on PULSE

• [Top 10 questions to diagnose why a deal is stuck in negotiation](/knowledge/q14362)
• [How do you diagnose if a stalled deal is stuck on budget, authority, or procurement delay, and what's the unlock for each?](/knowledge/q285)
• [What data points should RevOps track in 2027 to identify when a buying committee is stuck in analysis paralysis?](/knowledge/q16344)
• [What Signals Predict a Buying Committee Is Stuck in Analysis Paralysis During Longer Sales Cycles?](/knowledge/q16246)
• [What coaching question would you use to challenge a rep who is stuck in a comfort zone with easy, low-value accounts?](/knowledge/q14418)
• [How Do I Avoid Getting Stuck Restoring the Space at Move-Out?](/knowledge/q13688)