Most independent hotels run one rate card, seasoned twice a year. The property next door moves its prices daily, so it sells rooms on soft dates that would have stayed empty, and it holds a stronger rate on the dates everyone wants. The difference isn’t software sophistication — it’s answering one question daily: is demand for this date running hotter or colder than normal?
The two numbers that matter
Pace: how many rooms you have sold for a future date, versus how many you’d sold at the same distance for comparable past dates. Pickup: how many bookings that date gained in the last day or week. Pace says where you stand; pickup says which way you’re moving. Both come out of booking timestamps your PMS already stores.
Three rules that beat a static card
- Ahead of pace → raise. 70% sold three weeks out when normal is 45% means the date is underpriced. Raise in steps of ₹300–600, watch whether pickup holds, and raise again if it does.
- Behind pace → open value early. Discount three weeks out when plans are still being made — not 48 hours before, when nobody was coming anyway and you’ve only cheapened the guests who were.
- Never sell tonight cheapest on an OTA. If you drop rates to fill the evening, drop direct first and keep the offset. Emergency OTA discounts pay commission on top of desperation.
Seasonality is local, and only you know it
A national calendar knows Diwali. Only you know the exhibition week, the university convocation and the wedding dates that fill rooms in your city. That knowledge is worth writing down once: you type those dates in as special dates, and the engine respects them when it prices.
The rest comes from your own records. For any date, the engine starts from the rates your property actually achieved around that time of year, then moves up or down from there as pace and pickup change. Your own history is the reference — not a national curve.
Common failures
- Raising too late — the sell-out at yesterday’s rate is the missed revenue.
- Discount-loyalty — permanent 10%-off codes train guests to wait, not to book.
- Set-and-forget seasons — a “peak” from 2023 isn’t a strategy in 2026.
- Rate changes that don't propagate — a raise that reaches two of five channels is a parity mess, not a raise.
Practically: set a floor and a ceiling for each room type, let the engine move the rate between them as pace changes, and every move leaves for your channels on the next push — within the hour, or straight away when a booking lands. Large groups do this with analysts. You can do it with software that watches pace while you run the hotel.