A customer says yes. The deal has been in the forecast for two quarters. The contract is ready. Everyone on the selling side exhales.
Then nothing happens. The customer goes quiet. Emails get shorter. Meetings get rescheduled. The internal champion who was driving the deal suddenly needs “one more review with leadership.” A week passes. Then a month. The deal doesn’t die dramatically. It just stops moving.
I’ve seen this pattern on at least a dozen engagements. Studies suggest that 40 to 60% of qualified pipeline deals end in no decision — not lost to a competitor, not rejected on price. The customer simply couldn’t cross the finish line. They wanted to move forward. They said they would. And then they didn’t.
We spend enormous energy getting to “yes.” Refining the pitch. Building the business case. Running the demo. Handling objections. But “yes” isn’t the finish line. It’s the starting gun for the hardest part of the process: getting from agreement to action.
That space between “yes” and “done” is where deals die, implementations stall, and change initiatives quietly collapse.
The gap has a name
Every change goes through three phases. An ending, where people let go of the old way. A messy middle, the disorienting space where the old is gone but the new hasn’t taken root. And a new beginning, where the change becomes the new normal.
Organizations plan the ending. They announce the change, sign the contract, kick off the project. They celebrate the beginning: go-live, launch day, the first report from the new system. Nobody plans the messy middle.
This is exactly where most deals stall. The customer has intellectually agreed that things need to change. But they haven’t arrived at the new beginning. They’re floating in the space between. And floating feels terrible. It’s uncertain, it’s exposed, and every instinct tells them to retreat to solid ground — which means doing nothing.
The messy middle isn’t a failure of the process. It is the process. Trying to skip it doesn’t speed things up. It guarantees a collapse later.
Why pushing harder makes things worse
The instinct when a deal stalls is to push harder. More information. More urgency. Another ROI calculation. A tighter deadline.
This almost always makes things worse.
The hidden enemy isn’t indecision. It’s fear of making the wrong decision. People aren’t afraid of missing out on a good choice. They’re afraid of committing to a bad one. The pain of a wrong move outweighs the pain of no move. When you pile on more data and more pressure, you’re amplifying the stakes. Higher stakes mean more fear. More fear means more paralysis.
The customer who ghosts you after saying yes. The project sponsor who keeps asking for “one more review.” The team that nods in every meeting but changes nothing afterward. These aren’t resistance. They’re fear. Recognizing them as fear rather than obstruction changes how you respond. You stop pushing and start doing something much harder: helping people feel safe enough to take the next step.
What actually works in the gap
Four approaches that I’ve seen work in practice. They all share the same underlying logic: reduce fear rather than amplify vision.
Limit the options, don’t expand them. The conventional response to a stalling deal is to offer more: more features, more customization, more flexibility. This feels helpful. It’s actually destructive. Every additional option is another decision the customer has to make, and every decision is another opportunity to get something wrong.
I learned this on a CPQ implementation where the client couldn’t commit to a configuration approach. We’d presented three options with detailed trade-offs. Weeks of silence followed. When I went back with a single recommendation — “based on your product catalog and your channel mix, this is what I’d do” — they signed off in days. Give one recommendation. Then cap the exploration. You’re using your expertise to absorb the risk of the decision.
Name the gap. Most people in the gap don’t know they’re in it. They just know something feels off. So they stall. Acknowledge the discomfort directly. During a CRM migration last year, adoption stalled three weeks after go-live. Instead of pushing compliance, I said: “You’re between the old process and the new one. The old one is gone but the new one doesn’t feel natural yet. That’s expected. It takes about three months before it feels like yours instead of something that was imposed.” The room visibly relaxed. Naming the gap normalizes it. It turns a vague anxiety into a recognizable phase with a timeline.
Ask, don’t tell. When someone is stuck in the gap, the instinct is to provide answers: more data, more reassurance, more arguments for why they should move forward. Instead, ask: “What’s the real challenge here for you?”
The answer is almost never about the product or the price. On a recent deal that had stalled for six weeks after verbal agreement, I asked the champion what was actually hard about moving forward. The answer: “I’m the one who convinced leadership to do this. If it fails, that’s on me. And the last system we implemented was a disaster.” No amount of ROI modeling addresses that. But once it’s on the table, you can deal with it.
Build intimacy, not just credibility. Knowing your domain and doing what you say you’ll do are table stakes. But the thing that matters most in the gap is whether the other person believes you see them. Not just their business problem — them. Their career risk. Their reputation. What they’re afraid of. What they’re hoping for.
People in the messy middle don’t move forward because of your track record. They move because they trust that you understand what’s at stake for them personally and that you won’t let them fail.
This applies far beyond sales
The gap between “yes” and “done” exists everywhere.
A leadership team agrees to reorganize the commercial function. The announcement goes out. Six months later, nobody is sure who owns what. The old relationships still drive decisions. I’ve seen a commercial reorganization take 18 months to actually land — not because the design was wrong, but because nobody helped the team navigate the transition.
A company implements a new CRM. It goes live on schedule. Three months later, half the team is using workarounds. The system is technically done. The change hasn’t happened yet. This is the most common pattern in my work: a tool that’s live but not adopted, because nobody planned for the human side of the transition.
In closing
Most of us are trained for persuasion. Getting to yes. Making the case. Closing the deal. Almost none of us are trained for what comes after: accompanying someone through the uncertainty that follows a commitment.
Accompaniment is a different skill than persuasion. It’s slower. It’s less dramatic. It doesn’t produce the satisfaction of a close. It requires staying present when things are ambiguous, not rushing people to the other side, and helping them take the next small step instead of demanding the whole leap.
The best consultants, leaders, and salespeople don’t close gaps. They walk people across them.