Hotel DOSM and Revenue Manager preparing for the weekly revenue strategy meeting

Recipe 37 - The Weekly Revenue Strategy Meeting Prep: Arrive With a Position, Not a Status Report

August 08, 2026

Arrive With a Position, Not a Status Report

From The Spiral Sales Office Recipe Vault | By Paul Woodley

The weekly revenue strategy meeting is the single most important recurring conversation between the DOSM and the Revenue Manager. It is where the decisions that determine the next ninety days actually get made: which groups to accept or decline, which dates to adjust pricing on, which periods to protect and which to push hard on. And most DOSMs walk into it with a status report rather than a position.

A status report describes what the data shows. A position says what to do about it, and why, before anyone else in the room has drawn the same conclusion.

Recipe 37 is the prompt you run the day before the meeting to build that position from the data, so you arrive ready to lead the conversation rather than react to it.

What This Recipe Makes

A complete 90-day forward read that identifies the three weakest weeks by room nights to sell, provides specific sales-side actions for each, frames the three revenue-side questions to put to the RM, surfaces pending group displacement decisions, protects the strongest period in the window, and gives the DOSM a three-sentence opening statement to lead the meeting with.

  • Head Chef: DOSM, with the RM running the mirror version from the pricing side
  • When to Cook It: Weekly, the day before the meeting
  • Ingredients: Rolling 90-day rooms on the books and forecast; group pace and funnel for the same window; forward rate shop; current competitive index; any known citywide or event activity in the window

The Six Outputs This Prompt Returns

  1. The Week-by-Week Read - For each week in the 90-day window, one line: is this week strong, adequate, or soft, and what is driving it. The three weakest weeks flagged by remaining room nights to sell, not percentage. The DOSM who walks in knowing exactly which three weeks need the most attention this meeting arrives at a different place from the one who is working through the data in real time during the call
  2. The Sales-Side Answer for Each Weak Week - For each of the three weakest weeks, what sales can realistically still influence at this lead time. Short-cycle group, crew or contract business, extended stay, local corporate pickup, or an existing account with flexible dates. Specific about what is actually bookable inside the remaining window versus what is too late for the lead time to work
  3. The Revenue-Side Questions - Three questions to put to the Revenue Manager in the meeting, framed as questions rather than demands. Based on what the data shows rather than what the DOSM assumes the answer is. This is the framing that makes the revenue meeting collaborative rather than adversarial
  4. Group Decisions Pending - Any group in the funnel with dates in the 90-day window that will require a rate or displacement decision, flagged for which ones need a decision this week. Displacement decisions made under time pressure are almost always worse than decisions made with lead time. Recipe 37 surfaces them before the pressure arrives
  5. The Strength to Protect - The week or segment performing best in the window, and what would put it at risk. Strong periods get ignored until they stop being strong. This output ensures the strongest part of the forward book receives the same attention as the weakest
  6. My Opening Position - Three sentences the DOSM can lead with in the meeting: where we are, what the key issue is, and what decision we need to make today. Not a summary of the data. A statement of position

The Mirror Version

The prompt notes that the Revenue Manager should run a mirror version from the pricing side. When both the DOSM and the RM arrive at the weekly meeting with position papers built from their respective data views, the meeting shifts from information exchange to decision-making. That is a fundamentally more productive meeting, and it is what Recipe 37 is designed to enable on the sales side.

Where the Output Goes

The weekly revenue strategy meeting itself, where the six-section output structures the DOSM's agenda contribution. The resulting prospecting assignments, where the three weak weeks translate into specific seller actions for the following week. The decisions log, where displacement decisions and pricing actions agreed in the meeting are recorded with rationale.

The Mirror

In your last weekly revenue meeting, did you arrive with a specific position on what needed to be decided that day, or did you arrive with a report of where things stood? If the answer is the latter, Recipe 37 changes that for next week.

A Note on Data Handling

Confirm what your employer, owner, brand, and management company permit before pasting forward booking and rate-shop data into any AI platform. Ninety-day on-the-books data, rate positions, and competitive index information may be commercially sensitive. When in doubt, describe the position without pasting specific rate values or account names. Every output is a starting position. The revenue decisions still belong to you and your Revenue Manager.

Your Next Step

Set a calendar block the afternoon before every weekly revenue meeting. Pull the rolling 90-day data, group funnel, rate shop, and competitive index. Run Recipe 37. Walk into the meeting with the six-section output in front of you. Lead with your opening position. Then run the meeting from a decided view rather than an open question.

The revenue meeting that changes what happens next week starts with someone arriving with a position. Recipe 37 builds yours.

Paul Woodley | The Spiral Sales Office

Back to Blog