Three RevOps reviews in the last fortnight, three different companies, three different industries, one identical finding: roughly half of the open pipeline was past its expected close date. Not in commit. Not pushed once with a note. Past close date, sitting in an active stage, counted toward coverage. That is a stale pipeline. The forecasts derived from those pipelines were, to put it gently, fiction. And in every case, the symptom had been visible for months. Nobody had run the stale pipeline diagnostic.
How much of a typical inherited SaaS pipeline is stale?
Across three RevOps reviews Checkpoint GTM ran in a single fortnight, roughly 50% of open pipeline sat past its expected close date at every company. A pipeline that stale makes the forecast fiction. SaaStr's 2025 readout shows B2B SaaS sales cycles ran 19 to 25 weeks, so deals quietly age past close before anyone re-dates them.
Sales cycles in B2B SaaS got longer through 2025 and only recently started to compress again. SaaStr's mid-year readout had the cycle stretching from 25 weeks in H1 to 19 weeks in H2, which sounds like progress until you remember what that means for any pipeline whose stage definitions were written for a 12-week motion. The deals do not move faster because the rep is more motivated; they linger in stages that have no exit criteria, the close dates roll silently into next quarter, and the coverage ratio looks healthy right up until the moment the forecast misses by 30%.
This is not a forecasting problem. The forecast is downstream. The Harvard Business Review's foundational piece on forecast accuracy from a few years ago pointed at the same upstream cause: salespeople withhold information about deals that are not going well and cling to optimistic close dates on troubled ones. The longer a deal has been in pipeline, the lower its probability of closing, and the more aggressively most CRMs hide that signal under a coverage chart.
The issue is that everyone wants to debate the forecast methodology when the pipeline itself has not been triaged. So let me reframe it: there is no useful forecast review without a stale pipeline diagnostic first. The diagnostic is the cheap, falsifiable thing. Run it before the meeting, or do not have the meeting.
The stale pipeline diagnostic, in four numbers
Checkpoint GTM runs four queries in five minutes on any inherited HubSpot or Salesforce pipeline: percentage of deals past close date, median deal age per stage, count of active stages, and percentage with no activity in 14 days. Each resolves to one number, and together they show whether the forecast rests on real data.
For any HubSpot or Salesforce pipeline, four queries done in five minutes will tell you whether the forecast you are about to discuss is built on real data or wishful thinking. Each one resolves to a number. Treat the numbers as a triage signal, not a verdict. None of the four require new tooling; every modern CRM exposes them as a saved view or a custom report. The reason most teams do not have them on a dashboard is not that the data is hard to pull. It is that nobody wants to see a stale pipeline named for what it is.
1. Percentage of open deals past close date
The single most diagnostic number. Pull every open deal in the active sales pipeline. Compare expected close date to today. Anything past today is overdue. If this number is over 25%, the forecast is unreliable and there is no point arguing about methodology. If it is over 40%, the pipeline is not being managed at all and the next conversation is with the sales manager, not the RevOps team.
2. Median age of open deals, by stage
For every active stage, compute the median number of days deals have been sitting in that stage. Compare that number to the stage's published expected duration. If a stage's expected duration is 10 days and the median is 35, that stage either has no exit criteria, the exit criteria are not being enforced, or the stage definition is wrong. None of those are a forecast problem; all of them feed into the forecast being wrong.
3. Number of distinct stages in the active pipeline
Count the active deal stages, excluding closed-won and closed-lost. The right answer is between four and six. The OpenView research on stage definitions is clear about this: more than six stages produces fewer reliable stage transitions, not more granularity. Below four, you do not have enough signal to forecast. Above six, you have given reps somewhere to park a deal indefinitely. If the count is over eight, the stage architecture is the problem before the data is.
4. Percentage of open deals with no activity in the last 14 days
Pull every open deal and check last-engagement date: email, call, meeting, note, task completion, any logged activity. Deals with no activity in two weeks are not in pipeline; they are on a list. If this number is over 30%, the coverage ratio you are reporting upstream is overstating reality and the next quarter's forecast is going to embarrass somebody.
What do the four stale-pipeline numbers look like on a real account?
In one DACH mid-stage HubSpot review, Checkpoint GTM found the four numbers at 50% past close, 42% inactive, a 35-day median against a 10-day stage, and eleven active stages. Four hours of cleanup, one-page stage definitions, and a 14-day inactivity rule brought every number into band within eight weeks; the forecast then landed within 10%.
A B2B SaaS company in DACH at roughly the mid-stage, going through a HubSpot review, had the four numbers come in at 50%, 35 days against a 10-day expected duration, eleven active stages, and 42% no-activity, a textbook stale pipeline. None of those numbers were a surprise to anyone in the room when we put them on the screen. Three of them had been visible on dashboards the entire year. The team had a forecast accuracy problem because the team had a pipeline hygiene problem, and the pipeline hygiene problem was a stage architecture problem with a stage definition problem on top of it. The fix was not a better forecasting model. The fix was four hours of pipeline cleanup, a one-page stage-by-stage definition document, and an inactivity rule that automatically pushed deals to a re-engagement stage at the 14-day mark. After eight weeks, all four numbers were inside the acceptable bands. The forecast started landing within 10%. Nothing about the forecasting methodology had changed.
The playbook
For any team about to walk into a forecast review with a pipeline that has not been audited in the last quarter:
- Run the four numbers before the meeting. The query takes five minutes per pipeline in HubSpot or Salesforce. If any of the four is in the red, the next agenda item is the pipeline, not the forecast.
- Force a close-date update on everything past due. Every deal past its close date gets one of three actions before the meeting: closed-lost, moved to next quarter with a written reason, or escalated to the rep's manager for a real conversation. No fourth option.
- Write the stage definitions on one page. Every stage gets a one-sentence definition, an entry criterion, an exit criterion, and an owner. If you cannot write the page in a working session, the stage architecture is the problem.
- Cap the active-pipeline stage count at six. Consolidate any stage that does not survive the definition exercise. Pre-deal stages: lead, MQL, SQL: belong in the lifecycle, not the pipeline. The pipeline is for deals.
- Set an inactivity rule. Any open deal with no logged activity in 14 days routes to a re-engagement queue, a manager alert, or an automatic close-lost depending on stage. The cost of false negatives here is low; the cost of a fluffed pipeline is high.
- Re-run the four numbers monthly. Pipeline hygiene is not a project, it is a discipline. If the four numbers stay in band, the forecast methodology can be debated on its merits. If they do not, the forecast methodology is downstream noise.
If the playbook looks lightweight, it is. The cost is in the discipline of running it before every forecast review instead of after the miss. A stale pipeline does not become healthy because the methodology improves; it becomes healthy because somebody owns the four numbers.
Where Checkpoint comes in
Most of our revenue operations engagements start with a version of this diagnostic. The four numbers, run against an inherited HubSpot instance, predict where the rest of the cleanup is going to land more reliably than any framework we own. If your forecast has been wrong by more than 10% for two quarters in a row and the conversations keep being about methodology, the conversation you actually need is upstream: in the pipeline, not in the model. Get the four numbers first.
Sources
- "Slumping Deal Velocity? Embrace Contract Management to Generate Revenue." SaaStr, September 2025. saastr.com
- "From AI Billions to Sales Struggles: The Top 10 SaaStr Posts of The First Half of 2025." SaaStr, July 2025. saastr.com
- "Sales Teams Aren't Great at Forecasting. Here's How to Fix That." Harvard Business Review, March 2019. hbr.org