Unit 4 · Implementing Your Pricing Strategy · Lesson 4.9
Seasonal profiles and minimum price layers
This is where the three-step strategy becomes settings. Three separate minimum layers exist, one general, one weekend-only, one beyond a lead time, and they map onto the hedge weekday, hedge weekend and control prices respectively. Seasonal profiles sit alongside them, overriding everything for named date ranges.
The full lesson text below is an edited transcript of the video, published 2026-08-24. The complete course is free at the playbook.
Three floors, not one
The primary minimum in the main pricing pane is only the first of three. A weekend-only minimum applies to weekends alone and will normally be higher. A far-out minimum sets separate weekday and weekend floors beyond a lead time you define, and it overrides both of the others for those dates.
That structure is exactly the shape of a three-step strategy, which is why the mapping is mechanical: the primary minimum carries your hedge weekday price, the weekend minimum carries your hedge weekend price, and the far-out minimums carry your control weekday and weekend prices, with the lead time set to where your control step begins. Fixed prices are the simplest way to enter all of them.
On a sample listing with a 150 primary floor and a 278 base, adding a 250 weekend floor lifted the weekends that had been computing below it. Adding far-out floors of 250 on weekdays and 400 on weekends beyond 30 days then took over the second half of February from the 17th onwards, which the per-date breakdown confirms by showing which threshold applied to which date.
Seasonal profiles override everything
A custom seasonal profile defines its own pricing and restriction parameters for a specific date range: its own minimum and maximum, its own base price, and its own minimum stay profile. Anything it specifies overrides your general settings for those dates, which is what makes it the instrument for implementing seasonal prices.
Building one on the sample listing meant naming the range, setting its dates, and raising both floor and base above the general settings: a 250 minimum against the general 150, and a 450 base against the general 278, plus a stay profile requiring three nights on weekdays and four on weekends. The result was a visibly higher-priced week carrying its own stay requirement, with all of it listed in that date’s customisation summary.
One constraint decides when to use profiles at all: a profile applies to the same dates every year. That makes them right for recurring events and holidays, and wrong for a one-off. Multiple profiles can exist side by side.
The seasonality dial
Separate from all of the above is a seasonality setting, which does not set prices but changes how hard the tool’s own seasonal adjustments hit. A recommended profile applies even when the setting is off. Switching it on offers a conservative profile that subdues the swings, an aggressive one that amplifies them, and an option to remove seasonal adjustment altogether.
Viewed on a pricing graph the difference is unmistakable: the conservative profile produces a visibly flatter line across the year, while the aggressive one raises high-season prices and lowers low-season ones. Use it only if a need arises. For most markets the default already reflects the seasonality that exists, and reaching for this dial to fix a specific date range is a mistake, because it moves the entire year.