Pricing
The 80/20 and 75-55 rules explained for Airbnb hosts
The 80/20 rule and the 75-55 rule that Airbnb hosts trade are shorthand for the same thing: pace-based repricing. You set target booking percentages at points before arrival, check whether the calendar is ahead of or behind that pace, and nudge your base price to catch up. In the vault's version, you aim for about 50% booked at your booking-lead-time horizon and about 75% booked at half that horizon, adjusting the base price about 5% per step to stay on pace (HostRev vault, 2026, cheatsheet 02).
Key takeaways
- The "rules" are pace targets, not magic ratios. Hosts quote 80/20, 75-55, and other numbers, but the mechanic underneath is always: compare future occupancy to a target pace and reprice (HostRev vault, 2026, cheatsheet 02).
- Book lead time is the horizon you pace against. It is the point by which about half your bookings have arrived, read from your pro dashboard (HostRev vault, 2026, cheatsheet 02).
- Two targets, checked weekly. Aim for about 50% booked at your lead-time horizon and 75% at half that horizon, ideally 100% by arrival day (HostRev vault, 2026, cheatsheet 02).
- Move the base price about 5% per step. Behind pace, nudge down; ahead of pace, nudge up. On a $150 base that is roughly $10, on a $500 base roughly $25 (HostRev vault, 2026, cheatsheet 02).
- This is a routine, not a guarantee. The method is illustrative and correlational, cited to the vault, and your outcome depends on your market and listing.
What is the 80/20 rule for Airbnb?
The 80/20 rule, and the 75-55 variant, is host shorthand for pace-based repricing. There is no single official ratio, which is why the numbers hosts quote drift around. What they all point at is one habit: decide how booked your calendar should be at a few points before arrival, then check the real numbers against those targets and reprice to close the gap.
The vault's two-step pacing method targets about 50% booked at your booking-lead-time horizon and about 75% booked at half that horizon, adjusting the base price about 5% per step to stay on pace, an operational rule rather than a guarantee (HostRev vault, 2026, cheatsheet 02).
So when a host says "I follow the 80/20 rule," translate it as "I pace my calendar and reprice on pace." The specific fractions are less important than the discipline of checking every week. This is one concrete spoke of the wider Airbnb pricing strategy that prices for revenue, not occupancy: the base price is your anchor, and pacing is how you nudge that anchor.
What is booking lead time and why does it set the horizon?
Booking lead time is the point by which about half your bookings have arrived. If your booking lead time is 30 days, roughly half your reservations come between today and day 30, and the other half come from day 31 onward. You read it from your professional dashboard, and it becomes the horizon you pace against.
Here is the important part most hosts miss: occupancy in this method means future occupancy, not history. You are not looking at how full last month was. You are looking at how booked the next 30, 15, and 0 days are right now, and comparing that against where you want to be.
Across the vault, hosts stress that pacing runs on future occupancy, not past performance: at 30 days out with a 30-day booking lead time, you want to be roughly 50% booked, because that is the math of half your bookings arriving inside the window (HostRev vault, 2026, cheatsheet 02).
How do the two booking targets work?
You set two targets and check them on a fixed weekly slot. The first target sits at your full booking-lead-time horizon, the second at half of it, and arrival day is the implied third.
| Checkpoint | Target booked | What it tells you |
|---|---|---|
| At your booking-lead-time horizon | About 50% | Whether the calendar is filling on schedule |
| At half your lead-time horizon | About 75% | Whether near-term demand is on pace |
| At arrival day | Ideally 100% | Whether the last nights closed out |
Targets: HostRev vault, 2026, cheatsheet 02. These are pace targets to steer against, not guarantees of a specific occupancy.
At each checkpoint you compare the target to the real future occupancy and act. If you target 50% at 30 days and you are actually at 35%, you are behind pace, so you drop the base price. If you are at 65%, you are ahead, so you raise it. Then you apply any customizations for specific booking trends, and you leave it until next week.
How much should I move the base price?
Move the base price about 5% per adjustment. That keeps you on pace without swinging the price so hard that the model becomes unreadable and guests cannot trust the number they see.
In the vault's pacing method, each on-pace correction moves the base price about 5%, which is roughly $10 on a $150 base price and about $25 on a $500 base price, small enough to stay smooth and regular (HostRev vault, 2026, cheatsheet 02).
The direction is simple. Behind target, nudge down. Ahead of target, nudge up. On target, do nothing. The reason for small steps is that a base price that jerks up and down 20% at a time makes it impossible to read your own results, and it can look erratic to guests comparing your calendar. Small, consistent moves are how the pace method stays legible.
Why not just set one price and forget it?
Because demand is not static, and a fixed price ignores it. A missed night earns you nothing, so pacing exists to catch bookings before the day passes: that is the logic behind why an empty night earns you zero, not the rate it "should" have earned. Pacing is the early-warning system. It tells you a night is not going to fill at the current rate while you still have time to do something about it.
One caution: pace on the base price, not by slamming a giant last-minute discount at the end. Demand falls gradually, so your price should step down gradually too, not jump from 0% to 30% off on a single day. And keep your fees legible while you pace, because an oversized cleaning fee can make a well-paced cheap night still read as a scam. The whole point of pacing is a smooth, readable curve.
None of this guarantees a specific occupancy or revenue, because HostRev makes no guaranteed ranking or revenue claims and your result depends on your market and listing. It is the pace-based routine the operators in the vault report using, translated out of the shorthand.
Frequently asked questions
What is the 80/20 rule for Airbnb?
It is host shorthand for pace-based repricing: you check whether the calendar is booking ahead of or behind a target pace and adjust your base price to catch up. In the vault's version, you aim for about 50% booked at your booking-lead-time horizon and 75% booked at half that horizon, moving the base price about 5% per step (HostRev vault, 2026, cheatsheet 02). The exact ratios hosts quote vary; the method is the same.
What is booking lead time on Airbnb?
Booking lead time is the point by which about half your bookings have arrived. If your booking lead time is 30 days, roughly half your reservations come between today and day 30, and half come from day 31 onward (HostRev vault, 2026, cheatsheet 02). It is the horizon you pace against, and you read it from your professional dashboard.
How do I know if my Airbnb is priced too high?
Compare future occupancy against your pace targets, not against a hunch. If you target about 50% booked at your lead-time horizon and you are sitting at 35%, you are behind pace, so drop the base price about 5%, roughly $10 on a $150 base or $25 on a $500 base (HostRev vault, 2026, cheatsheet 02). If you are ahead of target, nudge it up instead.
How much should I change my Airbnb base price at a time?
About 5% per adjustment, in the vault's pacing method (HostRev vault, 2026, cheatsheet 02). That is roughly $10 on a $150 base price and $25 on a $500 base. Small, regular steps keep you on pace without whipsawing the price, which makes the pricing model hard to read.