Hey,
This is Part 4 of a 7-part series on a real revenue rebuild for a luxury short-term rental. [Part 1](https://cashflowdiary.substack.com/p/your-property-has-1-revenue-line) mapped the revenue-line gap. [Part 2](https://cashflowdiary.substack.com/p/mpi-the-one-number-that-tells-you) gave you MPI. [Part 3](https://cashflowdiary.substack.com/p/the-7-stations-why-your-guests-leak) mapped the seven stations. This issue is the one you can act on today. Details anonymized. Numbers real.
Before I built a single thing or charged a dollar on this engagement, I ran a settings audit on the $2M Hudson Valley estate you've been following since Part 1.
The audit surfaced a conservative modeled $17,351 a year in recoverable revenue. Not from marketing. Not from new channels. From settings that were already wrong — and every fix was free.1
Part 3 ended with a rule: fix the leaks before you pour. This issue is the leak list. Three settings, each one checkable on your own account this afternoon.
I've spent 15+ years in this space, trained more than 10,000 operators through CashFlowDiary, and recorded 237+ podcast episodes breaking down the deals that work and the ones that don't. A settings audit is the first hour of every engagement I run — because it's where the free money hides.
• • •
Fix #1 — The minimum-stay rule blocking the best-selling product
The property required 3-night stays on Fridays and Saturdays.
Now read its own booking history. 5 of its 17 bookings were 2-night Friday–Saturday weekends — at $940 per night net, 35% above the property's average rate, adding up to 28% of all net revenue.
The highest-paying product the property had ever sold was the exact product its settings now refused to sell. A 2-night weekend request now hits a wall the owner didn't know existed.
The fix is one toggle: drop the Fri/Sat minimum to 2 nights — and raise the Fri/Sat rate, because the history says these guests pay a premium. That's roughly $9,400 of proven, already-demonstrated demand, unblocked in under a minute.
⚠️ One nuance before you copy it: holiday minimums are different. This property carries 4-, 5-, and 7-night minimums on Thanksgiving, Christmas, and other peaks via date overrides — those take precedence, and they should survive. The problem was never long minimums; it was a long minimum on an ordinary weekend.
Fix #2 — A pricing tool configured for a different house
The property runs a dynamic pricing engine. The engine is fine. The numbers it was anchored to belong to a different property.
Base price: $600. The median listed rate for 7-bedroom properties in its own neighborhood: $959. Every price the algorithm generates is an adjustment applied to that base — so every night starts from a 37% discount to the segment and inherits the error.
Minimum price: $475. Roughly one forward night in five was pinned to that floor — and still not selling. A floor that low doesn't buy occupancy. It just lowers the average whenever a booking happens to land on it.
Maximum price: $1,900. On one peak fall weekend, a 9-bedroom comp listed at $2,063, a 7-bedroom comp at $2,593–2,893, and a brandless 5-bedroom log house at $1,840. The estate's ceiling sat below what smaller neighbors actually charge on peak dates. The best weekends of the year were capped by a number typed in months earlier.
The engagement's earlier research modeled this reconfiguration at roughly $22,000 a year. I'll be straight with you: that's a model, not a measurement — the mechanism is what's certain. A fifth of nights priced at a floor that isn't converting, and a base anchored 37% under the segment, is rate given away for nothing.
Fix #3 — The broken page teaching Google the wrong thing
The property's direct booking page was live and indexed — displaying "0 bedrooms."
That page occupied the best URL on the property's own domain. It was the first thing a search engine — and any guest doing their homework — learned about a 7-bedroom estate: that it apparently had no bedrooms and looked abandoned. Ten minutes to fix. It had been undermining every search result since launch.
And one more storefront problem in the same family: months after the owner bought the property, the old for-sale listing was still live on the major real-estate sites at just under $2M — the purchase price. Guests researching a luxury stay found a for-sale sign instead of a destination. One email to the listing agent closes it.
Why I'm giving you the fixes for free
Two reasons. First, the numbers overlap — the $9,400 and the ~$22,000 both push toward the same modeled scenario, which is why the conservative first-pass total is $17,351 and not the sum. Precision matters more to me than a bigger headline.
Second: these three fixes are the findings. What they have in common is the method that found them — reading the settings against the property's own booking history and its own segment, instead of against defaults. Your property's three fixes are almost certainly different from these three.
The methodology — how base, floor, ceiling, and the override rules actually interact, the five customizations that silently pierce your minimum price, the trap inside your pricing tool's own recommendation, and the 10-setting audit checklist — that's below the line.
How the four price controls actually interact
Your pricing tool has four controls that most owners treat as one. They behave differently, and two of them lie.
