Pipeline review meeting template: The agenda, the five reports and the questions marketing should answer

A pipeline review meeting agenda should cover two meetings that share one set of reports: a 30-minute weekly one-on-one between each rep and their manager on 3 to 5 priority deals, and a team review in six blocks. In this example agenda, the team hour runs 60 minutes on five reports (coverage, velocity, reverse funnel, slippage and stalled deals) and gives marketing a 15-minute block to answer for pipeline created.

What a pipeline review meeting agenda should cover

The direct answer: run two meetings with one shared set of reports. In this example, a 60-minute weekly team review looks at the pipeline as a system. A 30-minute one-on-one between each rep and their manager handles individual deals. That split is our method. The 30-minute length has outside support: Sybill's guide states that "the best pipeline reviews run 30 minutes", and its one-on-one agenda opens with 3 minutes of quick wins, then a 5-minute pipeline snapshot, then 15 minutes on priority deals.

Cadence follows the sales cycle. Salesforce describes the review as held weekly or twice a month. In our view, weekly fits teams whose deals close inside a quarter. Twice a month fits longer cycles, where a weekly look shows too little movement to act on.

Set a coverage target before the first meeting. Sybill gives 3x to 4x pipeline coverage for the quarter as the standard benchmark. Derive your own multiple from your win rate with the pipeline coverage calculator.

The five reports and who answers each

The team review runs on five reports. Each one carries a question with a named owner, so the hour does not turn into a deal-by-deal forecast call.

The stalled report needs a threshold, and the sources give two. Sybill flags deals with no activity in 14-plus days. A Sales Growth Company reassesses a deal that "hasn’t advanced in the past 30 days and has no clear next step". Choose one and keep it fixed. For slippage, Sybill's rule applies directly: every deal sitting past its original close date needs a reality check.

Why the team hour stays out of deal coaching

Salesforce argues that group pipeline reviews are almost always a waste of time. It makes an exception when multiple reps are involved in a sale. In our reading, that criticism targets team meetings that coach one rep's deal in front of everyone. The two-meeting split addresses this: coaching happens in the one-on-one, and the team hour covers the five reports and marketing's block.

The copyable agenda in this piece runs the team review in six blocks: last week's commitments, the snapshot, the marketing block, priority deals, slipped dates, and new commitments. Feed the velocity report from the pipeline velocity calculator.

The weekly pipeline meeting agenda you can copy

Two meetings share the name pipeline review, and they need different agendas. The first is the manager and rep one-on-one. The second is the team review, where marketing joins and owns a block of its own.

The rep one-on-one

Sybill describes an agenda that works for weekly one-on-one reviews between a manager and an individual rep. It runs 30 minutes and focuses on 3 to 5 priority deals rather than every open opportunity. It opens with quick wins for 3 minutes, then a pipeline snapshot for 5 minutes, then 15 minutes on priority deals. Marketing has no seat in this meeting, and it should not want one.

The team review with a marketing block

Revenue Grid advises teams to keep each meeting within 60 minutes. The team agenda below fits that limit and adds a block where marketing answers for pipeline created.

In this example, the minutes are our split of the hour: 5 + 10 + 15 + 15 + 10 + 5 = 60. The first block follows Sybill's rule that the action items from this week's review are the first thing you check in next week's review.

In the marketing block, the demand generation leader answers three things from the pipeline-created report: how much new pipeline marketing sourced since the last review, which sources produced it, and what marketing will run to close the gap the snapshot named. If the handoff terms are not written down, settle them in a marketing and sales SLA before this block becomes a debate.

Set the cadence by cycle length

Revenue Grid states that for SaaS companies with 3-12 month sales cycles, team reviews typically occur every two weeks or monthly. For cycles shorter than three months, we think a weekly team review fits, because deals can move a stage between meetings. Check your own numbers against sales cycle length benchmarks and pick the cadence first. Keep the rep one-on-one weekly either way.

The five reports, their formulas and the question each answers

Each report below maps to one decision. The formula column matches how we define the inputs in our calculators, so the number on the screen and the number in the tool agree. The threshold and action columns are our reading of when a report earns airtime.

The slippage row follows the advice to challenge close dates that keep moving without explanation.

Building each report from CRM filters

Most CRM sales reports share the same filter set. In HubSpot, the date filter filters the records that are within this date, based on their property values, the rep filter filters the records based on their owners, and the pipeline filter filters the records based on their deal pipeline.

