Airbnb Pricing Decision Tree

The host problem

You know you’re supposed to hold, cut, raise, reshape, or wait. But when you look at your calendar on a Tuesday morning, you don’t always know which one applies. The decision tree is the routing mechanism that turns calendar data into a specific action — or a specific decision not to act.

What the decision tree helps you decide

The tree routes every pricing review to one of the five moves based on three inputs: where you are in the lead-time window, what your occupancy and booking pace look like, and whether your current open inventory has a rate problem or a shape problem.

How the tree branches

The first branch is lead-time position. The question is: how many days separate you from the check-in dates you are evaluating?

If you are 60 or more days out, the early-cycle rules apply. The presumption is hold unless you see strong evidence of conversion rejection. Do not cut price at 60 days because the calendar looks thin — most listings haven’t entered the active booking window yet.

If you are 30 to 60 days out, you are in the middle of the primary booking window for most guest types. At this range, you ask: is booking pace tracking ahead of, in line with, or behind your baseline? If pace is ahead, consider whether a raise is appropriate on the strongest inventory. If pace is behind, check whether the gap is structural (a shape problem) or a rate problem.

If you are 14 to 30 days out, you are entering the active pressure zone. Midweek softness at this range warrants attention. Weekend softness at this range is a signal. Evaluate each night type separately rather than applying a blanket move.

If you are inside 14 days, you are in late-cycle. The priority shifts to inventory absorption. Hold rate on weekend nights unless there is clear evidence of conversion failure. Apply selective cuts or minimum-stay reductions to exposed weekday and orphan inventory. Do not cut strong nights to rescue weak ones.

The second branch is the rate-versus-shape question. If the open inventory has an isolated gap or an orphan structure, the right move is reshape or minimum-stay adjustment — not a rate cut. If the open inventory is broadly soft across multiple nights, a rate cut may be appropriate after confirming pace is behind expectations.

The third branch is the raise question. If pace is fast, early-fill is happening well ahead of your BLT baseline, and RCI is above your target, consider whether ANR can move up on the strongest remaining inventory.

What most hosts get wrong

Hosts shortcut the tree by going directly to “slow calendar, cut price.” The decision tree forces you to ask lead-time position and shape questions before reaching rate action. Cutting price at the wrong lead-time window or on the wrong inventory type costs revenue without improving results.

How to use it this week

At your weekly review, write down: today’s date, the check-in dates you are reviewing, lead time for each, booked nights so far in the target month, available nights, and whether any open nights are isolated or adjacent. Walk through the tree branches. Write down the action — or the decision to wait.

Connected articles

This tool connects to The Five Airbnb Pricing Moves: Hold, Cut, Raise, Reshape, Wait, A 30-Minute Weekly Airbnb Pricing Routine, Airbnb Calendar Pacing Explained, and Airbnb Rate Change Log.

Educational note

This page is educational. It is not tax, legal, investment, or guaranteed-income advice.