Managing revenue across a portfolio of hotels is one of the most demanding jobs in hospitality.
The theory is clean: align your pricing, standardize your decision-making, and let the strategy run. The reality? You're juggling multiple data sources, overstretched teams, shifting booking windows, and a set of properties that each have their own market dynamics, demand patterns, and quirks.
So, how do you build a single revenue strategy that actually holds without losing the local knowledge that makes each property perform?
In our recent webinar, we put that question to three Duetto experts — Erica, Director of Hospitality Solutions EMEA; Daniel, Director of Casino Solutions; and Nick, Director of Hospitality Solutions Americas — who between them have spent decades working inside hotels navigating exactly this challenge.
Here's what they had to say.
The role of the revenue manager has already changed. Has your strategy caught up?
The revenue manager of five years ago spent a significant chunk of their day pulling reports and correcting rates.
That role has shifted, and fast.
Today's revenue managers are being asked to think like profit managers: interpreting data, managing commercial funnels, and making strategy calls across multiple properties simultaneously.
Technology has changed with it. The best platforms now handle the data-gathering so teams can focus on what the data actually means. But not every organization has made that transition, and that gap is starting to show up in results.
As Nick puts it:
“Extreme demand volatility and shorter booking windows are making portfolio-level strategy harder to execute. At the same time, the industry is moving away from RevPAR as the primary success metric and toward total profitability — GOP and net revenue. That's a significant shift, and it creates real complexity when you're trying to apply it consistently across properties with different distribution mixes, labor models, and cost structures.”
The good news: the tools exist to manage it. The challenge is knowing which ones to trust and how to use them well.
Why centralization is harder than it looks.
Centralization sounds straightforward but in practice, it runs into several real-world barriers.
Data fragmentation. Each property generates its own data, integrates with its own systems, and often updates at different rates. If some of your hotels are pulling real-time feeds while others are running daily extracts, you're not actually looking at your portfolio — you're looking at a patchwork. Decisions made on incomplete or mismatched data are, at best, educated guesses.
Execution at scale. Even when you have the right data, acting on it is a different problem. How do you make a pricing change across 50 or 100 properties when you have a team of three? And how do you do it without either drowning in manual work or handing all control to automation you don't fully trust?
Team bandwidth and alignment. Revenue managers at portfolio level are being pulled in too many directions. They're in housekeeping meetings. They're reconciling reports. They're context-switching constantly. Strategic work — the kind that actually moves the needle — gets squeezed out. And when they're not working from a shared framework, GMs, sales teams, and finance are often speaking different commercial languages entirely.
Standardization isn't a one-size-fits-all trap.
A common fear with centralization is that it flattens everything. You standardize the strategy, lose the local nuance, and end up with a portfolio that looks consistent on a dashboard but performs inconsistently in reality.
That doesn't have to be the outcome but avoiding it requires building flexibility from the start.
A practical example: event-driven pricing.
- A 120-key city-center property might need to respond to an event of 10,000 attendees within a one-mile radius.
- A 600-key conference hotel in the same group might need 40,000 attendees across a 15-mile radius before it starts to see meaningful compression.
Same strategic logic, completely different parameters. The portfolio strategy has to accommodate both — and a good platform makes that kind of local configuration easy rather than time-consuming.
The same principle applies to booking windows:
- A boutique urban property might have a seven-day booking curve.
- A destination resort might be working 90 days out.
Automation settings, forecast horizons, and exception triggers all need to reflect those differences, not override them.
Centralization done well is flexibility within a framework, and the right platform should give you the tools to build it yourself — consistently, at scale, with the granularity each of your property needs.
Pricing by exception: what it means and why it matters.
One concept that keeps coming up in conversations with high-performing multi-property teams is pricing by exception.
The idea is simple: stop trying to manually review every rate across every date across every hotel. Use technology to handle the routine — low-demand dates, standard pricing adjustments, day-to-day rate management — and redirect your attention to the exceptions: the high-compression dates, the upcoming events, the segments that are over- or under-indexing.
But pricing by exception is also a broader philosophy.
It's a shift away from reactive yield management — correcting what went wrong yesterday — toward setting a strategic framework that runs proactively. If your data tells you one segment is consistently more profitable than another, you don't just adjust one hotel's rates. You set guidelines across the portfolio to shift business over time. The strategy runs; you manage the exceptions.
For this to work, you need a platform you trust enough to put on autopilot for routine decisions. If you can't do that — if every recommendation feels like it needs manual review before you'll act on it — you either don't have the right tool or it hasn't been configured to reflect your strategy.
Is your tech stack helping or holding you back?
Before buying anything new, audit what you already have.
Most hotel groups have tools they're paying for and not using. That's a symptom of an industry that's been bombarded with technology options while teams have stayed the same size.
But unused tools have a cost: financial, and in terms of the cognitive load they place on already-stretched teams.
The questions worth asking about every tool in your stack:
- Is it integrating in real time, or close to it? A platform where some hotels update every minute while others update once at 4am is not a unified picture of your portfolio.
- Is there a measurable return? Some tools — your PMS, for instance — are infrastructure. You need them. But revenue-related technology should be able to demonstrate what it's delivering.
- Does it connect to the rest of your stack, or is it another siloed data source?
Garbage in, garbage out. Clean, real-time, well-integrated data isn't a nice-to-have — it's the foundation everything else depends on.
How do you know your revenue process is working — before the results confirm it?
Results are a lagging indicator. They tell you what happened, but not what to do next.
There are more immediate signals worth paying attention to:
Are you making decisions quickly and confidently? At scale, speed matters. If your team is hesitating on rate changes, second-guessing recommendations, or waiting for a report before they act, something's slowing you down — and the market isn't waiting.
Do you trust your tools enough to let them run? A revenue management system that you don't trust on autopilot is a problem. Either the tool isn't flexible enough to reflect your strategy, or it hasn't been configured correctly.
Are you changing rates as often as you should? Most hotels could be making rate changes ten times more frequently than they currently do. The demand signals are there. The tools exist to act on them. The bottleneck is usually time, team capacity, and trust in the platform.
The Taylor Swift effect is real — not just for pop concerts, but for any event that moves your market before most teams are paying attention. By the time a 200-day-out date makes it onto your radar, someone else has already priced for it.
What good looks like and how to measure it.
Measuring success across a portfolio isn't as simple as aggregating RevPAR. Every investment group has different priorities. Every property sits at a different point in its maturity curve.
Some things worth tracking consistently:
- Top-line revenue changes across the portfolio — but always alongside margin, not instead of it. Driving revenue while eroding profitability isn’t a win.
- Property-level attribution toward portfolio performance — if one hotel is doing well, is it genuinely performing, or is it cannibalizing the hotel next door? You need to be able to tell the difference.
- Channel mix and distribution costs — are the bookings you're taking the most profitable ones available? Net revenue matters more than gross.
The right tool includes granular reporting at property level, portfolio-level visibility, and profit benchmarking against your competitive set, giving you the picture you need to answer these questions honestly.
One engine for the whole portfolio.
Everything we've described requires a system built to handle all of it together, and that's exactly what our Revenue and Profit Operating System (RP-OS) is designed to do.
For multi-property teams, that means pricing and forecasting across your entire portfolio from a single workspace. It means starting every morning with a clear view of what needs attention and what can run on autopilot, not an inbox full of reports to reconcile. It means AI-powered demand intelligence that flags high-opportunity dates before your pickup reports surface them, so your team is anticipating the market rather than reacting to it.
And it means going beyond revenue: seeing what your commercial decisions actually delivered in terms of GOPPAR, departmental margins, and profit benchmarked against your true competitive set.
Scale without the chaos.
Multi-property revenue management is hard. The complexity is real, and anyone who tells you the answer is simply to centralize everything and let the algorithms run probably hasn't managed a portfolio under pressure.
But the teams doing it well have the right engine behind them. One that runs a consistent strategy across the portfolio without sacrificing the local flexibility that makes each property competitive.