A pricing tool that was configured once and left alone is not a pricing strategy. It is a subscription. The algorithm keeps publishing rates every night whether or not anyone is checking them, and the nights it prices badly do not show up as errors. They show up as a booking that came in too cheap, or a Saturday in October that never booked at all. Nothing on your dashboard flags either one.
Owners tend to ask the wrong question about these tools. The question is not whether dynamic pricing beats a flat rate. It does, and that argument has been settled for years. The question is whether your tool, with your settings, on your street, is capturing what your home could have earned. That is an audit, and it is one you can run yourself in an afternoon.
Underpricing is rarely dramatic. A tool that is badly calibrated does not publish a rate that is half of market. It publishes a rate that is slightly under market, consistently, and it fills your calendar fast enough that everything looks healthy. High occupancy is the most common disguise for lost revenue. If your home books out four months ahead at a rate that never moves, the tool is not reading demand — it is clearing inventory.
Overpricing looks different and is easier to spot: gap nights, orphan nights between reservations, and a calendar that fills only in the last two weeks at whatever the algorithm panics down to. Both failures come from the same root cause, which is that the tool is comparing your home to the wrong set of homes.
Everything in this audit comes out of your own records. You do not need to buy market data to begin.
That last item is where most audits end early, because the comparison set is usually wrong.
Pricing algorithms build a comp set from what they can measure: bedroom count, bathroom count, guest capacity, distance, and star rating. They cannot measure the things that actually determine what a guest will pay. Whether the primary bedroom is on the ground floor. Whether the pool gets sun after two in the afternoon. Whether the street is the one that floods, or the one that backs onto a greenway, or the one where the neighbor keeps a boat in the driveway.
In our markets these distinctions are the whole ballgame. In Delray Beach and Deerfield Beach, a home eight blocks from the sand and a home three blocks from the sand are different products at different price points, and a radius-based comp set will treat them as substitutes. In Durham, a house walkable to Ninth Street prices differently than one the same size across the freeway, and no algorithm reading latitude and longitude knows why. In Raleigh, proximity to a hospital campus or to NC State changes not just the rate but the shape of the demand curve — which weeks are strong, which are dead, and how far ahead people book.
This is the structural reason a national manager's revenue desk cannot do this well. Someone pricing several thousand listings across forty markets from one screen has to trust the model, because they have no basis to overrule it. They have never stood in your driveway. Local knowledge is not a nicety in revenue management; it is the input the model is missing.
So rebuild the set by hand. Pick eight to twelve listings you would genuinely lose a booking to — the ones a guest would open in another browser tab before choosing yours. Then check whether your tool's set resembles yours. If it does not, most tools let you override it, and that single change often does more than every other adjustment combined.
| What you see | What it usually means | What to change |
|---|---|---|
| Calendar fills months ahead, rate barely moves | Base rate too low; tool clearing inventory rather than reading demand | Raise the base rate and the minimum, then watch pickup for three weeks |
| Far-out bookings cheaper than last-minute ones | The demand curve is inverted against you | Raise the floor for dates beyond sixty days out |
| Many nights sold at exactly the minimum rate | Your floor, not the market, set the price | Move the floor and re-check in a month |
| Scattered one and two-night gaps | Minimum stay rules blocking bookable nights | Enable gap-filling rules; allow shorter stays inside the booking window |
| Whole weeks empty in one month every year | Wrong seasonality profile for the market | Override the seasonal curve using your own booking history |
| Event weekends priced like ordinary weekends | Local calendar not in the tool | Add event dates manually and price them by hand |
| Comp set includes homes you would never lose a guest to | Radius-based matching | Replace the comp set with listings you selected |
Three settings do most of the damage, and all three are usually left at whatever the tool suggested during onboarding.
The minimum rate. Owners set a floor to feel protected, then forget it. A floor set two years ago is a floor priced for two years ago. It is also the number the tool retreats to on every soft date, which means a stale floor becomes your effective rate for a meaningful share of the year.
Minimum stay by season. A three-night minimum that makes sense in peak season costs you the entire shoulder season, when the inquiries are couples looking for two nights. Minimums should tighten and loosen with the calendar, and most tools support that.
The last-minute discount curve. The default is usually aggressive, because a tool that fills your calendar looks like a tool that is working. Aggressive discounting inside seven days teaches nothing except that your home is the cheap option. Flatten the curve and see whether the nights still fill.
We run this audit every quarter on every home we manage, comparing what each home actually booked against what our hand-selected comps achieved on the same nights. Not because the software is bad — the good tools are genuinely good — but because the inputs go stale. A new building opens. A competitor drops their rate for a season. An event moves off the calendar. The algorithm reacts to some of that and misses most of it.
This is the part that gets sold as passive income and is not. Short-term rental is a business, and revenue management is one of its recurring jobs. It can absolutely be passive for you — that is what hiring an operator buys — but it is passive because someone else is doing the work on a schedule, not because the work stopped existing. A pricing tool automates the publishing of rates. It does not automate the judgment about whether those rates are right.
If you would rather not spend a quarterly afternoon in spreadsheets, that is a reasonable position, and it is the job we do. We manage homes across the Triangle — Raleigh, Durham, and Chapel Hill — and Southeast Florida from Miami up through Fort Lauderdale, Pompano Beach, Deerfield Beach, and Delray Beach, and we price every one of them against a comp set we built by walking the neighborhood. Send us your address and last twelve months of bookings and we will run this audit on your home and tell you what we find, free. If the tool is doing fine, we will say so.
