A pipeline review cadence is the schedule for live deal inspection. It also names the handoff each meeting owes the next one. Set the rhythm from the buying motion, not from a calendar habit. A weekly review that only rereads CRM fields is a status meeting. A monthly review that tries to coach every deal is already late.
Heads of Sales, Revenue Operations, and Enablement feel the gap in different places. Sales wants a meeting that changes the next customer conversation. RevOps wants a rhythm that keeps stage, date, and next step honest. Enablement wants a pattern that can become coaching, a sharper deck, or a better demo script. Sales enablement consulting is where that rhythm gets designed. One standing meeting cannot do all three jobs at once.
What should a pipeline review cadence decide?
The cadence decides three things only: who meets, how often they meet, and what must be true before the meeting ends. It does not decide how to inspect a single opportunity. That work belongs on the MEDDIC pipeline review page. It also does not design the whole company rhythm. That work belongs on the revenue operating cadence page.
Use this test. If the team canceled the meeting, which customer action would slip? If the honest answer is "none," the meeting is a report. If the answer is "the seller would walk into Thursday's call without a named buyer step," the meeting earns its place on the calendar.
Summary: A useful pipeline review cadence names the forum, the trigger, and the handoff. It does not try to be the forecast call, the coaching session, and the quarterly plan at the same time.
- Forum: the people who can change the next customer step.
- Trigger: a buyer event, a stalled next step, or a stage change, not a full pipeline read-through.
- Handoff: one owner, one customer-facing action, and a date the next review can check.
How often should each forum meet?
Match the interval to how fast the buyer can change the deal. A 30-day land-and-expand motion needs a shorter loop than a nine-month enterprise evaluation. Research from Vantage Point Performance and the Sales Management Association, reported by Jason Jordan in Entrepreneur, found that companies effective at pipeline management grew revenue 15 percent faster than peers who were not. The study covered 62 B2B companies. The point is not a magic meeting count. The point is that a managed rhythm beats an unmanaged one.
RevCentric's Forecasting and Qualification work starts from the same idea. The playbook names a preferred forecasting cadence, then the questions for one-to-ones, team calls, and QBRs, before anyone argues about a dashboard. Classroom time is short. The longer block is live coaching on the calls the team already runs. Sellers teaching sellers means the operator sits in the real review, not a slide about reviews.
Four forums. Each one makes a single decision.| Forum | Interval | Who attends | Decision |
|---|---|---|---|
| Deal inspection | Weekly, or sooner. | Seller and manager. | Advance, slip, or stop. |
| Pattern review | Monthly. | Managers, RevOps, Enablement. | Pick one coaching fix. |
| Assumption check | Quarterly. | Sales, RevOps, Enablement. | Keep or revise stage rules. |
| Exception | On a named trigger. | Whoever can unblock it. | Reset the path, or wait. |
These intervals are a starting design, not a promise of results. A team with few complex deals may fold the weekly inspection into an existing one-to-one. A team with a short transactional cycle may need the deal forum twice a week and can skip a separate monthly meeting. Keep the decision. Drop the extra meeting.
What belongs in the weekly deal forum?
Bring only deals that need a decision this week. A useful filter is small: close date moved, stage changed, a buyer meeting is on the calendar, or nothing customer-facing has happened since the last review. Reading every open opportunity trains sellers to prepare a speech instead of a next step.
End each deal with one of three outcomes:
- Advance. Name the customer action, the owner, and the date.
- Slip. Say what evidence is missing and which date is no longer credible.
- Stop. Remove it from the active path when the buyer has no agreed next step.
Do not settle the commit number here. Route that judgment to the forecast call framework. When one meeting tries to coach, forecast, and inspect, the team rushes the evidence so it can argue about the date.

