Why Your STR Revenue Is Plateauing — And What To Do About It

Let's start with the most common one, and the one operators are least likely to admit to.

Airbnb's Smart Pricing tool is convenient. It updates automatically, it requires no configuration, and it gives the impression of dynamic pricing without any of the work. For a first-time host managing one or two properties, it's a reasonable starting point. For anyone serious about revenue, it's a liability.

The problem isn't that Smart Pricing doesn't work at all — it's that it's designed to optimise for Airbnb's objectives, not yours. The platform benefits from high occupancy and high booking volume. Your interest is in maximising revenue per available night, which is a different thing entirely. A pricing tool built by a distribution platform will always have an inherent bias toward filling calendars, even at rates that leave money on the table.

Smart Pricing also has no visibility into your specific cost structure, your local market dynamics, your competitor set, or your seasonal demand patterns. It operates on broad signals. Your market is specific.

If you are still using Smart Pricing as your primary pricing mechanism — whether you manage five properties or fifty — you are almost certainly underpricing during your peak periods and potentially overpricing during shoulder season, which is arguably worse because it creates gaps that never recover.

The fix is not simply to turn Smart Pricing off. The fix is to replace it with a deliberate pricing strategy, which brings us to the next problem.

The natural response to realising Smart Pricing isn't working is to subscribe to a dynamic pricing tool. PriceLabs, Wheelhouse, Beyond — the options are well-known, widely used, and genuinely powerful when configured correctly.

The operative phrase is "when configured correctly."

What I see repeatedly is operators — and property management companies — who have adopted a dynamic pricing tool, connected it to their PMS, set a base price, and assumed the tool will handle the rest. They treat it like a set-and-forget system. It is not.

Dynamic pricing tools are only as good as the inputs you give them and the ongoing attention you apply. A tool that doesn't know your minimum acceptable rate, your target occupancy by season, your comp set, your lead time patterns, or your specific market's demand calendar will make decisions that look algorithmic but are fundamentally uninformed.

The due diligence that most operators skip:

• Comp set selection. If your comp set includes properties that aren't actually comparable to yours — different size, different quality, different location — the benchmark is wrong and every price recommendation flows from a flawed baseline.
• Base price calibration. Your base price is the anchor from which the tool adjusts up and down. Too low, and even upward adjustments may still land below what the market would bear. Too high, and you'll see gaps that feel like demand problems but are pricing problems.
• Minimum price floors. Every property has a minimum viable rate below which you're covering costs but destroying long-term value. Many operators never set this, which means in low-demand periods the tool drops rates to levels that attract the wrong guests and generate negative reviews.
• Regular review cadence. Markets change. Events get announced. Competitors open or close. Platforms change algorithms. Weekly — or at minimum monthly — review is not optional. It's the job.

Subscribing to a dynamic pricing tool is not a revenue strategy. It is an input into a revenue strategy. The strategy itself requires human judgement.

There is a tendency in the STR industry — particularly as operators scale — to treat automation as the solution to every problem. Automation is genuinely valuable: it saves time, reduces errors, and enables scale. But there is a specific failure mode that emerges when operators become so dependent on their pricing tool that they stop applying their own market knowledge.

Dynamic pricing tools are excellent at processing data signals. They are not good at understanding context.

A tool doesn't know that a major local employer just announced redundancies and that leisure travel to your market will soften in Q3. It doesn't know that the festival that drove your best October last year has been cancelled this year. It doesn't know that a new hotel opened three months ago and is running an aggressive introductory rate that's temporarily suppressing your comp set's ADR.

You know these things, or you should. And when you know them, you need to be willing to override your tool's recommendations rather than defer to the algorithm.

The operators who break through revenue ceilings are the ones who use their tools as a starting point for decision-making, not the endpoint. They set a strategy, they configure the tool to execute that strategy, and they intervene when market intelligence tells them the tool's output doesn't match reality.

Over-reliance on automation is comfortable. It removes the discomfort of making active pricing decisions and being accountable for the results. But that comfort comes at a cost, and the cost shows up in your monthly revenue report.

Seasonal pricing is where I see some of the most consistent and costly mistakes. The pattern is almost always the same: an operator sets their peak season rates based on what worked the previous year, adjusts slightly for inflation or gut feel, and moves on.

The problem is that market conditions shift year on year in ways that aren't always intuitive. A market that was undersupplied last summer may have seen significant new inventory enter by this summer. A destination that was surging on the back of a trend — the "staycation boom," remote work migration, a viral social moment — may have normalised. Conversely, a market that looked soft last year may have a major event, infrastructure improvement, or regulatory change that makes this year fundamentally different.

Pricing for last year's season means you're always reacting to a market that no longer exists.

The discipline required is to build your seasonal pricing strategy from current data, not historical assumption. That means looking at forward-looking demand signals — search volume trends, competitor rate calendars, local event schedules, new supply data — not just what you charged in July last year.

It also means being willing to make asymmetric bets. If you have strong evidence that a particular week or weekend will see significantly elevated demand — a sold-out event, a public holiday that falls unusually, a competitor going offline — pricing confidently above your default peak rate is the right call. Most operators leave this money on the table because raising rates above their comfort level feels risky. It is only risky if you haven't done the analysis.

The inverse applies equally. If you can see from booking pace data that a particular month is tracking well below last year and the market is soft, holding your rates and watching your calendar stay empty is not a strategy. It's stubbornness. Understanding when to be aggressive on occupancy versus when to hold for rate is one of the most important skills in STR revenue management — and it requires reading the current market, not the historical one.

Revenue plateaus are almost always diagnosed as pricing problems. Frequently they are also distribution problems.

If the majority of your bookings are coming from a single OTA — most commonly Airbnb — you are exposed to that platform's algorithm changes, its fee structure, its competitive dynamics, and its decisions about which listings to surface and which to bury. When Airbnb changes how it ranks listings, your revenue changes. When a competitor in your market gets a burst of five-star reviews and leapfrogs you in search results, your revenue changes. You have limited control over any of this.

A more resilient revenue position comes from diversification: Booking.com, Vrbo, direct booking, corporate and relocation channels depending on your market. Each channel has different guest profiles, different demand patterns, and different cost structures. Together they create a more stable and often higher-yielding revenue mix.

Direct booking in particular is underinvested by most independent operators. The OTA commission you save on a direct booking — typically 15–20% — is real money. On a property generating £5,000 per month in revenue, even a 20% direct booking rate saves £150–200 per month in fees. At scale, across a portfolio, the numbers become significant.

Building direct booking capability takes time and investment — a proper website, a booking engine, a CRM to manage repeat guests, and a marketing strategy to drive awareness. But operators who treat it as a long-term infrastructure investment rather than a short-term quick win are the ones who ultimately break through the revenue ceiling that OTA dependency creates.

A revenue plateau is rarely a mystery once you're willing to look at it clearly. The causes are almost always some combination of the five issues above: passive pricing tools making decisions you should be making, dynamic pricing tools configured without proper care or ongoing attention, over-deference to automation at the expense of market judgement, seasonal pricing based on the past rather than the present, and distribution concentrated in channels you don't control.

None of these are insurmountable. They are the normal byproducts of a business that has grown faster than its revenue management sophistication. The good news is that closing that gap doesn't require a complete operational overhaul. It requires honest diagnosis, deliberate configuration of the tools you already have, and the discipline to review your strategy regularly rather than assuming it's working.

If you're hitting a ceiling and you're not sure which of these is the primary driver, the answer is usually to look at your data before you look at your pricing. Booking pace, lead time distribution, channel mix, and comp set performance will tell you more than your gut feeling — and faster than any tool will.