The host problem
A competitor two blocks away has a similar bedroom count and lists at $95 per night. You wonder if your $120 rate is too high. But you don’t know that competitor’s minimum stay, cleaning fee, turnover cost, or ALOS. Their $95 listed rate might work only because longer stays reduce turnover drag. Or they might be operating at a loss on churn and not know it.
Comps are useful for market context. They are not useful as a direct price target.
What a comp set is and is not
A comp set is a small group of listings — typically three to six — that are similar enough in size, location, and amenity profile to tell you something meaningful about your market’s demand and rate environment.
A comp set is not a pricing committee. It does not tell you what to charge. It tells you where your market sits, which you then interpret in light of your own cost structure, ALOS, and RevPAR targets.
What makes a valid comp
A valid comp shares most of these attributes with your listing: bedroom count within one, similar location or neighborhood demand, comparable minimum stay policy, comparable amenity tier (e.g., not comparing a standard unit to one with a pool and hot tub), and similar guest type or booking profile.
A listing that looks similar but runs a three-night minimum against your two-night minimum is not a clean comp. Its booking-shape economics may be structurally stronger because it absorbs fewer turnovers per month, even if its visible nightly rate looks lower.
What comps can tell you
You can use a comp set to understand: the general rate ceiling in your market for your property type, whether your price sits at the top, middle, or bottom of comparable options, and whether comps are booking at a rate that suggests market softness or strength.
What comps cannot tell you
Comps cannot tell you what your rate should be, because you cannot see their accommodation revenue, booked nights, occupancy rate, BLT distribution, or turnover costs. A fully booked comp at $85 may be running a worse Net RevPAR than your partially booked listing at $120.
What this helps you decide
Building and reading a comp set helps you understand where your listing sits in the market without mistaking a competitor’s listed price for a pricing target. The goal is context, not imitation.
Example
A host identifies three comps: Listing A at $95 listed rate, Listing B at $110, Listing C at $105. All three appear to have 1-night minimums. The host’s listing has a 2-night minimum and a TCP of $174. The host’s ANR is $125.
At 1-night minimums, Listing A may carry heavier turnover drag even if its listed rate looks attractive. The comp’s listed price is not a valid ceiling. The host uses the comp set to confirm she is in the upper tier of the local market — which is consistent with her 2-night minimum policy — not to justify cutting to $95.
What most hosts get wrong
Hosts match price to the lowest or median comp without asking whether that comp’s cost structure supports the rate. A comp running nightly turnover at a $95 rate may be losing money per booking. Copying that rate replicates the problem rather than solving it.
What to do this week
Choose three listings that match your bedroom count, general location, and amenity level. Note their listed prices and minimum stay policies. Calculate the implied nightly rate if a guest booked the minimum stay. Compare that to your ANR. Then decide: is your ANR above or below where the market sits for your listing type — accounting for minimum stay differences?
Where this fits in the STR Signals framework
Comp intelligence supports the rate-setting and rate-testing portions of the pricing framework. Read Airbnb Price Testing for One Listing to see how to use comp context to design a controlled rate test.