How to Run a Weekly Pipeline Review That Works

Most sales teams hold a weekly pipeline review. Few get much out of it. The usual version is a status meeting: reps read deal names from the CRM, the manager nods, someone says "they're very interested," and everyone leaves knowing roughly what they knew an hour earlier. The forecast slips anyway. The same deals sit in "Proposal Sent" for six weeks. Reps start treating the meeting as an interrogation to survive.

I've run pipeline reviews as a founder, as a sales leader, and with outbound teams across several markets. My conclusion is simple: a pipeline review works when it changes what people do next week. If it doesn't produce specific actions on specific deals, it's theater. Below is the format I use, the preparation it needs, the questions that matter, and the mistakes I've made along the way.

Why Most Pipeline Reviews Fail

Before fixing the meeting, it helps to name what goes wrong. In my experience, failed pipeline reviews share a few patterns:

• No shared stage definitions. One rep's "Qualified" is another rep's "had a nice first call." If stages don't have clear exit criteria, the pipeline is an opinion survey.
• Reporting instead of inspecting. Reps narrate. Managers listen. Nobody challenges the evidence behind a deal.
• Every deal gets equal airtime. A €5,000 deal in discovery gets the same ten minutes as a €120,000 deal two weeks from close.
• No follow-through. Actions are mentioned but never written down. Next week starts from zero.
• It's mixed up with the forecast call and coaching sessions. One meeting tries to do three jobs and does none of them well.

The fix isn't a new tool or a longer meeting. It's structure and discipline.

Pipeline Review, Forecast Call, and Deal Coaching Are Different Meetings

The single most useful change I've made is separating three conversations that often get blended together.

1. Pipeline review (weekly, team or 1:1): Is the pipeline healthy enough to hit future targets? Are deals progressing? Where are we stuck?
2. Forecast call (weekly or biweekly, leadership): What will close this month or quarter, and how confident are we?
3. Deal coaching (ad hoc, 1:1): How do we win this specific complex deal? What's the strategy for the next meeting?

The pipeline review looks at the whole funnel, including early-stage health and coverage for next quarter. The forecast call looks only at late-stage deals. Coaching goes deep on one opportunity. When you keep them separate, each meeting gets shorter and sharper.

If you're building a team from the ground up, set this cadence early. Retrofitting habits is harder than starting with them, which is something I covered in my post on how to build an outbound sales team from scratch.

Before the Meeting: The Preparation That Makes It Work

A good pipeline review is about 70% preparation. If people walk in unprepared, you spend the meeting doing data entry.

1. Define stages with exit criteria

Every stage needs an objective, verifiable condition for moving forward. Here's a simplified example for a mid-market B2B deal:

• Discovery: First meeting held. Prospect has confirmed a problem worth discussing.
• Qualified: Pain, budget range, decision process, and timeline identified. At least one champion named.
• Solution/Demo: Tailored demo delivered to more than one stakeholder. Success criteria agreed.
• Proposal: Written proposal sent after a verbal walk-through. Economic buyer has seen pricing.
• Negotiation: Prospect actively negotiating terms. Procurement or legal involved.
• Closed Won / Closed Lost.

Notice that "sent a proposal" alone doesn't qualify. If the economic buyer hasn't seen pricing, the deal isn't really in Proposal, no matter what the CRM says.

2. Set a CRM deadline

I ask reps to update their pipeline by a fixed time, such as Monday at 12:00 for a Tuesday morning review. Every open deal must have:

• A realistic close date (not the last day of the quarter by default)
• An amount based on an actual pricing conversation
• A next step with a date, written as an action ("Security review call with IT lead, 14 March"), not a hope ("Waiting to hear back")

That last rule alone will clean up a surprising amount of your pipeline.

3. Pull a short pre-read

The manager or RevOps person should prepare a one-page snapshot before the meeting. Keep it to the essentials:

• Total pipeline by stage, compared to last week
• Deals that moved forward, moved backward, or were created this week
• Deals with close dates that slipped
• Deals with no activity in 14+ days
• Pipeline coverage for this quarter and next

