How to Run a Weekly Pipeline Review (Template Included)

A weekly pipeline review is one of those things that everyone knows they should do, but most teams either skip entirely or run so badly that it becomes a waste of time. The meeting either turns into a status update where reps read out what happened last week, or it becomes an interrogation where the manager grills people on numbers while everyone else checks their phone.

Neither version is useful. A good pipeline review takes 30 minutes, focuses on what needs to happen next week (not what happened last week), and gives you an honest picture of where your revenue is actually going to come from. It's the single most important meeting in a sales team's week.

This article gives you a framework for running an effective pipeline review, including a section-by-section template you can copy and use starting this week. We'll cover what to review, how to handle stuck deals, and how to avoid the common mistakes that make these meetings pointless.

Why Weekly Pipeline Reviews Matter

A pipeline review isn't a sales meeting, a forecast call, or a coaching session — though it touches all three. Its purpose is to answer one question: "Based on what we know right now, which deals are going to move forward this week, and what do we need to do to make that happen?"

Without a regular pipeline review, several things go wrong:

• Deals stall without anyone noticing. A prospect who went quiet three weeks ago is still sitting in "Proposal Sent" stage, and nobody's acknowledged that it's dead or needs a recovery plan.
• Forecasts become fiction. The pipeline looks healthy because it's full of deals that haven't been scrutinised. When the end of the quarter arrives, half the "committed" deals slip.
• Reps don't get help on stuck deals. A rep struggling with a specific objection or decision-maker doesn't have a forum to ask for advice, so they keep banging their head against the wall alone.
• New leads get ignored. Fresh, high-intent leads sit in the CRM while reps focus on whatever they were working on yesterday. The hottest leads cool down before anyone touches them.

A weekly review catches all of this. It creates a rhythm of accountability, inspection, and problem-solving that keeps the pipeline honest and moving.

If you're also tracking lead quality, our guide to measuring warm lead quality pairs well with the pipeline review framework below.

What to Cover in 30 Minutes

Thirty minutes is tight, and that's the point. Parkinson's law applies to meetings more than anywhere else — if you give it an hour, it'll take an hour and accomplish the same amount. Here's the structure:

• Minutes 1–5: Quick wins and closed deals. Start with good news. What closed this week? What meetings were booked? Celebrate briefly, then move on.
• Minutes 5–15: Active deals — by stage. Walk through deals in the later stages first (Proposal, Negotiation, Verbal Commit), then move to earlier stages (Discovery, Qualification). For each deal, ask: what's the next action, when is it happening, and is anything blocking it?
• Minutes 15–22: Stuck and at-risk deals. Flag anything that hasn't moved stages in 2+ weeks. For each stuck deal, decide: push harder, try a different approach, or move it out of the pipeline?
• Minutes 22–27: New leads and fresh pipeline. Review any new leads that came in this week — inbound, outbound replies, referrals. Who's picking them up? What's the plan?
• Minutes 27–30: Actions and ownership. Recap who's doing what before the next review. Every deal discussed should have a clear next step and an owner.

That's it. No deep strategy discussions. No training. No process debates. Those belong in separate meetings. The pipeline review is about inspection and action.

The Review Template: Section by Section

Here's a template you can copy into a Google Doc, Notion page, or even a spreadsheet. Use it to structure every weekly review.

Section 1: Scoreboard (2 minutes)

Fill this in before the meeting so everyone can see it when they walk in.

• Deals closed this week: [number and total value]
• Meetings booked this week: [number]
• New leads added to pipeline: [number]
• Pipeline value (total open): [dollar amount]
• Deals expected to close this month: [number and value]

Don't spend time discussing these numbers — they're context for the conversation that follows. If someone wants to deep-dive on metrics, schedule a separate call.

Section 2: Deal-by-Deal Review (12 minutes)

For each active deal in late stages, capture:

• Deal name and value
• Current stage
• Days in current stage
• Next action — specific, not vague. "Send revised proposal by Wednesday" beats "follow up."
• Confidence level — each rep rates their own deal: Green (on track), Yellow (needs attention), Red (at risk).
• Blockers — anything preventing the deal from moving forward?

Not every deal needs detailed discussion. If a deal is Green with a clear next step, say "On track, next step is X, moving on." Spend the time on Yellow and Red deals.

Section 3: Stuck Deals (7 minutes)

Pull a list of deals that have been in the same stage for more than your average sales cycle length at that stage. If your average time in "Proposal" is 5 days and a deal has been there for 15, it's stuck.

For each stuck deal, decide one of three things:

• Revive it. Assign a specific action to break the logjam — a different contact, a new angle, a break-up email, an executive referral.
• Nurture it. Move it to a nurture sequence and remove it from active pipeline. It's not dead, but it's not getting attention this week.
• Kill it. Mark it as lost and move on. Keeping dead deals in the pipeline inflates your forecast and wastes mental energy.

Section 4: New Leads (5 minutes)

Review fresh leads that entered this week. For each one:

