Stage aging answers one blunt question on every open deal: how long has this one been sitting here, and is that normal for this stage? The answer drives the Monday review.
Stage aging is the number of days an open opportunity has sat in its current pipeline stage without advancing. It is a core pipeline hygiene signal, measured per deal and benchmarked against the median time deals spend in that stage. The standard flag is two to three times the median: once a deal crosses that threshold it is treated as stuck and surfaced to the next forecast call for review, re-qualification, or honest loss.
Six things to know about stage aging before the next forecast call: what it measures, how it differs from cycle length, and why a modern CRM flags it automatically.
Stage aging is a per-deal counter that resets every time the opportunity advances to a new stage. It measures only the current stage, not the whole journey. A deal that has been in the pipeline for ninety days total but only three days in the current stage has an age of three. That precision is what makes the signal useful.
The standard rule across modern sales teams is to flag any deal whose stage age exceeds two to three times the median time deals typically spend in that stage. If the median proposal-stage time is ten days, a proposal sitting for twenty-five days is a hygiene flag, and one sitting for forty days is stuck.
Sales cycle length measures the total days from first touch to closed-won across the entire pipeline. Stage aging measures only one stage at a time. A healthy cycle can still hide an unhealthy stage. Aging catches the stage-level stall that cycle-length averages hide inside the longer total.
Aging is one of the four classic hygiene checks every well-run pipeline review enforces: stale deals, missing next steps, close-date drift, and stage dwell past threshold. A deal that ages past its stage median is a deal that is probably not advancing on its own. Something has stalled.
A modern CRM calculates median stage time per stage, per segment, and per owner, then flags opportunities that cross the threshold as part of the pipeline board, the forecast view, and the weekly report. The flag is a prompt for a human conversation, not a verdict. The rep still owns the deal.
Aged deals get walked individually on the weekly forecast call. The manager asks four questions on each: what is the specific blocker, is the next step real, does the close date still make sense, and does this deal belong in the committed, upside, or lost column? Honest answers protect the forecast.
Stage aging is simple arithmetic on the deal record, but the quality of the signal depends on how carefully the inputs are maintained. A clean stage-change audit trail, honest stage transitions, and a per-stage median that reflects reality are what turn a raw day count into a hygiene indicator leadership can trust. The cards below walk the mechanics every revenue ops team should have in place.
Stage age equals today minus the date the opportunity entered its current stage. The CRM stamps the stage-entered date on every transition. A deal that moves from Discovery to Proposal on the first of the month and sits in Proposal through the twentieth has a stage age of nineteen days on the twentieth.
Median stage time is the typical number of days a closed deal spent in a given stage. It is computed per stage from historical won deals (sometimes won plus lost, depending on segment). The median is the comparison every stage-age flag is measured against: aged versus the normal time deals spend here.
The widely used threshold is two to three times the median stage time. Two times is the yellow flag, three times is the red flag. A deal that is one and a half times the median is normal variance. A deal at three times median is almost always stalled and almost never recovers without a specific intervention.
Every forward or backward stage move writes a new stage-entered date and resets the stage age counter. The old stage retains its final dwell time in the audit trail for the stage-conversion report. The new stage starts fresh. Deals that bounce between stages generate a dwell record for each visit.
A single company-wide median is almost always wrong. Enterprise deals legitimately dwell longer in Proposal than SMB deals. Modern pipeline tools compute per-segment medians (deal size, industry, product line) so the aged-deal flag reflects what is normal for that specific type of opportunity, not an average mashed across segments.
Teams often report age in four buckets rather than raw days: fresh (under one times median), aging (one to two times), stuck (two to three times), and dead (over three times). The bucket view fits on a dashboard and makes it instantly visible how much of the pipeline is in each state without reading individual counters.
A deal counter would be trivia if it did not change behavior. Stage aging matters because it exposes the specific stage where deals are stalling, flags the forecast line items most likely to slip, and gives the manager a short-list of real conversations to have each week. The cards below cover the operational uses that make aging worth tracking in the first place.
The headline use is identifying the deals that are no longer moving. A rep looking at thirty open deals cannot track dwell on all of them mentally. The aging flag surfaces the five or six that are past threshold, so the pipeline review focuses on real risk instead of walking every card in order.
On the weekly forecast call, every aged deal gets walked individually: what is blocking it, what is the next step, does the close date still hold, and should it stay in commit. Deals that cannot answer those questions move to upside or lost. The forecast tightens because the fiction leaves it.
Aggregating stage-age data by stage shows which stage is backing up across the whole team. If Discovery is clean but Proposal is full of two-times-median deals, the problem is probably the proposal process, not lead quality. Stage aging turns a vague forecast miss into a specific operational fix.
Comparing stage-age distribution across reps surfaces coaching opportunities. One rep whose deals routinely age in Negotiation while peers close faster in the same segment has a specific coachable gap. The data gives the one-on-one a concrete starting point instead of a vague work-your-deals nudge.
Pipeline coverage math improves when aged deals are weighted lower, or excluded, from the quarter's coverage total. A dollar in a fresh deal and a dollar in a six-times-median stuck deal are not equivalent. Discounting the aged portion gives leadership a more honest view of what the pipeline can actually produce.
If a stage is systemically aging across every rep and segment, the issue is probably the stage itself: criteria that are too loose, a handoff that is broken, a step that no longer serves the buyer. Chronic stage aging is a prompt to redesign the stage, not just push the deals through it.
The point of flagging a deal is to resolve it, not just to notice it. The playbook below is the common pattern across well-run revenue teams for handling an aged deal: diagnose the specific blocker, apply the right intervention, and either revive it with a committed next step or move it out of commit so the forecast stops lying. Automation and Strkr AI can surface the flag and suggest patterns, but the human conversation is what resolves the deal.
Rep and manager answer four questions on every aged deal: is the champion still engaged, has the buying problem changed, is the close date still real, and is there a specific action blocked. The answers point to the intervention. Vague answers are their own signal that the deal is probably not real.
The most common fix for an aged deal is a specific next step the rep commits to by name and date. Call the CFO Wednesday after their board meeting revives a Proposal that has been sitting. A vague follow-up-next-week does not. The quality of the next step predicts whether the deal moves.
Some aged deals need the manager or an executive sponsor from the Strkr-side to re-engage the buyer directly. Executive-to-executive outreach breaks stage dwell faster than another rep email. The playbook names when to escalate and which executive owns the outreach for each segment.
A deal that cannot answer the four diagnostic questions and has aged past three times median is almost always lost. The right move is marking it closed-lost with a specific reason (budget, timing, competitor, no decision, product fit) so the loss feeds the quarterly review and the pipeline stops lying about coverage.
Occasionally an aged deal is not stuck, it is misstaged. A deal flagged in Proposal that never actually had a champion identified belongs back in Discovery with the stage age reset. A backward stage move is honest, not a demotion. The clean data is worth the small ego cost.
Strkr AI looks at how similar aged deals resolved historically (revived, moved to lost, pushed to next quarter) and offers a suggested path on each flagged deal. The suggestion is a prompt for the manager, not a decision. The rep and manager still choose the action; the signal just surfaces the pattern.
Strkr computes stage aging automatically on every open deal, benchmarks it against your per-segment median, flags the ones past two to three times normal, and surfaces them to the pipeline board, forecast view, and weekly report. Start free, connect the pipeline, and run the next forecast call on the deals that actually need attention.
Stage aging is the number of days an open opportunity has been sitting in its current pipeline stage without advancing. It is measured per deal, resets every time the opportunity moves to a new stage, and is compared against the median time deals typically spend in that stage. A deal whose stage age exceeds two to three times the median is flagged as stuck and gets reviewed on the next forecast call.
Stage aging equals today minus the date the opportunity entered its current stage. The CRM writes a stage-entered timestamp on every forward or backward stage transition, which resets the counter. A deal that moved into Proposal twenty days ago and has not advanced since has a stage age of twenty days. The number is compared to the historical median for that stage to decide whether it is aging.
The widely used rule is two to three times the median stage time. Two times median is the yellow flag that prompts a hygiene check. Three times median is the red flag that treats the deal as stuck. If the median time in a stage is ten days, a deal at twenty days gets a yellow flag and one at thirty days or more gets a red flag. The thresholds are tuned per segment to avoid false positives on legitimately longer enterprise cycles.
Sales cycle length is the total number of days from first touch to closed-won across the entire pipeline. Stage aging is the number of days spent in just one stage at a time. A deal with a reasonable total cycle length can still have a serious stage-age problem hiding inside one specific stage. Cycle length is a summary average; stage aging is the stage-level signal that shows where the stall actually is.
Because a sales rep looking at thirty open deals cannot track dwell time mentally, and a manager reviewing a hundred deals across the team definitely cannot. Auto-flagging surfaces the small subset of deals past threshold so the pipeline review and forecast call focus on real risk. The flag is a prompt for a human conversation, not a verdict. The rep and manager still own the deal and the resolution.
Aged deals are the deals most likely to slip or lose, so a pipeline carrying many aged deals in commit will miss its forecast. Pulling aged deals out of commit, discounting them in coverage math, and resolving them each week (revive, push, or lose) tightens the forecast dramatically. Teams that enforce aging thresholds routinely see forecast accuracy improve within one or two quarters because the fiction leaves the number.
Yes. Enterprise deals legitimately spend longer in later stages than SMB deals, and some product lines have inherently longer sales motions. A single company-wide threshold produces false positives on normal enterprise motion and false negatives on fast SMB cycles. Modern pipeline tools compute per-segment medians (deal size, industry, product line) so the aging flag reflects what is normal for the specific type of opportunity.
Walk the deal with the rep and ask four questions: is the champion still engaged, has the buying problem changed, is the close date still real, and is there a specific blocked action. The answers point to the intervention: a specific next step, an executive sponsor, a reset to an earlier stage, or an honest closed-lost with a reason. Aged deals do not resolve by waiting; they resolve by a named action or a clean loss.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
