The deal is technically open. The stage hasn’t moved. But the buyer has gone quiet, and at some point after your last call, they stopped thinking about the problem they described in discovery.
It didn’t leave their business. A CRO running a leaky pipeline in week one of your sales cycle is still running it in week eight. The pain’s still there. What changed is that between your last call and now, two or three new fires broke out, and the thing you solve dropped off the weekly agenda. Pain doesn’t disappear. It gets outranked.
Most reps read the silence as a price issue, a product gap, or fading interest. It’s rarely any of those. And because they’ve misread the cause, they send a check-in email that asks the buyer to remember why they cared, without giving them a single reason to do it. Nothing happens.
Following up without a hook is waiting out loud
Some version of this email goes out dozens of times a week:
New Message
Hi Alex,
Just checking in to see if you had a chance to review the proposal. Happy to jump on a quick call if you have any questions.
Let me know when you're ready to pick this back up.
Best,
Jordan
The rep is active. The deal goes nowhere. That message costs Jordan nothing to send and gives Alex nothing to hold onto. No urgency anchor, no return to business stakes, no reason to act. It hands full control of the timeline back to the buyer and asks them to do the work of reviving a conversation they’ve mentally filed under “later.”
That’s waiting out loud. You type something, send it, and wait again with a timestamp on the waiting.
Could this go to any other account sitting in your pipeline right now? If it could, it's too generic to move anything. Good follow-up names the buyer's specific pain, returns to the stakes they already named, and proposes a concrete next step that fits where the deal actually sits.
If the pain was never implicated, there’s nothing to return to
Most stalled deals don’t reveal a follow-up problem. They reveal a discovery one.
Most reps find the pain and name it. “Reporting is a challenge.” That’s identifying it. It’s surface level, and it fades the moment the quarter gets busy.
Better reps quantify it. They build a business case, drop a number into an ROI slide, and hand it over. The buyer reads the figure, thinks “that’s a bit painful,” and files it. That’s indicating it. Better, but it’s something done to a document. Nobody feels it.
The best reps make the buyer feel the consequence personally. That’s implicating it, and it’s the only level that sticks.
Reporting isn’t just slow. Your VP Revenue builds the pipeline report manually every Monday. You missed a board presentation last quarter because the numbers weren’t ready. The hiring freeze means that’s not getting fixed internally any time soon. That’s a specific cost, attached to a real person, connected to a stake they’re personally carrying. Implicated pain doesn’t fade between touches, because it’s not an abstract problem on a slide. It’s a thing that happened to someone in the organisation and will happen again.
Discovery that stops at identifying or indicating leaves the rep with nothing sticky to return to. So when follow-up time comes, they write a generic “just checking in” because there genuinely isn’t anything else to say. That’s not a follow-up problem. That’s a discovery gap surfacing in the pipeline review.
The move in discovery is to walk the buyer through the progression: mirror the problem, ask what it causes downstream, put a number on it, then connect it to why it matters now and to whom. A useful prompt when you think you’ve found the pain is “other than the obvious hassle, what does that cause downstream?” That question is what separates a named problem from an implicated one.
If that conversation happened in discovery, follow-up has something specific to return to:
New Message
Hi Alex,
When we spoke in March, you mentioned your VP Revenue was still building the pipeline report manually every Monday. You'd missed one board presentation because the numbers weren't ready in time.
I don't know if that's still the setup, but if it is, that's usually something we can sort out in a few weeks, not quarters.
Worth 20 minutes this week to see if the timing makes sense now?
Best,
Jordan
That message earns a reply because it’s about Alex’s problem, not Jordan’s pipeline. It’s specific, it’s personal, and it’s tied to something Alex is accountable for. The buyer re-experiences the problem rather than being reminded that a proposal exists.
Passive standby vs timing-calibration
There’s a version of follow-up that’s slightly better than “just checking in” but just as structurally broken:
Happy to chat when the timing is right. Just let me know when you’re ready.
That’s passive standby. It signals availability without creating any mechanism for re-engagement. Timeline control passes entirely to the prospect. The rep waits for a signal that may never come, and the deal drifts into the far reaches of the pipeline where things go to be quietly removed from forecasts.
Timing-calibration is the alternative. It acknowledges that deals stall for real reasons (internal approvals, budget cycles, stakeholder alignment) and works with them directly rather than pretending they don’t exist:
New Message
Hi Alex,
You mentioned budget sign-off typically runs through your CFO in the first two weeks of each quarter. We're heading into that window now.
Has the internal timeline shifted, or does it make sense to get aligned before it closes? Even a short call to confirm scope would mean you're not starting from scratch if you want to move in Q3.
Best,
Jordan
That question names a common pattern, asks for useful information, and creates a natural window for a specific check-in. “I’ll leave it with you until Tuesday. If I haven’t heard anything by Wednesday I’ll check back in.” That’s a cadence with a mechanism. Not passive. Not aggressive. Calibrated to how the buyer’s world actually works.
When genuine disruption hits, extend rather than chase
Not every stall is about fading pain. Sometimes the timing is genuinely broken: a leadership change, a hiring freeze, a restructure, a competing internal priority that knocked this off the agenda. These are different from the normal “still evaluating” stall.
The instinct is to check in more. Stay visible. Don’t let the prospect forget you. That instinct is badly timed. When someone is dealing with genuine organisational upheaval, a follow-up email every ten days adds guilt and friction, not urgency. The buyer knows they owe you a response and can’t give you one. So they stop opening the emails.
The better move is to extend the follow-up timeline deliberately, further out than you’d normally go, and to say so explicitly:
I heard you’ve had some leadership changes on the team. Clearly not a moment to be pushing on decisions. I’ll give this a couple of weeks. Happy to come back then and, if it’s useful, bring the new head of operations across for context on the ROI case.
That email removes pressure instead of applying it. It shows situational awareness. It makes the next step achievable. RAIN Group research on lengthening sales cycles and rising no-decision rates points to the same pattern: buyers delay when they don’t perceive enough value in changing today versus staying the same. When the stall is real disruption, reducing pressure keeps the door open. Increasing it usually closes it.
Make the next yes smaller
Follow-up often fails because the rep is asking for the wrong thing. The proposal went out two weeks ago. The rep is implicitly asking for a decision: sign or don’t. But the buyer isn’t at the decision stage. They have questions they haven’t quite articulated, internal alignment they haven’t done, a new stakeholder who has concerns nobody has addressed yet.
The follow-up should propose the smallest next step that actually moves the deal forward, not the largest one it could theoretically justify. If the buyer needs to work through the commercial structure before committing, don’t ask for a signature. Propose a working session to walk through it together. If a new stakeholder has entered the process, offer a short call specifically for them rather than asking everyone to re-engage on the full proposal.
Before you send any follow-up, the useful question is: what does the buyer actually need to do to say yes? Whatever the answer is, that’s the step to propose. Skipping straight to the decision when three steps precede it doesn’t speed things up. It stalls the deal, because the buyer has nowhere honest to go except “not yet.”
What to inspect when a deal stalls
Pipeline reviews tend to produce the same question when a deal hasn’t moved: “Have you followed up?” That question doesn’t tell you much. What you want to know is whether the follow-up is doing any real work.
- What was the last piece of specific pain the buyer named, and has the rep returned to it in any follow-up since discovery?
- Did discovery produce implicated pain (quantified, tied to downstream impact) or just surface pain (acknowledged, then moved past)?
- Is the follow-up anchoring to a buyer event, a deadline, or implicated pain, or to nothing at all?
- Is there a specific next-contact date in the calendar, or is the rep waiting on the prospect to re-engage?
- Does the rep know why the deal stalled: genuine disruption or just drift?
- What's the next step being proposed? Is it proportionate to where the buyer actually is, or is the rep still pushing for a decision?
These questions shift the inspection from activity-checking to deal-reading. The answers will tell you quickly whether the rep is managing the deal or hoping the prospect comes back on their own.
Pain disappears from deals faster than prospects do. The job of follow-up is to keep it visible.