How should Sales, RevOps, and Enablement split the rhythm?
Give each leader a different question so the same hour is not fought over three times.
Head of Sales
Own the weekly deal forum and the exception trigger. The question is whether the seller will walk into the next call with a buyer-owned step. If the same stall shows up on three deals, hand the pattern to Enablement instead of reteaching it deal by deal.
Head of Revenue Operations
Own the definition of a meaningful change and the monthly read of whether the stage rules still match the motion. A note in the CRM is not movement. A changed stage, a changed close date, or a customer-confirmed next step is. RevOps should also say when the weekly forum is duplicating the forecast call, and cut one of them.
Head of Enablement
Own the monthly pattern, not the live deal. If sellers keep failing the same moment, the fix is a concrete asset: a prospecting note, a sales deck page, a demo script, or a proof-of-value plan. Teaching in the trenches means practicing that asset on a real upcoming call, not adding another workshop.
RevCentric runs that split as a program, not as a slide. Playbook design sets the cadence and the questions. A short classroom block teaches them. Live coaching then sits inside the one-to-ones and forecast calls the team already holds. Hours vary by engagement. They are a design input, not a guaranteed outcome.
How do you know the cadence is too heavy or too light?
Watch the handoff, not the attendance.
- Too heavy. Sellers update fields the morning of the meeting, and the same deals return next week with no new buyer step.
- Too light. A deal sits unchanged across two intervals while a buyer meeting comes and goes with no manager look.
- Split wrong. The weekly forum debates coverage math, or the monthly forum reopens individual close dates.
- No exit. Completed actions stay on the list, so the next meeting starts with history instead of the next call.
Fix the light cadence by adding a trigger, not by adding an hour. A security review that slips, an economic buyer who will not meet, or a close date that moved twice should pull that deal forward. Fix the heavy cadence by cutting deals that have no decision this interval.
The broader sales operating model still owns roles, metrics, and how the management system fits together. This page only sets how often pipeline reviews happen and what they must hand off. If the stage definitions themselves are the problem, start with how the sales process should follow buyer evidence, then come back and set the rhythm.
Dick Dunkel authored MEDDIC at PTC in 1996. RevCentric, the authors of MEDDIC, uses that qualification language inside the review, not as a second meeting. MEDDPIC, MEDDPICC, and MEDDICC variants belong in the evidence check on the pipeline review page. They do not change how often the forum should meet.
What should you do in the next two weeks?
Keep the change small enough to inspect.
- Write down the current forums and what each one actually decides. If two forums decide the same thing, merge them.
- For the weekly deal forum, publish a four-line filter: date moved, stage changed, buyer meeting booked, or no customer step since last time.
- Require every discussed deal to leave with advance, slip, or stop, plus an owner and a date.
- Hold one monthly hour for patterns only. Leave with one asset or one coaching rep, not a new dashboard.
- After two cycles, check whether the next customer action happened. If it did not, change the forum before you add another meeting.
That is the whole cadence: fewer deals, a named next step, and a date the next review can verify.
How should a complex deal change the interval?
Do not give every motion the same week. A cybersecurity platform sale with a security review, a proof, and a procurement path will not move every seven days. A usage-based expansion inside an existing account often will. The cadence should follow the slowest real buyer step, not the loudest internal habit.
Try this split when both motions sit on one team:
- Enterprise evaluation. Inspect only when a buyer step is due, a date moved, or the deal has gone quiet past the agreed interval. Weekly is the backstop, not the agenda.
- Land-and-expand. Inspect twice a week if the seller can create or lose the next step inside a few days. Keep each deal to a few minutes.
- Shared manager. Put the two motions in separate blocks. Mixing them lets the fast deals eat the hour the slow deals need.
Write the rule in one sentence the seller can repeat. For example: "We review an enterprise deal every week only if the buyer step, the date, or the stage changed. Otherwise it waits for the monthly pattern hour." A rule no one can say out loud will not survive the first busy Monday.
What does the handoff look like on one deal?
Picture a late-stage infrastructure opportunity. The seller says the technical win is done and the close date is the end of the month. The economic buyer has not agreed to a meeting. Procurement has not named its steps. The weekly forum should not relitigate the demo.
A clean handoff sounds like this. The seller will ask the champion, by Thursday, who signs and what procurement still requires. The manager will join only if that answer names a person. If Thursday produces no buyer step, the deal slips out of the current commit conversation and returns only when a date is real. Enablement does not build a new deck for this one deal. If the same procurement stall shows up next month on two more deals, that is the pattern hour, and the asset might be a one-page buying-path note.
Notice what the handoff refuses. It does not invent a win rate. It does not promise the quarter. It does not add a MEDDIC field for its own sake. It gives the next review something it can check.
Which signals say the cadence is working?
Judge the rhythm on actions you can see, not on how calm the meeting felt.
- The share of reviewed deals that leave with a dated customer step, checked at the next forum.
- The share of those steps that actually happened, even when the answer was no.
- Deals that returned with the same unknown two intervals in a row. That count should fall.
- One monthly pattern that became a real asset or a live coaching rep, not a note to "circle back."
These are inspection signals for the leadership team. They are not a forecast, a benchmark, or a guarantee that pipeline will grow. If the counts do not move after two cycles, change who attends or which deals qualify before you add another meeting. A heavier calendar is not a stronger cadence.
Frequently Asked Questions
How often should a B2B technology team hold pipeline reviews?
Hold a short deal inspection every week, or twice a week when the sales cycle is measured in days. Use a monthly forum for repeated patterns and a quarterly forum for the assumptions behind cycle time and stage rules. Add an exception review only when a named trigger fires, such as a close date that moved twice.
Is a pipeline review cadence the same as a forecast cadence?
No. The pipeline review cadence decides which deals get inspected and what customer action must happen next. The forecast cadence decides what revenue leadership is willing to stand behind. Run them on different questions even if the same people attend both.
What should a manager require before a deal leaves the review?
One of three outcomes: advance, slip, or stop. Each outcome needs an owner and a date. "Follow up" is not an outcome, because the next review cannot tell whether it happened.
Who should own the cadence?
The Head of Sales owns the weekly deal forum. Revenue Operations owns what counts as movement and whether the weekly forum duplicates the forecast call. Enablement owns the monthly pattern and the asset or live-call practice that fixes it.
What is a good first change if reviews already feel endless?
Stop reviewing the full book. For two weeks, discuss only deals with a moved date, a changed stage, a booked buyer meeting, or no customer step since the last review. If the meeting is still long, the filter is too loose. The hour is not the problem.






















