How to Run a Weekly Sales Pipeline Review in 45 Minutes

A weekly sales pipeline review should take 45 minutes and end with every active deal owned by a named person with a dated next step. If yours runs 90 minutes and produces a status update, the problem is the structure, not the people in the room.

At pre-seed and seed, this meeting sits inside a simple rhythm: weekly 1:1s with each seller, bi-weekly or monthly team forecast calls, and monthly business reviews at leadership level. The weekly session is where deal judgement moves out of the founder's head and into the team's. The agenda below is the one we use at dm(ventures) with founders who still run most deals themselves and now have one to five people selling alongside them. It builds on the go-to-market foundation for early founders that makes any of this repeatable.

The 45 minutes split like this:

• 5 minutes: what moved since last week
• 10 minutes: forecast categories and the number
• 20 minutes: three to five priority deals
• 5 minutes: blockers
• 5 minutes: owners, next steps, one-line summaries

What you need before the first review

You do not need a mature tool stack. You need three things.

• Deals in stages with written exit criteria. A spreadsheet is fine at pre-seed. What is not fine is a stage that means something different to each seller. If you have not standardised your stages yet, start with the steps to a documented revenue engine.
• A list of every deal that could close this quarter, with value, stage, expected close date and the date of the last buyer activity.
• A fixed slot in the calendar, same day, same time, with prep done before anyone joins.

(01) Build your deal sheet before the meeting

Pull every deal that could land this quarter into one view: value, stage, expected close date, probability and days since the last buyer activity. We call it the road to home. For most early teams that is 10 to 25 rows, and five of them decide the quarter.

Keep the top of the funnel separate from real opportunities. For booked calls, a simple weighting works: a discovery call booked counts at 90% (only no-show risk remains), a first call not yet held at 50%, and anything unqualified at 0%. The weights do not need to be clever. They need to stop a list of hopeful conversations from reading like revenue.

Then flag activity gaps. If more than four or five days open up between the first and second call, deal risk rises sharply. Any row with a gap that wide goes on the priority list, whether or not the seller raised it. Mid-market deals need daily attention between reviews; smaller deals usually do not.

(02) Sort every deal into three forecast categories

Sort the sheet into three groups: pipeline, best case and commit. Pipeline is everything real but early. Best case is genuine but unproven. Commit means you would stake your reputation on it.

This sort is the honesty mechanism. Top of funnel is not pipeline, and a booked call is not a qualified opportunity. Founders who skip it tend to carry three or four deals in their head as near-certain and discover in week 11 that none of them had a path to signature. If your pipeline looks thin after the sort, that is useful information, not a bad week. In Salesloft's State of Pipeline Generation survey, 39.6% of sellers said their current pipeline was weaker than the year before (Salesloft), so the answer is usually generation, not optimism. If creation is the gap, work through inbound and outbound priorities rather than reshuffling the same deals.

(03) Inspect deal health with PACT

For every deal in best case or commit, check the four parts of PACT, a common lightweight qualification framework: Pain, Authority, Consequence and Timeline. Twenty minutes covers three to five deals properly, which is the point. Reviewing all 25 produces nothing.

Consequence is the most telling of the four. If the buyer cannot say what happens to their business if they do nothing for two more quarters, the deal is not real yet, whatever the stage says. Pain without consequence produces pilots that never convert.

Authority is where early-stage deals quietly break. In G2's 2026 survey of more than 1,000 B2B software decision-makers, nearly half said their CFO had vetoed an already-approved software purchase in the past year (G2). A champion who likes the product is not authority. Ask who signs, who can veto, and whether either has been on a call.

Check how many people you know on the buyer's side. A commit deal that rests on a single contact belongs in best case until a second person joins the conversation.

Disagreement inside the buying group is normal and does not kill a deal on its own. In a Gartner survey of 632 B2B buyers, 74% of buying teams showed unhealthy conflict during the decision, and groups that reached consensus were 2.5 times more likely to report a high-quality deal (Gartner). So the review question is not whether the buying group agrees. It is what your champion needs to get them there.

(04) Give every deal a named owner and a dated next step

No deal leaves the review without one person responsible and one specific action with a date. "Follow up with legal" is not a next step. "Send the redlined DPA to their counsel on Thursday, call on Friday if there is no reply" is.

For any deal above your average contract value, write a mutual action plan with the buyer rather than for them: the remaining steps, the owner of each and the dates, from security review through legal and procurement to kickoff. A buyer who will not co-own a plan is telling you something about the timeline.

(05) Update the forecast and name what changed

Compare this week's commit and best-case totals with last week's. Then say what moved and why. Each deal advanced, slipped or stayed still. Standing still two weeks running is a slip that has not been admitted yet.

Keep commit ruthlessly small. A forecast that misses by 40% every week teaches nobody anything. A forecast that misses by 10% and explains the gap becomes a management tool, and it is what investors read when they ask whether your first revenue engine exists.

(06) Close with blockers and a one-line summary

Each seller names one blocker, not five. The team decides who unblocks it, usually the founder, and by when. Then each person gives a one-line summary of what they will do before the next review. Write it in the sheet, not in a notebook.

This closing ritual is what makes the process survive a growing team. In Salesloft's survey of 100 frontline sellers and sales managers, 40% of sellers said they frequently deviated from the sales process, and only 20% of managers believed deals followed a repeatable process (Salesloft). Weekly written commitments, checked the following week, close much of that gap. Once you pass three or four sellers, the same discipline is what makes territory and pod structures work.

Troubleshooting: what breaks the review

• The meeting runs over 45 minutes. You are qualifying deals in the room instead of before it. Move the deal sheet and the PACT check into prep, and cap the deep dives at five.
• The forecast does not improve week to week. Read last week's next steps. If they are verbs without dates, the problem is specificity, not judgement.
• Deals stall and nobody notices. Add one rule: any deal with more than four or five days between the first and second call is flagged and goes on the priority list.
• The founder answers every question. Stay quiet for the first deal. Whatever the seller cannot explain is the coaching topic for the month.

Key takeaways

• Sort every deal into pipeline, best case or commit before the meeting starts, and keep commit small enough that you would stake your reputation on it.
• Use Consequence as your sharpest qualification question: no stated cost of doing nothing means the deal moves out of commit this week.
• Do not close the review until every priority deal has one named owner and one dated action written in the sheet.
• Flag any deal with a gap of more than four or five days between first and second call.
• Move qualification work into prep so the 45 minutes buys you decisions, not status updates.

Next steps

Build the deal sheet first, run the 45-minute agenda for four weeks without changing it, and compare forecast with actuals at the end. Most teams find their next steps were too vague in week one and specific by week three. If you want a second read on your own review before you hand it to a first sales hire, Ask Dajana.