How to Run a Monthly Revenue Review Meeting

What is a monthly revenue review for?

A monthly revenue review explains the variance between the closed month and the plan, then commits to corrections while there is still quarter left to fix. It is a decision meeting, not a reporting meeting.

The weekly forecast call manages individual deals. The quarterly business review changes the structure of the plan. The monthly review occupies the gap between them, which is where most correction actually happens. Miss month one and you have two months to respond. Discover the same miss at the QBR and you are writing a post-mortem.

Run it in the first five business days after the month closes, once finance has locked the number. Any later and the correction window shrinks.

What should open the meeting?

Start with the ARR waterfall for the month, not with bookings. Bookings tell you what sales did. The waterfall tells you what happened to the business.

Build it as a reconciling sequence by month, where beginning ARR equals the prior month's ending ARR:

Reconciling this every month is the single highest-leverage habit in the review. It forces contraction and expansion into separate lines, so a strong new logo month cannot quietly cover a shrinking base. It also gives you gross and net revenue retention from the same table rather than from a separate model that never quite ties out.

How do you read the month against the quarter?

Compare the month to its position in the quarter, not to the previous month. Months inside a quarter are not comparable to each other.

The third month of a quarter closes more business than the first and second. Q2 and Q4 typically outperform Q1 and Q3. A team that reads month one of Q3 against month three of Q2 will conclude the business fell off a cliff, and will make a resourcing decision based on a calendar artifact.

Use two comparisons instead:

- Same month position, prior quarters. Month one of this quarter against month one of the last four quarters. - Percent of quarter delivered. How much of the quarterly target closed by this point in the last several quarters, versus now.

Those two views catch a real slowdown early and ignore seasonality that does not need a response.

Which metrics belong on the agenda?

Six, and each has to be tied to an owner who can change it. Everything else is background material.

- Win rate. Falling win rate at a steady volume points at pricing pressure or competitive entry. - Average deal size. Compare closed-won ASP against the ASP sitting in open pipeline. A pipeline averaging 80,000 dollars that closes at 40,000 dollars is a forecast problem before it is a sales problem. - Sales cycle length. Cycles stretching from qualified to closed usually mean buyers are hesitating, not that reps got slower. - Pipeline created versus plan. The only line in the meeting that describes the future. - Gross and net retention. Straight off the waterfall. - Forecast variance. Called number versus closed number, by segment.

Forecast variance is the metric that keeps everyone honest. Publishing it monthly by segment does more for forecast accuracy than any amount of coaching about optimism.

How do you turn variance into a decision?

Assign every gap to one of four causes before proposing a fix, because the fix differs by cause. Most misses trace back to the same root: something in the business or the market changed and the plan was still running on old assumptions. A competitor arrives and deal sizes compress. Interest rates rise, capital deployment slows, buyers cut cost, and win rates fall with them. You reorganize territories and execution dips while coverage still looks healthy. The monthly review exists to catch that class of change while there is still time to respond.

How do you keep it from turning into a presentation?

Publish the numbers the day before and open the meeting at the first question rather than the first slide.

The presentation failure is structural. When the data appears on screen for the first time in the room, the meeting becomes a reading exercise and the discussion gets whatever minutes are left. Attendees who disagree with a number spend the session reconciling it instead of acting on it.

Three rules hold the line. Publish the full data package twelve hours ahead and treat it as read. Assign RevOps a publishing role rather than a presenting role, so the analyst is in the room to answer questions rather than to narrate charts. And require that anyone disputing a number raises it before the meeting, so definitions get settled in writing instead of in front of an audience.

The seating matters too. Keep the room to leaders who can commit budget, headcount, or pricing authority in the moment. Once individual reps attend, the session becomes a performance review and honest discussion of pipeline quality stops.

What has to be recorded before the meeting ends?

A written correction list with named owners and dates, reviewed at the top of the next monthly session.

Cap it at five items. A monthly review that produces twelve actions produces none. Each entry needs the gap it addresses, the owner, the date, and the metric that will show whether it worked.

Then close the loop. The first agenda item next month is the previous month's list, marked done or not done. That single habit converts the review from a recurring presentation into an operating mechanism, and it makes the next quarter's revenue forecast something the team built rather than something they received.