The Guest Journey is a Technology Stack
What most people experience as a trip is, in reality, the coordinated output of dozens of independent technology systems that were mostly built separately, by different companies, for different purposes, and asked to work together after the fact.
Pick a trip. Any trip. A long weekend, a conference, a family vacation. It doesn’t matter where you’re going.
You open an app or a browser and search for flights. That query passes through a global distribution system — Sabre, Amadeus, one of a handful of platforms that aggregate inventory from hundreds of airlines simultaneously — applying revenue management algorithms that can change a fare between the moment you see it and the moment you click. You book. A payment is processed, a confirmation is generated, a record is created in at least three separate systems before you’ve had time to close the tab.
That’s before you’ve packed a bag.
What I want to do here is follow one person through one trip and watch what’s actually happening underneath. Article 1 made the case that hospitality is a prism — that looking closely at the industry reveals the intersection of travel, payments, logistics, real estate, and a dozen other sectors at once. The guest journey is where all of those intersecting systems have to work together, in sequence, in real time, for a person who has no interest in any of them. They just want the trip to go well.
You book a hotel. The confirmation that lands in your inbox was generated by a property management system — the operational core of almost every hotel on earth, the platform that tracks room availability, manages housekeeping queues, handles check-in and check-out, and posts charges to folios. That system is almost certainly talking to a central reservation system managing inventory across the brand, and to a channel manager keeping availability synchronized across every booking platform simultaneously. Miss a sync and the hotel oversells a room. It happens more often than guests realize, and the recovery is entirely human.
If the hotel is part of a loyalty program, your booking has also touched a separate identity and rewards infrastructure. Your account is pulled, your tier recognized, your preferences noted. A flag may go to the front desk: this guest has stayed fourteen times this year, or celebrated an anniversary on their last visit, or always requests a room away from the elevator. That data lives somewhere. Someone built the system that captures it, stores it, and surfaces it at the right moment to a front desk agent who has about thirty seconds to make it feel effortless.
None of this is visible to you. You just see a confirmation email.
You land, take a rideshare to the hotel — another stack entirely, managed by a different company under different infrastructure — and check in. Increasingly that happens on your phone before you arrive, through a mobile platform that communicates with the property management system, issues a digital key, and routes you to your room without a stop at the front desk. The credential on your phone is talking to a lock through an access management layer that has to be secure enough to protect guests and flexible enough to be issued and revoked remotely, at scale, across hundreds of rooms. It works, almost always. The “almost” is doing a lot of work in that sentence.
You order room service. The order moves through a point-of-sale system into a kitchen display system, through an inventory layer tracking what’s in the kitchen and what needs to be ordered tomorrow. Delivery is routed through a workforce management platform that knows who’s on shift and what they’re currently carrying. The charge posts to your folio automatically — or it should. When it doesn’t, someone at the front desk fixes it manually. That single sentence contains an entire category of integration problems the industry has been working on for decades, problems that persist not because no one has tried to solve them but because the underlying systems were never designed to speak the same language.
You go out to dinner at a restaurant inside the resort. The table you reserved was managed through a separate reservations platform. Your order runs through a point-of-sale system — Oracle MICROS or Agilysys are the names you’d most likely find at a property this size — though not necessarily the same system running the room service operation upstairs. Large resort properties accumulate their technology over time, through acquisitions, franchise agreements, and build-outs that happened years apart. Two restaurants on the same property, owned by the same company, serving guests with the same loyalty card, may be running systems that have never been formally introduced to each other. Tip processing, tax logic, foreign card conversion, loyalty point redemption — all of it resolves somewhere, somehow, usually correctly, across infrastructure that was never designed as a whole.
You come back and the room has been cleaned. Housekeeping ran on a dispatch system tracking room status in real time — occupied, vacant, dirty, clean, inspected — routing attendants based on priority, guest arrival times, and staff availability. The thermostat adjusted when you left and reset when the door opened on your return. A building management system, sitting beneath the hospitality layer, talking to sensors, talking to HVAC, talking to a platform tracking energy consumption across the property.
And woven through all of it: data. Every interaction generates a signal. Your booking source, your check-in time, your dining choices, your in-room requests, your departure, your satisfaction score if you fill out the survey. The data exists across the property management system, the point-of-sale, the loyalty platform, the building systems — each holding a piece of the picture, most of it siloed, poorly structured, and radically underused. The personalization that loyalty programs promise guests — the feeling that the property knows you, anticipates you, remembers you — depends on that data flowing cleanly across systems that were built by different vendors in different decades with no shared architecture. Sometimes it does. Often the gap between what the data could enable and what it actually produces is wider than anyone publicly acknowledges.
That gap isn’t an oversight. It’s a structural condition.
The hospitality technology stack was not designed. It accumulated. Each layer was added to address a specific operational need, procured from a different vendor, integrated with whatever already existed through interfaces that range from elegant to improvised. What resulted is an infrastructure of genuine sophistication — one that coordinates the physical and digital experience of millions of guests every day — built largely through patchwork.
That patchwork is also the industry’s central vulnerability — not only because it fails at the edges, but because accumulated systems with unclear ownership and high switching costs are extraordinarily difficult to improve systematically. Every vendor integration is a negotiation. Every upgrade risks breaking something adjacent. In most industries, a software failure is a software failure. In hospitality, failure is immediate, human, and visible. A housekeeping dispatch error means a guest standing at the door of a room that isn’t ready. A loyalty flag that doesn’t surface means a front desk agent with no idea they’re talking to someone who has stayed a hundred nights. A folio discrepancy at checkout means a conversation that the guest will remember long after they’ve forgotten everything else about the trip. The technology was designed to disappear — to recede into the background and leave only the experience. When it fails, it doesn’t fail quietly. The entire seamless architecture collapses into a single human interaction that has to repair it, in real time, in front of the person it just let down.
What strikes me as strange — and I keep returning to this — is what that structural condition implies. An industry running on fragmented, accumulated infrastructure, generating enormous amounts of data it can’t fully use, absorbing failures at the human layer because the technical layer wasn’t built to prevent them. And because the guest experience has been designed, deliberately, to make all of that invisible — because the measure of success in hospitality technology is that no one notices it — the pressure to address these structural problems systematically has always been easier to defer than to face.
So who is looking at the infrastructure? And who is accountable for improving it as a whole — not one system at a time, but the thing underneath all of them?
Some founders are already asking that question. Not as a grand project, but one integration, one failure point, one siloed dataset at a time. That’s probably how it gets solved — incrementally, from the inside, by people who understand both the technology and what it feels like when it breaks. There aren’t enough of them yet. But they exist, and they’re working.
Scott Hill is the Founder and Executive Director of The Proxenia Foundation and the founder of the Proxenia Accelerator programs in Central Florida.
