The revenue meeting from the leader's chair: how to run a data-driven debate

Thursday, ten o’clock. The revenue meeting begins, and Adam, the general manager, knows one thing: he isn’t the one who calculates the number. Daniel, the revenue manager, brings that. But he is the one who runs the decision — he is the meeting’s owner. And over the next twenty minutes it will be settled whether this forum is a decision-making body, or just a round where everyone recites what happened during the week.

The difference is enormous. A bad revenue meeting is an information swap: Daniel reads out the pace (the booking pace), Francis, the sales manager, reports on his negotiations, Esther on the campaigns, everyone nods, and they scatter. A good revenue meeting is a decision forum: every agenda item carries a question — what do we do, and what is it worth? — and at the end what’s produced is not a summary but a decision.

This lesson is about how you sit in the leader’s chair in this room: how you ask for a number behind every proposal, how you keep the focus on the decision, and how you resolve a sales–RM conflict in favour not of the louder voice, but of the data.

The meeting’s three rules that the leader holds to

The quality of a revenue meeting is decided not primarily by the participants’ expertise, but by the discipline the leader keeps on it. Three rules are enough.

1. Every proposal comes with a number. If someone says “let’s give a discount next week”, the leader’s answer isn’t “good idea” or “no”, but: “by how much, on how many rooms, and what does it bring — how much revenue does it protect or forgo?” Whoever proposes, calculates. This isn’t bureaucracy; it’s what separates the hunch from the decision.

2. We look forward, not back. Last week’s result is five minutes: what happened, what we learned. The rest of the time is about the dates of the next 30-90 days, where there is still room to act. You can no longer change the revenue that has already happened; next month’s weak Wednesdays you still can.

3. A decision has an owner and a deadline. “We’ll look into it” is not a decision. “Francis gets back to the group by Friday with 98 euros, and until then we hold the capacity” — that’s a decision. The leader’s task is to have every agenda item close like this.

The Peaqplus Revenue Meeting module gives a frame for this: it gathers the pace, the pickup (the bookings taken), the forecast and the open decisions into one place, so the debate isn’t about whose spreadsheet is the fresh one, but about what we do. But the module is only the frame — the discipline is what the leader adds.

The scene: Francis wants the group, Daniel opposes it

Let’s look at it live. On the agenda, a concrete case: Francis brings a 25-room group (an organised, multi-room booking) for two nights, on an October Thursday-Friday, at an 82 EUR/room flat rate, with two gala dinners.

Francis is enthusiastic: “That’s 25 rooms locked in for two nights, plus the F&B (Food & Beverage) revenue. Cash in hand, now, in black and white. Why would we say no to a sure deal?”

Daniel opposes it quietly: “Because the pace for those two nights is strong. Three weeks out we’re already at 71% (on the books), last year at this same moment we were at 60%, and the hotel ended up filling to 92%. This date nearly fills on its own — and well above 82 euros at that.”

Here’s the classic conflict: sales sees the guaranteed volume, the revenue manager sees the displaced revenue — the transient (individual, freely booking) guest who would pay far more than 82, except the group takes their place. At moments like this, the bad leader sides with the louder or the more likeable voice. The good leader asks both for a number.

The decision with data: we calculate the displacement

Adam doesn’t call a vote and doesn’t go on a hunch. He asks for the numbers, and from the data in front of him in the Revenue Meeting he writes up the displacement.

The starting point: for these two nights, based on the pace, the hotel would practically fill to a full house anyway, with transient guests, at an expected 118 EUR ADR. So the 25-room group largely displaces a pricier guest who would have arrived otherwise.

The picture suddenly comes into focus. At an 82-euro rate, even with the handsome F&B revenue, the group brings in 720 euros less than if we held the two nights for the transient guest who arrives on their own. Francis’s “sure deal” is really a 720-euro hidden loss — precisely because the date is strong anyway.

But Adam doesn’t stop at the “no”. He asks the decisive question: at what rate would it be worth it after all? The group breaks even when the room-side loss (R = the group’s room rate) does not exceed the 1,080-euro F&B contribution:

(118 − R) × 50 ≤ 1,080 → 118 − R ≤ 21.60 → R ≥ 96.40 EUR

In other words, above a ~97-euro room rate the group is already worth it. So Adam’s decision is not a plain rejection, but a data-driven counter-offer: “Francis, we say no at 82, because on this date that’s a 720-euro loss. Go back with 98 euros — there the group is already 80 euros ahead of the transient, and the dinner revenue is ours. If the partner won’t go up to 98, we let it go, because the pace says we fill the house on our own anyway.”

Let’s check the 98-euro offer: (118 − 98) × 50 = 20 × 50 = 1,000 EUR of room-side loss, against the 1,080 EUR F&B contribution → +80 EUR net upside. The decision has an owner (Francis), a number (98 EUR) and a deadline (Friday).

An important nuance that Adam says out loud: this holds for this specific, strong-pace date. On a weak-demand January week the same 25-room group at 82 euros would be a blessing — there’s no one to displace, every booked room is pure profit. The group isn’t good or bad in itself; the date’s demand situation decides. Which is exactly why every such case needs a number, not a principle.

Back to the meeting

The mood in the room shifts. Francis hasn’t “lost” — on the contrary: he now negotiates from a stronger position, because he knows exactly where his floor is (97 euros) and why. Daniel hasn’t “won” — it was his number that carried the decision, not his voice. And Adam didn’t pick a side: he let the data pick, he only kept the discipline.

This is the real value of the revenue meeting seen from the leader’s chair. It becomes good not because clever people sit in it — but because every proposal gets a number, every debate runs out to data, and every item closes with a decision that has an owner and a deadline. The leader is not the best analyst in the room. They are the one who makes sure the analysis decides, not the loudest voice.

And the more everyone looks at the same pace, forecast and open decisions from one shared system, the less rides on sheer discipline: the shared picture steers the debate toward the action on its own, and records what we decided — so the organisation learns from it too. It isn’t the leader who checks the RM; it’s the shared view that makes everyone’s work visible and alignable. (This is what the closing lesson 27 carries all the way through.)

The day-to-day running of the revenue meeting from the revenue manager’s side is covered by the RM Academy’s The weekly revenue meeting structure and Leading the revenue meeting lessons, and the detailed group-displacement calculation by the Group displacement analysis lesson.

Key takeaways

• The revenue meeting is a decision forum, not an information swap. If the end produces a summary and not a decision, you’ve wasted the hour.
• Every proposal comes with a number. Whoever proposes, calculates: by how much, on how many rooms, how much it protects or forgoes. This is what separates the hunch from the decision.
• Look forward. Last week is five minutes; most of the time should be about the still-shapeable dates of the next 30-90 days.
• The conflict is resolved by the data, not the loudest voice. The 25-room group at 82 euros is a 720 EUR hidden loss on a strong date — but above 98 euros it’s already profitable. The number decides, not sympathy.
• The group isn’t good or bad in itself — the date’s demand situation decides. What is displacement on a strong pace is a blessing on a weak one.