Elasticity Pricing: The Case for Deliberately Pricing Below Market
Price elasticity measures how strongly booking volume responds to rate changes. Elasticity pricing means choosing the rate that maximizes total revenue (rate × nights sold) across the booking curve — which in elastic conditions is often 5–10% below market, traded for 15–30 points of occupancy.
The most counter-intuitive habit of top operators: they don't always charge the most they could. Revenue is a rectangle — rate on one side, nights sold on the other — and maximizing one side is not the same as maximizing the area.
The result that makes the case
A rate-maximizer looks at that ADR Index and sees underpricing. The revenue line says otherwise: giving up 9% on rate bought 48% more occupancy than the market, and the portfolio banked a third more per available night. The extreme version: one Asok duplex priced at ADR Index 48 captured a 313% market-penetration index at 90% occupancy. No algorithm proposes "price half the market and win on volume" — that's a strategy call.
When volume wins, when rate wins
| Elasticity wins (price for volume) | Rate wins (price for premium) |
|---|---|
| Soft or uncertain baseline demand | Hard demand windows — NYE, Songkran, major events |
| Late-booking, reactive markets | Constrained supply in your tier |
| Post-event shoulders and troughs | Genuinely differentiated product — views, design, scarcity |
| Crowded tiers with weak comp discipline | Repeat-guest and loyalty-heavy segments |
Note what this implies: the same unit should run both strategies in the same year. Elasticity through the shoulder, rate through the event windows. The mistake is picking one identity — "we're a premium listing" — and letting it price your soft season.
Estimating your own elasticity (without a data team)
- Segment first. Elasticity differs by date type — midweek vs weekend, shoulder vs peak. Estimate per segment, not per listing. And make sure your reference price comes from a true comp set — elasticity against the wrong benchmark is noise.
- Run a three-unit test. Take three similar properties: price one for elasticity (−5–10%), one for rate (+5–10%), hold the control. Sixty days, then read RevPAR — not occupancy, not ADR.
- Watch conversion, not just bookings. Views-to-bookings moving sharply with small rate moves = elastic segment; flat conversion under rate changes = you have pricing power. Use it.
- Re-test seasonally. Elasticity isn't a property constant; it moves with guest mix and supply.
Elasticity pricing is not discounting. It's a chosen position with a hard floor: know your cost-covering rate, never let a volume strategy leak below it, and re-raise the moment demand firms. A volume strategy without a floor is just margin erosion with a thesis.
Why occupancy-at-a-discount beats empty-at-a-premium
Beyond the direct revenue math, occupancy compounds: more stays mean more reviews, faster response data, higher booking velocity — all signals ranking algorithms reward. The listing that wins its shoulder season on volume enters peak season with better placement and pricing power. Rate maximizers sitting empty don't just lose the night; they lose the momentum.
RevBnB prices the whole rectangle
The agent estimates elasticity per date segment and prices for total revenue — volume where demand is elastic, premium where you have power — and shows you which call it made and why.
Frequently asked questions
Doesn't pricing below market cheapen my brand?
A 5–10% positioning delta is invisible to guests — it reads as "good value," not "budget." Brand damage comes from volatility (tripling rates late) and from product signals, not from a deliberate value position in elastic seasons.
Won't the algorithm just do this for me?
Dynamic tools adjust around your base price, but the strategic position — volume vs rate, by season, by segment — is a parameter you set, not one they discover. Tools execute elasticity strategies; they don't choose them.
How low is too low?
Your floor is the rate below which a booking destroys value: variable costs (cleaning, turnover, wear, fees) plus a margin. Compute it per unit, set it as a hard floor in your tool, and let no strategy — yours or the algorithm's — breach it.
Does this work for small portfolios?
Yes — the three-unit test just becomes a three-month sequential test on one unit (alternate postures by comparable date blocks). Slower signal, same logic: judge every posture by RevPAR against the market, not by how full the calendar feels.