Every sales leader knows this deal: the one that has been "about to close" for six weeks. The rep sent the proposal, followed up three times, left a voicemail, and still has it at 70% in the CRM.
The buyer made their decision weeks ago. They just didn't tell anyone.
I call this Fantasy Pipeline Syndrome. The deal is already dead from the prospect's perspective. The salesperson is the last one to figure it out, and the manager finds out even later.
Most sales leaders recognize it the moment they hear the name. Fewer understand why it happens or how much it costs.
What Fantasy Pipeline Syndrome Looks Like
It rarely looks like a problem. It looks like persistence. The common signs:
- The rep is in chase mode, sending "just checking in" emails that get no reply.
- The deal hasn't moved stages, but its probability hasn't dropped either.
- The next step is something the seller will do, not something the buyer agreed to do.
- The same deals show up in every forecast call with a new reason for the delay.
None of these on its own proves a deal is dead. Together, they usually mean the buyer has moved on, and the pipeline hasn't.
Why Good Salespeople Fall into It
This isn't a laziness problem. Some of the hardest-working reps have the worst cases.
Fantasy Pipeline Syndrome is part mindset and part behavior. The mindset is that persistence wins deals, so silence means "keep going." The behavior is to follow up rather than ask a direct question that might get a no.
There's also a qualification gap underneath it. If the rep never learned how the buyer makes decisions, who's involved, and what happens if they do nothing, they have no way to tell when the process stalls. Silence gets read as "they're busy" because there's nothing better to measure it against.
And there's the number. Every deal on the board feels like progress. Removing one feels like admitting a miss, so it stays.
Why Managers Find Out Last
Most pipeline reviews run on the rep's interpretation. The manager asks, "How's this one looking?" and gets a story in return. The story is usually optimistic, because the rep believes it.
Managers also have their own pressure to show coverage. A full pipeline looks good to the owner or the board. So both people in the room have a reason not to look too closely, and dead deals survive one more week, then another.
What It Actually Costs
The obvious cost is the forecast. Deals that were never real can't close, and the miss shows up at the end of the quarter when it's too late to fix.
The higher cost is time. Every hour spent chasing a dead deal is an hour not spent prospecting. Fantasy Pipeline Syndrome doesn't just inflate this quarter's pipeline. It empties next quarter's.
How to Treat Fantasy Pipeline Syndrome
- Define stages by what the buyer has done. A deal shouldn't move forward because the rep sent something. It should move because the buyer confirmed something: the problem, the budget, the decision process, or a date.
- Make every next step mutual. A real next step has a date, a time, and the buyer's commitment attached. "I'll follow up next week" isn't a next step. "We're meeting Thursday at 2:00 with your CFO" is.
- Give your team permission to get a no. In Sandler, a clear no is a good outcome. It frees up time and ends the guessing. A rep who can say, "It feels like this may not be a priority anymore. Should we close the file?" will learn the truth faster than one who sends a fifth follow-up.
- Change the question in your pipeline review. Stop asking, "How's it looking?" Start asking, "What did the buyer do since our last conversation?" If the answer is nothing, that's the answer.
A Healthy Pipeline Is Usually Smaller
When teams start treating Fantasy Pipeline Syndrome, the pipeline shrinks. That can feel alarming at first. It's actually the first accurate picture the leader has had in a while.
A smaller pipeline of real opportunities is easier to forecast, coach, and grow because the team knows where its time is going.
If you're not sure how much of your current pipeline is real, that's worth finding out before the quarter ends. Let's connect.
