Koinometry turns heterogeneous hotel data into a shared semantic layer – making every property comparable without making them the same.
Request early accessEvery group runs different systems, different definitions, different logic. RevPAR means one thing in Opera and something subtly different in Cloudbeds. Occupancy at a city hotel and at a ski resort are not the same measurement – they share a name, not a definition.
The problem is not volume, and it is not quality. The data was never built to be compared across properties, because no common framework existed to make comparison possible.
Koinometry is that framework. A canonical schema and semantic layer that encodes what each metric means – its cohort, its regime, its conditions of validity – before comparison begins, not after it has already gone wrong.
What it refuses to measure is part of the specification. Two properties are declared comparable only when the framework can state the terms under which that comparison holds. Where it cannot, it says so.
USALI-aligned definitions that hold across systems. Not labels – encoded meaning that survives the journey from PMS to dashboard. RevPAR is the same RevPAR everywhere, or it is not reported.
Hotel data made queryable by language models without invented definitions. The semantic layer carries the meaning with the metric, so a query returns a figure and the conditions under which that figure is valid.
Cloudbeds, Mews, Opera, SiteMinder, D-EDGE. Each adapter translates its source system's logic into the koinometric standard at ingestion – before comparison begins, not after it has already gone wrong.
Compare unlike hotels on consistent terms. The comparison's scope – its cohort, regime, and exclusions – is stated explicitly alongside the result.
A single definition for every hospitality metric, USALI-aligned and system-agnostic. RevPAR means the same thing in every system that connects to Koinometry.
Metrics carry their meaning – cohort, regime, conditions of validity – not just their value. The data speaks for itself without a human intermediary to explain it.
Query hotel data in plain language without hallucinated definitions. The semantic layer makes the metrics machine-readable on their own terms, not the model's assumptions.
Ingest from Cloudbeds, Mews, Opera, SiteMinder, D-EDGE into the canonical standard at source. Translation happens at ingestion, not at query time.
Every comparison states what it includes, what it excludes, and why. If two properties cannot be compared on consistent terms, Koinometry says so rather than returning a misleading figure.
Twenty years building and running commercial data operations across Marriott, Expedia, Valentín Hotel Group, and Selina Hospitality. Director of Market Strategy, Senior Director of Lodging, CMO/CRO/CSO. The problem was lived across four continents, not observed from the outside.
Returns to Granada. Studio Oriente founded. First hotel data builds begin. The ceiling appears immediately: no two properties report the same metric the same way, and no existing tool addresses the underlying schema problem.
Rate intelligence system built for Compagnie des Alpes / MMV across 22 Alpine ski resort properties. Hotel BI platform prototyped at boutique scale. Both hit the same architectural ceiling: without a canonical schema, cross-property comparison requires bespoke engineering at every step.
The koinometric model is specified. Canonical schema, semantic layer, adapter architecture. USALI alignment confirmed. The standard is written before the product is built – the discipline precedes the software.
koinometry.com acquired. The name is coined: from koinós and -metry, a discipline that did not exist before it was needed. The vocabulary – koinometric model, koinometric layer, koinometric comparison – begins to form.
Accepting a small number of reference partners. Hotel groups who need comparable data across a heterogeneous portfolio. The standard is forming – early partners shape it.
The koiné was the shared Greek of the Hellenistic world – a common language that did not erase local dialects but made them legible to each other across the Mediterranean. Different cities kept their own ways of speaking. The koiné made them commensurable.
Koinometry borrows that logic and applies it to hotel data. Different properties keep their own systems, their own definitions, their own operational character. The koinometric standard makes them commensurable – comparable on consistent terms, without pretending they are the same.
The name is a coinage. No discipline called koinometry existed before the problem demanded one. That is the point: the standard had to be built because the field had not built it.
Koinometry is in active development with a small number of reference partners. If you run a hotel group and need comparable data across a heterogeneous portfolio, we would like to talk.
Request access