Unit 5 · Maximizing Performance Through Iteration · Lesson 5.9
When only your lowest prices book
If every booking arrives in the last day or two, at the lowest price in your strategy, the listing is not booking well. It is booking cheaply. The usual cause is control and test prices set far above what the market will pay, and the fix is to cut those two steps back toward the middle of the comp set while leaving the hedge alone.
The full lesson text below is an edited transcript of the video, published 2026-08-24. The complete course is free at the playbook.
Only the cheapest nights book
The listing in this case is a 2 bedroom property in downtown San Antonio, Texas. Its pricing strategy runs the usual three steps, split by booking window: the hedge covers 0 to 1 day out, the control covers 2 to 26 days out, and the test covers 27 to 365 days out. Cleaning runs at $100, tax is 13.5%, and nothing is added for service.
The symptom is narrow and specific. Bookings arrive in the hedge step and nowhere else. Nothing lands in the control step, nothing lands in the test step, and the calendar beyond the next 48 hours is empty. Conversion was checked first and ruled out: guests who see the listing in search results click it, and guests who click it go on to book.
That combination is worse than it first looks. The hedge is the lowest price in the strategy, and it exists as a safety net for the last day or two before a night expires unsold. If every booking is arriving there, the entire calendar is being sold at the floor, and there is no forward occupancy to protect or improve. Last minute bookings are not a win when they are the only bookings.
Rule out availability first
Before treating hedge only bookings as a pricing problem, confirm that the control and test nights were genuinely available to book. Zero bookings in a step whose nights were already blocked, or already sold, tells you nothing at all about price. Zero bookings in a step with open availability tells you a great deal.
Here the calendar was open across both steps. That leaves one explanation standing: the rates showing from 2 days out and further were rates the market would not pay, and the only price point clearing was the cheapest one.
What the numbers showed
Start with the hedge. That window is short enough that it contained no weekends, so only the midweek picture is readable. The listing was booking at around $102 a night, which sits between the 25th and the 50th percentile of the comp set. Cheap, but booking.
The control step is where the damage sits. Occupancy across it was zero, against expected market occupancy of 40% to 60% for the same dates. The rates being advertised were $189 midweek and $250 at weekends, both above the 90th percentile of the comp set.
Put those two facts side by side and the diagnosis writes itself. Asking above the 90th percentile in a market that is expected to reach 60% occupancy at best means competing for the last thin sliver of demand, and that only works when the property is significantly better than everything in its comp set. This one is not. The test step told the same story: no occupancy, with rates sitting between the 75th and the 90th percentile.
Why the hedge stays put
The hedge was set at $80 midweek and $99 at weekends. Those are the only prices in this strategy with evidence behind them, so they stay exactly where they are.
Two reasons. The control and test steps are about to move a long way, and moving all three at once destroys your ability to read the result. And leaving the floor untouched is deliberate insurance: if every new price fails, bookings still land at $80 and $99, so the listing keeps clearing nights while the experiment runs. That is a safe to fail design, not timidity.
The hedge does get revisited, just not in this iteration. Once the control and test steps are producing bookings, the fair question is whether $80 and $99 are leaving money behind. Asking it now, while nothing else is working, risks lifting prices across the board and getting booked nowhere.
Resetting the control step
Midweek first. Expected market occupancy across those dates runs about 41% to 42%, which is soft. Soft demand argues for the 50th percentile rather than anything above it, and the 50th percentile lands at roughly $110. That becomes the new midweek control rate.
Weekends are stronger, just under 60% expected occupancy, which supports sitting at or slightly above the 50th percentile. The first number on the table was $140. It came down to $130 on a simple check against the hedge: the weekend price that is actually converting is $99, so holding weekends far above that while nothing books is optimism rather than strategy.
The size of the cut matters as much as its direction. When nothing is booking, the urge is to slash. Taking a midweek rate from around $130 down to $90, barely above the hedge, would probably fill the calendar, but it hands back most of the money the correction was meant to recover. Step down in increments instead. If bookings are urgent the cut can be bigger, and the recommendation is still to take it in stages, so you can see which stage did the work.
Resetting the test step
The test step covers 27 days out to a year ahead, and there is almost no market occupancy showing that far out yet, which is normal. The useful reference is history: the same window a year earlier averaged 51% midweek and 69% at weekends, consistently. That demand is real, it just arrives later.
Because it is expected to arrive, the test step should sit above the control, by roughly 10% to 20%. Taking the top of that range, 20% on the control rates gives about $130 midweek and about $156 at weekends, rounded up to $160.
Set those against what was being advertised, $165 midweek and $195 at weekends, and both are real cuts. That is the point. The old test rates were priced for demand the market was not showing.
When more data adds nothing
There is a deeper layer available in a case like this, the month by month performance history, and here it would not have changed a single decision. The step level view showed where bookings were and were not happening. The comp set percentiles showed why. That was enough to act on.
This matters more than it sounds. Analysis has a cost, and the discipline is to stop once the data in front of you supports the decision. Digging further when the answer is already unambiguous is procrastination.
What the next iteration is for
The new iteration runs the following two weeks, the 26th through the 10th: hedge unchanged at $80 and $99, control at $110 and $130, test at $130 and $160. Loading those into the pricing tool that runs the calendar, such as PriceLabs, is the mechanical part. The judgement was all in the two decisions above, which step is failing and how far to move it.
Write down what you expect before the iteration runs. The goal here is explicit: bookings appearing in the control and test steps, and fewer of them arriving in the hedge. The control step is the real target, because in a healthy strategy the majority of bookings should land there, in the window between 2 and 26 days out.
None of these numbers are meant to be right. They are meant to be bookable. The immediate problem is that nothing at all was selling beyond the next 48 hours, and that problem gets solved first. The iteration after this one answers the finer question: whether $110 should have been $120 or $125, whether the weekend rates can push higher, and whether the hedge can finally come up off $80 and $99.
It is a common failure, and a cheap one to correct. Prices that only book at the floor are not evidence that the market is weak. They are evidence that everything above the floor was priced for a market that does not exist.