How Shaza Hotels Built a Tech Stack That Matches Their Service Standard

Amir Ali

Hospitality Technology Leader · Shaza Hotels

Amir Ali leads technology and digital operations at Shaza Hotels, a luxury hospitality brand operating across the Middle East. He has spent over a decade integrating enterprise systems across hotel portfolios, from PMS and CRS to in-stay guest experience platforms.

April 15, 202648 min

Key Takeaways

  • In luxury, the tech stack is invisible or it is a problem. No guest should ever see the seams between your systems.
  • PMS data alone tells you what a guest did. Layering CRM and F&B gives you why, and why is what drives the next stay.
  • Buying an off-the-shelf platform is fast. Bending it to a luxury workflow takes longer than building the right thing from scratch.
  • The front desk team will not use a tool that slows them down mid-conversation with a guest. Adoption lives or dies in the first 30 seconds of the check-in flow.
  • Start with the data model. Every integration problem I have seen traces back to two systems that could not agree on what a 'guest' is.

Luxury hospitality operates on a different margin of error. A missed guest preference at a midscale property is an inconvenience. At Shaza, it breaks the promise the brand makes on arrival. Amir Ali has spent years building systems that hold that promise across the portfolio: connecting PMS, CRS, F&B, and in-stay platforms so the right data reaches the right team member at the right moment. In this conversation, he breaks down which integrations his team built first, how they evaluated build versus buy for a luxury property portfolio, and why the hardest part of any hospitality tech project is the data discipline that precedes it.

The loyalty data was there. The F&B preference was there. The suite upgrade trigger was there. But the three systems had never been introduced to each other. That is where we started.

Amir Ali, Shaza Hotels

A luxury guest does not want to explain themselves twice. If they told you at check-in, your system should remember it at dinner. That sounds obvious. It took us two years to make it work.

Amir Ali, Shaza Hotels

Transcript

Full transcript coming soon. In the meantime, watch the episode or download the white paper for the key frameworks from this conversation.

More episodes

Questions from this episode

Buying platforms before agreeing on the data model. Two systems that define a 'guest' differently cannot share data cleanly, no matter how good the integration. Amir Ali says every integration problem he has seen traces back to that single disagreement.
Design for the first 30 seconds of a check-in interaction. If the tool slows staff down in that window, adoption will fail regardless of the feature set. The system has to be faster than the workaround — and the workaround in a luxury hotel is always a hand-written note.
Not always. The real question is whether the platform can flex to your workflow or whether you will spend more time bending to the platform than building the right thing. Off-the-shelf is fast. Adapting it to a luxury workflow can take longer than a custom build.

What's next

Book a Free Ops Audit

Tell us which process costs you the most time or money. We'll map it, score it, and show you exactly where AI or automation delivers results. No charge for the assessment.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.

Book your audit