A demo that goes well and then goes quiet is the most common shape of a stalled B2B SaaS deal. The rep leaves the call with positive feedback, books a follow-up, and the thread dies. Two weeks later the opportunity sits in the same stage, at the same amount, with the same close date.
The stall is not the real problem. The problem is that stalled deals stay in the forecast at full value and full probability until someone forces a decision.
Why do deals stall after the demo?
Deals stall after the demo because the demo answered a product question the buyer had, and nobody confirmed a business problem worth funding.The demo is the easiest meeting in the process to get. It requires no budget conversation, no executive sponsor, and no timeline. A curious evaluator can book one on their own authority. When the demo becomes the first substantive meeting instead of a checkpoint inside a qualified process, the deal enters your pipeline carrying a stage label that overstates its maturity.
The second cause is audience. A technical evaluator watches a feature tour and confirms the product works. Nothing in that meeting creates urgency for the person who signs the contract. The deal then waits for a business case that nobody has been assigned to write.
The third cause is access. A champion who cannot get you in front of the budget owner will keep the relationship warm and the deal frozen. Warmth reads like progress in a pipeline review. It is not progress.
How do I tell a stalled deal from a slow deal?
A slow deal keeps generating changes in the record. A stalled deal generates nothing.At ORM we treat meaningful activity as a change in stage, close date, or amount. Emails and logged calls are useful color, but they are cheap to produce and easy to mistake for movement. Field changes map directly to forecast inputs, so they are the ones worth watching.
A deal that takes seven months in a segment where your median is six months is slow. A deal that has not changed a single forecast-relevant field since the demo is stalled, no matter how recent the last logged touch.
Build the check into your pipeline review. For every open deal with a close date in the current quarter, display days since the last stage change, days since the last close date change, and days since the last amount change. Sort by the largest of the three. The deals at the top of that list get the questions.
What does silence on a deal actually predict?
Silence is the earliest slippage signal you get, and it shows up before the close date moves.The strongest confirmed signal that a deal will slip is a rep changing the close date. Once a deal slips from one quarter into the next it becomes less likely to close, even when it is sitting in commit. That signal is dependable, and it arrives late. By the time the date moves, the quarter has already lost the revenue.
The earlier signal is the lack of a signal. No returned email, no answered call, no field changing, no new notes. From the seller's side, a buyer who has stopped responding is a bad sign well before anything in the CRM formally changes. Track deal slippage as an outcome, but diagnose it from the quiet period that precedes it.
Which stall causes can I separate with CRM data alone?
Four patterns cover most post-demo stalls, and each one leaves a different fingerprint in the record.| Pattern in the record | Likely cause | How to confirm | First move |
|---|---|---|---|
| One contact on the opportunity, none added since the demo | Single-threaded with no path to the buyer | Contact roles on the account | Ask the champion for an introduction to the budget owner with a specific agenda |
| Amount unchanged since creation, no quote or proposal sent | Never reached a commercial conversation | Quote and proposal records | Put priced scope in front of the buyer and let the reaction qualify the deal |
| Close date set to the last day of the month or quarter | Date assigned by convention, not by the buyer | Distribution of close dates across open pipeline | Replace with a date tied to a buyer event, then treat any later change as new information |
| Stage advanced with no exit criteria recorded | Stage inflation at the demo step | Your documented stage exit criteria | Move the deal back to the stage the evidence supports |
How do I run a post-demo stall diagnostic in one pipeline review?
Filter to deals that entered the demo stage more than one median stage duration ago and have produced no field change since.1. Pull every open opportunity where the demo has been completed and the stage entry date is older than the segment median. 2. Add the three staleness columns: days since stage change, days since close date change, days since amount change. 3. Split the list by rep and by lead source. Concentration in one rep points to execution. Concentration in one source points to lead quality, which is a sourcing fix rather than a coaching fix. 4. For each deal, ask one question. What does the buyer do next, and on what date? An answer describing seller activity is not an answer.
Deals that fail step four should come out of the committed number, which will move your pipeline coverage and your sales velocity math in the same pass.
What should I do with deals that have already stalled?
Set an aging rule, apply it every quarter, and stop carrying stalled deals at full value.Most ORM customers run a 12 month rule for opportunity aging. Across ORM customer data, 10% or more of pipeline is stale and has not been touched in 12 months. That value still sits inside coverage ratios and makes the quarter look better funded than it is.
At ORM each opportunity is grouped by a machine learning model, and every group gets a predicted curve for how long it takes to close. Those curves run from 1 to 80 weeks. Most of the expectation lands before week 12, and very few groups carry expectation past 52 weeks. A deal sitting far outside the close window for its group is not a late deal. Your own history says it is a dead one.
Three dispositions cover the cohort:
- Reset the deal to the stage its evidence supports and re-qualify it from there. - Recycle it to nurture with a re-engagement trigger and remove it from the forecast entirely. - Close it lost with a reason code so the pattern shows up in your next win-loss review.
None of those options are punishments. They are what makes the remaining pipeline mean something.
Frequently Asked Questions
How long after a demo should I consider a deal stalled?
Use your own median stage duration for that segment rather than a fixed number of days. A deal that has been in the demo stage longer than the median for its segment and has produced no change in stage, close date, or amount is stalled. Enterprise cycles run long by design, so length alone is a weak signal.
What counts as meaningful activity on an opportunity?
At ORM we treat meaningful activity as a change in stage, close date, or amount. Logged calls and emails are useful color, but they are easy to generate without the deal moving. Field changes are harder to fake and map directly to forecast inputs.
Is a rep changing the close date a good sign or a bad sign?
It is the strongest signal that a deal will slip. Once a deal moves from one quarter into the next it becomes less likely to close at all, even when it sits in commit. The signal is reliable but late, which is why silence on the record matters more for early diagnosis.
Should stalled deals stay in pipeline coverage?
Not at full value. Across ORM customers, 10% or more of pipeline is stale and has not been touched in 12 months. That value sits inside coverage ratios and makes them look healthier than the quarter actually is.
What is the fastest way to test whether a stalled deal is recoverable?
Ask for a buyer action with a date attached. A meeting with someone new, a security review kickoff, or a redlined contract all qualify. If the rep can only describe what the seller will do next, the deal is not forecastable yet.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo