Lighthouse Performance: How hotels turn data into a commercial operating layer

Italian version

Italian version

Pace Graph: spot patterns before they become problems

Most soft dates do not look urgent when they first appear. Pickup is a little behind last year. A shoulder weekend is building more slowly than expected. Transient demand has not materialized yet. At that stage, the question is usually not whether the date is soft. It is whether it is soft enough to require action now, or whether the market will correct naturally over the next few days.

That distinction becomes harder to spot across a large portfolio, especially when teams are still pulling reports from multiple systems before the morning revenue call even starts.

The Pace Graph in Lighthouse Performance compares current pickup against prior year or another reference period so teams can immediately see where pace is slipping and whether the gap is widening. Instead of rebuilding the picture manually, the trend is already visible in one view.

Channel and segment performance: stop investigating, start fixing

Once pace starts falling behind, the next problem is figuring out what actually changed.

Did direct slow down? Did wholesale pick up at lower rates? Is occupancy holding because OTA contribution increased? Across a large portfolio, answering those questions usually means pulling reports from multiple places and trying to reconcile the story before the commercial meeting moves on.

That process slows down when teams are working from different data cuts or trying to reconcile reporting across multiple systems. Revenue is looking at pace and ADR. Sales is looking at account production and group contribution. Before anyone agrees on the response, the team first has to agree on what actually changed.

Channel and segment performance brings those views together in one place: channel actuals, segment contribution, ADR and occupancy by segment, all against the same date range and pace period. Instead of rebuilding the analysis manually, teams can immediately see whether the issue is pricing, mix, channel dependency or something more localized to a specific segment.

"With the analysis we have, low ADR segments produced higher revenue compared to last year, with almost 20% ADR growth in our wholesale accounts," explains Dimitri Swandanu, E-commerce Manager at Potato Head. “Now I just share access. Other teams can deep dive themselves. In revenue meetings, everyone already knows the data and the actions needed." 

By the time the revenue call starts, the discussion is already focused on response: pricing adjustments, segment strategy, channel mix or whether the date needs intervention at all.

Account and company production: understand which accounts are actually driving performance

At some point in almost every revenue meeting, somebody asks the same question: which accounts are actually behind?

The segment view usually gets the discussion started, but not much further than that. Sometimes the issue is a broader segment softness. Sometimes it is two high-volume accounts that shifted production somewhere else, or that negotiated business is still filling rooms, but at rates that stop making sense once compression starts building.

That is usually where the spreadsheet work starts. Teams pull account production separately, compare pickup against negotiated rates and try to work out whether the business is still worth holding on peak nights.

Account and company production brings those views together in Lighthouse Performance: production by account, agency or source alongside ADR, pickup and contribution across different occupancy periods. Instead of rebuilding displacement analysis manually, teams can immediately see which accounts are behind pace, which are overproducing at low rates and which still justify the inventory they are consuming.

The conversation with sales becomes much more specific: not “corporate is behind,” but which accounts are underperforming, where the rate gaps sit and whether the business still fits the strategy for those dates.

Budget and forecast: keep the forecast aligned with the business

Forecast conversations usually become difficult once different teams are no longer working from the same version of the business.

Revenue may already be adjusting expectations for a soft period while finance is still reporting against last month’s projection and sales expects negotiated production to recover later in the quarter. The numbers themselves are not usually the problem. The problem is that updating the forecast across a large portfolio is still heavily manual in many organizations, so by the time revised assumptions circulate, the market has often shifted again.

That is where forecast versioning becomes important. Instead of carrying the same projection forward until the next review cycle, teams can continuously update assumptions as pace, segment mix and demand conditions change.

Budget and forecast in Lighthouse Performance keeps actuals, budget and forecast updates connected in the same workflow. Revenue teams can immediately see where performance is moving away from expectations and adjust forecasts before the variance becomes a month-end explanation exercise.

For Austin Dunn, General Manager at Holiday Inn Cleveland-Mayfield, it saves him time and makes it easy to access and interpret the data needed to make smarter decisions. "It reduces my forecasting prep time by 50%."

Having reliable models helps him plan labor and expenses with much more precision.

The forecast stays closer to the business the team is actually managing week to week, rather than becoming a static number that only gets corrected after the gap is already visible to ownership.

Smart Compset: benchmark against the competitors guests are actually comparing you against

Compsets tend to stay unchanged for years once they are built, even though the market around them keeps shifting. New supply enters, competitors reposition themselves and guest consideration patterns gradually change, but updating compsets across a portfolio is usually manual enough that the original structure simply carries forward.

Over time, revenue teams can end up benchmarking very accurately against a competitive picture that no longer fully reflects how travelers are actually shopping the market.

The problem usually surfaces gradually rather than all at once. A property starts losing share against competitors that are not even part of the official compset. Conversion softens even though pricing still looks competitive against the reported market. Revenue teams keep seeing the same properties appear in win-loss discussions despite never formally tracking them.

