The weekly pipeline review: 30 minutes that save your month

There are two kinds of sales meetings: those where deals are read aloud, and those where deals get moved. The weekly pipeline review belongs to the second kind – a fixed 30-minute slot in which the team makes decisions on the critical deals instead of reporting status. This guide delivers the agenda, the questions to ask per deal and the typical mistakes. The focus here is the team ritual – each person's individual data upkeep happens before the meeting, as its own short routine.

What is a pipeline review – and what is it not?

A pipeline review is a decision meeting: the team looks at the critical open deals and sets the next step for each one. It is explicitly not a report ("I sent three proposals"), not an interrogation and not a completeness check of every deal.

The difference shows in the question being asked. In a report it is: "What did you do?" In a review it is: "What does this deal need to move forward – and who does that by when?" The first question produces justifications; the second produces movement. The prerequisite is a well-kept pipeline: if the data is wrong, the review turns into a correction session – which is why data hygiene as a weekly routine beforehand pays off.

Why do 30 minutes a week save your month?

Because almost every lost month traces back to the same cause: problems were seen too late. The deal that was silent for three weeks. The proposal that was never discussed. The pipeline that was already too thin for the target on the first of the month. A weekly look catches all of this while there is still time to act.

The weekly cadence is no accident: monthly is too rare to correct course – whoever notices on the 25th that the pipeline is thin cannot save that month any more. Daily is too frequent to discuss substance. Weekly means four opportunities per month to adjust course before the number is final. And because the slot is short and always structured the same way, it survives stressful weeks too.

What does the 30-minute agenda look like?

Four blocks, always in the same order – the repetition is what makes the meeting fast:

1. Numbers check (5 minutes): pipeline value against target, the week's new deals and closes, conversion anomalies. Look, do not discuss.
2. Critical deals (15 minutes): the three to five most important at-risk or blocked deals – not all of them. Per deal: the situation in one sentence, then the deal questions from the next chapter, then a decision.
3. Decisions (5 minutes): what gets escalated, what gets marked lost, where do we change price or approach? Losing is allowed – undecided is not.
4. Commitments (5 minutes): every agreed action gets a person and a date and is captured immediately as a task in the CRM. What is not captured was not agreed.

You do not need more than 30 minutes if two rules hold: the pipeline is current before the meeting (everyone maintains their own deals beforehand), and only what needs a decision gets discussed.

Which questions do you ask per deal?

Four questions are enough – and they work on any deal: What is the agreed next step, with a date? When did the customer last do something (not: when did we last send something)? Is the close date still realistic? And: what would have to happen for us to lose this deal?

The last question is the most valuable. It forces an honest look at risk without attacking anyone – and it uncovers the silent killers: no access to the decision-maker, an unanswered budget question, a competitor in the building. If nobody knows the answer, you have already found the most important next step: finding out.

Which mistakes do teams make in pipeline reviews?

The most common is status theatre: every deal is read out in turn, nobody decides anything, and after 60 minutes everyone is tired. The countermeasure is above – critical deals only, each with a decision. The second mistake is the interrogation: once the review becomes a justification round, people start polishing their pipeline, and the data becomes worthless. The rule "we discuss deals, not people" sounds trivial but changes the tone completely.

Mistake three: the meeting only happens when "something is going on". That kills the routine within weeks. The slot is fixed, even if it takes only 15 minutes in a quiet week. And mistake four: commitments without capture. What was agreed verbally on Tuesday is forgotten by Friday – unless it sits in the CRM as a task with a date.

How do you introduce the review to your team?

With a clear announcement and four weeks of patience. Explain what the review is (decisions on critical deals) and what it is not (surveillance), put it in a fixed slot – Monday or Tuesday morning works well – and moderate the first sessions strictly along the agenda. The first meeting typically runs 45 minutes, because legacy issues surface: deals that should have been decided long ago. That is not failure; it is the point of the exercise.

By week three or four the rhythm settles, and the real effect becomes visible: people update the pipeline before the meeting, because nobody wants to sit in the review with stale deals. This quiet discipline effect is half the value of the ritual – and cleanly cut pipeline stages provide the shared language it runs on.

How does AI prepare the review?

The most tedious part of any review is the preparation: finding out which deals are critical. That is exactly what Autopilot in Advanzo takes over – its daily scans flag deals without updates and deals past their close date as at risk, each with AI reasoning and a confidence level. Your agenda for block 2 practically writes itself.

On top of that, the AI Deal Score provides fast prioritisation: 0 to 100, calculated from engagement, momentum, timing and size, shown as a badge directly on the Kanban board. To be fair about it: the score is a snapshot on demand, does not update itself and can vary slightly between runs – it is no substitute for the discussion, but it is strong as a filter for "which five deals do we discuss today". Both are part of the AI add-on at CHF 9 per user per month; the feature overview shows what else is included.

Frequently asked questions (FAQ)

Who should attend the pipeline review?

Everyone who actively owns deals – and nobody else. In an SME that is often two to five people including management. The smaller the circle, the more honest the conversation; guests without their own deals quickly turn the review into a presentation.

How is it different from the weekly sales meeting?

The pipeline review covers deals and decisions about them – exclusively. Topics like marketing, products or organisation belong in a separate slot; otherwise the general items eat the 30 minutes and the deals are left behind again.

Does a pipeline review work solo?

Yes, as a structured conversation with yourself: same agenda, same four questions per deal, same commitments – just without an audience. Solo founders benefit most, because otherwise nobody asks the uncomfortable questions. The calendar slot is mandatory, or daily business will crowd it out.

Should we go through every deal in the review?

No – that is the surest path to the 90-minute meeting nobody wants. Only deals that need a decision get discussed: at risk, blocked or unusual. Everything else lives in the CRM and needs no meeting.

Which metrics belong in the numbers check?

Three are enough: weighted pipeline value against target, the week's new deals, and deals won/lost. Deeper analysis belongs in a quarterly session – the weekly review is for steering, not analysing.

A good pipeline review takes no talent – just a fixed slot, a short agenda and a CRM that surfaces the critical deals on its own. Advanzo delivers exactly that: a Kanban pipeline, dated tasks on every deal and an Autopilot that flags at-risk deals before the meeting. Swiss hosting, FADP/GDPR compliant, free up to 25 deals. Start for free and turn your meeting into a review.