This insight summarizes Stephan Wiesener and Mike Rawson's PhocusWire opinion on hidden model concentration risk in hotel technology.
AI dependency accumulates invisibly. Revenue systems, guest messaging, concierge tools and review workflows may arrive through different software vendors while relying on the same underlying foundation model. Hotels often do not hold the direct provider relationship or receive model-deprecation notices. One pricing change, retirement or policy shift can therefore disrupt several workflows at once.
Adoption has outpaced continuity planning. The authors cite H2c's 2025 global study: 78% of hotel chains deploy AI, but only 7% have a comprehensive AI strategy. Traditional disaster recovery plans cover infrastructure outages and cyber incidents; many do not yet inventory which models support critical processes or what happens when their behavior changes.
A real continuity plan has four layers. First, map every embedded AI dependency and identify concentration risk. Second, decouple applications from individual providers through an abstraction layer, including standards such as Model Context Protocol. Third, route tasks across multiple models based on cost, latency, capability or data residency. Fourth, version and regression-test the entire system so a fallback is proven before it is needed.
The portable asset is the governance layer. Prompts, business rules, approval flows, authority ceilings and operating procedures—not the rented model—contain the hotel's accumulated operational knowledge. The authors recommend treating those assets as code: store them in version control and validate outputs against primary and fallback models through automated testing.
Takeaway for hotel CIOs. A backup provider alone is not resilience. Prompt behavior can change across models, and proprietary models cannot be backed up. Keep the AI layer separate from core systems, require vendors to disclose model dependencies and preserve the governance that makes automated decisions trustworthy. Model churn is now a normal lifecycle condition, so architecture must assume it.