A fake war story explains why your sales forecast is fiction.
Here's a hysterical piece of fake news I just ran into. Iranian naval forces captured the Israeli port of Be'er Sheva.
A naval operation. In a city with no sea.
"They fought all night... Led by Admiral Ali Baber Lengi... Captured a strategic shipment of dates." (!)
Backed by "credible sources" like Kish-Media (Tajikistan) and Pyat Express (Voronezh).
Full story. Detailed. Confident. Complete bullshit.
Here is the uncomfortable part. This is exactly how sales information flows in most companies.
Salesperson, manager, CEO, board
Four stops. At every one of them the story becomes cleaner, more optimistic and more likely to close.
Follow a single deal through the chain. A rep has a good call with a mid-level contact who says "this looks interesting, send me a proposal." In the CRM that becomes an opportunity with an amount and a close date. The manager has his own number to hit. He reviews the deal for two minutes in the weekly meeting, hears "they asked for a proposal," and adds it to his forecast. The CEO sees a total. The board sees a slide with a line going up.
Each handoff strips out the doubt. The rep knew his contact had no authority over budget, but there is no CRM field for that. The manager knew this rep is always optimistic, but that does not survive the roll-up either. By the time the deal is a line on a slide, the port of Be'er Sheva has an admiral and a strategic cargo.
You end up with a beautiful pipeline, a confident forecast, and revenue that never shows up.
Nobody is lying
That is what makes it so hard to catch. What actually travels up the chain is:
- assumptions presented as facts
- optimism presented as probability
- conversations presented as deals
It happens because everyone in the chain is rewarded for a good story and punished for a bad one. A rep with a thin pipeline gets pressure, and a rep with a full one gets left alone. A manager who cuts his team's forecast has to face the CEO, and a CEO who cuts the number has to face the board. No one decides to deceive anyone. Everyone rounds up by one notch, and four notches later you have fiction.
This is exactly what I fix, hands-on. Monthly, no contract, no exit fines. If revenue is stuck, tell me where.
Let's TalkDetail makes it worse. The fake war story works because of its details: an admiral with a name, a battle that lasted all night, a cargo of dates, sources with cities attached. A pipeline review full of company names, amounts, stages and close dates feels like data in exactly the same way. The one fact that would kill the story is missing. The city has no sea. The buyer has no budget. Nobody asks.
By the time it reaches the CEO, it looks real. It isn't.
How to tell your forecast is a war story
- Close dates slide from month to month, and the deal stays in the forecast.
- A deal's stage reflects what the rep did. What the buyer did is not recorded anywhere.
- When you ask "who signs?" the answer is the name of a company.
- You have a private discount that you apply to the sales number before you believe it.
If you already cut the forecast in your head before you take it to the board, you know the story is being edited on its way to you.
Break the story, deal by deal
That's what I do. I go into companies and break the story. Deal by deal.
I check four things, and you can run the same check on your ten biggest open deals this week:
- Is there a real buyer? A named person who can sign, or who has direct access to the one who can, and who has spoken to you recently.
- Is there a real reason to change? Something that costs them money or exposes them to risk today. "They like the product" does not count.
- Is there real competition? If the rep says there is none, the competitor is doing nothing, and doing nothing wins a lot of deals.
- Is the timeline real? The date came from the buyer and is tied to something on his side, such as a budget cycle or a contract that ends.
For each answer, ask for evidence: an email, a meeting in the calendar, a name. The rep's feeling about the deal is not evidence. Whatever fails comes out of the forecast. It can stay in the pipeline as work to be done.
Expect your first honest forecast to be smaller than the one you had. It is also the first one you can plan a budget on.
Breaking the story once is an audit. The real fix is a system that produces true information without me in the room:
- Stage definitions based on what the buyer has done, written down, the same for every rep.
- A weekly pipeline review built around the four questions, in place of "so how is it going?"
- A habit of thanking the rep who removes a dead deal. Punish that once and nobody will do it again.
- A forecast that the sales manager has to defend deal by deal, with the evidence in front of him.
I go deeper into the mechanics in two guides: why your sales forecast is always wrong and sales pipeline and forecasting. Owning that weekly rhythm is a large part of what a fractional CRO is there to do.
The goal is revenue that functions in reality. A CRM full of confident updates proves nothing.
"My team wouldn't inflate the numbers"
You are probably right, and they don't need to. Honest people produced every step of the chain I described, each one adding a small, reasonable bit of optimism. Your best reps will welcome the inspection, because for once someone is helping them work the deal instead of just asking for a number.
If your pipeline sounds great but something doesn't add up, you're probably right.
Get these in your inbox
No fluff. Sales, revenue and go-to-market, straight from the field.
Your sales suck. You don't know why. I do.
A 15-minute call, no pitch. You will leave with at least one concrete thing to fix, whether or not we work together.
Book a 15-Minute Call