What is a stage aging report — and how do you use it to clean pipeline?
A stage aging report shows how long each open opportunity has been sitting in its current pipeline stage, measured against a benchmark — usually the median time other deals spend in that same stage. It surfaces what is stuck without forcing managers to read every AE's notes. For mid-market B2B SaaS the typical medians are 7-14 days in qualified, 10-21 days in discovery, 14-30 days in demo, 14-30 days in proposal, and 7-21 days in verbal. Anything past 2.5x the stage median is a stuck-deal red flag; past 4x with zero buyer activity is almost always dead.
TL;DR
- Stage aging measures days-in-current-stage, not days-since-opportunity-created — those are completely different signals.
- Mid-market B2B SaaS benchmarks (Gong Labs 2024): 7-14 / 10-21 / 14-30 / 14-30 / 7-21 days across the five stages.
- 2.5x stage median equals stuck; 4x median plus no buyer activity equals dead — pull from forecast.
- Stage-2 aging creeping up by 30 percent QoQ means top-of-funnel quality is dropping; stage-4 aging creeping up means pricing, legal, or procurement is the friction.
- The report only works if you triage it weekly with named owners and actions — otherwise it becomes dashboard wallpaper.
Median Aging Benchmarks by Stage
The benchmarks below are mid-market B2B SaaS medians from Gong Labs' 2024 Pipeline Velocity study, cross-referenced with Clari's Pipeline Inspection aggregate data and ICONIQ's 2024 Operating Metrics. They are starting points — every business should recalibrate against its own closed-won history after one full quarter of data.
| Stage | Median Days | Red Flag (2.5x) | Fix Action |
|---|---|---|---|
| 1. Qualified | 7-14 days | 30+ days | Confirm budget signal; if no champion in 30 days, demote to nurture. |
| 2. Discovered | 10-21 days | 45+ days | Pressure-test pain on a multi-threaded call; if buyer cannot articulate impact, pull from forecast. |
| 3. Demoed | 14-30 days | 60+ days | Force a mutual action plan with named buyer owners and dated milestones. |
| 4. Proposal | 14-30 days | 60+ days | Escalate to manager call; pricing, legal, or procurement is almost always the friction. |
| 5. Verbal | 7-21 days | 35+ days | Lock redlines and security review in parallel; verbal past 35 days is usually a soft no. |
Two cohort effects matter when reading these numbers. First, deal size shifts the medians up — $100K-plus ACV opportunities run roughly 1.5x to 2x the medians above because procurement and InfoSec add real cycle time. Second, repeat buyers and warm referrals run 30-40 percent faster in discovery and demo, so segment your benchmarks before triaging or you will harass good AEs running fast deals.
The 4 Diagnostic Patterns
Pattern 1: Opp at 2.5x stage median equals stuck. A deal sitting at stage 3 for 75 days against a 30-day median is not "still working" — it is stuck. The buyer has either de-prioritized the project, lost the internal champion, or is shopping you against an incumbent renewal. Action: schedule a multi-threaded call within seven days or pull from forecast.
Pattern 2: Opp at 4x stage median plus zero buyer activity equals dead. When a deal is 4x the median AND there has been no inbound email, no meeting accepted, and no asset opened in 21 days, it is almost certainly closed-lost no-decision. Gong's 2024 data shows under 4 percent of deals matching this pattern ever close. Move them to closed-lost and reclaim AE capacity.
Pattern 3: Stage 2 average aging up 30 percent QoQ equals top-of-funnel quality dropping. If discovery aging quietly drifts from 15 days to 20 days quarter over quarter, marketing-sourced lead quality has slipped or SDRs are pushing through unqualified meetings to hit activity targets. Worked example: a $30M ARR Series C SaaS company analyzed stage aging and found median stage-2-to-3 days had crept from 14 days to 27 days over four quarters. Root cause was AEs over-promising discovery quality early — demos showed buyers were not ready. They tightened discovery qualification (mandatory pain, budget signal, and timeline before stage advance), stage 2-to-3 returned to 16 days, and stage-3-to-4 win rate rose 9 percentage points.
Pattern 4: Stage 4 aging up 30 percent equals pricing, legal, or procurement friction. When proposal-stage aging balloons but earlier stages look healthy, the deal is dying in paperwork. The usual suspects are list-price increases that have not been pre-socialized, MSA redlines stuck with legal, or InfoSec questionnaires sitting with a single overloaded security engineer. Fix: build a standing Friday legal-and-procurement standup with a named owner per deal.
The 3 Report Failure Modes That Make It Wallpaper
Failure 1: Measuring days-open instead of days-in-current-stage. A 90-day-open opportunity that just advanced from demo to proposal yesterday is healthy. A 30-day-open opportunity that has been stuck at stage 2 for 28 of those days is concerning. Days-open averages every stage together and washes out the signal. The correct field is the delta between today and the most recent OpportunityFieldHistory change of the StageName field — Salesforce Pipeline Inspection and Clari Pipeline Flow compute this natively. If your team is reading days-open, your report is lying to you.
Failure 2: No per-stage benchmark. A 25-day stage-3 deal sounds long until you see the median is 22 days — it is normal. A 25-day stage-1 deal sounds short until you see the median is 9 days — it is stuck. Without a stage-specific benchmark column on every row, managers cannot distinguish normal from stuck, and AEs argue every flag in deal reviews. Put the stage median and the 2.5x threshold on the report itself, not in a wiki.
Failure 3: Report not triaged weekly. The report is a tool, not an artifact. If no one pulls the over-benchmark list every Monday, assigns owners by Tuesday, runs AE actions by Wednesday, and reviews exceptions at the Thursday forecast call, the dashboard becomes wallpaper. Sales teams that triage stage aging weekly run 18-22 percent shorter average cycle time than teams that look at it ad hoc (Pavilion 2024 RevOps Benchmark).
Tooling matters less than discipline. Salesforce Pipeline Inspection is free, native, and the default for most teams. Clari Pipeline Flow adds buyer-activity overlays. Sigma or Looker dashboards directly on the OpportunityFieldHistory table give the most flexibility for custom benchmarks and cohort cuts. Pick one, instrument the stage-median column, and run the weekly triage shown below.
Related on PULSE
- [When does aging pipeline become unrecoverable — 60 days, 90, 120?](/knowledge/q45)
- [What's the right way to clean up a pipeline that has 60% deals older than 90 days?](/knowledge/q1134)
- [What specific data points must RevOps clean before feeding them to an AI predictive lead model?](/knowledge/q16577)
- [How Do I Stop CRM Data Decay and Keep My Database Clean in 2027?](/knowledge/q16206)
- [Should I open or buy a Clean Juice franchise in 2027?](/knowledge/q15165)
- [Should I open or buy a ServiceMaster Clean franchise in 2027?](/knowledge/q14748)
How to Set Up Your First Stage Aging Report in Your CRM
Most modern CRMs (Salesforce, HubSpot, Pipedrive) include a built-in stage aging field or report type, but you often need to configure it explicitly. In Salesforce, create a report using the "Opportunities" object and add the "Stage Aging" field to your columns — this calculates days in current stage automatically. In HubSpot, use the "Deal Stage Time" property under custom reports, or install a free app from the marketplace that tracks stage duration. If your CRM lacks a native field, create a custom formula: TODAY() - [Date Entered Stage]. For accuracy, ensure your CRM logs the exact date a deal enters each stage (most do by default when you change the stage dropdown). Set up a dashboard view that filters for deals exceeding 2x your stage median, sorted by longest aging first. Refresh this report weekly — daily is overkill for most B2B cycles and can lead to false positives from deals that legitimately need extra time.
Common Pitfalls When Interpreting Stage Aging Data
Stage aging reports are powerful but easy to misinterpret. The biggest mistake is treating every aged deal as dead — some opportunities genuinely need longer evaluation cycles (e.g., enterprise deals with procurement legal reviews often sit 30-45 days in proposal). Instead of a hard cutoff, use a "traffic light" system: green (within median), yellow (1.5-2.5x median — prompt a check-in), red (over 2.5x median — require manager review). Another pitfall is ignoring stage re-entry — if a deal moves back to a previous stage, the aging clock often resets, masking the true duration. Always check the deal history to see if a rep moved a deal backward to "hide" aging. Also avoid comparing aging across different deal sizes or segments — a $5k SMB deal aging 30 days in demo is far more concerning than a $50k enterprise deal doing the same. Segment your report by deal size band or buyer persona to get meaningful benchmarks. Finally, don't use aging alone — combine it with buyer activity data (emails sent, documents viewed, meetings booked) to distinguish between "stuck" and "patiently progressing."
Actionable Workflow: Cleaning Pipeline Using Stage Aging
Turn your stage aging report into a weekly cleanup routine with three specific actions. First, export the top 20% of aged deals (those past 2.5x median) and assign each to a manager for a 5-minute "stuck deal audit" — the manager asks the rep one question: "What specific step is the buyer waiting on from us?" If the rep can't answer within 30 seconds, the deal likely needs to be moved to a "nurture" or "closed lost" stage. Second, create an automated email or Slack notification that triggers when a deal crosses the 2x median threshold — this prompts the rep to send a "check-in" email or book a next-step call within 48 hours. Third, schedule a 15-minute weekly "pipeline scrub" meeting where your team reviews the top 10 aged deals as a group, deciding to either (a) schedule a specific next action, (b) move to a longer-term nurture stage, or (c) close lost. Teams that run this process consistently report reducing their stuck pipeline by 30-50% within 60 days, while also improving forecast accuracy — because you're no longer counting deals that have been silently dying for months.
FAQ
What exactly counts as "stuck" in a stage aging report? Any deal that has been in a stage longer than 2.5 times the median time for that stage is a red flag. For example, if the median in discovery is 14 days, a deal sitting there for 35 days or more is considered stuck. Past 4 times the median with no buyer activity, it is almost certainly dead.
Do I need special software to run a stage aging report? Most CRM platforms like Salesforce, HubSpot, or Pipedrive can generate this report with built-in filters or simple custom reports. You just need to define stage durations and set a benchmark median for each stage. No expensive add-ons are required.
How often should I review the stage aging report? Weekly reviews are typical for most sales teams, though high-velocity teams may check daily. The key is consistency — reviewing it monthly is too infrequent to catch deals before they go cold. A weekly cadence lets you act before a deal becomes truly stuck.
Can a stage aging report replace a full pipeline review? No, it is a diagnostic tool, not a replacement. It surfaces which deals need attention, but you still need to read notes, listen to calls, or talk to reps to understand *why* a deal is stuck. Think of it as a smoke alarm, not a fire investigation.
What if my team's stage medians are very different from the ones listed? The medians given (7-14 days in qualified, 10-21 in discovery, etc.) are typical for mid-market B2B SaaS, but your own historical data will be more accurate. Calculate your team's actual medians from closed-won deals over the last 6-12 months. If yours are much longer, that may indicate a process issue.
How do I clean the pipeline using this report without demoralizing reps? Focus on the data, not blame. Show the report in a team meeting and ask, "What help do you need to move these deals forward?" For deals past 4x median with no activity, agree together to move them to a "closed lost" or "nurture" stage. Frame it as clearing space for better opportunities, not punishing reps.
Sources
- Gong Labs. *2024 Pipeline Velocity and Stage Aging Study* — median stage durations across 5,000+ B2B SaaS opportunities.
- Clari. *Pipeline Inspection Benchmarks 2024* — buyer-activity overlays and re-opened deal cohort data.
- Salesforce. *Pipeline Inspection Documentation* —
OpportunityFieldHistoryfield tracking and stage-duration calculation. - Pavilion. *2024 RevOps Benchmark Report* — weekly triage cadence impact on cycle time (18-22 percent reduction).
- Force Management. *Command of the Message — Stage Qualification Criteria* — discovery-quality framework referenced in worked example.
- ICONIQ Growth. *2024 Operating Metrics for Cloud Companies* — ACV-tier impact on stage duration (1.5x to 2x for enterprise).
- SaaStr. *Jason Lemkin on Stuck Deals and No-Decision Loss* — the 4x median plus no-activity equals dead heuristic.
- RevOps Co-op. *Stage Aging Triage Playbooks 2024* — Mon-through-Fri workflow patterns from member RevOps teams.