Airbnb Booking Pace Strategy: The Break-Even Discount Rule
A Nashville host checks her calendar 24 days out from a weekend that should already be half sold. Last year, this exact week was 68 percent booked at this point in the lead time. This year it is sitting at 54 percent. That is a 14 point pace deficit, and her pricing tool is already suggesting a 20 percent cut across the remaining nights. Before she touches the rate, there is a question almost nobody in short-term rental pricing actually answers with numbers: how far behind pace do you need to be before a discount is the correct move, and how big does that discount need to be to pay for itself? The math exists. Most hosts have just never seen it written down.
Table of Contents
- What Booking Pace Actually Tells You
- The 75-55 Rule, Untangled
- Why “Behind Pace” Doesn’t Automatically Mean Discount
- The Break-Even Discount Formula
- Building Your Own Pace Deficit Threshold
- A Worked Example: The Nashville Host
- The Pace and Discount Decision Table
- Three Mistakes That Cost More Than the Discount
- Frequently Asked Questions
- Conclusion
What Booking Pace Actually Tells You
Occupancy tells you what already happened. Pace tells you what is about to happen, which is why every serious revenue manager watches it more closely than the calendar itself. Booking pace is simply the share of a future date range that is booked as of today, compared against the same point in the calendar last year, or against your comp set right now. If 54 percent of your nights three weeks out are booked today, versus 68 percent at the same lead time last year, you are 14 points behind pace. That single number is an early warning system. It shows up weeks before a soft occupancy month would ever appear in your bank statement.
The reason pace matters more than raw occupancy is timing. A host who waits until the week of arrival to notice empty nights has already lost the pricing leverage that comes from reacting early. A host who tracks pace weekly against last year’s same-week booked percentage, and against a handful of true comparable listings, sees the gap forming while there is still runway to do something about it. Tools such as PriceLabs and Wheelhouse both build pace into their pricing engines for exactly this reason, one through pickup reporting, the other by triggering rate changes directly off booking velocity rather than the calendar date. Neither tool, on its own, tells you the dollar threshold at which a pace gap is worth closing with a discount. That threshold has to come from your own numbers, and building it is the point of this article.
The 75-55 Rule, Untangled
Search for pricing help on a pace deficit and the first thing that surfaces is the so-called 75-55 rule. The trouble is that the term now means at least three different things, depending on which corner of the internet you land in, and most of the confusion comes from people repeating a number without checking what it was measuring in the first place.
| Version | What it claims | Who actually uses it | Useful for pricing decisions? |
|---|---|---|---|
| Investment screening rule | A market is healthy if comparable listings are running roughly 75 percent booked 30 days out and 55 percent booked 60 days out | Buyers doing due diligence before purchasing a property | No. It answers “should I buy here,” not “what should I charge tonight” |
| Income rule of thumb | Assume 75 percent annual occupancy, then assume 55 percent of gross revenue survives as net income after expenses | New hosts building a rough income forecast | No. It is an expense ratio, not a pricing signal |
| Discount floor rule | Hold 75 percent of your calendar nights at target ADR, and let only the remaining 25 percent (the last-minute window) discount down to a hard floor of 55 percent of target | Operators managing live pricing against a compressed booking window | Partially. It is the only version that touches a real pricing decision |
The discount floor version is the one worth keeping, because it at least sets a guardrail: never let a pricing tool discount a listing below 55 percent of its target rate just to chase occupancy, and never let more than a quarter of your nights fall into that discounted bucket. What it does not do is explain why 75 and 55 are the right numbers for your listing, your market, or your current pace deficit. Those numbers were set as a rough starting assumption by one well-known operator, not derived from a formula. The rest of this article builds the formula that tells you, for your own listing, whether a discount at any depth actually pays for itself.
Why “Behind Pace” Doesn’t Automatically Mean Discount
The instinct when a pace report shows red is to cut the rate immediately. That instinct is usually wrong, for a reason that has nothing to do with optimism and everything to do with cost structure. An empty night on a short-term rental has almost no marginal cost. You are not paying a cleaner, you are not restocking supplies, and you are not running the utilities load of an occupied stay. The real cost of an empty night is opportunity cost, not cash out the door.
A discount, on the other hand, has a very real and immediate cash cost. It applies to every guest who books that night, including the ones who would have booked at full rate anyway. That is the asymmetry a lot of pricing advice glosses over. Cutting the rate to fill a night that had near-zero holding cost only makes sense if the incremental bookings the discount attracts are worth more than the revenue given up on guests who did not need the discount to convert. That is a break-even calculation, and it is the one almost nobody runs before touching the rate.
The Break-Even Discount Formula
The formula is a version of the same logic used across revenue management to decide whether a price cut earns its keep: the percentage increase in bookings a discount needs to generate, just to leave revenue unchanged, equals the discount rate divided by one minus the discount rate.
| Discount applied | Required booking uplift to break even |
|---|---|
| 10% | 11.1% |
| 15% | 17.6% |
| 20% | 25.0% |
| 25% | 33.3% |
Read the table plainly. A 20 percent discount does not need to fill 20 percent more nights to break even, it needs 25 percent more, because you are also giving up 20 percent of the revenue on every night that would have booked anyway. This is the number your pace deficit has to clear before a discount is worth applying. If your own booking history shows that a similar discount, at a similar lead time, has historically closed a pace gap of that size or larger, the discount is a rational move. If your history shows discounts of that depth typically close a smaller gap than the break-even threshold requires, holding the rate and accepting the vacancy is the more profitable choice, even though it feels worse in the moment.
Building Your Own Pace Deficit Threshold
You do not need a full revenue management platform to build this. You need your own transaction history and about thirty minutes.
- Pull two years of confirmed bookings from your PMS or channel manager export, and for each one record the booking date, check-in date, and nightly payout.
- Calculate days-to-check-in for every booking (check-in date minus booking date).
- Group bookings into three windows: 21-plus days out, 7 to 20 days out, and 0 to 6 days out.
- For each window, find the instances where you applied a discount, and record the discount depth and the occupancy change that followed in the two weeks after.
- Compare that occupancy change against the break-even uplift required for the discount depth you used, from the table above.
- Anywhere your historical uplift consistently beat the break-even threshold, that discount depth is validated for that lead-time window. Anywhere it consistently fell short, mark that depth as unprofitable and stop using your pricing tool’s default suggestion for it.
This turns a generic pricing tool recommendation into a rule that is actually calibrated to your property, your market, and your guest mix, rather than a blanket setting built for an average listing that does not exist.
A Worked Example: The Nashville Host
Back to the host from the opening. Her target ADR for the weekend in question is $220. She is 24 days out, sitting at a 14 point pace deficit against the same week last year. Her remaining unbooked inventory in that window is 23 room-nights. Her pricing tool suggests a 20 percent cut, bringing the rate to $176.
Using the table above, a 20 percent discount needs a 25 percent booking uplift to break even. Her own two years of transaction history show that a 20 percent discount applied at a 21 to 24 day lead time has, on four prior occasions, recovered an average pace gap of 9 points, never more than 12. A 25 percent uplift on her remaining inventory is well outside what her own market has ever delivered at that discount depth and that lead time. The math says the 20 percent cut loses money relative to holding the rate, even though her calendar stays partially empty a little longer.
Her history does show something else worth acting on: a 10 percent discount, applied specifically to the Tuesday and Wednesday nights inside that window rather than across the whole weekend, has recovered pace gaps of 10 to 15 points on five prior occasions, comfortably clearing the 11.1 percent break-even bar for a 10 percent cut. The correct move is not the blanket 20 percent discount her tool suggested. It is a targeted 10 percent cut on the two weakest weeknights, with the weekend rate held at target. That single adjustment, built from her own numbers instead of a generic algorithm default, is the difference between a discount that pays for itself and one that quietly erodes revenue on nights that would have booked anyway.
The Pace and Discount Decision Table
Once you have your own break-even thresholds calibrated, the decision at any point in the booking window comes down to two inputs: how far behind pace you are, and how many days remain before arrival.
| Pace deficit | 21+ days out | 7 to 20 days out | 0 to 6 days out |
|---|---|---|---|
| 0 to 5 points | Hold rate, no action needed | Hold rate, monitor weekend pickup | Hold rate, late demand is still arriving |
| 6 to 12 points | Hold rate, check comp set for a market-wide slowdown | Test a discount only on your validated weeknight depth | Apply your validated weeknight discount, hold weekend floor |
| 13+ points | Audit listing quality (photos, reviews, title) before touching price | Discount weeknights at your validated depth, hold weekend at target | Discount broadly but never below your 55 percent floor |
The table assumes the discount depths in each cell have already been validated against your own break-even history, not pulled from a generic recommendation. A pace deficit alone is a symptom. Whether the cure is a discount, and how deep, depends entirely on whether your own data says that discount has ever actually closed a gap that size.
Three Mistakes That Cost More Than the Discount
Automating the discount without a floor is the first one. A pricing tool left on its default last-minute setting will keep cutting toward zero as arrival approaches, with no concept of a hard floor or of what that floor does to your review scores from guests who feel they overpaid the week before. Set a floor manually and hold it, the way the discount version of the 75-55 rule intends.
Treating every night in the window the same is the second one. Weekend nights and weeknights have different demand curves and different guests behind them. A blanket discount across a whole soft window drags down the weekend rate that would have booked at full price anyway, which is exactly the revenue leak the break-even formula is built to catch.
Cutting price before checking whether the problem is actually price is the third. A pace deficit caused by weak photos, a thin review count, or a listing title that buries your amenities will not respond to a discount, because the guest never sees the listing in the first place. Before running the break-even math on a discount, confirm bookings are actually being lost at the price point, not lost before a guest ever clicked through.
Frequently Asked Questions
What is a good booking pace for a short-term rental?
There is no single healthy number, because pace only means something in comparison. The useful benchmark is your own booked percentage at a given lead time this year against the same lead time last year, and against your true comp set right now, not an industry-wide average.
What is the Airbnb 75-55 rule?
The term is used for at least three different concepts. The version relevant to live pricing holds 75 percent of calendar nights at target rate and floors the remaining 25 percent of last-minute nights at 55 percent of target, as a guardrail against a pricing tool discounting without limit.
How much should I discount my Airbnb when bookings are behind pace?
Only as much as your own booking history shows has previously recovered a pace gap of that size. The break-even formula tells you the minimum booking uplift a given discount needs to generate; your transaction history tells you whether a discount of that depth has ever actually delivered it.
Does a lower price actually fix a booking pace deficit?
Sometimes. It depends on why the deficit exists. If the market itself has softened, a validated discount can recover lost pace. If the deficit is caused by a listing quality problem such as weak photos or a thin review count, a discount will not fix it, because the listing is not being seen at the price you already have.
Should I discount weekends the same as weekdays when behind pace?
No. Weekend and weeknight demand behave differently in almost every leisure market. Holding the weekend rate at target while discounting only the weaker weeknights protects the revenue you would have earned anyway on the nights that do not need help.
How do I calculate my own pace deficit without a pricing tool?
Export your confirmed bookings, group them by lead-time window, and compare this year’s booked percentage at a given point in the calendar against the same point last year. It is a spreadsheet exercise, not a software requirement.
Is pace-based pricing better than calendar-based last-minute discounting?
Yes, for one specific reason: calendar-based discounting triggers on a fixed day count regardless of demand, while pace-based pricing triggers on whether you are actually behind where you should be. A property that is ahead of pace fourteen days out has no reason to discount just because a calendar rule says so.
Conclusion
A pace deficit is information, not an instruction. The number tells you that something has shifted against your normal booking curve. Whether the right response is a discount, and how deep that discount should go, is a question your own transaction history can answer with more precision than any default setting in a pricing tool. Build the break-even threshold once, calibrate it against what has actually worked on your listing before, and every future pace report becomes a decision you can make in minutes instead of a guess you make under pressure. If you would rather have that threshold built and monitored for you across a full portfolio, talk to Revenuenaire about setting up dynamic pricing and pace tracking the right way.
Related reading: our breakdown of the Airbnb ADR versus occupancy break-even rate, the length-of-stay discount math behind the same uplift formula used here, and how we price single orphan nights inside a compressed calendar. For the tools behind pace-based pricing day to day, see our dynamic pricing strategy service, our dedicated PriceLabs setup and Wheelhouse setup services, and our broader Airbnb revenue management offering.
