Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Sales Forecasting

Deals Stuck in the Negotiation Stage: How to Diagnose What Is Blocking Them

Pete Furseth 6 min read
deal slippagepipeline hygienesales process
Deals Stuck in the Negotiation Stage: How to Diagnose What Is Blocking Them
Home/ Blog/ Deals Stuck in the Negotiation Stage: How to Diagnose What Is Blocking Them

Why do deals get stuck in the negotiation stage?

Deals stall at negotiation because a decision moved to someone who was never in the deal, or because the value case was never strong enough to survive procurement. Negotiation is where the buying process stops being a conversation with your champion and starts being a review by finance, legal, security, and whoever owns the budget line. A deal that arrives there without those people already engaged does not fail on price. It fails because nobody outside the champion's team has a reason to prioritize it.

The second pattern is a timing mismatch. The buyer's need is real, but the funding event sits in a future period, so the deal parks at the last stage until the money exists.

Put this to work on your numbers
Run your own numbers with the free Sales Commission Calculator, then see how ORM builds it into a custom model.

How do you tell a slow deal from a dead one?

Compare the deal to how long deals like it normally take, not to a fixed number of days. At ORM, each opportunity gets grouped by a machine learning model and every group carries a predicted close curve. Those curves span 1 to 80 weeks, most of the expectation falls before week 12, and very few groups have meaningful expectation past 52 weeks. A deal that is 15 weeks into a group whose curve peaks at week 8 is not slow. It has passed the point where deals in its group close.

Fixed rules miss this. An enterprise security deal at week 20 can be perfectly healthy while a mid market renewal expansion at week 20 is finished.

What counts as meaningful activity on a deal?

ORM counts a change in stage, close date, or amount as meaningful activity, and nothing else. Calls, emails, and meeting invites are rep effort. They tell you the seller is working, not that the buyer is moving. A record full of logged activity with no change to those three fields is the signature of a deal being carried rather than progressed.

The earliest warning sign is the absence of any signal at all. No data changing, no notes, no reply to the last three emails. From the seller's side, if the buyer is not returning email, not taking calls, and not texting back, the deal has already changed status. The CRM just has not caught up.

What is actually blocking the deal?

Name the blocker before you build a plan, because each blocker has a different test and a different action.
BlockerWhat you see in the dataThe test to runThe action
No economic buyer engagedChampion is the only named contactAsk for a call with the budget owner this weekTrade something for access or requalify
Procurement or legal queueStage unchanged, close date pushed onceAsk for the redline owner and the queue positionGet a dated commitment from the queue owner
Security or IT reviewLong gap after a technical winConfirm the review is scheduled and staffedEscalate to your own security lead
Budget timingClose date pushed to a period boundaryAsk which funding cycle the money sits inReforecast to the real period, do not discount
Competitor still activeAmount revised downward lateAsk what changed since the proposalRebuild the differentiated case or exit
Priority lossNo response across channelsAsk the champion what moved ahead of youPark the deal and stop forecasting it

How many close date pushes are too many?

The best single predictor of slippage is a rep changing the close date, and the second push is the one to act on. A deal that slips from one quarter to the next is less likely to close than it was before the slip, even when it still sits in commit. The rep's confidence does not update fast enough, so the forecast keeps carrying a deal whose odds have already changed.

Track pushes as a field, not a memory. Count the number of close date changes on every open opportunity and sort the late stage pipeline by that count. The deals at the top are your forecast risk, and they are usually the same deals the sales leader has been describing as sure things for two quarters. The mechanics are covered in more depth under deal slippage.

How should stuck deals be handled in the forecast?

Take them out of commit and reweight them against how deals in their group actually behave, not against rep confidence. Rep confidence is an input. It is not a probability. A stage based weighted pipeline will overstate a stalled negotiation deal, because stage weighting assumes deals in that stage are moving. A stalled deal is in the stage without the motion that gives the stage its weight.

The cleaner approach is to separate the number into what will close from deals already moving, what still has to be created and closed this period, and what you would be pulling forward from a future period to save the current one. Stalled negotiation deals belong in none of those buckets until the blocker has a name and a date.

What should you do this week?

Force a decision on every late stage deal that has not changed stage, close date, or amount in 30 days. For each one, get the blocker named by the buyer rather than assumed by the rep, get a dated next step on the buyer's calendar, and set an exit date after which the deal moves out of the forecast. If the buyer will not give you a date, that is the answer.

Clearing stalled deals costs you nothing in real revenue and buys back forecast accuracy immediately. The revenue was never there. Only the number was.

Frequently Asked Questions

How long can a deal sit in negotiation before it is dead?

There is no universal number, because close timelines vary by deal type. ORM models a close curve for each group of similar opportunities, and those curves run from 1 to 80 weeks with most of the expectation landing before week 12. The practical test is whether a deal has passed the point on its own curve where deals like it normally close, not whether it has crossed a fixed day count.

What counts as real activity on a stalled deal?

ORM treats a change in stage, close date, or amount as meaningful activity. Logged calls and emails are inputs, but they are easy to generate and do not indicate the buyer moved. A deal with heavy rep activity and no change to stage, date, or amount is stalled regardless of how busy the record looks.

Should a stuck negotiation deal stay in commit?

Only if a specific blocker has been named and a dated resolution exists. A deal in commit with no identified blocker and no scheduled next step is a forecast liability. Move it to best case, keep working it, and remove the dependency from the number you are committing to.

Does pushing the close date make a deal less likely to close?

Yes. When a deal slips from one quarter to the next it is less likely to close, even when the rep still calls it commit. Treat the close date change itself as the signal rather than waiting for a stage change or a loss.

What is the difference between a stalled deal and a stale deal?

A stalled deal is still active in the buyer's world but has stopped moving on a specific blocker. A stale deal has had no meaningful change for a long stretch, often 12 months or more. ORM sees more than 10 percent of pipeline sitting untouched for 12 months at many customers. Stalled deals get worked. Stale deals get closed out.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

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