1. Set the date range to the close date for coverage and slippage, and to the create date for the reverse funnel pace.
2. Filter to one pipeline so new business and renewals do not mix.
3. Group by owner for the one-on-ones, by team for the leadership review.

The deal change history report already labels two of the inputs. It defines Close Date Pushed as deals for which the close date was within report timeframe but then were pushed beyond the report timeframe, and Stage Moved Backward as deals that moved to a new pipeline stage that had lower probability during the report timeframe. The average deal size report shows the average deal amount across the deals per deal owner or team, which feeds both velocity and the reverse funnel.

A worked velocity check

Open opportunities:   40
Win rate:             25%
Average deal size:    $30,000
Sales cycle:          90 days

Velocity = (40 × 0.25 × 30,000) ÷ 90 = $3,333 per day

Run your own inputs in the pipeline velocity calculator and size the gap with the reverse funnel calculator.

What marketing should answer on coverage and pipeline created

Sales owns deal movement in the meeting. Marketing owns the supply of new opportunities, and it should arrive with three answers ready, not a slide of lead counts.

1. Is the pipeline big enough for the target? A pipeline review exists in part to show whether the pipeline is big enough and strong enough to hit sales goals. Marketing answers with the pipeline coverage figure for the current and next quarter. It does not use the opportunity count.
2. How does created pipeline compare with the reverse-funnel target, by source and segment?
3. Which program changes follow? Each change needs a named owner and a date.

Build the target before the meeting

Work the target backward from bookings with the reverse funnel calculator, then split it by source and segment.

Pipeline to create = Bookings target / Win rate
Opportunities needed = Pipeline to create / Average deal size
Target by source = Pipeline to create x planned source share
Pace to date (%) = Created to date / Target to date x 100

Here is an illustrative quarter. In this example, the plan splits it 50% marketing-sourced, 35% sales-sourced and 15% partner-sourced.

When coverage is weak, the guidance is that the focus needs to shift toward opportunity creation rather than progressing the deals already in the pipeline. That is the point where marketing's answer changes the meeting. A healthy pipeline also needs new pipeline generation that keeps future quarters covered. Report next quarter's created pipeline as its own line.

Keep sourced and influenced apart

Report marketing-sourced pipeline and marketing-influenced pipeline as two separate numbers. Never add them together. An influenced opportunity can also be sales-sourced, so a combined figure counts the same dollar twice. We think that double count is the fastest way for marketing to lose the room. The rules for each are in our method for sourced versus influenced. Sourced pipeline answers the coverage question. Influenced pipeline shows where programs touch deals that sales opened.

Close the block with one sentence for each program change: the row it fixes, the dollar gap and the date marketing will report back.

How to read stage conversion and velocity without arguing about definitions

Stage conversion only means something when every rep moves a deal for the same reason. HubSpot describes stages as steps that signal where a record is in a process.

The fix is to write exit criteria for each stage and keep them in the pipeline settings, where everyone sees the same text. Control who edits them: Edit property settings permissions are required to create and edit pipelines or stages. Keep one pipeline unless the process truly differs. HubSpot's guidance is that separate pipelines are only recommended if your processes have unique stages.

Stage: Solution fit
Exit criteria (all required):
- Buyer confirmed the problem in their words (logged in notes)
- Economic buyer named on the deal record
- Next meeting booked with a date
Owner of this definition: RevOps
Last changed: date / Reason: text

When a definition changes mid-quarter, conversion before and after the change is not comparable, so mark the date on the trend chart.

Reading a drop at one stage

1. Confirm the exit criteria did not change in the period.
2. Pull the deal change history report, which shows changes to stages, amounts and close dates, and list deals that entered the stage.
3. Split the drop by source and by owner. A drop concentrated in one rep is a coaching item. A drop concentrated in one source is a marketing item, often an SQL definition that let weaker deals in upstream.
4. Check backward moves, covered in the reports section, before calling it lost demand.

Separating volume from conversion

Velocity uses four inputs:

Pipeline velocity per day =
  (open opportunities x win rate x average deal size) / sales cycle length in days

A falling velocity number alone starts arguments. The inputs end them.

Compare your stage rates against funnel conversion benchmarks and win rate benchmarks, and test scenarios in the pipeline velocity calculator.

How to spot stalled deals with a pipeline aging report

An accounts receivable aging report sorts open invoices by how long they have been due, with standard buckets of 0, 30 days, 31, 60 days, 61, 90 days, and over 90 days. Swap invoices for open deals and due dates for stage entry dates, and you have a pipeline aging report. We borrow the method only. Finance's outcome figures stay with finance.

