Beyond the Rooms View: Deconstructing the Great PMS Debate from the Inside
A closed-door HITEC San Antonio debate between PMS CEOs and hotel CIOs exposes structural gaps in hospitality tech, from labor-cost bias to the myth of seamless cloud integration.
Photo by TRAVHOTECH
Organised by Hospitality Net, a closed-door session recently took place on the sidelines of HITEC San Antonio under the Chatham House Rule. It brought together the chief executives of the world’s leading property management systems (PMS) and global hotel group CIOs to openly debate the widening gap between what suppliers are building and what operators are optimizing for.
Key Insights: Google’s Agentic Shift toward Hospitality
-
Recent discussions at HITEC San Antonio highlighted the disconnect between property management systems (PMS) and hotel operators.
-
The hospitality industry must shift its focus from cost-cutting on labor to enhancing guest experience for real efficiency.
-
Comparing hotels to airlines is misleading; hotels operate multi-departmental ecosystems that require deeper integration.
-
A unified approach is essential; hospitality assets share the common foundation of space, time, and price.
-
Technical leadership needs empowerment to improve enterprise technology penetration and drive operational efficiencies.
At TRAVHOTECH, we look at this dialogue from a 360-degree viewpoint. Having spent a career moving between corporate hotel operations, senior advisory networks, and enterprise software delivery, we view these boardrooms without an interest in supporting one side or tearing down the other. Instead, we see a collection of structural illusions and legacy behaviors that continue to stall actual innovation.
If we want to turn modern technology into a true competitive advantage, we must stop falling for marketing narratives and address the true nature of the hospitality product.
1. The Human Cost Fallacy: The Unmeasured Toll of Inefficiency
The live polling inside the room exposed a persistent industry reflex: prioritizing cost savings on labor (scoring 4.4 out of 5) well ahead of the actual guest experience (3.6). The current artificial intelligence paradigm has made this hollowing-out reflex even more acute.
The fundamental error here lies in how the hospitality industry evaluates business performance:
The Structural Disconnect: Hotel financial frameworks are designed to measure direct labor expense with microscopic precision, but they fail completely to measure the cost of structural operational inefficiency.
It is a textbook cop-out to treat headcount as the only adjustable lever simply because it represents a large expense line on the P&L. If our tools properly enable revenue generation and operational efficiency, the staff expense line naturally aligns with a more profitable business model.
Yet, if you keep deploying the same tired, fragmented model of narrow tools, your people remain permanently stuck in manual back-office workflows. All the business achieves is passing the manual administrative workload directly back onto the customer. True efficiency isn’t about running an empty building; it is about building a system that allows your people to operate at peak capacity.
2. Dismantling the Myth: Airlines Are Not Hotels
During the debate, the familiar story reemerged that hotel technology lags a decade behind retail and banking. This comparison is an exceptionally poor reference point for our industry and needs to stop.
An airline controls a highly centralized, single-SKU environment: a seat. They place a customer into a pressurized container next to a stranger, move them from point A to point B, and exit them. Retail relies on a similarly linear, high-volume transactional flow.
Hospitality is an entirely different operational reality. A premium hotel or lifestyle resort is a complex network of multi-departmental ecosystems running simultaneously under one physical footprint:
-
Lodging & Rooms Operations
-
Complex Multi-Outlet Food & Beverage
-
High-End Luxury Spa, Golf, and Wellness Facilities
-
Casino and Player Gaming Environments
-
Meeting, Event, and Convention Spaces
While distribution is a common denominator, the hotelier’s landscape is exponentially more intricate. Total distribution is far more than a bedroom. To move forward, we must abandon airline transit analogies entirely and shift our focus toward managing a unified digital shelf capable of dynamically exposing our complete inventory.
3. Space, Time, and Price: A Common Operational Foundation
For decades, property management architecture has been restricted by a myopic “rooms view.” The core problem is that things have not genuinely changed; we still spruik the value of distinctly separate technology products while trying to sell a distinctly combined business experience to the guest.
A frequent, tired argument used to defend fragmented stacks is that hotel departments—rooms, golf, spa, and food & beverage—are completely separate businesses that require distinct, isolated tech architectures. This represents a failure of architectural imagination.
While these departments are not identical, they are entirely common in their nature. Structurally, every core asset in hospitality follows the exact same foundation: It is about space, time, and price.
-
A hotel bedroom is a space sold for a specific time at a fluid price.
-
A spa treatment table is a space sold for a specific time at a fluid price.
-
A golf tee time or a restaurant table follows the exact same pattern.
Every single one of these assets is highly perishable inventory units that must move before the clock runs out.
Drawing from direct experience in the comprehensive consolidation of hospitality operations through technology, the business benefits of a single operating framework are definitive. When you look at the estate through a unified product lens, you eliminate artificial departmental boundaries. To put it subtly: if an observer, executive, or vendor has never actually lived and executed inside that consolidated environment, their objective comparison is pure speculation, not fact.
4. The Integration Illusion: Exposing the Marketing Speak
The boardroom debate highlighted a classic disconnect: vendor CEOs insisted their systems are perfectly open and free, while hotel CIOs noted they still face immense commercial and operational friction.
Let’s call this what it is: marketing speak. The persistent trade-show narrative that legacy platforms are inherently broken while modern cloud tech automatically solves every issue is a sales pitch illusion. Just because an enterprise platform is not on the latest version of code does not mean it lacks immense business capability.
The industry has simply substituted the word “integration” to obfuscate the reality that operators are still paying for dressed-up, high-overhead interfaces. The vendor CEOs in that HITEC room were pushing self-serving product narratives to protect their positions, while global corporate CIOs lacked the future vision required to see through the interface jigsaw puzzle.
True operational friction is not removed by managing connections better; it is removed by eliminating the point of friction—the connectivity itself through cohesive platforms processing data under a single, native framework. Real structural efficiency requires cohesive operational platforms that process data under a single framework, giving both your staff and your guests a singular, reliable environment rather than a sprawling jigsaw puzzle of connections.
5. Who is Driving the Car? The Enterprise Penetration Failure
A central frustration for software providers is enterprise penetration—signing a global corporate agreement only to spend years persuading individual third-party owners and franchisees to fund the deployment.
But there is a sharper, internal operational bottleneck that has destroyed more opportunity than it has created: If technical leadership is not running technology, programs will have zero penetration.
In too many organizations, core architectural choices are driven by isolated business units, marketing groups, or asset managers focused strictly on procurement cost lines. When strategic technology execution is abdicated to non-technical stakeholders, enterprise roadmaps fracture, application data leaks into silos, and long-term capital investments fail to realize their value.
Technology is a sovereign business asset. If hoteliers want to secure a sustainable market advantage, technical leadership must be fully empowered to govern the enterprise architecture, oversee the asset lifecycle, and drive decisions based on actual domain expertise.
Moving Forward with Clarity
The closed-door discussions in San Antonio confirmed that the barriers holding back digital transformation in hospitality are behavioral, commercial, and structural.
True competitive advantage will not be found by chasing short-sighted headcount reductions or copying airline models. The future belongs to progressive organizations that look past the myopic rooms view, accept that all hospitality assets share a common foundation of space, time, and price, and empower technical leaders to execute clean, unified digital ecosystems. When we match deep operational know-how with technical execution, we stop building jigsaw puzzles and start delivering profitable market leadership.
Frequently Asked Questions
Why is focusing primarily on headcount reduction when implementing hospitality technology a mistake?
Hotel financial frameworks measure direct labor expenses with extreme detail, but they completely fail to capture the financial toll of structural operational inefficiency. Approaching technology with the intention of cutting headcount usually leads to deploying fragmented, narrow tools. This leaves employees stuck in back-office silos and pushes administrative friction directly onto the guest. When technology is built to create an efficient revenue engine and cohesive operating layer, cost efficiency follows naturally without degrading brand standards.
Why shouldn’t the hotel industry use airlines as a benchmark for technology adoption?
Comparing hotels to airlines is an invalid reference point. Airlines manage a concentrated, single-SKU environment—a seat—designed to transport passengers from point A to point B in a uniform flow. A hotel or resort is a multi-departmental ecosystem (lodging, dining, spa, golf, gaming, events) operating under one physical roof. Total distribution for hospitality is far more complex than selling a seat; it requires managing a unified digital shelf across a wide array of perishable assets.
What does TRAVHOTECH mean by viewing inventory through “Space, Time, and Price”?
Instead of treating rooms, spas, golf courses, and restaurants as separate businesses requiring isolated technology stacks, hoteliers must recognize their common foundation. Every core asset in hospitality is perishable inventory defined by space (a bedroom, a table, a treatment room), time (a night, an hour, a slot), and price (fluid rate). Understanding this commonality allows operators to unify their systems under a single product lens rather than building isolated software silos.
Are modern cloud “integrations” genuinely different from legacy “interfaces”?
In many cases, substituting the term “integration” for “interface” is simply marketing speak that obfuscates high-overhead, vendor-driven connection fees. Newer cloud tools have not eliminated integration friction; they have often just created a sprawling jigsaw puzzle of narrow solutions. Real operational efficiency isn’t achieved by managing connections better—it is achieved by reducing the points of connectivity through cohesive, native platforms that hold and process data under a single framework.
Why do global hotel groups struggle with enterprise technology penetration?
Enterprise penetration fails primarily when technical leadership is excluded from running technology. Core architectural decisions are frequently driven by isolated business departments, marketing teams, or asset managers looking strictly at immediate procurement costs. Additionally, the disconnect between asset-light brand mandates and third-party property owners stalls deployment. To achieve true penetration, technical leadership must be fully empowered to govern the enterprise architecture as a sovereign business asset.
Comments
Comments for this content
0 comments available