Smart Compset in Lighthouse Performance continuously analyzes booking and search behavior across Lighthouse’s global hotel network to identify which properties travelers are actively comparing during the shopping process. The network processes more than 143 TB of raw data daily, achieving 99.7% data completion across the last 30 days, which means the competitive picture it surfaces is built on a foundation that static, manually maintained compsets cannot match. Instead of relying entirely on a static list created during implementation, teams can see when competitive behavior starts shifting and where new properties are entering the consideration set.

That becomes especially important at portfolio level, where outdated compsets can distort RGI benchmarking, pricing decisions and market-share analysis across dozens of different markets at the same time.

Revenue teams still decide which competitors matter strategically. Smart Compset gives them an earlier warning when guest behavior starts pointing somewhere the traditional compset does not. That's important because once the competitive frame is wrong, pricing decisions, RGI interpretation and market-share conversations all start from the wrong baseline.

RevPak: keep the commercial organization working from the same structure

As portfolios grow, reporting complexity usually grows with them.

Different properties evolve differently over time – PMS configurations change, reporting structures get adapted locally, segmentation logic shifts, ownership groups ask for different views of the business. None of those decisions are necessarily wrong individually, but across a large portfolio they gradually make performance harder to compare, forecast and explain consistently.

That is part of why portfolio reporting often becomes so dependent on manual oversight. Revenue teams end up acting as translators between properties, systems and ownership expectations instead of working from a stable commercial structure shared across the organization.

RevPak in Lighthouse Performance standardizes reporting across the portfolio so performance, forecasts and commercial discussions stay anchored to the same framework even as operational setups evolve underneath them. Historical packets remain archived in the same structure as well, which makes it much easier to revisit prior assumptions, strategy decisions and ownership discussions without reconstructing the context manually every cycle.

Central Mapping helps maintain that consistency operationally by standardizing PMS rate-code and configuration changes into the existing reporting hierarchy before they create downstream reporting gaps.

Over time, the reporting process becomes less dependent on individual properties maintaining their own logic and more dependent on a consistent commercial framework across the portfolio.

From reporting workflow to commercial operating layer

None of these workflows really exists in isolation.

A soft shoulder weekend spotted in Pace Graph turns into a channel discussion, then an account-production conversation, then a forecast adjustment, then part of the ownership review at the end of the month. Most revenue teams are already doing all of that work today. The issue is how much of the process still depends on manually rebuilding context between systems, reports and meetings.

That is the shift Lighthouse Performance is designed to remove.

Over time, the workflows stop feeling like separate tasks and start functioning more like a connected commercial operating layer across the portfolio. Teams spend less time assembling the picture and more time responding to what the picture is actually telling them.

Revenue Agent pushes that model even further.

Instead of waiting for somebody to find the anomaly manually, Revenue Agent continuously monitors pace, pricing, market behavior and commercial performance in the background, scanning billions of market signals to surface the changes most likely to matter before the morning revenue review even begins. Its Smart Insights skill surfaces anomalies over the next 90 days, while Smart Summaries deliver the picture to your inbox before the morning call begins

That changes the starting point of the day quite significantly. The workflow no longer begins with pulling reports and trying to work out where attention is needed. The signal is already surfaced, prioritized and connected to the surrounding commercial context. The discussion starts closer to the decision itself.

And that is really the throughline connecting all six workflows. The value is not just faster reporting or fewer spreadsheets. It is that revenue leaders spend less of the day searching for context and more of it making decisions.

"Lighthouse is our most essential revenue management tool. It saves time, ensures accuracy, and serves as the foundation for all our strategy meetings." – Jenny Jung, Revenue Manager, Lotte Hotels and Resorts.

FAQs

How is Lighthouse Performance different from a traditional BI tool?

Traditional BI tools show internal performance data – what happened in your PMS. Lighthouse Performance combines that with external competitive benchmarking in the same workflow, so teams can immediately see whether a RevPAR shift reflects their own performance or a broader market move. Revenue Agent then layers on top to surface what needs attention before teams have to go looking for it.

How long does it take to get Lighthouse Performance up and running?

Most chains are live within 45 to 60 days, including PMS integration and team training. Central Mapping handles the ongoing work of standardizing new rate codes and configuration changes automatically, so the setup effort does not repeat every time the portfolio changes.

We already use a benchmarking tool. Do we still need Lighthouse Performance?

The question is whether your benchmarking and your internal BI are connected. If your team is still switching between tools to answer "did we drop or did the market drop," the workflows in this article are what close that gap. Lighthouse Performance unifies both views in one platform so the diagnosis happens in minutes rather than across a morning of tab-switching.

How does Smart Compset work and how often does it update?

Smart Compset continuously analyzes booking and search behavior across Lighthouse's global hotel network – processing more than 143 TB of raw data daily – to identify which properties travelers are actively comparing you against. It updates dynamically rather than on a fixed schedule, so competitive shifts surface as they happen rather than at the next manual review.

How does Lighthouse Performance support above-property and cluster revenue managers specifically?

The platform is built for portfolio-level oversight. RevPak standardizes reporting packets across properties so cluster managers are not rebuilding context for every review. Multi-property views let a single manager monitor performance across a cluster in one screen. And Revenue Agent's Smart Summaries deliver a daily performance narrative for every property straight to the inbox — so the morning check scales across a large portfolio without scaling the manual work that goes with it.