Fix the counting rule first

Every aging report depends on one anchor date. Indiana University's controller calculates days outstanding as the number of days between the approval date of an invoice and the report run date. For deals, use the date the deal entered its current stage, and use the report run date as the end point.

Pick the anchor once and keep it. Upflow's guidance on invoice aging applies here too: Either works, as long as you use the same method every time so your reports stay comparable. If one week counts from creation date and the next from stage entry, the buckets move and the deals do not.

Days in stage  = report_run_date - stage_entry_date
Bucket (Sheets) = IF(E2<=30,"0-30",IF(E2<=60,"31-60",IF(E2<=90,"61-90","90+")))
  where E2 = days in stage
Bucket share   = sum of amount in bucket / sum of amount in all open deals

Segment, then assign the next step

Finance does not treat every late invoice the same. Stripe's method says to segment customers based on risk profiles like payment history, creditworthiness, or account size. For deals, segment by amount, by stage and by whether a buyer has engaged recently. The same source recommends you incorporate a section for action items or next steps. Each row gets one next step and one named owner.

Sort by bucket, then by amount. The review starts with the oldest buckets and the rows in them that carry the most value.

Do not borrow the collection rates

Stripe cites a 2022 analysis in which an invoice that remained unpaid after 90 days had only an 18% chance of being paid. That figure describes invoices a customer already agreed to pay. An open deal has no such agreement, so in our reading the number says nothing about a 90-day-old opportunity's odds of closing. Build your own close rate by bucket from your CRM history and compare against that. For context on what a normal stage duration looks like, see our sales cycle length benchmarks.

A worked example of one weekly pipeline review

The numbers below are invented for illustration. They show how one filled template reads for a single business unit in week six of a quarter.

The snapshot

Remaining target   = 1,200,000 - 400,000 = 800,000
Coverage ratio     = 2,400,000 / 800,000  = 3.0x

You can rerun this with your own figures in the pipeline coverage calculator.

The stage that dropped

The team agreed the drop was the topic for this week, not the total.

Velocity

Velocity = (open opportunities x win rate x average deal size) / cycle length in days
         = (60 x 0.25 x 40,000) / 75
         = 600,000 / 75
         = 8,000 per day

The five decisions and who owns them

The exit-criteria fix follows a method Salesforce describes: crafting two to three questions for each stage, with answers that show whether a deal is ready to move. In our reading, a conversion drop concentrated in one stage points to a definition problem before it points to a lead quality problem, so that is where the team started.

Every decision has one named owner and a date. For follow-through, Salesforce suggests that managers connect with reps by phone or email at the end of the week. The five rows above become the first agenda item at the next review.

How to turn the pipeline review into actions and track them between meetings

A review that ends without a written record leaves no way to test follow-through. Salesforce's sample agenda for a rep review closes with a block of "5 minutes: Wrap up and identify action items". Use that block to write the log, not to recap the deals.

Write the action log before anyone leaves

Each line answers three things: what the obstacle is, who removes it and which number should change. Salesforce frames the owner question as whether the rep, the manager or executive leadership takes each obstacle, and says actions should be "clearly defined and aligned with metrics so both managers and reps can measure progress." Copy this into a shared sheet or a CRM note field:

ACTION LOG: week of date
ID | Deal | Obstacle | Action | Owner | Due date | Metric it should move | Value now | Value expected | Status
A1 | deal | obstacle | action | name | date | stage / close date / amount / forecast category |   |   | open / done / slipped

One owner per line. If two people share an action, split it into two lines.

Check follow-through with change tracking

Do not rely on the rep's account of what happened. Check the record. In Salesforce, Pipeline Inspection "can show where opportunities were moved in or out, where amounts and close dates changed, and changes in stage and forecast category." It does this by annotating the Amount, Close Date, Forecast Category, and Stage fields with colors and icons, and it depends on historical trending on the opportunities object, so confirm that trending is switched on before the first review. Managers can also bookmark specific deals for further discussion, which gives you the agenda for the next call.

Open the next meeting with the log

Spend the first minutes on the log only: done, slipped, or dropped with a reason. Then move forward. Salesforce argues each review should "focus on action items for the week ahead, not what happened the week before," so we keep the backward check short and carry slipped lines into the new log with a new due date. A line that slips twice goes to the manager as owner.

What this page does not cover

This page does not cover forecasting methods, sales compensation, or how to choose or set up a customer relationship management (CRM) system beyond the report filters it describes. The figures in the worked examples are illustrative, and none of this is financial or legal advice.