Create a Hotel Dynamic Pricing Strategy
Build clear pricing rules for demand, day-of-week, lead time and events instead of a flat rate.
A single flat rate charged all week is the most expensive habit an independent hotel can have. It leaves money on the table on the nights guests would happily pay more — peak weekends, event dates, the last few rooms before sell-out — and it leaves rooms empty on the soft nights where a lower rate would have filled them. Dynamic pricing simply lets the rate follow demand instead of ignoring it.
Big chains do this with expensive revenue-management systems, but the logic underneath is learnable and can be run by hand or as simple rules in your PMS. The four signals that matter are occupancy pace (how fast a date is filling), day of week, lead time (how far out the booking is) and known local events. This prompt turns those signals into concrete thresholds — 'raise the rate by X% when pickup for a date passes Y%' — rather than vague encouragement to 'price smarter'.
Two guardrails keep it safe: a floor you won't sell below (chasing occupancy under it usually destroys RevPAR) and a ceiling that keeps you credible. Reach for this when you sense your rate is too static, and pair it with the RevPAR prompt to make sure a rate change is actually growing revenue and not just shuffling it.
You are a hotel revenue manager. Design a dynamic pricing strategy I can apply manually or through my PMS. Context: - Hotel: [HOTEL NAME] in [LOCATION], [NUMBER OF ROOMS] rooms - Current base rate (BAR): [AVERAGE ROOM RATE] - Typical occupancy pattern: [PATTERN, e.g. weekends strong, weekdays soft] - Local demand drivers: [EVENTS/SEASONS] - Room types and their share: [ROOM TYPES] Deliver: 1. A pricing framework using occupancy pace, day-of-week, lead time and events. 2. Specific rate rules (e.g. 'raise BAR by X% when pickup for a date exceeds Y%'). 3. A floor rate and a ceiling rate, with the logic for each. 4. How to handle last-minute unsold rooms without training guests to wait. 5. A weekly pricing routine I can follow in under 30 minutes. Give me concrete percentages and thresholds tuned for a [NUMBER OF ROOMS]-room independent hotel, not vague advice.
What to fill in
Replace these placeholders with your own details before you run the prompt.
[HOTEL NAME]- Your property's name.
[LOCATION]- City / area.
[NUMBER OF ROOMS]- Room count — affects how aggressively you can flex rate.
[AVERAGE ROOM RATE]- Your current base rate (BAR).
[PATTERN]- Your occupancy rhythm across the week/season.
[EVENTS/SEASONS]- Local events and seasons that spike or drop demand.
[ROOM TYPES]- Your room categories and their rough mix.
How to use this prompt
- 1Give real occupancy patterns — pricing rules are only useful if they match your demand curve.
- 2Ask for concrete thresholds (percentages, days out) you can turn into PMS rules.
- 3Start by applying the rules to the next 30 days, then review what actually picked up.
Example input
Hotel: Shimla Hillside Inn, 28 rooms, BAR ₹5,000, weekends strong / weekdays soft, demand drivers: summer holidays + long weekends. Room types: 70% deluxe, 30% suites.
What you'll get
A framework with day-of-week multipliers (weekends +25-40%, weekdays at or below BAR), pace-based rules (raise 10% when 30-day pickup > 60%), a floor of ₹3,200 and ceiling of ₹8,500 with logic, a last-minute strategy that avoids deep discounts, and a 25-minute weekly pricing routine.
Pro tips
- •The biggest pricing mistake independents make is a flat rate all week — you leave money on strong dates and empty rooms on weak ones.
- •Set a real floor rate. Chasing occupancy below it usually destroys RevPAR.