Connecting dynamic pricing and revenue forecasting

Prices move daily. The forecast stays where it was set.

Most short-term rental property managers run budgeting and forecasting separately from their dynamic pricing tool.

The pricing tool updates rates every day. It reacts to market shifts, competitor moves and events. Meanwhile the forecast lives in a spreadsheet that was built at the start of the year and maybe gets revisited once a quarter.

So your prices keep changing, and your forecasted rent stays the same.

If you've ever been in an owner meeting where you couldn't explain why revenue is tracking 12% behind budget even though "the pricing tool is running," you've felt this gap. The problem isn't your team or your spreadsheet. The two processes are answering different questions.

Pricing tools don't predict revenue. They calculate adjustments.

Here's what most dynamic pricing tools in the STR industry do. They:

Start with a base rate
Look at market signals: comp set rates, day of week, seasonality, events, lead time
Apply multipliers to the base rate

Say your tool sees that Friday market rates are 10% above average. It raises your Friday rate by 10%.

That sounds sensible. But look at what that adjustment doesn't tell you:

How much demand is there for your listing on that Friday?
What is the probability that you get booked at that price?
If you do get booked, how much rent will you actually collect?

A 10% bump is a relative move. It describes your price compared to the market. It says nothing about the outcome. The tool isn't forecasting anything. It's doing arithmetic on a base rate.

An adjustment stops at the rate. A demand model carries the price through to expected rent.

Why this breaks your forecasting process

Because the pricing tool can't tell you what revenue to expect, forecasting gets pushed somewhere else. Usually that means:

Last year's actuals plus a growth assumption
Occupancy targets multiplied by an assumed ADR
A market data report that gets pulled into a spreadsheet
Owner expectations that are hard to walk back

None of these inputs know what your pricing tool is doing. The forecast assumes a $350 ADR for July while the tool is quietly pricing July at $310 because comps dropped. Or the tool pushes rates up for a festival weekend while the forecast assumes a booking pace that no longer holds at the higher price.

That leaves you with two sources of truth that never meet.

The tool that sets your prices isn't accountable for revenue. The process that is accountable doesn't control your prices.

The real cost of the disconnect

This isn't just a reporting headache. It has real consequences.

You find problems too late. If your forecast doesn't move when prices move, you won't see a revenue shortfall until it's already in your actuals. By then the booking window for those dates has closed.

Owner conversations get harder. Owners don't care about multipliers. They care about what they'll earn. When you can't connect pricing decisions to expected revenue, every conversation turns into defending the tool instead of showing a plan.

Your team does duplicate work. Revenue managers end up keeping the pricing tool and a separate forecasting model in sync by hand, exporting data, reconciling numbers and rebuilding spreadsheets. That time could go toward actually improving performance.

You optimize for the wrong thing. Matching or beating the market rate isn't the goal. Maximizing the rent you collect is. A price that's 10% above market but has a 30% chance of booking can be worth far less than a price slightly below market with an 80% chance.

An alternative: price and forecast from one model

The gap closes when the model that sets the price also predicts the outcome. This is the idea behind probabilistic, or demand-based, pricing. It's the approach we take at Quibble, but the concept applies whatever tools you use.

Instead of applying adjustments to a base rate, a probabilistic model predicts demand for each listing on each night, then picks the price that maximizes expected rent. It works in three steps:

For every night, the model estimates the probability of getting booked at different price points.
It weighs higher prices against lower booking probability to find the price that maximizes expected rent: price × probability of booking.
Because the model already knows the probability of booking and the optimal price, the forecast comes directly out of the pricing decision.

When the price changes, the forecast changes with it. When demand softens, you see it in expected revenue right away, not three months later in your actuals.

Illustrative example: expected rent peaks at $295, below the highest price on the curve.

Go back to the Friday example. Instead of "the market is 10% higher, so raise the rate 10%," a demand model reasons like this:

At $280 there's a high chance this Friday books. At $320 the chance drops. Expected rent is highest at $295, and that expected rent is what goes into the forecast.

The price and the forecast are two outputs of the same calculation, so they can't drift apart. It's also a decision you can explain to an owner.

What changes when pricing and forecasting share a model

Forecasts stay current. They update whenever market conditions or prices change.
Shortfalls show up earlier. Gaps between forecast and target appear while there's still time to adjust strategy, minimum stays or marketing.
Owner reporting connects price to outcome. You can show what you're charging, what you expect to earn and why.
There's less to reconcile. Nobody has to keep a pricing tool and a separate forecasting spreadsheet in sync by hand.
The target is expected rent. Matching the comp set becomes an input, not the goal.

How to check your own setup

A few questions will tell you how connected your pricing and forecasting are today:

Does your pricing tool give you a revenue or occupancy forecast, or only rates?
When rates change, does your forecast change? How often is it refreshed?
For a given price, can you see the booking probability or expected occupancy behind it?
Do you track booking pace against the forecast for each stay date?
When actuals miss the forecast, can you trace the miss back to a pricing decision?

If most answers are no, you can still narrow the gap with your current tools. Re-forecast at least monthly using the rates that are actually live, not the ones in the original budget. Compare on-the-books revenue for each future month against the same point last year. Treat a large gap between your current rate and your budgeted ADR as an early warning instead of waiting for month-end actuals.

The takeaway

Budgeting, forecasting and pricing are all parts of one question: how much revenue will this property earn, and how do we make it more?

When they run as separate processes, with separate tools, assumptions and spreadsheets, the answers drift apart. Whatever tools you use, the aim is the same: forecasts that reflect your current prices, and prices chosen with their likely outcome in mind.