Pipeline review: a leadership ritual, not a read-aloud session
Why the weekly pipeline round moves nothing in most sales organisations, how to define stages with exit criteria instead of gut feeling, which four questions every deal has to survive, how to calculate pipeline coverage instead of guessing a forecast — and what the works council has a say in the moment the CRM starts logging activity per employee.
The short answer
A pipeline review is a decision meeting, not a status round. It works when three things are settled: every stage has an exit criterion that the customer fulfils, not the salesperson; every deal discussed leaves the meeting with a next step and a date; and deals without a next step drop out. I have seen many such rounds that lasted an hour and in which not a single deal left the list. That is the most reliable sign that someone was reading aloud rather than leading.
Why most pipeline rounds move nothing
Three patterns repeat themselves. The first is the reading hour: everyone presents their list, the manager nods, nobody objects. That costs six people an hour each and produces not one decision. The second is forecast defence: because the salesperson's appraisal hangs on the number, he defends it instead of explaining it. Anyone who gets punished in the review when a deal tips over will report the tipping later — precisely when nobody can intervene any more. The third is number worship: people look at totals and percentages instead of talking about individual deals. Totals have no contact person you can call.
The common denominator: in all three cases the conversation is about the state of things, not about the next step.
Stages need an exit criterion, otherwise you are talking about feelings
As long as “50 per cent” means the salesperson has a good feeling, the pipeline cannot be checked. It becomes checkable when every stage is tied to an observable action by the customer. A grid that has proven itself in deals that require explanation — the percentages are an example, not a standard:
| Stage | Exit criterion (the customer has …) | Typical mistake |
|---|---|---|
| Qualified | named the need, clarified who is responsible | a business card counts as a need |
| Need confirmed | disclosed the current situation and order of magnitude | the salesperson estimates the need himself |
| Offer outstanding | received the offer and confirmed receipt | “sent” counts as “on the table” |
| Decision scheduled | named a date, the decision-maker and the budget route | the salesperson's wished-for date |
| Close | signed | a verbal commitment gets booked in |
The right-hand column is the real value of this table. Almost every bloated pipeline grows out of these five confusions.
The format: 45 minutes, four blocks
- Movement (10 minutes). What has changed since the last round — newly added, won, lost, postponed? Changes only, no full run-through.
- Deals at risk (20 minutes). Not the biggest ones, but the oldest ones and the ones postponed twice. This is where the meeting earns its keep.
- Clearing out (10 minutes). Every deal without a next step and a date either gets one or leaves the list. Without this block the pipeline only ever grows.
- Commitments (5 minutes). Who does what by when. Minuted, three lines, not a report.
What does not happen here: coaching on the individual conversation. That is the right and important meeting — but a different one, one to one.
The four questions every deal has to survive
“What did the customer last do — not say, do?”
Separates progress from friendliness. A customer who has only been returning calls for three weeks is not moving.
“Who signs, and has that person seen us yet?”
The most common cause of deals that die in the final metre: the decision-maker was never in the room.
“How would we notice that we had lost?”
Forces a criterion instead of hope — and makes it possible to close the deal later without losing face.
“What is the next step, with a date?”
The question the whole meeting hangs on. If there is no answer, there is no deal.
Calculate coverage instead of guessing the forecast
The most useful number in the review is not the pipeline total but its coverage: pipeline value divided by the outstanding target in the same period. The following calculation is a model calculation with freely chosen figures:
| Measure | Value |
|---|---|
| Outstanding quarterly target | €150,000 |
| Pipeline value in the time window | €450,000 |
| Coverage | factor 3.0 |
| Historical close rate from the “offer outstanding” stage | 30% |
| Expected value | €135,000 — i.e. €15,000 short of cover |
The point is the last line. Anyone who knows their own close rate sees the gap in the first month of the quarter instead of the last. Anyone who does not know it replaces it with confidence — and factor 3 is the most popular placeholder for that, without anything supporting it. The rate has to come from your own data, not from a rule of thumb.
When the CRM keeps records: what the works council has a say in
The moment the review rests on reports that show activity per employee, it is no longer purely a leadership matter. Under § 87 (1) no. 6 BetrVG (German Works Constitution Act) the works council has a right of co-determination on the “introduction and use of technical devices designed to monitor the conduct or performance of employees”. Under settled case law it is enough that a system is objectively suitable for monitoring; the employer's intention to monitor is irrelevant. On 16 July 2024 (1 ABR 16/23) the Bundesarbeitsgericht (Federal Labour Court) confirmed that co-determination applies even when nothing is recorded or stored — the mere possibility of listening in was sufficient there.
In practice that means: a CRM dashboard with call numbers per salesperson is subject to co-determination, no matter how well intentioned it is. Anyone who has a works agreement on the matter should look into it before introducing new reports; anyone without a works council is not bound by this limit — the data protection principle of purpose limitation remains untouched by it.
Action list
- Redefine the stages: one exit criterion per stage describing an observable action by the customer. In writing, one page.
- Clear out once: close or downgrade every deal without a next step and a date. The pipeline gets shorter — that is the purpose, not the damage.
- Set a fixed weekly meeting, 45 minutes, four blocks, same order. Explicitly move coaching and pricing approvals out of it.
- Calculate your own close rate from the “offer outstanding” stage over the last six months and derive the coverage factor from it, instead of adopting a factor.
- Print out the four questions and put them somewhere visible in the review — they are the difference between examining and reading aloud.
- Minute the commitments and open the next round with them. A review without a look back at the last commitments teaches people to make commitments cheaply.
- Involve the works council before introducing new personal-data reports — beforehand, not once the dashboard is running.