The Hedonic Value Verdict · 259,647 reviews · 117 hotels · 8 countries

The guest already decided. The rating hasn't caught up.

16.3% of guests render an explicit price verdict in their review text. Among those guests, "overpriced" predicts non-return at a rate that no other signal in the dataset matches: not friction, not sentiment, not the published score.

57.0%
"Overpriced" verdict
churn risk (CI 56.1–57.8%)
n = 13,061 reviews
vs
2.7%
"Worth it" verdict
churn risk (CI 2.4–3.0%)
n = 13,745 reviews

Churn = unlikely_return + will_not_return, NLP-inferred from review text. Denominator: reviews with a price verdict (16.3% of all reviews). Newcombe difference: 54.3pp (CI 52.5–56.0pp). Replicates in 2025-only data: overpriced 55.8%, worth-it 2.0%.

Note: stronger NLP signals (explicit detractor language, low ratings) predict churn at higher rates; this finding ranks high on predictiveness among non-extreme signals, as it surfaces even when rating and sentiment appear neutral.

The concealment problem

The same 8/10 carries a 6.4x churn split.

Among guests rating exactly 8/10 with neutral sentiment: overpriced churn 17.3% vs worth-it 2.7%. Among all guests rating 8 or higher: 17.1% overpriced churn vs 2.6% for the rest. The score is identical. The verdict is not.

17.3%

Rating 8/10. Overpriced verdict. Neutral sentiment.

This guest gave a score that would look fine on any dashboard. The sentiment is neutral: no flag, no crisis. But 17.3% of guests in this exact combination signal non-return: a rate 6.4x higher than the guest one cell over in the same table.

denominator: reviews rated 8/10, neutral sentiment, with overpriced price verdict · cohort-117
2.7%

Rating 8/10. Worth-it verdict. Same neutral sentiment.

Same rating. Same sentiment. The worth-it guest churns at 2.7%. The rating gives no signal of the gap: the 17.3% and the 2.7% sit behind identical published scores on the same booking page.

denominator: reviews rated 8/10, neutral sentiment, with worth-it price verdict · cohort-117
17.1%

Guests rating 8+, overpriced verdict.

Among all guests rating 8 or higher (the population most investors and operators consider "satisfied"), the overpriced verdict still predicts 17.1% churn vs 2.6% for the non-overpriced population at the same score range.

denominator: reviews rated 8–10 with price verdict; among overpriced vs non-overpriced (residual price signal control) · cohort-117
5.8%

A Luxury overperformer. 5.8% overpriced rate among price-mentioners.

In the same cohort, Luxury underperformers reach 38 to 42%. The overpriced rate separates Luxury properties more cleanly than any friction metric in the dataset. (Anonymised: tier + country only, no hotel or location named.)

denominator: price-mentioning reviews per hotel, luxury segment; hotel-level comparison · private to named engagements
The mechanism

"Overpriced" means friction made the rate feel unjustified.

The natural fix is to lower the rate. The data disagrees. 95.1% of overpriced reviews carry an identified friction event. Worth-it reviews: 34.2%. The difference is not the ADR; it is what happened during the stay.

Friction event present in...
Overpriced
95.1%
Worth-it
34.2%

denominator: reviews with price verdict · friction event = identified friction_detail in the structured extraction. Persists at ratings 9–10: 84.8% overpriced vs 25.6% worth-it.

Among satisfied guests who churn over price
60.2%

cite ancillary charges, not the room rate.

Among guests who rated 8 or higher, signalled churn over price, and named specific items: 60.2% point to breakfast, parking, minibar, or other add-ons as the friction making the stay feel overpriced. The room rate is rarely the cited item.

denominator: guests rated 8+, price verdict = overpriced, named friction items, with churn signal · 259,647 reviews · 117 hotels

This matters for the decision shape. "Lower the rate" is a revenue action. "Remove the breakfast surcharge" or "fix the parking policy" is an operational action. The read names which specific ancillary is doing the damage, and the decision is different from cutting ADR.

What the read is for

The operator's platform tells them the score. We tell the person deciding the asset what it means.

STR covers the market. Reputation platforms cover the operator's rating. This finding lives in the third layer: the why under the rating, read from outside, for the seat deciding on the asset.

Asset manager
The overpriced rate among price-mentioning guests separates Luxury over and underperformers more cleanly than any friction metric. A property with 38% overpriced rate is a different asset to underwrite than one at 5.8%, even at an identical score. The read names the specific friction making the rate feel unjustified: that's the CapEx case.
Operator / GM
Among satisfied guests (8+) who churn over price and name items, 60.2% cite ancillaries (breakfast, parking, minibar). The room rate is rarely the lever. The read names the specific line item, with Wilson CIs on the sample. Monday morning: the lever is a policy decision, not a pricing one.
DD analyst
The overpriced rate is readable from public reviews alone, no operator cooperation. It is a pre-acquisition signal for whether the current ADR is earning its position or running ahead of the guest experience. The read is available in 14 days on any named target.

The finding is public. The named version, on a specific asset, with its specific ancillary friction identified, is a paid engagement. The next one is yours.

Where this finding stops

What the value verdict can and cannot do.

Volunteered, before you ask.

Source
Price_overall is NLP-inferred from review text, not a survey response. The denominator is guests who wrote about price (16.3% of all reviews). Null means price was not mentioned, not that the guest had no view.
Churn signal
Churn is inferred from language (return intent, discouragement, "won't be back"). It signals intent; it does not confirm a booking was not made.
Cohort
117 hotels · 259,647 reviews · 8 countries · luxury to midscale · European-heavy. Within-cohort finding; market extrapolation is not warranted. The effect is robust across all 4 platforms and all 4 tiers tested.
Causality
The read identifies the friction co-occurring with the overpriced verdict. It does not prove the friction caused the verdict in every case. The named engagement refines which specific friction is the likely driver for a given property.

Everything above re-runs from the same public base. We'll show you the working before you ever pay for a number.

The named version, on your asset

The score is public. The read is not.

This page shows the pattern across the cohort. The named engagement shows you the overpriced rate for a specific property, which specific ancillaries are driving it, and the Wilson-CI-bounded decision case for changing the policy or the capex. One hotel you name, delivered in 14 days.

You just read a finding that no reputation platform will send you. Your pipeline is full of the same scores with the same verdict hiding inside.

STR reads the market. Reputation platforms read the operator's rating. What this page demonstrates is the third layer: the why under the rating, read from outside, for the seat deciding the asset.

You pay only if it surfaces a finding worth acting on; you set the threshold; if it doesn't clear it, there's no invoice. One hotel you name, delivered in 14 days.

Know someone underwriting a hotel on its rating? Forward this page. The number that breaks them out of it is the first one up.

Book a 20-min read intro