When everyone sees the same numbers before the meeting, you skip the "let me find that" moments.

The 60-Minute Agenda

For a team of four to eight reps, an hour is enough if you stay disciplined. Larger teams should split into pods or run 1:1 reviews and a shorter team session.

Minutes 0–10: The numbers

Start with the snapshot. No deal stories yet, only the shape of the pipeline.

Say a team has a quarterly target of €300,000. Many teams use roughly 3x coverage as a rule of thumb, though the right multiple depends on your historical win rate. If your win rate is around one in three, you'd want about €900,000 in qualified pipeline for the quarter. If you have €600,000, the conversation that week is not about polishing late-stage deals. It's about where the missing €300,000 of pipeline comes from.

Questions for this block:

• Did total qualified pipeline grow or shrink?
• How much new pipeline did we create this week versus our weekly target?
• Is next quarter's pipeline building, or are we borrowing from the future?

Minutes 10–35: Inspect the deals that matter

Don't go deal by deal through the whole CRM. Focus on:

• The top deals by value in later stages
• Deals that changed stage this week, in either direction
• Deals with a close date in the next 30 days

For each, the rep gives a 60-second summary using a consistent format: who the buyer is, what problem we solve, where it stands, what happens next, and what could kill it. The manager then asks two or three evidence-based questions (more on those below).

Minutes 35–50: Stuck, slipping, and dead deals

This is where most of the real value sits, and where most teams avoid looking.

• Stuck deals: In the same stage longer than your typical stage duration. If deals normally spend about two weeks in Solution, anything at five weeks needs a decision.
• Slipping deals: Close date pushed more than once. One push is normal. Two is a pattern. Three usually means the deal isn't real in this timeframe.
• Zombie deals: No meaningful buyer activity in 21+ days. Either create a specific re-engagement plan or close them as lost.

I encourage reps to close deals as lost without penalty. A smaller, honest pipeline is worth far more than a bloated one. Closing a zombie deal is a sign of good judgment, not failure.

Minutes 50–60: Commitments

End by writing down specific actions, with owners and dates. For example:

• "Ayşe: book a call with the CFO at the logistics prospect before Friday to confirm budget."
• "Mert: send a mutual action plan to the software prospect by Wednesday."
• "Team: create €80,000 in new qualified pipeline this week to close the coverage gap."

Next week's meeting starts by reviewing these commitments. That's the habit that turns the review from a report into a management system.

The Questions That Actually Reveal Deal Health

The quality of a pipeline review depends on the quality of the questions. Vague questions get vague answers. "How's the deal going?" will always get "Good, they're interested."

Here are the questions I rely on:

• "What did the buyer do, not say, this week?" Did they introduce a new stakeholder, share internal data, or book the next meeting? Actions are evidence. Compliments aren't.
• "Who is the economic buyer, and have we spoken to them?" If the answer is no, the deal is probably at an earlier stage than the CRM shows.
• "What happens if they do nothing?" If there's no cost to inaction, there's no urgency, and the close date is a guess.
• "Why this close date?" Is it tied to a budget cycle, a contract renewal, or a project launch? Or did the rep pick the end of the month?
• "Who else are they evaluating, including doing it in-house?" "No competition" usually means we don't know.
• "What's the next step, and is it in the buyer's calendar?" A next step that lives only in our CRM isn't a next step.

These questions also build reps' skills over time. After a few months, good reps start asking themselves these questions before the meeting, which is the point.

The Metrics to Track Week Over Week

You don't need a dashboard with 40 charts. Track a handful of metrics consistently and watch the trends.

1. Pipeline coverage: Qualified pipeline divided by remaining target, for this quarter and next.
2. New pipeline created: Value and number of new qualified opportunities per week. This is the leading indicator most teams ignore until it's too late.
3. Stage conversion rates: What share of deals move from each stage to the next. A sudden drop between Demo and Proposal tells you something specific.
4. Average days in stage: Helps you define "stuck" with your own data rather than gut feel.
5. Sales cycle length: From creation to close, for won deals.
6. Win rate: By segment, deal size, and lead source.

