Technology

The most transformative disruption we’ll bring to the hospitality industry by 2026 lies in end-to-end workflow automation across hotel operations, not just individual tasks, but entire processes that currently require too much manual effort with too many handoffs and that may unnecessarily create security risks in today's high data security environment.

We believe AI will most profoundly disrupt operational scheduling and resource allocation across spa, wellness, and leisure departments. These areas are traditionally managed through manual guesswork, disconnected systems, or static templates.

I believe the biggest disruption isn’t a single task - it’s the entire commercial workflow behind meetings and group bookings. A third of all hotel room nights tie back to a meeting or group, yet hotels still burn thousands of hours on manual qualification, data gathering, and proposal-building.

It's abundantly clear that the US hyperscalers are unable and unwilling to regulate themselves. A $100 million pro-AI super PAC formed in August, backed by OpenAI's president, has identified its first pro-legislation target to oust.

The divergence in AI regulation is less about "innovation versus control" and more about who will define the operating system of the future economy. The US optimises for velocity and scale; the EU for rights, accountability, and systemic risk.

Yes, the gap in AI innovation and adoption will continue and expand. This disparity is less about well-intentioned policy and more about an ongoing geopolitical battlefield where technology sits squarely in the 'armed forces' of the major powers.

In my previous airline and telcoms world, we used service buses like TIBCO to sit on top of enterprise systems. The upside was the potential of plug and play (although we never actually changed back end ERPs). The downside was extra latency and cost.

The integration hub solution is different for every hotel. The easiest answer starts with new brands or independents. Heading into 2026, there are several great PMS and GEMS players that can fulfill a variety of central operations so that one-off integrations amongst disparate, single-use services aren't as necessary as they were a few years ago.

In practice, it's not that simple. A hub always depends on common integration standards — yet many systems still lack proper REST APIs to communicate effectively. For example, we dynamically manage room assignments and reassignments based on guest fit and preferences, but not all PMSs even offer APIs that allow us to do this.

The problem isn't that personalization fails on property. The problem starts much earlier: we still don't speak the right language of guest experience in the digital space. Take booking. A traveler may want a big bed, a walk-in shower, and a quiet location.

Online personalisation is easy, as it's mostly a pattern-matching algorithm between known guest preferences and available services. It isn't personalisation, rather just mass customisation. On property, a guest walking around is essentially anonymous, even after checking in.

This is a question at the heart of hospitality’s digital transformation. Hotels excel at digital personalisation (curated offers, smooth booking, and tailored communications) because online, data is structured, accessible, and actionable.

When it comes to where our Distribution landscape is headed - it's not even a question. Of course uniting our efforts is the only way to go. Otherwise we'll lose another OTA battle. But there's much more to the world of AI functionalities, it has its tenticles in every part of our tech ecosystem, not distribution alone.

I think we are in danger of running before we can walk here. MCP is Anthropic’s pitch for an open standard to let "agentic AI" bots built on next-word LLMs share data, for example, an OpenAI bot talking to a Gemini bot. Unless you are Marriott or Hilton with hundreds of in-house developers, or a big OTA like Expedia or Booking.com, this really isn’t something you need to worry about.

You could establish your own protocols instead of MCP, A2A, or other widely endorsed standards for agentic interactions. But that would be like creating your own version of HTTP. Not a great idea. The good news is I don't think companies feel the need to change that basic agent-friendly plumbing.