Verified, time-stamped room-level ground truth is the hotel data incumbents pay hundreds of millions for — and still cannot collect themselves

Asked (summary)

What hotel and travel data is most valuable and hardest for Expedia, Booking, Google and AI platforms to collect themselves? What do travel companies currently pay or license for hotel content, photos, reviews, mapping and performance data — named companies and price or deal benchmarks (e.g. CoStar/STR, Lighthouse, Amadeus, Hotelbeds, DerbySoft)? And how would verified, in-person, time-stamped, room-level hotel data plus the questions travelers ask compound into a defensible data moat those companies would want to license?

Evidence base: 140 source-linked records gathered to 2026-10-24 — 60 public commercial benchmarks (acquisitions, funding, product and API prices, coverage metrics), 35 transaction and funding records with named buyers, and 45 documented examples of what hotel data fields incumbents can and cannot see. Amounts keep their source currency and date; whole-business deal values are not like-for-like dataset license prices.

What the market pays for hotel data — and the flywheel that compounds past it

Left: strategic deal and funding benchmarks (log scale, source currency, deduplicated by deal) against public product starting prices — the gap between a $100/month rate feed and a $1.52B data-and-distribution acquisition is four orders of magnitude. Right: the collection flywheel in which traveler questions act as a demand oracle that schedules the next in-person audit. Hover any bar or step for detail.

Acquisition / IPO (whole business)Funding roundPublished product starting price (monthly / per 1k calls)

What the benchmarks say

CoStar agreed to buy STR for $450M in cash — a benchmarking dataset of 65,000+ hotels and nearly 9 million rooms in 180+ countries, built on daily operating data hotels volunteer, which no OTA can scrape. costar.com
Amadeus paid $1.52B for TravelClick (25,000+ customers, 176 countries); TUI sold Hotelbeds for just under €1.2B; HBX's 2025 IPO raised €725M on a 250,000-hotel network — buyers pay for data plus the pipes and relationships that keep it fresh. corporate.amadeus.com
Lighthouse raised $370M led by KKR at a reported $1B+ valuation on 70,000+ hospitality customers and data on 300,000+ hotels — yet its rate product starts at $100/month: the moat is the network and refresh cadence, not any single feed. finsmes.com
Public price anchors are tiny by comparison — GIATA Drive from $100/mo, Hotellistat from $300/mo, DerbySoft connectivity from $1,000/mo, Google Place Details with reviews cited at $25 per 1,000 requests — while enterprise STR, Amadeus, Hotelbeds and DerbySoft terms stay quote-based, which is itself a finding: scarce verified data is priced by negotiation, not list. monocrawl.com

Defensibility scorecard: what is worth collecting in person

Qualitative scoring (1–5 dots) of value to licensees × collection difficulty × refresh burden × rights defensibility, synthesized from the 45 field-level evidence records. Incumbent APIs expose names, rates, amenity flags and reviews; none return measured room geometry, time-of-day noise, in-room Wi-Fi, accessibility clearances or verified amenity operating status.

Data layer
Value
Hard to copy
Refresh burden
Rights defensibility
Who buys it

The schema the flywheel fills

Eight linked layers, joined at canonical hotel → building/tower → room category → sampled physical room, every observation carrying observed_at, valid_from/valid_to, evidence hash, confidence and rights scope.

1 · Entity and mapping

Canonical property ID; brand, owner, operator; address, lat/lon, entrance coordinates; tower/building, floor plan; room-category aliases by Expedia, Booking, Google and the hotel; supplier IDs and merge/split history.

2 · Room physical ground truth

Marketed category vs sampled physical room (number tokenized), floor, measured square footage, layout, bed type/count/measurements, occupancy, connecting-door truth, bathroom type, shower/tub, grab bars and clearances, outlets/USB, desk, HVAC, window openability, blackout, safe/laptop fit, view direction and obstructions, elevator distance and accessible route.

3 · Condition and experience

Cleanliness, odor/smoke, wear, mattress and linen condition, water pressure and temperature, light and sound levels by time of day, noise sources (corridor, street, club, elevator), in-room Wi-Fi SSID/speed/latency, cellular signal, housekeeping frequency, pest/maintenance observations, renovation state.

4 · Operational amenities

Breakfast contents, hours and crowding; pool/gym/spa status and hours; parking price, clearance, EV chargers; shuttle, lounge, kids/pet rules, beach/ski access, laundry, restaurant and room-service hours, accessibility equipment, construction, closures and outages.

5 · Media provenance

Hotel/building/room/category IDs, captured_at, GPS, compass direction, device and collector, original EXIF and hash, scene label, before/after renovation link, manipulation record, ownership and license scope, releases, expiration and takedown status.

6 · Commerce and performance

Room/rate-plan, observed_at, stay dates, price, taxes/fees/resort fee, inclusions, refund/cancel/payment terms, availability, parity, minimum stay, sellout; occupancy, ADR, RevPAR, forward demand, profitability where licensed; conversion, cancellation, refund and support-contact outcomes.

7 · Traveler questions

Raw question, normalized intent, segment and trip context, hotel/building/room target, asked_at, frequency, answer, evidence IDs, answered_at, confidence and freshness, contradiction/unresolved status, helpfulness, booking and post-stay validation.

8 · Universal provenance

Observation ID, collector and method, source class, observed_at, valid_from/valid_to, location accuracy, units, evidence hash/URL, confidence, QA reviewer, rights and permitted uses.

Why each buyer licenses it

Expedia and Booking — room matching and content completeness, conversion, post-booking expectation setting, fraud and content QA, fewer refunds and support contacts; Booking's own details API caps queries at 100 IDs and returns static, property-supplied content. developers.booking.com
Google — hotel and place entity resolution, factual panels, photo labeling, true map entrances and grounded local answers; its hotel price pipeline depends on partner-supplied structured data that must merely match the partner's own page. developers.google.com
AI travel agents — answer-level evidence with citations, contradiction handling and room/rate compatibility; an audit of twelve LLM assistants (61,459 calls) shows they choose hotels from thin reputation signals because verified ground truth is absent. arxiv.org
Hotel tech, investors and operators — longitudinal condition histories for benchmarking, renovation underwriting, comps and quality monitoring, the role STR's daily operating panel plays for revenue metrics. apers.app

All 95 benchmark and evidence records

Every pricing, deal and scale record behind the charts, labeled by kind so unlike units are not read as comparable. Click a header to sort. Major deals appear under several corroborating sources; read them as one deal each.

Provider ↕Kind ↕Amount / metric ↕ScopeSource

Method: 140 records from three result sets researched to 2026-10-24 — 60 public commercial benchmarks, 35 transaction/funding records, 45 field-level evidence examples — each linked to its source page. Chart deduplicates corroborating deal reports to one bar per transaction and keeps source currencies; deal values price whole businesses (technology, customers, distribution), not datasets alone, and many enterprise license terms are quote-based and unobservable. Scorecard dots are qualitative synthesis, not source numbers. Some third-party-reported prices (e.g. the Google Place Details benchmark) are as cited by the reporting site. Evidence excerpts trimmed for space.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.

Keenable SELECTAsk your own question
Made with Keenable SELECT