A pipeline that everyone fills in and nobody trusts is not a management tool. It is a ceremony.
Most commercial organisations can have a clear sales process, trained and documented, while the pipeline that is supposed to reflect it tells a quite different story. Opportunities sit in stages they do not belong in. The close dates are optimistic. The probability weightings have not been updated since the first conversation. And the management team, reviewing this data, is making decisions on hiring, on resource allocation, on board reporting, on the basis of a picture that bears only a passing resemblance to reality.
A well designed sales process tells the organisation how to sell. Pipeline governance tells the organisation whether it is actually happening. The distinction matters because organisations can invest heavily in the first and barely notice they are missing the second.
THREE QUESTIONS MOST ORGANISATIONS LEAVE VAGUE
Pipeline governance is the set of rules, rhythms and management practices that determine how opportunities move through the sales process. It answers three questions.
What are the criteria for an opportunity to move from one stage to the next? Not the salesperson’s instinct, not the passage of time, but specific, observable conditions: a confirmed problem, an identified economic owner, a stated budget. When these criteria are defined clearly, the pipeline stages mean the same thing to everyone.
What are the rhythms of review? The individual review is for prioritisation, the team review is for mutual challenge, and the leadership review is for forecasting and resource decisions. Each requires different information and a different cadence, and confusing them is a common source of frustration.
What happens when things are off track? A governance structure without consequence is a suggestion. The organisations that maintain pipeline integrity are those where the answer is clear and consistently applied.
THREE LEVELS, ONE PIPELINE
Effective pipeline governance operates at three levels simultaneously, and confusing them is a common source of frustration. At the individual level, the salesperson is managing their own pipeline as a daily working tool. The one who updates it just before the review meeting is creating a retrospective justification for decisions already made.
At the team level, the sales manager is using the pipeline to create collective accountability and shared learning. A well run team review is where a salesperson who has been stuck on the same obstacle for three weeks discovers that a colleague solved the same problem two months ago.
At the leadership level, the pipeline is a forecasting and decision making tool. It is interested in the aggregate picture: whether the organisation is on track, where the risk lies, and whether the pipeline composition reflects the strategic priorities. A leadership review that descends into deal level discussion is substituting one level for another and depriving both of their purpose.
WHY SALESPEOPLE HAVE A COMPLICATED RELATIONSHIP WITH THEIR PIPELINE
Salespeople are optimists. They need to be: persistent pursuit of uncertain outcomes requires a certain disposition toward possibility. But that same optimism means opportunities tend to stay in the pipeline longer than they should, at probability estimates higher than the evidence supports. This is not dishonesty. It is the natural product of a profession that requires sustained belief in outcomes that have not yet materialised.
The consequence is that a pipeline built on unmanaged optimism consistently overstates what is actually coming. Because the gap between forecast and outcome is explained, each time, by specific deal slippage rather than systematic overestimation, the structural problem is never named clearly enough to address. Pipeline governance addresses this not by demanding pessimism, but by demanding accuracy.
| WHAT WE’VE SEEN We worked with a mid sized B2B business with around twenty salespeople operating across several markets. The business had invested in a CRM, defined its pipeline stages, and conducted regular forecast reviews. The quarter end results bore little relationship to what the forecast had suggested was coming. Proposal sent meant a formal document submitted to procurement in one team, and an email with a rough estimate in another. Stage criteria were redefined in terms of what the customer had done or said. The pipeline shrank. The forecast was revised downward. Neither was welcome news in the short term. What changed over the following quarters was that the pipeline became something the business could actually manage from, and the leadership team stopped being surprised at quarter end. |
CRM IS WHAT MAKES GOVERNANCE POSSIBLE
Pipeline governance tells the organisation how to manage opportunities. CRM is what makes that possible in practice. A CRM without governance produces a well organised archive of commercial activity that nobody acts on. Governance without reliable data produces a ritual: structured conversations about a picture of reality that does not match what is actually happening in the field.
| “A CRM that reflects last year’s commercial model is providing accurate data about the wrong thing. Configuration is a strategy decision, not an IT decision.” |
Pipeline logic is the architecture beneath the data: the specification of what each stage label actually means in observable customer behaviour. A deal is not in the proposal stage because a proposal was sent. It is in the proposal stage because the customer has confirmed the problem, engaged the relevant stakeholders, and received a proposal that addresses their stated criteria. Treating labels as criteria is one of the most consistent sources of forecast inaccuracy in commercial organisations.
WHAT A RELIABLE PIPELINE MAKES POSSIBLE
For the individual salesperson, a real time pipeline is a prioritisation tool. For the sales manager, it is a coaching tool, turning the pipeline review into a genuine development conversation rather than a negotiation about what the numbers mean. For leadership, it is a decision making tool: are we on track, where is the concentrated risk, and does the pipeline composition reflect the strategy we agreed.
These are the questions a board wants answered. They cannot be answered if the pipeline is an optimistic fiction.
A pipeline review that does not produce decisions about which opportunities to advance, which to reassign and which to close out is not governance. It is a reporting ritual. The two can look identical from the outside. The commercial outcomes are entirely different, and the difference compounds every single quarter it is left unaddressed.
None of this requires new technology. Most organisations already own a CRM capable of supporting real pipeline logic. What is usually missing is a handful of stage criteria decisions and review rhythms that a leadership team can agree in a single working session, and the discipline to hold to them once the pressure of a difficult quarter makes the old, more comfortable version of the pipeline tempting again.
| WHERE THIS LEADS Would you bet your own bonus on it? That is the honest test of a pipeline. If the answer is no, the gap is rarely a technology gap. It is usually a handful of stage criteria and review habits away from being closed. If you would like a second opinion on what your own pipeline would show under this kind of scrutiny, we would be glad to look at it with you. |
