From numbers to judgement: How STR revenue managers win the room with leadership

https://youtu.be/h1U77p1lkr4

You can be technically brilliant at short-term rental revenue management and still lose the meeting. That's the uncomfortable truth Zak Ali – President of the ISTRM and one of the sharpest minds in STR revenue management – set out to fix on his latest appearance on STR Pricing Pulse, the series powered by Host Planet and Beyond. This episode wasn't about the mechanics of pricing. It was about the part of the job nobody trains you for: standing in front of leadership and turning all that analysis into a decision they'll back. Catch the full episode on YouTube, Spotify, or Apple Podcasts.

During the episode, Zak walks through Beyond's Revenue Meeting Guide, which suggests to lead with the answer, back it up with numbers, and end with a decision that senior management can act on. Click here to download a copy of Beyond's Revenue Meeting Guide.

Key takeaways from the episode for STR revenue managers

• The revenue leader's job isn't to transfer information – it's to reduce uncertainty around a specific decision.

• Lead with the answer, back it with the evidence, close with the recommendation – in that order.

• Prep for the three questions leadership always asks: are we outperforming, where are we exposed, and can we scale without losing control?

• The single biggest mistake is hiding behind the data when the room gets uncomfortable.

• Growth tells you your business got bigger; like-for-like performance tells you it got better.

Revenue management vs revenue leadership

Revenue management produces an enormous amount of information – pricing, pace, occupancy, market movement, the list is endless. According to Zak, the mistake is assuming leadership needs all of it. "The job of the revenue leader isn't to transfer information – it's to reduce uncertainty around a specific decision."

The tension is structural. Revenue managers are trained to be analytically complete: check pricing, pace, competitors, events and restrictions before moving. Leadership doesn't reward completeness – it rewards clarity. So a manager walks in wanting to show everything they considered, while the CEO is thinking, "What changed? Why does it matter? What do you want us to do?" Neither is wrong; they're just operating at different levels. The skill, Zak says, is being able to move between them: "Analytical depth should be available on demand, but it shouldn't be imposed by default."

Lead with the answer, not the analysis

The habit that changes everything is reversing the order most managers use. Instead of building thirty slides and then asking "what story does this tell?", Zak argues you should answer first, evidence second, recommendation third.

In practice it sounds like this: "We're likely to finish around target-minus-£300k. The gap is concentrated in two markets. Pace started weakening three weeks ago. We've checked price, availability, restrictions, and conversion – and here's what we think is driving it. My recommendation is to intervene in those two markets now and review in seven days." Everyone has a frame for the conversation before a single chart appears.

There's a crucial caveat: this is not confirmation bias. You don't decide the answer you want and hunt for data to prove it. You do the analysis properly, challenge your assumptions, look for evidence that might prove you wrong – then form a view and build the meeting around it. As Zak puts it, that's "the habit that moves somebody from being the person who brings numbers to the person who brings judgement."

Growth is not the same as performance

One of the sharpest points: growth feels like success but can quietly mislead. Manage 100 properties producing £10m one year, then 120 properties producing £11m the next, and revenue is up 10% – but the portfolio grew 20%. Did you get better at generating revenue, or just have more inventory to sell? "The easiest way to misread performance is to let the denominator change without acknowledging it." The fix is looking at RevPAN (revenue per available night) on a like-for-like basis – and still asking why it moved: ADR, occupancy, availability, or property mix.

The three questions to prep for

Zak framed leadership's real agenda as three questions every revenue manager should be able to answer in a sentence:

1. Are we outperforming, not just growing? Outperformance needs a comparison – versus last year, versus plan, versus market – and each is flawed alone, so triangulate. Then translate it into money: "5% ahead of market across 300,000 available nights" becomes a concrete revenue figure leadership can feel.

2. Where are we exposed? Revenue at risk is simply the gap between the agreed target and a realistic forecast – not every unsold night multiplied by a rate. Grade it by likelihood, how early you saw it, and how controllable it is. The killer question: "When did we first know?"

3. Can we scale without losing control? The automation question. Manage by exception – let the system handle routine decisions within set boundaries, and escalate only what genuinely needs human judgement. This is revenue governance, not micromanagement.

The biggest mistake – and the one change to make Monday

When results get challenged and the room gets uncomfortable, the instinct is to open another dashboard and show another chart. That's hiding behind the data, and Zak says it's the number-one mistake. Leadership isn't asking for another number – they're asking what you think.

His single most valuable tip: before you build anything, imagine the CEO gives you 30 seconds and asks, "What do I actually need to know?" Answer that first – then build the evidence underneath it.