The RevOps Operating Cadence: Weekly, Monthly, Quarterly

Why cadence is part of the system

A well-architected revenue system degrades continuously. Fields get added, definitions drift, integrations fail quietly, and reps develop workarounds. None of this is anyone's fault — it is the default behaviour of any system in use.

Cadence is the counterforce. It is the only mechanism that reliably surfaces drift before it becomes a rebuild, which is why treating it as a scheduling detail rather than a design component is how companies end up re-implementing their CRM every three years.

The weekly pipeline review

The most-run and most-wasted meeting in B2B. Done badly it is a status round-robin where each rep narrates their deals and nothing is decided. Done well it is the forum where the quarter is actually managed.

1. 01
   Run it in the CRM, on live data

   Not a slide, not a spreadsheet. This is non-negotiable and it is the single highest-leverage rule in the whole cadence — the moment leadership runs the number outside the system, everyone learns the system is optional.

2. 02
   Open with coverage against plan

   One number: do we have enough qualified pipeline to hit the quarter at our historical win rate. Everything else in the meeting is downstream of that answer.

3. 03
   Review movement, not status

   Deals that changed stage, deals that slipped, deals with no activity in 14 days. Ignore deals that are progressing normally — they do not need meeting time.

4. 04
   Name the intervention

   Every stalled deal leaves with a specific action and an owner. Not we will follow up — a named person doing a named thing by a named date.

5. 05
   Close with data quality exceptions

   Deals with close dates in the past, missing required fields, or no contact role. Two minutes, and it keeps the system honest without a separate meeting.

The monthly metrics review

Where trends get read rather than moments. The weekly review is tactical; this is where you notice that stage-three conversion has dropped six points over four months and nobody flagged it because each individual week looked fine.

A working agenda, same order every month:

• Pipeline created versus plan, by source, with the trend rather than the single month.
• Stage conversion, compared against the trailing six months rather than the prior month.
• Sales velocity — deal size, win rate, cycle length, and what changed in each.
• Cost per qualified opportunity by source, fully loaded.
• Retention and expansion against cohorts — see recurring revenue metrics.
• One anomaly, investigated properly. Not a list of anomalies; one, with a conclusion.

The last item is what separates this from a reporting exercise. A meeting that reviews twelve metrics and investigates none of them produces awareness without decisions.

The quarterly system review

The one everyone skips, and the one that prevents the expensive rebuild. Ninety minutes, once a quarter, covering the health of the system rather than the health of the pipeline.

The renewals row is the commercially valuable one. Reviewing a contract 90 days out is the only moment you have leverage; reviewing it in the annual audit three weeks after auto-renewal means paying a full year to act on the finding.

The annual architecture review

One question: does the data model still match how the company actually sells? Motions change faster than models — a company that added a product-led tier, moved upmarket, or started selling through partners is now running a model designed for a business it no longer is.

This is the review that decides whether next year is an incremental year or a re-architecture year, and having it deliberately once is considerably cheaper than discovering the answer through accumulated pain.

How cadence fails

• Variable agendas. The meeting becomes whatever is most urgent, which means the system-level items never get discussed. Fix the agenda and hold it.
• No named owners on actions. Items return unchanged week after week until everyone stops raising them.
• Reporting instead of deciding. If a meeting produces no decision, it is a broadcast and should be an email.
• Running on exported data. Reintroduces the trust problem the cadence exists to prevent.
• Skipping the quarterly when things are busy. It is always busy, and the quarterly is the one that compounds.

The cadence is the last step in building a revenue system for a reason: it is what keeps everything built before it true. Without it, the architecture, the definitions, and the data quality work all decay on roughly the same two-quarter timeline — see how to build a RevOps strategy. Where the cadence surfaces a specific drag, nine efficiency levers covers what to do about it.