The Reason Your Hotel's Systems Don't Talk to Each Other

Some of your vendors actually make more money when your systems can't talk to each other.

It works two ways. Either a vendor charges per call once a real connection exists, so the more your systems talk, the more it costs. Or almost nobody is willing to build the bridge at all, so whoever finally does can charge whatever they want.

• The first case: a real API connection between a hotel's systems still gets billed per call, in both directions. A simple guest lookup can trigger several charges before it even finishes.
• The second case: some systems just aren't built to connect that deep. A guest asks how much credit they have left for dinner, and nobody can answer instantly, because going that deep was never worth it unless you paid extra.

Then there's the cost of fixing it yourself. One operator quoted a modern CRM at half a million dollars a year, only to find the middleware to feed it hotel data cost over 600,000 on its own, because almost nobody else does that work.

One operator I spoke with put it bluntly:

"As an industry, we suck at this."

A major procurement platform in the space relaunched a few years back as a shiny "cloud-based version." Same product, just a browser tab now.

None of this means giving up on connecting your systems. It means owning your data layer instead of renting someone else's.

We dug into this live on July 28. See the session.