But hotel relationships end the way marriages do — a sale, a succession, a slow drift in performance, or simply someone new at a conference. The interesting question was never whether yours will end. It's what you'll be holding when it does.
The inventory
Run the thought experiment. Your operator leaves next month — amicably, even. What stays?
The building, obviously. The wallpaper. The debt, naturally.
Now the other list. The Booking.com account, with its nine years of reviews and ranking history — registered to the operator. The PMS and everything it knows about your guests — their license, their configuration. The channel manager, the payment terminals, the door-lock software. The website, the domain, the Google listing, the Instagram, the guest database and every email address in it. The linen contract, the energy deal, the accountant — all contracted to a company that is currently packing its boxes.
The walls are yours. The operating system just left the building.
No villain required — the standard structure simply stacks contracts vertically: you pay the operator, the operator pays everyone else, and every relationship built that way is one more strand tying the asset to them instead of to you. Ten years in, leaving costs so much that performance almost stops mattering. Which is a strange thing to pay a management fee for.
The divorce test
Five questions X-ray any operator — us included. Ask them while everyone still likes each other:
- Who do the suppliers contract with — my entity or yours? This one predicts the other four.
- Do you earn anything on the cost side? "The fee is our entire compensation" is the only clean answer.
- If we part ways, what transfers — and at what cost? Ask for the list: accounts, licenses, logins, data.
- Is your incentive tied to revenue or to profit? Revenue rewards volume. GOP means they earn when you do.
- Is pre-opening priced separately from operations? A project with an end date — or an engagement designed never to finish?
An aligned operator answers all five without checking with legal.
Declaring our interest
We built Weave so the divorce test is boring: everything — contracts, accounts, configurations — belongs to the owner's entity from day one, and the asset moves intact if it ever needs to. How it works is on the model page; how it runs is in the portfolio.
Marriages should last. Contracts should assume they might not.
Talk to us — we'll happily take the test.