Sales Pipeline Review

Overview

A sales pipeline review is a weekly operational meeting where the sales team examines active opportunities, assesses pipeline health, and refines the revenue forecast. The session serves two purposes simultaneously: it gives leadership an accurate view of where the quarter is heading, and it creates a structured coaching opportunity for individual account executives.

Unlike a forecast call, which focuses narrowly on the numbers, a pipeline review examines the underlying deal dynamics. It asks why deals are progressing or stalling, whether the right stakeholders are engaged, and what specific actions will move each opportunity forward. This dual focus on metrics and deal quality is what distinguishes a high-performing sales organisation from one that merely tracks numbers. Explore our business review templates for complementary meeting formats.

The recommended cadence is weekly, ideally on Monday or Tuesday so that the team can act on insights for the remainder of the week. Most teams find that 60 minutes is sufficient for a team of 6 to 10 account executives, though larger teams may need to split into regional or segment-based sessions.

When to Use This Framework

This template applies to any B2B sales organisation with a defined pipeline of opportunities that move through stages over time. It is particularly valuable when forecast accuracy is a priority, when the sales cycle is longer than 30 days, or when deal values are large enough to warrant individual scrutiny.

• B2B SaaS or enterprise sales teams with multi-stage pipelines and defined sales methodologies
• Teams approaching quarter-end who need to tighten forecast accuracy for board reporting
• Newly formed teams or teams with junior AEs who benefit from structured coaching alongside the review, supplemented by regular one-on-one meetings
• Organisations experiencing pipeline conversion challenges and needing to identify systemic bottlenecks
• Teams that have recently changed CRM systems, pricing models, or territory structures and need to recalibrate deal hygiene
• Any sales function where leadership requires weekly visibility into revenue trajectory

Who Should Attend

Sample Agenda

Example Use Case

DataFlow Analytics is a B2B SaaS company selling a data integration platform to mid-market and enterprise clients. The sales team consists of eight account executives, a sales development team of four, and a VP of Sales who runs a weekly pipeline review every Tuesday at 9:00 AM.

This week, the team is six weeks into Q2 with a quarterly target of $1.8M in new ARR. RevOps opens the meeting by showing that total weighted pipeline stands at $3.2M across 47 active opportunities, but stage 3-to-4 conversion has dropped from 62% to 48% over the past three weeks. The VP flags this immediately and asks each AE to explain where their stage 3 deals stand.

During the deal inspection, AE James reveals that his largest opportunity, a $240K deal with a logistics company, has stalled because the prospect's IT security team has introduced a new vendor assessment process that was not anticipated. The VP coaches James to request a joint call with the CISO to address security concerns directly rather than letting the assessment run through email. She also asks the solutions engineer to prepare a pre-completed security questionnaire based on similar deals. Use Best Meeting Planner to schedule these follow-up sessions promptly. Before the meeting closes, each AE states their three priority actions for the week, and RevOps logs them in the CRM for follow-up at next Tuesday's session.

Best Practices

• Inspect deals, not just numbers. Pipeline value on its own is meaningless without understanding deal quality. Ask about stakeholder access, decision criteria, timeline drivers, and competitive positioning for every deal above a certain threshold.
• Use a consistent deal qualification framework. Whether your team uses MEDDPICC, BANT, or a custom methodology, apply it uniformly so that stage definitions are objective and comparable across the team.
• Focus on movement, not static snapshots. The most useful metric is how deals have moved since last week. Deals that have not changed stage or had meaningful activity in two or more weeks should be flagged for review.
• Separate coaching from accountability. The review should be a safe space to discuss challenges and ask for help. If AEs feel the meeting is purely about pressure and judgement, they will sandpaper their updates and hide problems until it is too late.
• Limit the number of deals reviewed in depth. Trying to cover every opportunity in a 60-minute meeting is impossible. Focus on the top 10 to 15 deals by value, plus any at-risk deals flagged by AEs. Trust the CRM data for the rest.
• Update the CRM before the meeting, not during it. AEs should update their opportunities at least 24 hours before the review so that RevOps can prepare accurate reports. Real-time data entry during the meeting wastes everyone's time.
• End with specific, time-bound actions. "Follow up with the prospect" is not an action. "Send the revised proposal to CFO by Thursday and schedule a 15-minute call for Friday" is an action. Precision drives execution.
• Track week-on-week forecast accuracy. Over time, compare each week's forecast to actual results, and bring these trends into the quarterly business review. This reveals systematic biases, such as a tendency to overweight early-stage deals or undercount late-quarter acceleration.

Common Mistakes

• Turning the review into a forecast interrogation. If the meeting feels like a courtroom, AEs will stop being transparent. The goal is to help the team win deals, not to catch people out on numbers.
• Spending too long on won or lost deals. A brief mention of recent wins and losses is fine for morale and learning, but the bulk of the meeting should focus on active pipeline that can still be influenced.
• Accepting vague next steps. "The prospect seemed interested" is not a pipeline update. Push for specifics: who said what, when is the next meeting, what does the prospect need to move forward.
• Ignoring pipeline generation. Incorporate insights from customer feedback reviews to understand what is driving or hindering new interest. Reviewing existing deals without examining the top of the funnel creates a false sense of security. If pipeline creation has dried up, the problem will hit the forecast two to three months later.
• Reviewing every deal at the same depth. A $15K transactional deal does not need the same scrutiny as a $300K enterprise opportunity. Allocate time proportionally to deal value and strategic importance.
• Skipping the review when things look good. The best time to identify emerging risks is when the pipeline appears healthy. Cancelling the review during strong weeks builds a habit of inconsistency that makes the meeting feel punitive when it does happen.
• Not involving solutions engineering early enough. Technical blockers are among the most common reasons deals stall in the middle of the pipeline. Having a solutions engineer in the review ensures these issues surface and get addressed before they become deal-killers.

Related Templates

Related Tools