The hotel is part of a larger industrial group, which meant leadership came in with high expectations for what operational infrastructure should look like — and real frustration that theirs consistently fell short. The ERP they had was not bad software. It had been chosen at an earlier stage of the business, when the hotel’s operational complexity was a fraction of what it had become. By the time we were brought in, that system was acting more like a ceiling than a foundation.
Department heads worked around it constantly. Procurement made decisions on spreadsheets because the inventory module had never been properly configured for their workflows. Front desk and back office operated in partial isolation, which meant financial reconciliation happened late, manually, and with predictable errors. When leadership asked for a cross-functional reporting view, someone had to compile it by hand. The gap between what the system promised and what it actually supported was significant — and every month it went unaddressed, the gap widened.
What We Found When We Got Inside
We began with a full AS-IS process audit — not because the ERP replacement was in question, but because we’ve seen too many organizations replace a constraining system with a different constraining system, simply because the underlying workflow problems were never mapped. The hotel’s issue was not the software. It was that the software had been configured around the wrong version of the business.
Interdepartmental coordination was running through informal channels: group messaging, phone calls, printed reports that were outdated the moment they were printed. Guest experience processes depended on individual staff initiative rather than any systemic logic. Executive reporting was a monthly exercise that consumed significant time from multiple people and still produced an incomplete picture.
Before selecting a replacement system, we needed to engineer the TO-BE operating model first. Only then would we know what the new infrastructure actually had to do.
Building the Operating Architecture Before Touching the Technology
The ERP replacement was the visible part of the engagement. The less visible — and more consequential — part was redesigning how the hotel actually operated before any technology was selected.
We mapped the full operational flow across departments, identified where coordination broke down, and documented precisely which data flows needed to be automated versus which needed to be redesigned entirely. Procurement logic was restructured. Financial reconciliation was redesigned to happen as a byproduct of operations rather than as a separate periodic exercise. The guest experience process — from pre-arrival communication through post-stay follow-up — was reengineered as a system, not a collection of individual staff behaviors that varied based on who was on shift.
The new ERP was then implemented and configured against this redesigned architecture. Front-office and back-office operations became integrated for the first time. Centralized procurement management replaced the spreadsheet-and-phone-call coordination that had been the norm. Reporting that had been a manual weekly ordeal became available on demand — consolidated, accurate, and current.
Where intel2b™ Changed the Equation
The most transformative layer was deploying intel2b™ — our Universal AI Enterprise Core — as the intelligence backbone of the new system.
intel2b™ is not a standalone AI tool layered on top of existing infrastructure. It operates as a centralized intelligence engine embedded within the enterprise system itself, which is what made it effective here. Staff were not asked to switch between their regular system and a separate AI assistant. The intelligence was built into the operational logic they were already using.
Across departments, intel2b™ handled recognition-based automation that previously required manual data entry, intelligent autofill that reduced administrative overhead on routine tasks, and predictive data structuring that made reporting almost instant rather than a compilation exercise. Anomaly detection meant that irregularities that previously surfaced only in monthly reconciliations were flagged in real time. Decision assistance at the process level meant staff spent less time figuring out what to do next and more time doing it. The cumulative effect was a shift from a system that people worked around to one they could genuinely rely on.
What Changed for Leadership
The change that mattered most to ownership was visibility. Before the engagement, the executive view of hotel operations was assembled manually, always lagged, and frequently incomplete. After, it was real time, cross-departmental, and structured for actual decision-making rather than retrospective review. That distinction sounds abstract until you’re the person who no longer needs to wait three days for a cost summary.
The hotel transitioned from system dependency — where the system’s limitations constrained what was operationally possible — to system control, where the infrastructure adapted to the business rather than the other way around. And beyond the immediate operational improvements, what the engagement produced was a platform built to scale. As the hotel’s service complexity grows, the infrastructure can absorb that growth without requiring another overhaul.
A Note for Hospitality Leaders
Hotels that operate within larger business groups carry a particular risk: they are often held to enterprise performance standards while running on infrastructure that was never designed at enterprise scale. The gap between expectation and operational reality tends to widen quietly, until the cost of addressing it becomes significant.
The work here was not digital transformation in the way that phrase is usually used. It was operational intelligence engineering — the deliberate alignment of system architecture, workflow design, and AI capability into something that actually serves the business it is supposed to serve.
If your hotel is running on infrastructure that was right for an earlier version of the operation, the question is not whether to address it. It’s whether to address it before or after it starts costing you.
Request an Enterprise Architecture Diagnostic
We assess your current operational architecture against where the business is going — identifying structural gaps, automation opportunities, and the specific sequence of changes that will produce the most impact. The output is a transformation roadmap built around your actual operational reality.