Unit 4 · Implementing Your Pricing Strategy · Lesson 4.14
Implementing test prices
Test prices are implemented with a far-out premium rather than typed in date by date, and the setup holds one non-obvious decision: start the premium ramping up well before your test step begins, so the increase is already meaningful by the time the step arrives. A gradual ramp also avoids the sharp jump a flat premium creates.
The full lesson text below is an edited transcript of the video, published 2026-08-24. The complete course is free at the playbook.
Validate before you adjust
Before changing anything, read the calendar through the booking window your test step covers and ask whether an adjustment is needed at all. The standard is the same one that governed the base price: low-demand dates at the near end of the step should sit close to your stated minimums, while dates further out and dates with real demand should be running above them.
On the sample listing, the test step began about 95 days out. Reading forward from there, several weekday dates late in the month were falling short of the 240 minimum, and although the weekends were at or above their 350 minimum, those dates were showing good demand and should have been higher still. The following month told the same story, with prices sitting closer to the minimums than the demand justified. That is what a listing that needs a premium looks like.
Use a far-out premium, not manual entry
Test prices are not entered date by date. They are produced by a far-out premium: a rule that lifts prices as dates move further into the future. Before switching one on, read what the default already does, because you are adjusting a behaviour rather than creating one from nothing.
In the sample tool the default was a gradual 20% premium beginning 60 days out, ramping across 171 days until the full premium applied from 231 days and beyond. Knowing that number matters, because if prices need to rise the premium has to be set above the default rather than merely switched on. The listing here went to 30%, and the honest caveat is that landing on the right percentage usually takes some trial and error.
Start the ramp before the step starts
The setup detail worth understanding is where the ramp begins. It is tempting to start the premium exactly where the test step starts. The better move is to start it earlier, because a gradual premium builds over time: if the ramp begins around 60 days out and climbs across the following 60 days, then by its midpoint, which is roughly where the test step opens, a meaningful premium is already in force. Start the ramp at the step boundary instead and the earliest test dates carry almost no premium at all.
Compressing the ramp matters too. Narrowing it from the default 171 days to 60 raises the increment applied per day, so the premium accumulates faster. And a gradual ramp is generally preferable to a flat percentage, which lifts every far-out date by the same amount and produces a visible step change in the calendar. Both are available; the gradual version is the gentler instrument.
With that in place on the sample listing, the late-month dates lifted and the following month moved above its minimums, which is exactly what the validation pass had been asking for.