A property manager at 50 units is paying for software in at least four categories. A property management system, a channel manager (often bundled inside the PMS), a dynamic pricing tool, and some kind of market data product. The annual spend across those tools, for a mid-size portfolio, regularly runs into five figures.
And yet most operators we audit cannot cleanly articulate what each one is supposed to do, where one stops and the next picks up, and where the gaps in the stack are quietly costing them revenue. The categories overlap, the vendors all sell each other's features, and the buyer ends up with a pile of tools whose total is less than the sum of their parts.
Here is the honest map of the stack, what each layer owns, and what it does not.
"Most operators are paying for four layers of software and missing the fifth. The fifth is the one that turns the other four into revenue."
The five layers, end to end
Layer 1. Property Management System (PMS).
The system of record. Guesty, Hostaway, Track, Streamline, Hospitable, OwnerRez, and a handful of others. The PMS holds the reservations, owns the calendar, handles guest messaging, generates owner statements, and is the source of truth for what happened. What it does not do: decide your rate, run your distribution strategy, or tell you what the market is doing.
Layer 2. Channel manager.
The integration layer between the PMS and the OTAs (Airbnb, Vrbo, Booking.com, and the long tail). It pushes rates, availability, and listing content out and pulls bookings back in. On most modern PMS platforms it is built in and you will never see it as a separate purchase. The job is technical plumbing, not strategy. A working channel manager is invisible. A broken one is a double-booking emergency.
Layer 3. Dynamic pricing tool.
PriceLabs, Wheelhouse, Beyond, and a few smaller players. The tool sets a nightly rate per unit based on market signals, your base price, occupancy, lead time, and a set of rules you configure. It is genuinely useful and most operators at any scale should use one. What it does not do: design the rate strategy, decide your fee architecture, set length-of-stay rules deliberately, manage channel mix, or talk to your owners. It optimizes the nightly number inside the box you draw for it.
Layer 4. Market data.
AirDNA, Key Data, Rabbu, Mashvisor, and the rest of the category we covered in the <a href="/resources/blog/airdna-alternatives">AirDNA alternatives</a> piece. These tools tell you what the market is doing, often at a submarket and comp set level. They are an input into decisions. They do not, on their own, make any of them.
Layer 5. Revenue management.
The strategy and decision layer that sits on top of the other four. The function reads pace and market data, decides the rate strategy, configures the pricing tool, designs fee and LOS structure, manages channel mix, audits the OTA listings, equips the property manager for owner conversations, and runs the whole loop on a weekly cadence. This is the layer that turns the first four into actual revenue, and it is the one most often missing.
Why operators think they are covered when they are not
Almost every vendor in layers one through four markets itself as if it covered layer five. The PMS pitches "revenue management" because it shows you a calendar. The channel manager pitches "yield" because it pushes rates to platforms. The pricing tool pitches "revenue optimization" because it adjusts a number. It is honest marketing on each side and collectively it produces a buyer who thinks the box is checked.
It is not checked. The pricing tool optimizes the nightly rate inside the constraints you give it. The PMS records what happened. Neither one is reading pace and deciding which dates to attack this week, sequencing the levers, or sitting on a Friday owner call when the Q3 numbers are soft. That work either gets done by a person, or it does not get done at all. On most portfolios at the 20 to 200 unit range, it does not get done at all.
"Every vendor in the stack markets itself as if it owned the revenue management layer. None of them do. That is a feature of the category, not a bug in your evaluation."
What good looks like, layer by layer
A clean stack at scale is not about owning the most tools. It is about each layer doing its job and handing the next layer clean inputs.
- 01The PMS is configured cleanly. Unit metadata is correct, fees are structured consistently, owner statements reconcile, and the calendar is the single source of truth.
- 02The channel manager is silent. Rates and availability flow in both directions without manual intervention. Listings on Airbnb, Vrbo, and Booking.com match the PMS without drift.
- 03The pricing tool is configured intentionally. Base rates, min stays, premiums and discounts, seasonal layers, and event days are all set on purpose, not on default. The tool is doing what it is good at because someone gave it the right inputs.
- 04Market data flows weekly. Pace, comp set, and supply changes are read on a cadence, not pulled when something looks wrong.
- 05Revenue management closes the loop. Someone reads pace and market data, sets the strategy, configures the tools, makes the calls, and equips the property manager for owner conversations. The decisions are documented and the results are measured same-store.
Where Pacer sits, on purpose
Pacer is layer five. We are not a PMS, not a channel manager, not a pricing tool, and not a market data vendor. We run on top of whichever combination an operator has chosen, configure the pricing tool to fit a deliberate strategy, integrate the market data, and run the weekly decision loop with the property manager. The other four layers stay in place. The work of turning them into revenue is what we own.
If you want to read more about how that layer actually operates, the pieces on what revenue management actually is and what a revenue manager actually does all week cover it in detail.
If your stack is fully populated in layers one through four and the results are still flat, the gap is layer five. That is the layer Pacer runs: we set the strategy, configure the pricing tool to fit it, read the market data weekly, and close the loop the other tools leave open. Casago Heber City ran that loop with us across 14 ski-market units. Same-store Adjusted RevPAR went from $97 to $120 in 23 months, a 25% lift, measured in KeyData. If you want to see where your layers are leaking, we will map your stack and benchmark your book, free.
Adapted from Pacer's editorial archive, April 2026.