Study 01 · Finished, adversarially verified, ready to read
259,647 reviews · 117 hotels · 8 countries · 4 platforms · 25 to 26 languages
The kind of finding a due-diligence memo is usually written without: which guests are already gone, which tier and price posture concentrates the loss, and what early recovery is worth in points of return intent. Eight chapters, each closing in a decision, not a description.
86%
of 81 qualifying hotels show a 40-point swing in who comes back, between guests who called the stay overpriced and guests who called it worth it, a split most acquisition screens never run
16.2%
Luxury hotels lose guests at four times the Midscale rate, at the identical 8-out-of-10 score, the gap a capex reposition case has to clear
43pp
more guests recommend the place when recovery happens before they complain rather than after, comparing like-for-like problems, and it's used in under 4% of the cases that call for it
Sample details & methodology
DD Gap: 81 of 117 cohort hotels clearing n≥39 in both price-verdict cells, mean gap 53.8pp (95% CI 51.3–56.4), 86% of qualifying hotels clear the 40pp threshold. Tier churn: rating-8 reviews with churn signal populated, n=24,005 of 47,666 (50% coverage), Wilson 95% CI 14.5–18.0% (Luxury) / 3.6–4.4% (Midscale). Early recovery: matched-severity medium friction events, n=5,373 of 67,709, Newcombe CI 40.8–45.1pp on the 43-point gap.
How the risk is sized
Churn and non-return figures above are read from what guests write, not from reservation data. They signal intent, never confirm a booking.
What this means for a buyer
The gap concentrates where the underwriting case is hardest to reverse: once capital is committed to a Luxury reposition, a won't-return rate four times the Midscale baseline is the kind of number that erodes the return case quietly, deal by deal, long after the bid is signed.
Has a won't-return screen run on the assets already in your portfolio, or only on the ones you're bidding on?
Study 02 · Published
500 hotels · 1,596,417 reviews · 4 platforms · national index
The kind of read a listing page can't give you: which hotel looks risky but isn't, which one looks safe but is quietly losing its own guests, and what a "resolved" ticket still costs when the guest had to fight for it. Every finding closes in a decision, not a description.
3x
An underrated hotel, one its own guests already rank higher than its blended score shows, flags real risk about three times more often than average. A hotel whose rating looks a little too good flags at close to zero: the opposite of the instinctive read.
+12.8pp
More guests turn against a hotel when they had to push, follow up, or argue for a fix, even though the problem gets fully resolved either way. The gap is bigger, not smaller, once a fix actually lands.
11%
is all a hotel's own star rating explains about whether its guests are loyal to the property itself or just to the destination around it, tested three separate ways, same answer each time.
First national release, 2026-07-10. Adversarially tested the same way as Study 01.
1.6M+ reviews
/
500 hotels, national index
/
4 platforms at once
/
Booking, Expedia, TripAdvisor, Google
Sample details & methodology
Flattered vs. underrated: underrated hotels (rank_gap ≥70 positions) flag RED 42.3% [Wilson 25.5–61.1], k=11/26, vs 14.8% [11.4–19.1] base rate, k=48/324; flattered hotels flag RED 0.0% [0.0–13.3], k=0/25. Effort scar: holding severity and resolution status fixed, high guest-effort runs +12.84pp [95% CI 10.75–14.93] more detractors than low-effort within fully-resolved cases; replicates on churn likelihood at +17.65pp. Property-Pull Index: the published rating explains just 11% of which kind of asset you're looking at (R²=0.112, Spearman ρ=0.319, Pearson r=0.334, n=493). 145,674 friction events detected nationally across 500 hotels and four platforms; 130,912 of those, 89.9% (Wilson 95% CI 89.7–90.0%), are coded never-addressed by the guest's own account. Read from what guests write, not an operations log: signal, not a resolution record. Confirmed platform- and scale-invariant to within 3pp on every cut tested. Corpus: 1,596,417 reviews extracted of 1,665,388 collected.
How the risk is sized
Read from what guests write, not from an operations log: signal, not a resolution record.
What this means for a buyer
The instinct is to worry about the hotel whose rating looks a little too good. This inverts it: the hotel that should worry you is the one its own guests already rank higher than the world does, and a complaint that shows as "resolved" in an ops log can still be quietly costing you the guest who had to fight for the fix.
The index exists now. Have you checked where the hotel you're deciding on sits in it?