Why Deals Stall in Pipeline (And How to Unstick Them)

Deals stall in pipeline for a different reason at every single stage, and the fix that works at discovery will do nothing for a deal stuck in procurement. That is the whole problem with generic “follow up more” advice. A stalled deal is a symptom, and if you treat the symptom without diagnosing the stage-specific cause, you just annoy a buyer who was never going to move for the reason you think they were. Over 5+ years selling B2B SaaS and closing north of €4M, I have watched hundreds of deals freeze. The good news: stalls are predictable. Each stage fails in its own way, and each has a specific unstick move.

Let me walk you through the diagnosis stage by stage, the way I actually do it when I audit someone’s pipeline.

First, define what “stalled” even means

Before you fix anything, you need a real definition, not a feeling. A deal is stalled when it has been sitting in one stage significantly longer than your average for that stage, with no meaningful buyer-initiated activity. Not “I haven’t heard back in a while.” An actual number.

If you do not have per-stage cycle times, that is your first job, and it starts with clean sales pipeline stages and definitions so every deal means the same thing when it moves. You cannot spot an outlier if every rep interprets “proposal sent” differently.

Stage 1: Stalled in discovery, you never found real pain

The most common early stall, and the one people misdiagnose the most. The deal goes quiet after a great first call. You thought it went well. They said “this looks interesting, let me think.” Then silence.

What actually happened: you found a mild inconvenience, not a bleeding-neck problem. “Interesting” is the polite word buyers use when something is nice-to-have. Nobody ghosts a solution to a problem that is genuinely costing them money or sleep.

The diagnosis question: can you write, in one sentence, what this deal costs the buyer if they do nothing? If you cannot, you never qualified the pain, you qualified the interest.

The unstick move: go back and quantify inaction. Not “here are more features.” Send something like: “Hey [first name], I have been thinking about the [specific process] you mentioned. If I understood right, that is roughly [X hours per week] across your team. At your rates that is around [Y per month] you are spending to keep it the way it is. Is that number roughly right, or am I off?” You are not selling. You are making the cost of doing nothing visible. Deals move when staying still starts to hurt.

Stage 2: Stalled after the demo, no single owner

The demo lands, everyone nods, and then nothing. Nine times out of ten this is a champion problem. Your contact loved it but they cannot, or will not, drive it internally. They are a fan, not a buyer.

The unstick move: arm your contact or go around them, gently. Give your fan the internal-selling tools they need: a one-page business case, a short async video they can forward, exact numbers. If that fails, ask the honest question: “Who else needs to be comfortable with this before it can move forward?” If they dodge that twice, you do not have a deal, you have a demo attendee.

Stage 3: Deals stall in pipeline at the proposal, sticker shock or vague scope

Proposal sent, then the temperature drops. This stall has two flavors and they need opposite fixes, so diagnose before you react.

Flavor one, price shock. The value you built in discovery did not match the number on the page. This is almost always a discovery failure showing up late. You cannot fix a value gap with a discount, you just confirm the price was made up. Instead, reconnect the number to the cost of inaction you established earlier: “The investment is [X]. Against the [Y] this is costing you now, you are net positive inside [Z] months.”

Flavor two, vague scope. The proposal was a wall of features and the buyer cannot picture what actually happens after they sign. Fear of a messy rollout freezes more deals than price ever will. Fix it by making the next 30 days concrete: who does what, when, and what they will see working by day 14.

Stage 4: Stalled in procurement and legal, real but manageable

This one is genuinely not your fault, but it is still your job. Big deals hit security reviews, legal redlines, and procurement queues. My biggest single deals, one of them €120K, all sat in this swamp for weeks. The stall here is structural, not emotional.

The unstick move for a procurement stall is almost never persuasion. It is project management. You are removing friction, not overcoming objections.

Stage 5: Verbal yes, then radio silence

The cruelest stall. They said yes. They meant it when they said it. Then a competing priority ate their week, and momentum quietly died. This is not a lost deal, it is a deprioritized one, and those are winnable if you move fast.

The unstick move: create a reason to act now that is real, not manufactured urgency. Manufactured urgency (“this price expires Friday!”) smells like desperation and buyers hate it. Real urgency is tied to their world: a hiring plan, a quarter starting, an integration window, a problem that gets worse each month you both wait. Reconnect the deal to a deadline that already exists in their business.

The system underneath all of this

Here is the honest bit. You can memorise every unstick move above and still have a pipeline full of frozen deals, because individual heroics do not fix a structural leak. If deals stall in pipeline at the same stage over and over, that is not a rep problem, that is a process problem.

Two things fix it at the root. First, a repeatable sales process with clear exit criteria per stage, so a deal cannot advance until the real blocker is cleared. No more “proposal sent” to a fan with no budget. Second, a CRM set up properly for an early-stage SaaS that actually tracks time-in-stage, so stalls surface automatically instead of you discovering a dead deal three months late.

Then you look at the pattern on a schedule. This is exactly what a proper sales QBR is for: not celebrating wins, but staring at where deals consistently freeze and fixing the stage that keeps failing. When I ran this discipline with Venture Challenge, the clarity on where deals stalled was a big part of how we drove 170 qualified leads in 90 days across 25 teams at €5K each. You cannot improve a stage you are not measuring.

The move most reps skip: close the loop honestly

The hardest and most effective unstick tactic is also the simplest. For a deal that has gone truly cold, send the direct, low-ego message: “Hey [first name], I do not want to keep chasing something that is not a priority anymore. Totally fine if the timing is off or this is no longer on the table, just let me know either way and I will stop bugging you.”

This does two things. It gives the buyer permission to be honest, which most of them secretly want, and it flushes fake deals out of your pipeline so you stop lying to yourself in the forecast. With IKI Health, being ruthless about which deals were real versus hopeful is part of how we turned month one into 30+ calls and 2 high-ticket deals. A clean pipeline is not a smaller pipeline, it is an honest one, and honest pipelines are the only kind you can actually manage.

Half the time, that permission-to-say-no email revives the deal, because it turns out they were just buried, not gone. The other half, you get a clean no and your week back. Both outcomes beat a deal rotting in stage three for a quarter.

Where to start

Do not try to fix all five stages at once. Pull your pipeline, find the stage where the most deals are currently frozen, and apply just that stage’s unstick move to every deal sitting there. One stage, this week. Then build the process so it stops happening.

If you want a second set of eyes on where your deals actually die, that is exactly what I do. Book a sales audit and I will diagnose your pipeline stage by stage with you, or see how the revenue operations side of things ties the whole system together over on the services page. Let’s find the stall and kill it.

Frequently Asked Questions

How do I know if a deal is genuinely stalled or just slow?

Compare the deal's time in its current stage against your average for that stage. If it has been sitting for more than 1.5x your normal cycle time with no inbound activity from the buyer, it is stalled, not slow. A slow deal still has movement, replies, forwarded emails, questions. A stalled deal goes quiet.

Should I keep working a stalled deal or mark it closed-lost?

Give it one clear, honest close-the-loop attempt first. Ask directly whether the priority has changed or the project is dead. Most reps never ask, so the deal rots in the pipeline for months. If you get no answer after that direct attempt, mark it closed-lost and move on. A clean pipeline beats a hopeful one every time.

What is the single most common reason B2B SaaS deals stall?

No compelling reason to change now. The buyer likes your product but the pain of staying put is still lower than the pain of buying, onboarding, and getting budget signed off. You unstick this by quantifying the cost of inaction, not by adding more features to the pitch.