Win rate by lead source is especially useful. If inbound deals close at twice the rate of outbound deals, that changes how much outbound pipeline you need. It's also a good input when you look at how buyer behavior is changing, a topic I explored in B2B buying shifts toward digital.

A Worked Example

Here's a simplified version of a review I'd run with a five-person team.

The numbers: Quarterly target is €300,000. Closed so far: €70,000. Remaining: €230,000. Qualified pipeline for the quarter: €520,000, which is about 2.3x coverage against what's left. Historical win rate is around 30%, so we need closer to 3.3x. Gap: roughly €240,000 of qualified pipeline.

Deal inspection: The largest deal, €60,000, is in Negotiation with a close date in two weeks. When asked, the rep confirms legal is reviewing the contract and there's a signing call booked. Good evidence. The second largest, €45,000, is marked Proposal, but the economic buyer hasn't seen pricing. We move it back to Solution and set an action to get a meeting with the buyer.

Stuck and slipping: Three deals totaling €55,000 have had their close date pushed twice and show no buyer activity in over three weeks. Two get closed as lost. One gets a final re-engagement plan with a clear deadline.

Result: Honest pipeline drops from €520,000 to around €430,000. The coverage gap is now bigger, but real. The team leaves with a clear priority: generate new qualified pipeline, not just chase existing deals.

This is where the review connects directly to prospecting. When the gap is pipeline volume, the answer is more targeted outbound: better lists, tighter ideal customer profiles, and consistent sequences. Tools like Apollo.io help with contact data and sequencing. Some teams bring in specialist support, such as outbound lead generation for B2B SaaS from SAAS Corner, to refill the top of the funnel while account executives stay focused on closing.

Adapting the Format for Founders and Small Teams

If you're a founder selling on your own or with one or two reps, a 60-minute team meeting is overkill. The principles still apply, just compressed:

• Block 30 minutes every Friday to review your own pipeline using the same questions.
• Be ruthless about closing zombie deals. Founders are often the worst offenders here, because every deal feels personal.
• Track new pipeline created as your main weekly metric. Early-stage companies rarely fail because of poor late-stage execution. They fail because the top of the funnel dries up.

I've also found that AI tools now help with preparation: summarizing call notes, flagging deals with no recent activity, or drafting the weekly snapshot. They don't replace the judgment in the room, though. I wrote more about where automation helps and where it doesn't in Can AI replace your SDRs? A practical answer.

Common Mistakes to Avoid

• Using the review to blame people. If reps fear the meeting, they'll inflate the pipeline to protect themselves. You want honesty, so reward it.
• Letting the manager do all the talking. The rep should own their deals. The manager's job is to ask questions, not to tell stories.
• Skipping weeks. Consistency matters more than perfection. A short review every week beats a long one every month.
• Ignoring early-stage pipeline. If you only inspect late-stage deals, you'll discover your coverage problem when it's too late to fix.
• No written record. Keep a shared document or CRM note with weekly commitments. Memory isn't a system.

Conclusion

A weekly pipeline review that works isn't complicated. It needs clear stage definitions, a CRM that's updated before the meeting, a tight agenda, evidence-based questions, and written commitments that carry into the following week. Separate it from your forecast call and your deal coaching. Give the most airtime to the deals and problems that matter most. Make it safe to close dead deals. Over a few months, you'll find your forecast gets more accurate, your reps get sharper, and the meeting becomes something people value rather than endure.

If you're building or rebuilding a sales process and want to compare notes on pipeline management, outbound, or scaling a B2B team, I'd be glad to hear from you. You can reach me through [my personal site](/).

Related Posts

• When Should a Founder Hire Their First Sales Rep?
• Can AI Replace Your SDRs? A Practical Answer
• How to Build an Outbound Sales Team from Scratch
• Adapting to the New B2B Sales Landscape