Salesloft estimates 19.7% of pipeline faces stalls, slipped close dates, or execution breakdowns; approximately 32% can instantly diagnose a stalled deal.
Key takeaways
- Compare scope: the 19.7% estimate combines stalled deals, slipped close dates, and other execution breakdowns.
- Check diagnosis: use approximately 32% as a reference for instant diagnosis, rather than a target.
- Keep context separate: the 35.2 touch average concerns creating a qualified opportunity.
- Count open deals with a stalled or slipped close date and record your definition before calculating their share.
Those two figures work as points of comparison, not as targets for your team. Your own stalled share and diagnosis rate belong beside them, and both need the same definition of stalled. The survey numbers frame the question, while your own counts show where your pipeline stands.
Why a stalled deal needs a number in review
A slipped close date is often explained in a single sentence during a deal review, and that sentence rarely comes with a reference point. A buyer went quiet, a close date moved, or a champion went silent, and the meeting moves on. Without a second figure beside the explanation, the room cannot tell whether one slipped deal is unusual or ordinary for the quarter.
A reference point does not need to be perfect to be useful, but it does need to be counted the same way each time. If the definition of a stalled deal changes from one review to the next, the trend shows the change in the rule rather than the change in the pipeline. A written definition kept with the deal review notes is the simplest safeguard.
Salesloft's estimate is broad, and according to Salesloft it covers stalled deals, slipped close dates, and other execution breakdowns. Your own count should use the same breadth if the comparison is meant to be fair. A count of stalled deals alone and a count that also includes slipped close dates answer different questions, so write down which one you used.
Tasks belong in the same picture. Aviso's product page, according to Aviso, says tasks and next steps assigned tend to get stuck in one platform and never get acted upon. A reviewer who reads only the deal stage may miss where a follow-up actually sits, so the review question should name the platform where each open task lives.
See weekly deal review filters, and keep the filter list beside the stall count in your notes. Keeping the two together lets the same deals appear in both places each week, so the next review can be compared with this one. The pairing is a recommendation, not a rule from any source.
Who answered the survey and when
The scope of the survey shapes how far these figures can travel. Salesloft worked with Censuswide to survey 500 U.S. sales and revenue decision-makers at organizations with 200 or more employees, according to Salesloft, and that group defines the comparison.
The respondents are described as sales and revenue leaders, and the questions covered a wide range of topics. The survey, according to Salesloft, covered what those leaders are seeing across pipeline generation, deal execution, forecasting, seller performance, coaching, AI, and revenue technology strategy.
Timing is part of the context. Fieldwork, according to Salesloft, was conducted between May 28 and June 10, 2026. A figure gathered in that window describes what leaders reported during those weeks, so a later pipeline should be compared with it carefully.
The employee floor is the boundary to keep in view. The survey covered organizations with 200 or more employees, so it does not establish a benchmark for smaller firms. A firm near that line should check its headcount before treating the comparison as direct.
A useful practice is to write your company's headcount next to your own stalled figures in the review notes. That note shows whether your organization sits inside the range the survey covered, so the reader can judge the comparison without guessing. It is a small detail, but it changes how the room reads the numbers.
Figure one: 19.7% of pipeline affected by stalled deals
The first figure, according to Salesloft, is that an estimated 19.7% of pipeline is affected by stalled deals, slipped close dates, and other execution breakdowns. It is the figure most likely to be quoted in a review, so its definition deserves attention.
The single percentage combines three kinds of problem, and that combination is the detail to keep in mind. A deal can be stalled, a close date can slip, or an execution step can break down, and the one share does not show which of those dominates your own pipeline.
A simple method is to count open deals with a stalled or slipped close date, then divide that count by total open deals. This gives a local deal-count share, which may differ in scope and measurement from the survey estimate. Keeping the same open-deal scope each time lets the share be read across reviews.
A stable definition matters more than a precise one. If you add a new kind of breakdown to the count, note the change, because a higher or lower share after that change would reflect the rule rather than the pipeline.
The number you get is a comparison point. Any gap from 19.7% works as a question for the room to explore, not as a verdict on the team.
Figure two: approximately 32% can diagnose a stall
The second figure, according to Salesloft, is that only approximately 32% can instantly diagnose why a deal has stalled. It measures diagnosis, not the number of stalled deals.
The word instantly carries the weight here. For your own review, decide whether instant diagnosis means explaining the cause before searching past records.
A practical test is to pick a few stalled deals from the last review and write one sentence on the cause of each. Each sentence should be written from memory before anyone opens the record, so the test shows how instant the diagnosis really is.
Track how often the cause sentence is clear without a record search. A cause that needs a search through notes, emails, or call logs would fail this local test; check the explanation against the record afterward. Record each result as a yes or no, then divide the yes count by the number of deals tested.
Where the information sits matters for this test. Aviso's product page, according to Aviso, describes a feature to pull up past calls, summaries or snippets all in one place. It is worth checking whether your own platform offers that view before judging a diagnosis slow.
Context figures: 35.2 touches and 62% attainment
This section covers two context figures that do not measure stalled deals. The first is a touch count, and according to Salesloft, teams average 35.2 touches to create a qualified opportunity.
A touch count is a different kind of number from a stall share. A high touch count therefore should not be read as a stall signal, and a low one does not show clean pipeline.
The second context figure, according to Salesloft, is that average quota attainment is approximately 62%, while the top 10% of sellers generate 47.4% of closed-won revenue.
The 62% figure is not a measure of stalled deals. It describes attainment against quota, so placing it beside your stalled share would blend two separate questions in one meeting.
It is useful to keep these context figures in a notes section rather than the headline. A reader who sees 62% next to a stall share may read the two as linked. A separate line for context keeps the stall discussion clean.
Limits of each figure and how to compare your own
Each figure has its own limit, and the limits matter more than the headline numbers. The 19.7% share combines a set of problems, the 32% rate concerns instant diagnosis, and the 35.2 touch count sits outside the stall question.
Keep survey findings separate from product claims when reviewing these pages.
| Publisher | Page | Figure or claim |
|---|---|---|
| Salesloft | Revenue benchmark report | estimated 19.7% of pipeline affected by stalled deals, slipped close dates, and other execution breakdowns; approximately 32% can instantly diagnose a stall |
| Aviso | AI Revenue Command Center | Tasks and next steps assigned tend to get stuck in one platform |
| Xactlycorp | Intelligent Revenue Platform | flags forecast risks |
Scope is the first limit, and according to Salesloft, the survey covered 500 U.S. sales and revenue decision-makers at organizations with 200 or more employees.
Wording is the second limit. The figures use approximately and estimated, so avoid treating them as exact counts or precise cut-offs in your review.
The Intelligent Revenue Platform page describes a Fleet of AI Agents, according to Xactlycorp, that surfaces performance gaps, flags forecast risks. That statement is a claim to verify before it enters your stall count, not a result. The documentation behind that claim is the thing to check.
The comparison method is simple: use the same definition, the same period, and the same scope, then compare the two numbers.
Illustrative example: count affected deals
In an illustrative pipeline of 200 open deals, 40 have a stalled or slipped close date. Divide 40 by 200 to calculate the local share. Label it as a deal-count measure, record the definition, and keep other execution breakdowns separate unless your counting rule includes them.
Next step for your deal review
Today, count open deals in your current pipeline with a stalled or slipped close date, then divide that count by total open deals. Record the count, the total, and the definition you used so the next review repeats the method. Keep a close date change log beside the calculation.
Questions about stalled deal survey figures
Who answered the survey?
The survey, according to Salesloft, covered 500 U.S. sales and revenue decision-makers at organizations with 200 or more employees. The sample is a scope to note, so the figures describe that group rather than every firm.
What share of pipeline was affected by stalled deals?
The source, according to Salesloft, estimates that 19.7% of pipeline is affected by stalled deals, slipped close dates, and other execution breakdowns. Ask whether your own measure counts deals or pipeline value before comparing it with that estimate.
How many teams can diagnose a stall right away?
The source, according to Salesloft, reports that only approximately 32% can instantly diagnose why a deal has stalled. A useful check is to test how many recent stalled deals your team can explain in one sentence each.
When was the survey fielded?
A pipeline from a later period falls outside that window, so compare figures with that date in mind. It is useful to note the date beside your own figures so the reader knows the period.
Does the 35.2 touch figure measure stalled deals?
No, the 35.2 figure is a touch count, not a stall measure. Teams average 35.2 touches to create a qualified opportunity, according to Salesloft, and that average appears beside the stall figure in the same source.
Should my team treat 32% as a target?
No, the 32% figure is a point of comparison, not a target. Track your local diagnosis test consistently so changes between reviews can be examined.