A Seasonal Pricing Calendar You Can Set in an Afternoon

One rate all year sells July in March and leaves November empty. A seasonal calendar fixes that with four multipliers on your base rate and a minimum stay for each. It takes an afternoon to set and fifteen minutes a week to run.

Start with the base

The base rate is where you sit among five comparable listings on an ordinary week. The floor is the rate a night cannot go under without losing money. Both come from the costs article and the worksheet. Everything below assumes you have them written down.

Four seasons, four multipliers

These are starting points to test against your own comp set. They are a place to begin, and the first season of your own numbers will move them.

Finding your peak weeks

Open last year's calendar, or a competitor's if this is year one, and look for the weeks that were booked months ahead. Those are peak. For a ski town it is the holidays and February. For a lake it is July and August. For a city it may be conference season or the weeks around a university's move-in. If you have two of them, you have two peaks, and the calendar should show both.

Finding event weekends

Search the town's tourism calendar for the year and write down every festival, race, long weekend, graduation, and concert that fills hotels. Add the ones you know from living there. Each is a block of two or three nights with its own multiplier and a three-night minimum. Do it in January, before the early bookers, because an event weekend booked in February at the shoulder rate is money gone.

Put dates on it

1. Mark the peak weeks for your market.
2. Mark event weekends.
3. The weeks either side of peak are shoulder.
4. Everything else is low.

Set the multiplier and the minimum for each block in the platform's calendar. Do it once a year, in an afternoon, and then adjust rather than rebuild.

A worked example

Base rate 200, floor 150. Peak at 1.4 is 280 with a three-night minimum. An event weekend at 1.75 is 350 with three nights. Shoulder at 1.1 is 220 with two nights. Low at 0.8 is 160, above the floor, with any-day check-in and a one-night minimum. A year with ten peak weeks, six event weekends, twelve shoulder weeks and the rest low prices itself from those five numbers.

The existing seasonality pricing article goes deeper on why demand moves the way it does. This one is the afternoon's work of setting it.

The discount ladder

• Early bird: a modest discount for bookings made well ahead of peak. Cap it where the multiplier still clears the floor.
• Last minute: for open nights inside the next seven days, step down toward the floor. An empty night earns nothing.
• Repeat guests and direct bookings: the platform fee you are not paying is the discount budget. Give part to the guest and keep the rest.
• Never under the floor, except an orphan night. The orphan night article covers that exception. Never on an event weekend.

The fifteen-minute weekly review

1. Pace: how many of the next thirty nights are booked, compared with the same point last month or last year.
2. Pickup: how many nights booked in the last seven days, and at what rate.
3. Gaps: every open night inside the next fourteen days. Discount toward the floor, or hold.
4. A two-minute look at the five comparable listings. If they moved and you did not, you are the one out of line.
5. One change, written in the log with the date.

When to hand it to software

Dynamic pricing tools move rates from market demand. They earn their fee once you have more than one property or a market with real event swings. They are only as good as the floor, the base, and the minimums you give them, so set those first, and set the floor in the tool as a hard minimum. Check what it did once a week; a tool that dropped an event weekend to the shoulder rate because it did not know about the festival is common.

The Pricing and Seasonality Worksheet holds the arithmetic for all of this on one sheet. The revenue management page connects it to the playbook and the weekly review.