Say a five-property hotel group has its head office in Vienna and no revenue operations (RevOps) software tying its hotels together. Each hotel runs its own revenue management system (RMS), keeps its own notes on competitor rates and makes its own read on demand. During a big regional trade fair, two properties hold rates flat because they expect the event to be quieter than last year. Two others raise rates early and sell out fast. The overflow lands at the fifth hotel, which is still selling at its normal midweek rate. No single pricing decision was wrong. The problem was that nobody at group level could see all five decisions in one place before they went live. That gap is what RevOps software, and the routine around it, is meant to close.
RevOps Software Versus a Single-Property RMS
An RMS sets prices for one hotel. It forecasts demand, tracks competitor rates and recommends a rate for each room type and date. If you want the basics, our guide to revenue management software explains how hotels use one day to day. Most RMS set-ups are built around one property at a time. Unless the group has switched on portfolio features, the system has little idea what the sister hotel twelve kilometres away is charging that same weekend.
Revenue operations sits one level above that. It is the mix of process, reporting and software that decides how pricing calls get made across a portfolio, who is accountable for them, and whether every team works from the same numbers. An RMS is one input into that system. A group can run a strong RMS at every hotel and still have a RevOps problem, because the RMS answers “what should this hotel charge?” and leaves open whether that rate makes sense next to the other four during the same event. The job at single-hotel level is described in the hotel revenue manager role.
The Software Layers in a Hotel RevOps Stack
Groups tend to build this stack in roughly this order, often without planning it.
The RMS layer. This produces the pricing recommendations for each property. Some vendors now sell portfolio features on top. IDeaS (a SAS company) added Portfolio Navigator to its G3 RMS in March 2024. It shows every property’s performance in one view and lets a group push a revenue strategy to several hotels from one place. Atomize, which Mews bought in November 2024, lists multi-property and group pricing among its main features. Duetto’s GameChanger handles pricing, and groups such as Sandman Hotel Group pair it with Duetto’s reporting tool, ScoreBoard. Some groups run the same RMS at every hotel. Others run different ones, depending on when each hotel joined. That mix is a RevOps question in itself, and it gets harder to fix the longer it runs. A wider comparison sits in best revenue management software for hotels.
The business intelligence (BI) and reporting layer. A single hotel can often skip this. A group usually can’t. It is the dashboard that brings occupancy, average daily rate (ADR), revenue per available room (RevPAR) and booking pace from every property into one view a regional revenue director can open each morning. It can be a general BI tool, a data warehouse that pulls from each hotel’s property management system (PMS) and RMS, or a hospitality reporting product such as Duetto ScoreBoard, which Sandman uses to produce and share multi-property reports. Without it, comparing notes means someone copying numbers between spreadsheets by hand, which is what happened in our Vienna example. How data moves between these systems is covered in our article on the revenue management platform.
The forecasting and pricing routine. It needs a shared calendar that flags regional events for every property, a regular check-in (or one triggered by an event) where revenue managers compare planned moves before they make them, and a written answer to who has the final say when two hotels disagree. The forecasting side has its own guide: demand forecasting for hotels.
Distribution and channel software. This carries the group’s pricing decisions to what guests see on your own website and on online travel agencies (OTAs) such as Booking.com and Expedia. A well-coordinated decision only pays off if it reaches the booking engine and every channel in the same form.
None of these layers can stand in for another. A BI dashboard without a shared routine produces a report that changes nothing. A routine without shared data produces a meeting built on five different sets of numbers. Groups that take RevOps seriously build all of them on purpose, rather than letting the reporting layer be whichever spreadsheet survived the longest.
Signs a Group Has Outgrown Ad Hoc Reporting
A few patterns tend to show up before a group decides it needs a RevOps layer.
Pricing during shared demand events, such as a regional conference, a city-wide holiday or a big sporting fixture, comes out inconsistent across properties, as in Vienna, and nobody chose that on purpose.
A portfolio-wide snapshot of occupancy or RevPAR takes half a day of stitching together exports from each hotel’s PMS or RMS, because there is no dashboard that is already up to date.
Revenue managers at different hotels don’t know what their colleagues are doing this week, and there is no fixed point where plans get compared before rates go live.
Nobody clearly owns the final pricing call during a group-wide event. Every property manager trusts their own number, but nobody checks whether the numbers make sense side by side.
New hotels join the group and, months later, still don’t report into the dashboard the rest of the portfolio uses, because nobody owns bringing them in.
Any one of these may be tolerable on its own. Several together usually mean the group is still running revenue management as five (or fifty) separate small businesses instead of one portfolio.
To check whether coordinated pricing is improving results, track it against GOPPAR and RevPAR at group level as well as hotel by hotel.
What Resaco Recommends
We don’t sell or implement RMS, BI or reporting software. Our advice is about order. Before you shop for a “RevOps platform”, work out which layer is missing. A group that jumps straight to a new RMS may find that the real gap was a shared view and a decision routine above property level. Often a reporting layer that pulls existing RMS output into one dashboard, plus a short weekly check-in before rates go live, closes much of the Vienna-style gap without changing RMS vendor.
Our own work sits next to that coordination problem. We help hotel groups bring direct-booking performance into one report across all their properties, so it sits alongside the RMS and distribution reporting they already have. That matters because the guests who book on your own website are the ones you can welcome properly before arrival and invite back, and they are worth more over time than guests who arrive through an OTA. A group that sees its pricing and its direct bookings together can act on both in the same meeting.
For a property-by-property view of your group’s direct channel, book a free analysis.
Frequently Asked Questions
Is RevOps Software a Separate Product From an RMS?
Usually, yes. No single tool covers the whole job today, although some RMS vendors now add portfolio views. An RMS sets prices for each property. The RevOps layer is typically a BI or reporting tool connected to each hotel’s data, plus a defined routine, sitting on top of whichever RMS the group already runs.
Do All Hotel Groups Need a Dedicated RevOps Layer?
Property count matters less than how often your hotels compete for the same demand. A five-property group clustered in one city or region, all drawing on the same guests during shared events, tends to need coordination sooner than a group whose hotels sit in separate markets that rarely peak at the same time.
Can a Group Build a RevOps Reporting Layer With Tools It Already Owns?
Often partly, yes. A spreadsheet dashboard or an existing BI licence can get a group most of the way to a shared view before any new software purchase makes sense. The harder part is usually the routine: getting revenue managers to use a shared review rhythm.
Does a RevOps Layer Replace Property-Level Revenue Managers?
No. It changes what they are accountable to. Local judgement about each hotel’s demand still matters. The RevOps layer keeps five (or more) sets of that judgement from working against each other in the weeks when it matters most.
Related Reading
- Revenue Management Software: What It Is and How Hotels Use It
- Hotel Profitability Metrics: GOPPAR and RevPAR
- Direct Bookers vs. OTA Guests: The Lifetime Value Analysis
- Best Revenue Management Software for Hotels in 2026
- Revenue Management Platform: How It Fits Your Hotel Tech Stack
- The Hotel Revenue Manager Role: What the Job Involves
- Demand Forecasting for Hotels: Methods and Data Sources