The real cost of a slow month: pricing problem or booking problem?
When revenue drops, most hosts guess at why. Occupancy, ADR, and RevPAR turn that guess into a diagnosis you can actually act on.
A slow month feels the same from the outside no matter what’s causing it: revenue is down, and something needs to change. But “something needs to change” isn’t a plan — and without the right numbers, hosts often fix the wrong thing.
Two different problems that look identical
A drop in revenue can come from two very different places. Either fewer nights got booked — a demand or booking problem — or the nights that did get booked earned less — a pricing problem. From the bank account alone, both look exactly the same: less money came in. But the fix for each is close to the opposite of the other.
If demand is the issue, dropping your price further usually makes things worse, not better — you’re already not getting booked, and a lower price just shrinks the revenue you do get. If pricing is the issue, chasing more bookings without adjusting rate just means staying full while leaving money on the table every single night.
Telling them apart
This is exactly what occupancy rate and ADR are for. Occupancy tells you what share of available nights got booked — the demand side. ADR tells you what you earned, on average, for the nights that did get booked — the pricing side. Look at them together during a slow month, and the picture usually clarifies fast.
Low occupancy with steady ADR means the price wasn’t the problem — not enough people booked at all, which points to visibility, seasonality, or competition worth researching. Steady occupancy with falling ADR means demand was fine, but you gave too much of it away, which points to a pricing correction. RevPAR — revenue per available night — gives you the combined size of the gap, so you know how much is really on the table before you start making changes.
Why this needs to be fast, not retrospective
The value of this diagnosis drops sharply if it only shows up months later in a spreadsheet you built after the fact. A slow month is actionable while it’s happening — a pricing adjustment or a promotion works far better mid-month than as a postmortem three months later. And once you make that change, HostLog records it against the metrics that follow, so you can tell whether the fix actually worked.
HostLedger calculates occupancy, ADR, and RevPAR automatically for any month you pick, which means the moment a month looks slow, the diagnosis is already sitting there — not buried in a spreadsheet you’ll get around to updating eventually.