• Source (inbound, outbound, referral, intent signal)
• ICP fit (quick assessment — strong, moderate, weak)
• Owner (who's working this lead?)
• First action and deadline

If you're using a CRM set up for intent-based pipeline management, this section is where intent-triggered leads get assigned and discussed.

Section 5: Actions Summary (4 minutes)

End the meeting with a quick recap of actions. Each action should have three elements: what, who, and by when. Write them down in the shared template so they're visible to everyone. These become the first checkpoint at the start of next week's review — did the actions happen?

How to Handle Stuck Deals and Stale Leads

Stuck deals are the biggest source of pipeline inflation. They sit there looking like revenue, but they're not going anywhere. Here's a practical framework for dealing with them.

Define "stuck" with a number, not a feeling. If your average deal moves from Discovery to Proposal in 7 days, any deal that's been in Discovery for 14+ days is stuck. Use actual stage-duration data from your CRM, not gut feeling. If you don't have that data yet, start tracking it — even in a spreadsheet.

Apply the 3-touch rule before killing a deal. Before marking a deal as lost, make sure you've tried at least three different approaches: different channel (email vs LinkedIn vs phone), different person at the company, or different angle (value prop, case study, introduction from a mutual connection). If three diverse touches get no response over two weeks, the deal is effectively dead.

Separate "not now" from "not ever." A prospect who says "We're interested but not until Q3" is a nurture lead, not a dead one. Move them to a dated follow-up with a specific re-engagement plan. A prospect who says "We went with a competitor" is a loss — mark it, learn from it, and move on.

Track your "kill rate." A healthy pipeline review should result in 10–20% of stuck deals being removed each week. If you're not killing anything, you're not being honest. If you're killing 50%+, your qualification process needs work.

Stale leads — leads that were never worked properly — need a different approach. If a lead is more than 7 days old and nobody has contacted them, either assign them immediately or archive them. Old leads with no outreach are worse than no leads at all — they create the illusion of pipeline without any actual movement.

Common Mistakes and How to Avoid Them

Turning the review into a status update. "I called them on Tuesday. They said they'd get back to me. I'll follow up next week." That's not a review — that's a diary entry. Every deal discussed should result in a specific next action, not a description of what happened.

Reviewing every deal every week. You don't have time, and you don't need to. Focus on deals in late stages (close to revenue), stuck deals (at risk), and new leads (need assignment). Early-stage deals that are progressing normally can be reviewed every other week.

No pre-work. If reps haven't updated their CRM before the meeting, you'll spend half the time asking "what's the latest on this?" Require CRM updates by end-of-day the day before the review. No update, no review.

Manager-only talking. If the review is just the manager asking questions and reps answering, it's an interrogation. Encourage peer discussion: "Has anyone else dealt with this objection?" or "Who has a contact at that company?" The best insights often come from other reps, not the manager.

Not tracking actions. If you don't write down the actions and check them the following week, the review has no teeth. People will say what they plan to do, not do it, and say something different next week. Document actions and follow up.

Skipping the review when things are "busy." This is when you need it most. The pipeline review is the mechanism that prevents busy weeks from turning into chaotic, unproductive ones. Never skip it.

How This Connects to Intent-Based Lead Gen

If you're using intent data to generate leads — either from your own monitoring or through a service — the weekly pipeline review is where those leads get integrated into your workflow.

Intent-triggered leads have a shorter shelf life than cold outbound leads. If someone is actively evaluating solutions and you wait two weeks to contact them, you've likely missed the window. The "New Leads" section of your pipeline review is where you catch these and make sure they're being worked immediately.

The review also helps you track the quality of your lead sources over time. Are intent-triggered leads converting at a higher rate than cold outbound? Are referrals better than both? This data builds up week over week and helps you make better decisions about where to invest your prospecting budget.

For teams using Totalremoto's intent-based lead generation, the weekly review is where you assess the leads we deliver, track how they're progressing through your pipeline, and give us feedback on quality so we can refine targeting.

Frequently Asked Questions

How many people should be in a pipeline review?

Keep it small — the sales team and whoever manages pipeline (usually a sales manager or founder). Typically 3–8 people. If you have more than 8, split into two groups (e.g. by territory or deal size). Beyond 8 people, the meeting becomes too slow, and most attendees spend most of the time waiting for their deals to be discussed.

What if our team is just one or two people?

You still need a review — it's just with yourself. Block 20 minutes every Monday. Open your CRM or pipeline spreadsheet. Go through the same sections: wins, active deals, stuck deals, new leads, actions. The discipline of reviewing your own pipeline weekly prevents the drift that happens when you're heads-down in execution and not looking at the big picture.

Should we do the review at the start or end of the week?

Monday morning or Tuesday morning works best for most teams. You get clarity at the start of the week about what to focus on. Friday reviews tend to be low-energy and the actions don't get started until Monday anyway. If you're a global team, pick whatever day gives you the most overlap across time zones.

What CRM setup works best for pipeline reviews?

At minimum, you need: deal stages that reflect your actual sales process, a "last activity date" field, a "next step" field, and the ability to sort by stage and value. Custom fields for confidence level (Green/Yellow/Red) and lead source are helpful but not essential. Any CRM can do this — HubSpot, Pipedrive, even a well-structured spreadsheet. The tool matters less than the discipline of keeping it updated.

What if reps resist the review or see it as micromanagement?

This usually happens when the review is run as an interrogation rather than a problem-solving session. Reframe it: "This isn't about checking up on you. It's about making sure you have what you need to close deals." Focus on helping reps unstick their deals, not grilling them on activity metrics. If the review consistently helps reps win deals, the resistance disappears.

How do I know if our pipeline reviews are working?

Track two things: forecast accuracy and pipeline velocity. If your forecast accuracy improves (actual revenue comes closer to predicted revenue each month), the reviews are adding clarity. If pipeline velocity increases (deals move through stages faster on average), the reviews are driving action. If neither metric improves after 4–6 weeks of consistent reviews, the format needs adjusting.