Resources
Everything we have published, in one place.
The long-form guides, the vendor comparisons, the glossary and the notes from the team.
From the house
June 2026
The hotel tech stack question that Reddit cannot quite answer
Every forum thread about which PMS to switch to is really about the same underlying problem. And it is not the PMS.
June 2026
What hotel operators say about OTA dependency (and the part they do not mention)
The OTA commission frustration is real. But the structural problem behind it is about guest identity, not booking engines.
June 2026
What hotel operators ask about guest data software (and the question behind the question)
Hotel operators in hospitality forums keep asking which CRM to use. The answer they are looking for is not in the CRM.
Insights
Guest data
Why hotel loyalty programmes miss repeat guests
Loyalty programmes fail at recognition, not rewards. Enrolment is a separate event from staying, and the stay is stored as unlinked copies.
Guest data
What a hotel master profile is (and why the PMS one is not it)
A guest can book a room, eat at the restaurant and visit the spa yet appear as three different people across hotel systems. A hotel master profile brings those fragments together as one durable guest record.
Guest data
What a hotel semantic layer is, and what it is not
A hotel semantic layer gives guests, reservations, stays and folios consistent meanings across systems and agents. It does not determine which records belong to the same person. That is guest identity resolution.
Guest data
Guest identity resolution for hotel groups
The same guest can exist as several unconnected records across a group's properties and systems. This guide explains why it happens, what identity resolution actually does, and why the resolved record is the layer your agents run on.
Guest data
Hotel CDP vs guest identity layer
A CDP and an identity layer look the same on a slide. They differ in what they are for, who ends up controlling the record, and what survives when you change vendors. We build one of them, so the case for the other is put carefully.
Glossary
Definition
Guest identity resolution
The process of matching and merging fragmented guest records across hotel systems into one authoritative profile.
Definition
Hotel master profile
A guest can book a room, eat at the restaurant and visit the spa yet appear as three different people. A hotel master profile brings those fragments together as one durable guest record.
Definition
Hotel semantic layer
A shared business representation of guests, reservations, stays and folios. It does not determine which records belong to the same person. That is guest identity resolution.
Use cases
IT / CTO
One trusted guest identity for the stack.
Stop wiring guest records system to system. One Master Profile sits above the stack, served over REST and MCP, with access you scope per connection.
Operations Director
Recognition at every outlet, from one record.
The desk, the bar and the spa should not have to vote on who the guest is. One resolved record, read beside the systems those teams already use.
General Manager
The house remembers the same guest.
A returning guest should not be a stranger at check-in. The record sits above the property system, so the house can recognise the same person.
Commercial Director
Commercial teams acting on one profile.
Loyalty and CRM should read the resolved guest, not own a second copy. Recognition is the layer’s job; the programme keeps the points engine.
PMS
Guest recognition above the property system.
The PMS guest card is not one person across the house. Recognition lives above the property system, so a PMS switch does not rebuild the guest.
AI agents
Agents that read the same Master Profile.
An agent pointed at one system inherits that system’s fragments. Point every agent at the Master Profile over MCP or REST instead.