Manifesto
Your guest record should outlive your software
Who holds the guest record today, what that costs you, and what we are building instead.
A returning guest walks into your hotel. Eighth stay. She booked through an OTA, so the booking engine greets her as a stranger. The PMS holds three versions of her under two spellings. The spa knows her treatment history but not her room preference. The bar knows her tab but not her name.
One company holds the complete picture: how often she travels, what she pays, what she books next. It is not you. It is the channel that sold you her booking, then sold her your competitor.
The register belonged to the house.
Hospitality solved this problem two centuries before software existed. The register at the front desk recorded who stayed, what they preferred, how they paid. It belonged to the house, full stop.
Software did not kill the register. It shattered it. Every system bought to serve the guest (PMS, POS, booking engine, spa, F&B) took a shard of her identity and kept it. Distribution took the rest: every channel booking enriches the intermediary's profile of your guest and starves yours. Twenty years of technology bought in the guest's name has made her unrecognisable to the people serving her.
The industry's answer has been CRMs and CDPs bolted on top: suite-locked, channel-shaped, priced behind demo calls. Every one of them will tell you the data is yours. The record is still formatted for someone else's roadmap and still hostage to someone else's exit terms, and being told you own it changes neither.
Software did not kill the register. It shattered it.
Why this matters now.
AI runs on context. The agents now arriving in hospitality (upselling, personalising, negotiating rates) will act on whatever guest record they can reach. If that record is channel-owned, AI does not loosen the dependency. It compounds it, permanently.
The next decade of hospitality software will be built on guest context. The only open question is what that layer is attached to.
What we believe.
Guest identity is infrastructure.
Not a module in a suite, not a marketing feature. A layer beneath every system the hotel runs, and part of none of them.
The house's register, not the channel's.
Shaped by no OTA, no PMS vendor and no suite, including ours: we sell none of the applications that read it. Held in trust for the guest, governed by the hotel.
The record outlives every vendor.
Switch PMS, change POS, rebuild your stack; the register survives. Continuity of identity is the point.
Straight answers, first time.
A real number on the first call, not after three. A straight answer on what we have built and what we have not. If you have to sit through a sales process to learn the price, the price is the process.
What we are building.
Casa Layer is the guest data layer that belongs to none of your suppliers. It resolves one Master Profile for every guest across the systems you already run, then serves that record through an open REST API and an MCP server, so your team, your CRM and any agent you choose all work from the same ground truth. We build that record and we hold it, and we will not dress that up as giving it back to you. What makes it different from the suite version is that we sell none of the applications it feeds, so there is nothing here to keep you inside: replace your CRM, your PMS or your upsell tool and the resolved record is untouched, because it never lived in any of them. It arrives working with your stack, it never asks you to move your data into it, and what it can do inside each of your systems is yours to set and yours to revoke.
Help us build the register back.
We are signing a first group of early access partners across Europe. Book a demo and we will be direct about whether it is a good fit, and about what is not built yet.