Every pipeline we open has the same problem. Stages are labelled. Nobody can tell you what each one actually means.
“Qualified” is qualified because the rep said so. “Proposal sent” is proposal sent because a document left the building. “Verbal” is verbal because somebody nodded in a meeting three weeks ago. The stages are real. The evidence behind them is not.
If you cannot describe the exit criteria for each stage in one sentence, you do not have a pipeline. You have a story.
Why this costs you money
A story-pipeline does three things to a business. It inflates the forecast. It hides the deals that should be killed. And it tells you to hire, because the number looks big enough to need more people to deliver it.
Then the number does not land. And the explanations get creative. And the board stops trusting the forecast, which means they stop trusting the founder, which means every conversation about strategy starts from the wrong place.
How we rebuild it in three weeks
Week one: we define each stage as a verb and a piece of evidence. Not a feeling. A thing that exists in writing, in the CRM, between the rep and the customer.
Week two: we grade every live deal against the new stages. Most move backwards. Some get killed. The number drops. That is the point. The new number is real.
Week three: we install the review rhythm. Weekly pipeline review, owned by one person, with the evidence pulled from the CRM in front of the whole commercial team. Nobody argues the number. They argue the evidence.
The forecast is not the thing you build. It is the thing that falls out, once the pipeline is evidence-based.
Most businesses get to ±5% forecast variance within two months of doing this. Some faster. The number stops being a story. It starts being a tool.
