Resource

Where short-term rental revenue actually hides, and which tool already found it.

Most of the revenue an operator is missing is not hidden. It is sitting in a system they already pay for, waiting for a question nobody has asked it. Here are nine worth asking, one we asked and then deleted, and the rule that came out of it.

When we build a revenue system for a professional operator, the first thing we do is not build anything. We list the questions their existing data could answer if someone asked it every morning. Then we check, one by one, whether a tool they already run is answering it.

That second step is the whole point of this article, so it comes last. First, the questions.

01Nine questions your booking data can already answer

Each of these is a separate detector. They run independently and land on one ranked list with a common shape: what, where, when, how much, and why now.

1. Gap nights. Two to four night holes in the near calendar, the ones worth a call.
2. Repeat guests due to return. Past guests inside their return window right now.
3. Fresh inquiries not yet converted. Quotes that are still warm.
4. Last-minute open inventory. Nights inside the booking window that are still empty.
5. High-demand dates still open. Weekends and events that should have sold.
6. Lost quotes worth re-approaching. Inquiries that carried a full price and went cold.
7. Price above recommendation. Homes where the asking rate has drifted from what the pricing tool suggests.
8. Stay-extension candidates. Guests whose next night is open and cheap to offer.
9. Same-time-last-year gaps. Dates that had sold by this point last year and have not sold this year.

None of these needs data you do not already have. All of them need it in one place, with enough history to compare, and someone to run the question every day. That last part is where most operators stop, which is fair. Nobody has the time to run nine reports before breakfast.

02Rank by the right measure or the list is useless

The first version of the repeat-guest detector ranked people by lifetime value. It looked sensible. It was wrong, and it took over the list: eight of the top twelve items on the whole board were repeat guests, crowding out every other kind of opportunity.

Lifetime value identifies your best customers. It does not identify your best opportunity today. Re-ranked on average stay value, with lifetime value moved to the detail row, the list became usable immediately.

The general rule: a detector that dominates the list is mis-ranked, not successful. If one kind of opportunity is always at the top, the ranking is measuring the wrong thing.

03The detector we built, measured, and deleted

We built a detector for orphan nights caused by minimum-stay rules. The reasoning was sound. A three-night minimum next to a two-night gap leaves the gap unbookable, and that is revenue lost to a setting.

The operator pushed back. They thought their pricing tool already handled it. So we measured, home by home, instead of arguing.

Almost every home in the portfolio already varied its minimum stay by date. There were zero blocked gaps. The pricing tool had been doing the job properly for months.

We retired the detector. What remains is a silent monitor that fires only if that assumption ever stops holding. It has not fired.

This is worth being honest about, because the opposite story is the one every vendor tells. We could have shipped the detector, shown a list of gaps with rules attached, and let the operator conclude the tool had found something. It would have found nothing that was not already being handled, and the first sharp revenue manager to look at it would have known.

04The rule that came out of it

Before building any detector, measure whether the tools already in the stack solve the problem. Not ask. Measure.

In practice this becomes a question at onboarding: which tools do you run, and what do they already do? A good pricing tool handles rate and minimum stay. A good guest messaging tool handles the pre-arrival journey. A good CRM handles the follow-up sequence. None of that needs rebuilding, and rebuilding it is the fastest way to lose an operator's trust.

What the stack does not do is compare this year to the same point last year, night by night, across the whole portfolio. It does not mine cold quotes. It does not tell a named person which four properties to call this morning. Those are the gaps that survive contact with a well-run operation, and they are the only ones worth building for.

05An opportunity without an owner is just a number

The most important thing we learned came from an operator, not from us. Identifying opportunity is the easy half. A list of gap nights is interesting for about a week. Then it becomes another dashboard nobody opens.

The list has to become a queue. Priority, subject, action, potential value, owner, deadline, status. When each item belongs to a person and has a date, the loop closes, and you can report what was actually recovered.

That number, recovered revenue, is the only one that justifies the system. Everything above exists to make it honest.