Pricing School
TL;DR
Sean Rakidzich emphasizes that pricing strategy, not just algorithms, is crucial for successful Airbnb management, as two hosts with identical setups can achieve a 72-point occupancy spread in slow season.
The article highlights the importance of manual overrides and fortnightly supply-demand reads, showing that daily data is noise while fortnightly data provides actionable signals for better pricing decisions.
Sean recommends setting a base rate based on a weighted average of occupied nights, defending a slow-season floor calculated from cleaning costs and variable expenses, and avoiding creeping adjustments to maintain pricing accuracy. By Sean Rakidzich, 155-property operator. Strategy session at rakidzich.com/book.
Key Facts
| Metric | Source | Healthy Signal | Shift Signal |
|---|---|---|---|
| Active comp listings | AirROI or manual scrape | Flat or falling | Up 10% fortnight over fortnight |
| Competitor ADR at bed count | Comp set pull | Flat to rising | Falling 5% or more |
| Next-30 booking ratio | Your PMS dashboard | Above last fortnight | Below last fortnight |
- Algorithm ≠ strategy. Software prices nights. The operator sets the base rate, floor, ceiling, and override calendar.
- Fortnightly cadence. Pull 3 supply-demand numbers every 2 weeks, not daily.
- Manual override wins. The algorithm reacts 3 to 4 weeks late. You cannot wait for it.
Why A Price Is Not A Strategy
A pricing algorithm gives you a number for tomorrow night. It does not tell you why that number is correct, whether it serves your slow season goal, or what to do when the number is wrong. The model is executing against a signal set that does not include your philosophy.
The strategy layer answers four questions the software cannot. What is my base rate. What is the floor I will defend. What is the ceiling I will not cross. Which calendar dates do I override by hand.
Miss any one of those four and you are renting your revenue decisions out to a vendor.
The Four Author-Level Inputs
Base rate is the anchor the algorithm multiplies against. Floor is the number below which a vacancy is better than a booking. Ceiling is the number above which price-fragile guests leave 3-star reviews. Override days are the local spikes the scraper has not learned yet, like a college home game or a regional trade show.
A tool like PriceLabs or Wheelhouse will happily run without any of these inputs set correctly. It just will not run well.
The Fortnightly Supply And Demand Read
Reading a short-term rental market is a 2-week cadence, not a daily one. Daily data is noise. Fortnightly data is signal. The operator who checks comp sets every morning burns hours and still reacts late.
Three numbers go on one sheet, every other Monday. Active listing count for the comp set in your immediate neighborhood. Average daily rate of competitors at your bed count. Ratio of bookings on the next 30 days versus the prior fortnight's run rate.
The Three-Number Sheet
| Metric | Source | Healthy Signal | Shift Signal |
|---|---|---|---|
| Active comp listings | AirROI or manual scrape | Flat or falling | Up 10% fortnight over fortnight |
| Competitor ADR at bed count | Comp set pull | Flat to rising | Falling 5% or more |
| Next-30 booking ratio | Your PMS dashboard | Above last fortnight | Below last fortnight |
All three shifting the wrong way at once is a floor-drop event. Two out of three is a watch. One is noise.
The Base Rate Reset
Most hosts set a base rate in year one and never revisit it. The market has moved. The base rate has not. Every calendar night the algorithm produces is multiplied against a stale anchor.
A correct base rate in 2026 is the price at which you would be indifferent between booking and not booking on a neutral midweek night in shoulder season. Not your best night. Not your worst. The middle.
Base Rate Reset Procedure
- Pull 90 days of occupied nights. Weighted average ADR from your PMS. Ignore blocked and owner-stay nights.
- Strip out peak and trough weeks. Remove the top 20% and bottom 20% of ADR nights. The middle 60% is your true center.
- Compare to your current base. If the middle 60% average is more than 8% above or below your set base, you are misanchored.
- Reset in a single move. Do not creep. Set the new base in one adjustment and hold 14 days.
- Watch pickup compression. If the 7-day pickup tightens, the new base is correct.
Slow Season Floor Logic
Slow season is where strategy separates from software. The algorithm wants to fill every night. You might not. A 20% occupancy month at a defended floor can out-earn a 92% occupancy month at a collapsed floor, depending on your cost stack and your review profile.
The floor is not a guess. It is cleaning cost plus variable cost plus a minimum margin you will accept. Below that number, the booking costs you money in wear, supplies, and review risk.
Defend it.
The Floor Math
Peak Season Ceiling Logic
Price-fragile guests exist. They book at the ceiling and they judge against it. Every dollar above the ceiling is borrowed from your review score.
The ceiling is the price at which your listing stops looking like a value and starts looking like an extraction.
A defensible peak ceiling for most non-event STR markets, expressed as a multiple of your base rate. Above 1.4x without a named event driver, review risk climbs faster than revenue.
The Override Calendar
No scraper catches every local spike. Your regional college's homecoming, the medical conference at the convention center, the music festival that just added a second weekend, the high school state championship that moves cities every year. The algorithm will price those nights as ordinary.
They are not ordinary. They are the highest revenue nights of your year, and the software will miss half of them in the first year of any new listing.
You keep the override calendar. The algorithm does not.
Building The Override Sheet
Override Calendar Build
- List every annual local event. College games, conferences, festivals, graduations, championships. Go back 3 years of local news.
- Tag each with a multiplier. 1.3x, 1.6x, 2.0x based on historical pickup speed and comp set response.
- Set the override 180 days out. Before the algorithm starts pricing those nights, your number is already in.
- Lock the minimum stay. Most event nights deserve a 2 or 3 night minimum to block single-night arbitrage.
- Review quarterly. Add new events. Adjust multipliers based on how fast bookings came in last year.
This is the layer pricing software has no way to author. The Airbnb help center will not tell you about your city's trade show calendar. AirROI market data will not capture a first-year festival. You capture it.
A pricing algorithm gives you a price, not a strategy. Two hosts run the same config on the same listing and one sees 20% occupancy in slow season while the other sees 92%. The difference is not the algorithm.
How Pricing School Fits In
Pricing School is a $80 curriculum at ps.rakidzich.com that walks through base rate setting, slow season floor logic, peak season ceiling logic, and the override calendar. It is built from managing 100 plus listings and ships the strategy layer that pricing software does not include. Hosts finish the course with a configured PriceLabs or Wheelhouse account that reflects their philosophy, not the vendor's defaults.
The course is execution-focused. Every module ends with a spreadsheet, a procedure, or a calendar template you copy into your own operation that week.
It pairs well with your PMS choice, because pricing strategy and channel execution are two different skills and both have to be solved.
Who It Is Not For
If you have one listing and plan to stay at one listing forever, a $80 pricing course is over-engineered. Set a reasonable base, run Smart Pricing, and reinvest the fee in better photos. The course is built for operators at 3 listings and up, or anyone scaling toward a portfolio.
Frequently Asked Questions
Why is a price not a strategy?
You must define four key inputs that the software cannot determine on its own. These include setting your base rate, the floor you will defend, the ceiling you will not cross, and the specific calendar dates you override by hand. Missing any of these four elements means you are effectively renting your revenue decisions out to a vendor.
How does the fortnightly supply and demand read work?
You should track three specific metrics every other Monday instead of checking data daily. These metrics include the active listing count for your comp set, the average daily rate of competitors at your bed count, and the ratio of bookings on the next 30 days versus the prior fortnight. When all three numbers shift the wrong way at once, it signals a floor-drop event rather than waiting for the algorithm to react.
What is the base rate reset?
What is slow season floor logic?
The floor is the specific price point below which a vacancy is financially better for you than accepting a booking. You must manually drop this floor when supply shifts and the booking ratio drops, rather than waiting for the algorithm to react weeks later. This manual override ensures you maintain occupancy during slow seasons when the software lags behind market inflections.
What is peak season ceiling logic?
The ceiling represents the maximum price point above which price-fragile guests will leave 3-star reviews. You should not cross this limit even if the algorithm suggests higher rates during high demand periods. Setting this cap protects your reputation and prevents losing guests who are sensitive to excessive pricing spikes.
About the Author
This analysis is by Sean Rakidzich, an 11-year short-term rental operator who manages 155 Airbnb properties generating $1M+/month in revenue. Sean has trained 5,000+ students across 76 countries with $1.4B+ in collective student results and is the author of The Revenue Manager's Handbook.
For Sean's framework on pricing strategy, not just algorithms, is crucial for successful Airbnb management, as two hosts with identical setups can achieve a 72-point occupancy spread in slow season, see his full content library at rakidzich.com or book a 30-minute strategy session at rakidzich.com/book.