Opportunity Isn't Attribution: Why a Revenue Estimate Isn't a Forecast

The slide shows a figure of CHF 1.13M to 1.25M.

Someone around the table leans back and asks, “Does that mean we’ll add this much revenue next year?”

There’s a pause. It is an understandable conclusion to draw from the number, but it is not what the number tells us.

That moment captures the point of this article. A revenue estimate based on guest feedback can be useful, but it measures potential opportunity - not a forecast, and not proof of what caused a result. Understanding the difference between hotel revenue opportunity and a forecast matters.

What does a revenue opportunity figure really tell you?

It estimates the revenue that may be available if gaps in guest sentiment are addressed. It does not predict what the hotel will actually earn.

The process is straightforward in principle. We compare recurring complaint themes with a healthy benchmark, then account for how often guests mention each theme. Those weighted gaps are combined into a hotel-level score, translated into a revenue range using published hospitality research, and divided across four broad pillars.

For the full methodology, see How the Hotel Revenue Opportunity Score (ROS) Works [link to add]. From Sentiment Score to P&L: How a Review Theme Becomes a Revenue Figure explains the translation step by step. From Sentiment Score to P&L: How a Review Theme Becomes a Revenue Figure

Each step helps describe a gap. None guarantees a financial outcome.

An opportunity estimate describes what may be available. A forecast describes what is expected to happen. They are not interchangeable.

Why should the total be treated as a ceiling rather than a forecast?

Because the full figure assumes every gap closes at the same time. In practice, hotels do not improve every area at once.

Consider our reference property: an anonymized 156-room hotel in the Lake Geneva region. Its estimated annual revenue opportunity is CHF 1.13M to 1.25M. The underlying reviews are real; the operating inputs, including room count, rate and occupancy, are illustrative.

Collecting the full amount would mean bringing every underperforming theme up to the benchmark and keeping it there. Maintenance, bathrooms, noise, housekeeping, service recovery and perceived value would all need to improve together. That is a ceiling scenario: it illustrates the scale of the potential, not how much revenue the hotel will capture.

There are two further points worth keeping in mind.

First, the research used to translate sentiment into revenue reflects average relationships across many hotels, and mostly modest changes. Applying those relationships to a scenario in which every gap closes pushes beyond the conditions they were designed to describe.

Second, the range is a way to communicate uncertainty, not a claim of statistical precision. We show a band of about 5% around the midpoint to avoid suggesting that one exact number is certain. It is not a confidence interval, and we do not present it as one.

The sensible way to use CHF 1.13M to 1.25M is as an upper-bound scenario against which to discuss priorities—not as a figure to insert into next year’s budget. This complements Why We Won’t Put a Price on a Fix From Review Data [link to add]: reviews cannot tell you what a fix will cost, and an estimated revenue opportunity cannot be promised as an outcome.

Why not add up the individual pillars and treat each figure as certain?

Because guest feedback often describes several connected issues at once.

The pillars divide one hotel-level estimate, so the overall total is not inflated by adding them. That part of the calculation is clear.

The uncertainty lies in how the themes relate to one another. Guests rarely experience or describe issues in isolation. A poor value-for-money rating may reflect a tired room; a bathroom complaint may also be about room quality or housekeeping. Several themes can point back to the same stay and the same underlying problem.

It is better to be transparent about that overlap. The pillar split helps show where the opportunity is concentrated, but it does not mean each portion can be captured independently - or that fixing one issue will leave related issues unaffected.

That is also why we do not assign a revenue figure to every individual theme. We rank themes by score lift and priority, where the comparisons are more defensible. A dollar amount for each theme would imply a level of precision that overlapping feedback cannot support. See Renovate, Retrain, or Reprice? How to Decide What to Fix First [link to add] for more on prioritization.

If revenue changes after a fix, does that mean the fix caused it?

Not on its own. This is where measuring an opportunity and attributing a result become two different tasks.

Imagine a hotel puts its action plan into practice and revenue per available room increases over the following two quarters. It would be easy to credit the plan, but other factors may have played a part. Market rates change, seasons turn, competitors may close for renovations or open new properties, and the amount of supply across the city can shift. Any of these can affect performance, whether or not housekeeping or another department has improved.

The same caution applies to the targets in the action plan. Each theme has a 90-day checkpoint set using one consistent rule: take the distance between today’s result and the benchmark, move halfway toward that benchmark, and round to a whole point. The rule is fixed rather than adjusted to make a target look more encouraging.

For the reference property, Housekeeping & Cleanliness is at 42% today, with a 90-day checkpoint of 64%. Front Desk & Staff is at 82%, with a checkpoint of 84%. These checkpoints provide a consistent way to review progress; they are not promises about future results.

Reaching a checkpoint still does not identify which initiative made the difference. Several actions may affect the same theme. Meeting the target suggests that progress moved in the intended direction, but it does not establish which action deserves the credit. The action-plan structure is explained in From Ranking to Roadmap: How a Hotel Guest-Experience Action Plan Gets Built.

A checkpoint is not a guarantee, and a change in results does not by itself prove what caused it.

Why should measuring results be treated as a separate step?

Because estimating, planning and measuring are designed to answer different questions.

Estimating asks: how much opportunity may be available, and where is it concentrated?

Planning asks: what should happen first, who is responsible, and which budget will fund the work?

Measuring asks: did the change last, and what actually moved?

Each stage needs its own evidence. Public review data can support the estimate and help shape the plan. To measure what happened, the hotel needs a baseline recorded before work begins and a follow-up check afterward.

A fair review of progress can look at whether complaints about a particular theme appear less often and whether guest sentiment has improved compared with the baseline. Financial outcomes - such as operating costs or the hotel’s own revenue figures - must be assessed using the property’s internal data. That requires work with the hotel, not public reviews alone.

Measuring outcomes is the next layer we are developing. Keeping it separate is intentional: it prevents an estimate from being presented as evidence of results that have not yet been measured.

How should you use the number in practice?

Use it to support the decisions it can inform, without asking it to do more than that.

A guest-feedback revenue estimate can help you:

• identify where the largest gaps appear across the hotel.
• compare pillars and ground prioritization discussions in evidence.
• understand the scale of the potential so effort and budget can be discussed in proportion.
• give owners and general managers a shared starting point for the conversation.

It cannot:

• promise how much revenue the hotel will earn next year.
• prove which improvement produced a particular result.
• justify a budget decision on its own.
• replace the hotel’s own financial information.

Used carefully, the estimate keeps the conversation focused and honest. Treated as a forecast, it can become a number repeated in board papers long after the assumptions behind it have been forgotten.

Before your next budget meeting

When a guest-feedback revenue figure comes up, pause and ask four practical questions:

1. Is the figure clearly described as a ceiling scenario, or is someone treating it as a forecast?
2. Which themes overlap? Could we be mentally counting the same guest experience more than once?
3. What baseline will we use to assess the results?
4. Who will review the outcome, and when will that review happen?

If the last two questions have no clear answers, the estimate is not yet enough to support a decision on its own.

The bottom line

Opportunity shows you what may be worth pursuing. Measurement helps you understand whether you achieved it.

A useful estimate helps put the right problems in the right order. It should not be treated as a promise of future performance - or as proof that a particular action delivered the result.