Seasonality, Cash Flow, and the Limits of Peak-Season Thinking
Almost every property calculates its annual obligations against its expected annual revenue. Yet, few properties let that calculation actually govern how pricing decisions get made week to week, through the year that follows.
This is a real gap, and it is easy to miss, because it does not look like a planning failure. The annual budget exists. The numbers are correct. What breaks down is the connection between that yearly figure and the pricing behavior that is supposed to protect it: because the budget is typically produced once, often by a different process or a different person than the one setting rates day to day, and the two rarely stay in active conversation with each other once the season actually begins.
This disconnect shows up in the property’s own pricing behavior long before it shows up as a cash shortfall. Two patterns are especially common. The first is holding peak rates artificially high on the assumption that demand will simply arrive, only to discount heavily at the last minute once it becomes clear it won’t. The second is treating shoulder seasons as a minor, secondary source of revenue, when in many destinations they collectively span more operating days than peak season itself. Both patterns are made in the moment, under real-time pressure, disconnected from the annual reserve target that was calculated separately and is not actively present in the decision.
This is where pricing strategy and financial planning are often treated as separate disciplines, executed on separate timelines, when they need to function as one continuous system. The annual number is not simply a target to hit by year-end. It is a constraint that should actively shape every seasonal pricing decision made along the way: how aggressively to hold peak rates, how early to discount if demand is soft, how much strategic attention shoulder season actually deserves relative to its real share of the calendar.
Properties that treat the annual budget as a document, produced once and referenced occasionally, tend to make pricing decisions that look reasonable in isolation and create strain in combination. Properties that treat it as a living constraint, actively present in each pricing decision through the year, are the ones where the number calculated in January and the numbers actually realized in December tend to match.
