Pipeline health reviews in most revenue operations setups focus heavily on new pipeline creation: how much was generated this week, what's the coverage ratio against quota, how does velocity look on current-stage opportunities. These are legitimate questions and the metrics that drive them are well-understood. What gets less systematic attention is the pipeline that's already in the CRM and going nowhere — deals stalling between stages, leads sitting in qualification limbo, MQL cohorts that converted to SAL status and then stopped moving. Dormancy is a form of pipeline health failure that aggregate metrics obscure.
This guide focuses on the diagnostic side: how to measure dormancy systematically across the full funnel, what the key metrics are that indicate a dormancy problem versus a normal-velocity deal, and what an action plan looks like once you've identified the scope of the issue. The reactivation tactics themselves (sequencing, scoring, channel selection) are covered in other articles in this series — this is the diagnostic framework that informs which contacts and opportunities belong in those tactical motions.
Why Pipeline Dormancy Is Hard to See in Standard Reports
The core measurement problem with dormancy is that it's defined by absence. Active pipeline is visible because it has recent activity — stage changes, meeting activity, proposal sends. Dormant pipeline looks exactly like active pipeline in many standard CRM reports because it still has a status, still has a close date (usually the rep's best guess from when the deal was created), and still contributes to your coverage ratio calculation.
Consider a RevOps team at a growing B2B SaaS company with 80 open opportunities in their Salesforce pipeline. Standard reports show $4.2M in total pipeline against a $1.8M quarterly target — 2.3x coverage, looks healthy. But a dormancy audit shows that 23 of those 80 opportunities have had no logged activity (call, email, meeting, stage change) in the past 30 days. Those 23 opportunities represent $1.1M of the pipeline. Adjusted coverage: ($4.2M - $1.1M) / $1.8M = 1.7x — below the 2x floor most RevOps leaders use as a minimum healthy ratio. The dormancy wasn't visible in the headline coverage number; it required a second layer of analysis to surface.
This is why pipeline health reviews that only look at aggregate coverage, weighted pipeline, and velocity metrics systematically undercount dormancy risk. The diagnostic framework needs to include time-since-last-activity as a first-class metric, tracked at the individual opportunity and contact level, not just the aggregate pipeline level.
Key Metrics for Diagnosing Dormancy at Each Funnel Stage
Different funnel stages have different healthy activity thresholds, and what counts as "dormant" varies accordingly. Applying a single 30-day rule to the entire funnel miscategorizes both long-cycle enterprise deals (where 30 days between touches might be normal) and fast-moving SMB deals (where 7 days without activity is a red flag).
At the MQL/SAL stage, dormancy threshold is typically 14 to 21 days from last engagement without an attempted contact or status update. A lead that is in "Sales Accepted" status and has no logged contact attempt in 21 days should be considered dormant. This is a handoff failure — it reached the sales team but wasn't acted on. The diagnostic metric: SAL-to-contacted rate by cohort week, and the average days between SAL creation and first logged contact attempt. If this number is climbing, your SDR team has a capacity or prioritization problem.
At the SQL/opportunity stage, dormancy thresholds depend on your sales cycle length. For companies with 30 to 60 day sales cycles, 14 days without activity on an opportunity is a concern. For 90 to 180 day enterprise cycles, 30 days may still be within normal range. The useful diagnostic metric here is days-since-last-activity relative to the stage average for deals that eventually closed won. Build a baseline of what active, progressing deals look like at each stage — how frequently they have logged activity, what the typical time-in-stage is — and flag opportunities that are running 1.5 to 2x the normal time-in-stage without activity as dormancy candidates.
At the MQL-and-below (contacts) stage: contacts with MQL or SAL status older than 60 days with no stage progression and no activity in the last 30 days are by definition dormant. The metric to track: the ratio of dormant contacts to total marketing-qualified contacts in your CRM. If this ratio is above 40 percent, you have a structural reactivation problem, not an individual deal problem. That's typically where the deeper diagnostic work — dormancy root cause analysis, ICP scoring on the dormant cohort, intent signal monitoring — becomes the priority.
Building a Dormancy Diagnostic in Salesforce and HubSpot
In Salesforce, dormancy diagnostics are typically built as custom reports on the Activity object joined to Opportunity and Contact, filtering for records where last activity date falls outside a configurable window. A useful operational dashboard includes: opportunities with zero activities in the last 30 days by stage (sorted by opportunity value); contacts with MQL or SAL status and last engagement date older than 45 days; and a dormancy rate trend — the percentage of your open opportunities meeting dormancy criteria, tracked week over week to identify whether the problem is improving or worsening.
In HubSpot, similar visibility is available through custom contact and deal reports using the "Last activity date" property. HubSpot's deal board views can be filtered by last activity, which makes dormancy visible in the deal review context without requiring a custom report. The limitation of HubSpot for dormancy tracking at scale is that activity tracking depends on sales team behavior — HubSpot's auto-activity logging from email and calendar integration helps, but if your team uses Outreach or Salesloft for sequence management and logs activities back to HubSpot imperfectly, your activity data will have gaps that make dormancy metrics unreliable.
Outreach and Salesloft both have their own inactivity reporting on contacts enrolled in sequences, but this is sequence-scoped activity, not full contact or opportunity activity. A contact can be "active in Outreach" (receiving automated sequence touches) while being genuinely dormant from a pipeline perspective (no positive response, no stage movement, no meeting booked). This is a critical distinction that RevOps teams running engagement platforms need to build into their definitions — sequence enrollment is not equivalent to sales activity.
Root Cause Analysis: Why Pipeline Goes Dormant
Dormancy doesn't have a single cause, and the right reactivation approach depends on which cause applies to a given segment of your dormant pipeline. The five most common root causes, and what each implies for the diagnostic: timing mismatch — the contact or company was genuinely interested but the timing wasn't right (budget cycle, competing initiative, organizational change). These leads tend to have strong initial engagement, a reasonable firmographic profile, and clear documented reasons for going quiet in the CRM notes. They are the highest-quality reactivation candidates.
ICP drift — the lead was qualified against an older version of your ICP that no longer matches your current go-to-market. As companies evolve from broad early-stage go-to-market to a more targeted ICP, old leads that were qualified under the prior model may sit dormant because they're implicitly deprioritized without being formally disqualified. These leads need an ICP re-evaluation before reactivation.
Sales handoff failure — the lead arrived in the sales team's queue and never got a meaningful first contact. This is a process failure, not a lead quality failure. The leads in this category may still be highly qualified; they simply weren't worked. Distinguishing them from timing-mismatch leads requires checking the activity log: zero logged contact attempts means handoff failure; one or two attempts with no response means something else.
Champion departure — the contact who was championing the internal evaluation left the company or changed roles. This is particularly common in dormant opportunities that were at the SQL or late evaluation stage. The opportunity doesn't disappear when the champion leaves, but it requires identifying and building a relationship with a new internal contact before it can progress.
Genuine competitive loss without disqualification — the lead evaluated and chose another vendor, but no one logged the loss or updated the CRM record. This produces phantom pipeline that inflates coverage ratios. The diagnostic for this: compare your closed-lost rate to your dormancy rate. If dormancy rate significantly exceeds your documented closed-lost rate, you likely have undocumented losses sitting in your pipeline as "open" or "stalled."
Building a Reactivation Action Plan From the Diagnostic
Once you've run the diagnostic and classified your dormant pipeline by root cause and stage, the action plan is essentially a routing exercise. Timing-mismatch MQLs and SALs with strong initial engagement go into a scored reactivation queue for systematic outreach. ICP-drift contacts get re-evaluated and either archived or re-scored against current ICP criteria. Handoff-failure contacts get immediate escalation to SDR manager for coverage assignment. Champion-departure opportunities get assigned to an AE for new contact identification and relationship building. Undocumented competitive losses get updated CRM status and moved to closed-lost, cleaning up your pipeline coverage metric.
The action plan cadence: monthly for the dormancy audit itself (review key metrics, flag new dormant contacts/opportunities); quarterly for the deeper root cause classification (requires time to do well; don't rush this exercise); and weekly for the tactical reactivation queue (who's being worked this week from the scored dormant cohort, what's the response rate, what's moving to active stage).
Pipeline health is ultimately a measure of information quality — how accurately your CRM reflects the real state of your buying relationships. Dormancy is a symptom of information decay: leads that were once accurately characterized have aged into ambiguity, and the ambiguity is obscuring the real health of the pipeline. The diagnostic process is about replacing ambiguity with clarity — not to produce a cleaner report, but to make better decisions about where to focus the sales team's limited attention.