How to identify a deal at risk before it stalls

A deal at risk announces itself in behavior long before it shows up in the pipeline. The close date is the last thing to move, not the first — by the time a rep pushes it a quarter, the deal has usually been drifting for a month. The signals that predict a stall are all present earlier, and none of them live in a CRM field.

Here are the six that matter most, roughly in the order they tend to appear, and what to do about each one.

1. Response latency stretches

The most reliable early signal is also the dullest: a contact who replied within four hours for six weeks now takes three days. Nothing was said. Nothing changed in the record. But the deal's priority inside that organization moved, and the reply gap is the first place it shows.

What matters is the change, not the absolute number. Some buyers are slow throughout and close on time. Measure each thread against its own baseline.

What to do: don't send another check-in. A slowing champion is usually a champion who has lost internal traction, and a fourth "just circling back" makes it worse. Give them something they can forward — a business case, a rollout plan — that does the internal selling they can no longer do alone.

2. The economic buyer never actually shows up

Count the meetings the person who signs has attended. On a healthy enterprise deal at proposal stage, that number is rarely zero. When it is, the deal is being evaluated by people who can recommend but not decide, and the recommendation will eventually meet a budget conversation it wasn't built for.

This one is easy to miss because the deal feels good: your champion is enthusiastic, the technical evaluation is going well, and the CRM shows steady activity.

What to do: stop advancing the stage until you have executive access, and ask for it as an exchange rather than a favor — an executive alignment session, a mutual action plan review, something that gives them a reason to attend.

3. An objection gets raised more than twice

A concern raised once is a question. Raised three times, it's a blocker being politely restated because your answer isn't landing.

This is the pattern that costs the most deals and is hardest to see from inside a single conversation. Each individual call feels fine — the objection came up, you handled it, the meeting ended cordially. It's only when you look across the whole deal that you notice the buyer has asked about implementation timelines on three separate occasions and each time received a slightly different answer.

The third time an objection comes up, the problem is no longer the objection. It's that nobody noticed it was the same one.

What to do: name it explicitly. "You've asked about the rollout timeline a few times — I don't think I've given you an answer you can take to your team. What would a convincing one look like?" Buyers reward this. It's also why reading calls in deal context matters more than analyzing them one at a time.

4. Procurement arrives before executive alignment does

Procurement entering a deal is normally a good sign — it means someone decided to buy. It's a bad sign when it happens before the economic buyer has engaged, because it usually means the deal has been delegated downward rather than championed upward.

A procurement-led deal without executive sponsorship optimizes for one thing: price. You will be benchmarked, asked for concessions, and compared to alternatives on a spreadsheet where your differentiation doesn't appear.

What to do: get the economic buyer into the conversation before you send revised pricing. Once you've discounted into a procurement process, you've set the anchor and lost the ability to trade concessions for commitments.

5. The champion goes quiet after a specific moment

Silence is informative, but the timing is what makes it diagnostic. A champion who goes quiet after you send pricing is telling you something different from one who goes quiet after a bad demo, or after an internal reorg they haven't mentioned yet.

Anchor the silence to the last thing that happened. Most quiet periods have a cause that was visible three days earlier, in an exchange that seemed unremarkable at the time.

What to do: route around rather than through. If your champion has stalled, a light-touch message to a secondary contact often surfaces what actually happened — a budget freeze, a competing priority, a reorganization — faster than four more emails to the same person.

6. Seller behavior changes under pressure

The signal nobody looks at is the one coming from your own side. Reps under quota pressure discount earlier, skip discovery, and answer objections with concessions instead of information. That behavior predicts outcomes as reliably as anything the buyer does.

The clearest version: a buyer raises an implementation concern and receives a discount. The price was never the problem, so the discount doesn't resolve anything — it just teaches the buyer that pressure produces movement, and now you have both an unresolved objection and a weaker position.

What to do: treat this as a coaching pattern, not a rep failing. It shows up across a team the same way it shows up in one deal, and it responds well to being named with specifics: "your last six pricing calls ended without a next meeting booked."

Why most teams catch these too late

None of these signals are subtle. Any good sales manager would spot every one of them if they sat through the calls, read the email threads, and tracked the stakeholder graph for each deal. The problem is arithmetic: eight reps, thirty deals each, hundreds of interactions a week. Nobody can hold that in working memory, so it gets compressed into a stage field and a close date — and the compression throws away exactly the information that predicts the outcome.

That's the gap deal intelligence is meant to close: watching every deal for these patterns continuously, and surfacing the change with its evidence rather than a score with no explanation.

A practical starting point

If you want to do this without new software, pick two signals and instrument them manually for a quarter:

• Economic buyer attendance. One field, updated after every meeting. Review any proposal-stage deal where it's still zero.
• Days since last inbound reply. Not last activity — last message from them. Anything past nine days on an active deal gets looked at.

Both are crude. Both will still find deals your pipeline review missed, which is usually enough to convince a team that the pipeline report was never the problem — the data underneath it was.