Event season pays in two currencies and most operators only count one. The obvious one is the premium night: the high rate during ACL, the F1 weekend payout, the October total. The hidden one is the repeat guest, the person who stayed during the rush and could come back for years. Operators chase the first and discard the second. They are leaving the more valuable currency on the table.

The leak is short-term accounting. A premium night is worth what it pays once. A repeat guest is worth every future booking, every referral, every direct stay that skips the platform fee, across the whole relationship. When you treat event guests as one-time transactions, you collect the small reward and forfeit the large one. The real prize of event season is not the October revenue. It is the list of people October introduced you to.

A first booking costs you acquisition: platform fees, competition, the work of getting found. A repeat booking from a known guest costs almost nothing, because you already won them. Over several stays, a repeat guest delivers revenue at a fraction of the acquisition cost of chasing new ones each time. They also book the quiet months, review more readily, and create fewer problems because they know the place. One captured repeat guest can outperform several one-time premium nights over a year.

The events deliver a volume of guests you could never afford to acquire on your own. ACL and F1 hand you a stream of people, many of whom would happily return if you gave them a reason and a path. That is the opportunity hiding inside the peak: not just the premium nights, but the introduction to a year's worth of potential repeat guests, delivered at the festival's expense, not yours. Squandering that by failing to capture them is the most expensive mistake of the season.

Most operators lose the repeat guest because the operation never recorded them in a usable way. The booking lives on the platform, the guest leaves, and there is no owned contact, no tag, no follow-up. By the time the operator thinks about repeat business, the relationship has gone cold and the data is trapped where they cannot reach it. The failure is not strategy. It is the absence of a system that captures every guest into something you control during the rush, not after.

The capture has to be automatic because the peak is too busy for manual work. Every booking becomes an owned contact, tagged by event and stay type. A follow-up sequence earns the review and plants the return offer. A reactivation message fires before the next relevant window. Built into the operating layer, this turns October's crowd into a durable list that pays out for years. Built nowhere, October's crowd evaporates the day they check out.

Picture two operators after the same event season. Both earned strong premium nights. One captured every guest into a system and reactivated them; a year later a measurable share have rebooked, several directly, and the calendar carries a repeat-guest floor. The other kept only the October payout and starts every month cold. Same peak, but one built an asset and the other spent it. The compounding is the whole point: a repeat list grows every event season instead of resetting.

Own the rails before demand exposes the leaks. A demand engine that does not need an event is the goal, and repeat guests captured during the events are its richest fuel.

If event season ends and you keep the revenue but lose the guests, you have a capture leak, and it is the most expensive one in the business. The free STR Leak Scorecard shows you what your past guests are worth and where the relationship is leaking. Run it before the next peak introduces you to a list you will throw away.