Why Two Identical Listings Need Two Different Prices

The observation that started our revenue-management system: two listings in the same building — same floorplan, same aspect, similar furniture — routinely produce completely different results. Same market, same nights, different revenue. If pricing were only about location, that should be impossible.

It happens because a listing is more than its address. One of the pair has 40 reviews and books three weeks ahead; the other is new, has nine, and books inside five days. On an event weekend the first can hold a premium rate and still fill; the second fills the same nights only by being sharp early or discounting late.

A market-average price is wrong for both listings at once — too timid for the established one, too brave for the new one. Averages conceal exactly the differences that move money: review depth, booking lead time, conversion rate, and how a listing has historically behaved into an event weekend.

The practical consequence: any pricing approach that starts from "what does this suburb charge" — including copying the listing next door — imports someone else’s booking behaviour onto a property that does not share it.

Each listing needs its own comparable set — similar properties nearby, read continuously — and its own nightly answer to three questions: how is it booking relative to those comparables, how far ahead, and at what rate. From that, base price, last-minute behaviour and minimum-night rules are set per listing, not per building.

This is the premise of both our software and our curriculum: the two identical apartments end up with different base prices and different rules because they are genuinely different businesses that happen to share a lift.