Based on his thirty years of exposure to hundreds of hotel technology projects, former Hospitality Upgrade columnist Doug Rice put it plainly: “Most attempts to deploy new technologies at hotels fail.” Not most pilots. Not most early-stage trials. Most deployments. The technology works. The implementation does not.
The Lodging Technology Study found that 69% of hospitality professionals identify integrating new technology as their biggest operational challenge. Academic research confirms that only 5.7% of hotels fully implement intelligent agent technology even after adoption decisions are made. The gap between purchase and full use is where hotel investment goes to die, quietly, expensively, and usually without anyone filing a report about it.
The Boutique Hotel Problem
A boutique property on the Adriatic coast purchased a property management system that covered reservations, restaurant operations, and bar management. The vendor was reputable. The system was capable. Training was conducted online because the vendor was based in another region and on-site visits were not part of the package.
The owner and the sales manager, who specialized in MICE, attended the training. No one from F&B operations was in the room.
What followed was predictable in retrospect and invisible in the moment. Data entry was inconsistent from day one. Receiving records were not entered, so inventory could never be reconciled. Restaurant articles were not configured correctly, so the F&B side of the system never connected properly to the rest of the property. When staff needed information, they called vendor support instead of running reports, because running reports required too many steps and daily operations were always more urgent than learning to do it correctly.
Revenue management was never activated. The system was used for the minimum necessary functions. A fraction of its capability was ever touched.
The vendor’s support team was responsive. The software was not the problem. The problem was that the people who needed to configure and own the system were not present when it was designed, and the daily pressure of running a hotel in peak season made catching up feel permanently deferrable. It never stopped being deferrable.
This is not an unusual story. It is the standard story, told in different languages across different property types, every season.
What Engagement Actually Looks Like
Wyndham Hotels rolled out an AI-enabled guest engagement platform across more than 5,000 properties. The platform was provided at no incremental cost to franchisees. The technology was identical across properties. The outcomes were not.
Highly engaged properties generated more than $60,000 in incremental annual revenue. The highest-performing single property exceeded $200,000. Properties that adopted the platform passively, enabling it without actively configuring upsell offers, training staff on messaging workflows, or treating it as a sales channel, generated results close to zero.
Same software. Same brand. Same price. The variable was operator engagement.
Wyndham’s CEO described the difference in terms that have nothing to do with technology: active franchisees configure dynamic upsells, promote the platform’s capabilities to staff, and treat it as a revenue tool rather than a back-office function. Passive franchisees enable the system and wait. The platform cannot close that gap on its own.
The Operator as Architect
Greg Stafford, General Manager of the Texas A&M Hotel and Conference Center, approached a PMS and housekeeping technology implementation by starting with operational pain points rather than software features. What specific friction existed between housekeeping, front desk, and maintenance? What did staff need to do differently? Where was time being lost?
The technology was selected and configured to address those questions. Not the other way around.
After one year, housekeeping board creation had dropped to 20 minutes. Room inspections fell from 30 minutes to under 10. Payroll came in close to 12% below budget. Guest satisfaction reached 96.6%.
Stafford attributed the outcomes directly to team engagement with the system, including gamification features that made housekeeping performance visible and competitive, and to an ongoing dialogue with the vendor for refinements. The technology did not produce those results. The operational decision to make staff ownership of the technology a management priority produced those results.
Papis Diouf, F&B Manager at Bohemia Suites and Spa, took the same approach to a POS implementation. He mapped ideal F&B workflows before configuring the system, rather than adapting existing processes to software defaults. Breakfast service for 200 guests, previously requiring five or more minutes per paper order, accelerated significantly after the system was built around the process rather than the process being built around the system.
The pattern is consistent across documented cases. Operators who succeed with technology implementations start with operations and move toward configuration. Operators who struggle start with installation and move toward adoption. The sequence matters more than the software.
What Failure Looks Like Before It Looks Like Failure
Ryan King, a hospitality technology implementation specialist, has described the moment an implementation begins to fail: a property champion receives training and resigns a week later. No one else knows the system. Resistance spreads. Months of negativity follow. The system is present but not operational.
This is rarely visible on any dashboard. Food cost reports still run. Reservations still process. The revenue management module sits unused because no one was trained on it before the person who was trained left. The system is not broken. It is simply never used for what it was purchased to do.
Every failed implementation I have read about or witnessed shares the same mechanisms: insufficient change management, lack of process adaptation, weak leadership alignment, and the treatment of implementation as a technology project rather than an operational one. Industry estimates consistently suggest that projects with structured change management are significantly more likely to achieve their original objectives, with some analyses putting the gap at 30 to 40 percentage points.
The boutique hotel on the Adriatic coast never ran a revenue management report. The capability was there from day one. The operational conditions to use it were never created.
The Implementation Question No One Asks at Purchase
Hotels evaluate technology on features, price, integration capability, and vendor reputation. These are reasonable criteria. They are also insufficient.
The question that determines whether a system delivers its promised return is not asked at purchase. It is asked six months after go-live, when someone finally looks at how much of the system is actually being used: who will own this operationally, what processes need to change before we go live, and which department heads need to be in the room during configuration, not just during training?
Vendor support answers questions about the software. It does not redesign checkout workflows, configure upsell offers, or decide which staff member will own the system when the initial champion moves on. That is operator work. It happens before go-live, during configuration, and continuously after launch. The technology cannot do it, and the vendor cannot do it on the operator’s behalf.
The implementation gap in hospitality is not a technology problem. It is a sequencing problem. And the operator is the only one who can fix the sequence.
By Leo Ljubičić, Founder of LPI LABS
