DEV Community

Michael Inghilterra
Michael Inghilterra

Posted on Originally published at michaelinghilterra.com

The deals in your forecast that are quietly fiction

The deals in your forecast that are quietly fiction

Most forecasts miss for a boring reason. Not because the market turned or a big deal slipped, but because a share of the pipeline underneath the number was never real to begin with. The forecast was a hope with a number attached, and the number inherited every soft deal the hope was built on.

I have spent my career in revenue operations, and pipeline quality is the dimension I check first, because it is usually the root cause of the two problems leaders complain about most: a forecast nobody trusts and reporting nobody acts on. You cannot report your way out of a pipeline that is not true. So before anyone touches the dashboard, I look at the deals themselves and ask a plain question about each one: is this real, or does it just have a stage and a dollar amount?

Three kinds of fiction show up over and over. Here is how to spot each.

Fiction one: fluff

Fluff is the deal that is technically open and effectively dead. No recent activity. A close date that has already passed and quietly rolled forward again. Stuck in the same stage for a quarter while everyone politely looks away.

Fluff is easy to find and easy to ignore, which is exactly why it accumulates. Nobody wants to be the one who marks their own deal closed-lost, so it sits, padding the pipeline coverage ratio and making the top of the funnel look healthier than it is. The tell is simple: sort by last-activity date and look at anything untouched in the last few weeks that is still counted as active. Most of it is not a deal. It is a deal-shaped placeholder.

The fix is not a cleanup project every quarter. It is a rule: no activity in X days moves a deal to a review state automatically, and the rep either revives it with a real next step or lets it go. Clean once and it re-rots. Enforce at the edge and it stays honest.

Fiction two: sandbagging

Sandbagging is the opposite problem, and it is sneakier because it hides inside good news. It is the deal that is ready to close now but forecast two quarters out. The rep is protecting themselves, banking a deal they are confident in so next quarter starts with a cushion.

I understand the human incentive. But treat it as a scheduling quirk and you miss what it actually is: a data-integrity problem and a culture signal. When your best deals are deliberately misdated, your forecast is wrong in both directions at once. This quarter looks light, next quarter looks padded, and neither picture is real. You end up managing to a calendar the reps privately know is fake.

The tell is a deal with strong qualification, a champion, a paper process underway, and a close date that does not match any of that momentum. When the evidence says now and the date says later, the date is the thing to question. Naming it out loud, without punishing the rep, is usually enough to start straightening the dates out.

Fiction three: the unqualified commit

The third kind is the most expensive, because it looks the most legitimate. It is the deal sitting in commit or forecast with a confident number next to it and almost nothing underneath. No identified economic buyer. No understanding of how the customer actually buys. A champion who is really just a friendly contact with no power.

This is where qualification earns its keep. You do not need a heavy framework to catch it, just the discipline to ask what is actually known. MEDDPICC is the shorthand I use, and the letters that matter most for a commit are the ones people skip: the Economic Buyer, the Decision Process, and the Paper Process. If a deal is forecast to close and nobody can name the person who signs, or describe the steps between a yes and a signature, that is not a commit. It is optimism with a due date.

The single highest-leverage rule I have seen here is small: you cannot put a deal in commit without an economic buyer. Full stop. It sounds obvious. Watch how many deals fail it the first time you enforce it.

Why this is the root cause, not a side issue

Here is the part that makes pipeline quality worth fixing before anything else. The two problems everyone wants solved, a trusted forecast and reporting that drives decisions, both sit downstream of this. If the deals are fiction, the forecast built on them is fiction, and the dashboard on top is a very clean picture of something untrue. You can rebuild the reporting layer beautifully and still be wrong, because the error was underneath it the whole time.

Fixing it is not glamorous. It is evidence gates on stage entry, so moving a deal forward requires something you can point to instead of a rep's feeling. It is honest dates. It is a weekly pipeline inspection that treats these three fictions as things to catch, not things to be polite about. Do that, and the forecast stops being a hope with a number attached and starts being a read on reality. Everything downstream gets easier, because it is finally standing on something true.

The uncomfortable first step is admitting how much of the current number is one of these three. Most teams are surprised. The good news is that once you can see it, it is fixable, and the fix compounds.

I write about the systems that make revenue legible, and I run a productized Revenue Engine Audit that scores this and four other dimensions of a revenue operation. If your forecast is not trusted, this is usually where it starts.

Top comments (0)