Real estate and hospitality
One record of every building, unit and guest, across every system you run.
Why estates and hotels struggle to act as one
A property portfolio or a resort runs on many systems that rarely talk to each other: building devices, a property ERP, point-of-sale in every outlet, booking and guest services. Each new project adds another one, and guests and tenants feel the gaps first.
Systems that do not talk
Building devices, the property ERP, outlet tills and guest services each keep their own record.
Every project adds a system
Giga-projects and new properties bring new platforms faster than they can be connected.
New rules to meet
E-invoicing mandates and data-residency laws now apply to every invoice and every guest record.
What changes
What changes when the systems are connected: one record of each building, unit and guest; sales and stock that reach the ERP as they happen; and operations teams who see the whole estate in one place instead of in separate screens.
One record of each building and guest
Units, assets, tenants and guests recognised the same way in every system.
Sales and stock in real time
Outlet sales, returns and stock reach the ERP as they happen.
One view of the estate
Operations teams see buildings, outlets and guest services in one place.
Invoices that clear
E-invoices validated and cleared with the tax authority, straight from the ERP.
Where we work
What we build
- Platforms that collect building IoT data at the edge and make it usable
- Real-time 3D digital twins of buildings and districts, built with Unity, Unreal Engine or NVIDIA Omniverse
- Operations dashboards and command centres for facilities teams
What we build
- Property ERP implementations and extensions, on SAP, Oracle, Microsoft Dynamics 365 or Odoo
- Tenant and owner portals and mobile apps
- Automated invoicing, collections and reconciliation
Typical integrations
- Banks, for collections and statements in ISO 20022 and MT940
What we build
- Guest super-apps: one app for stay, dining, services and payments
- AI receptionists and speech-reasoning voice agents that answer guests and act through your systems
- Guest experience systems for staff, connected to property operations
What we build, connect and secure
Guest and tenant apps
Native iOS and Android or cross-platform apps (React Native, Flutter) that bring booking, services and payments into one place.
Digital twins
A live 3D model of a building, resort or district, fed by its devices, for planning, operations and training.
Property ERP
The ERP that holds units, contracts, assets and finance, implemented or synchronised with the systems around it.
Smart point-of-sale
Outlet sales, returns, prices and stock carried to the ERP as they happen, so finance and operations see the same numbers.
AI reception and contact centres
Voice and chat agents that understand guests, complete requests through your systems, and hand over to staff when they should.
Operations command centres
Dashboards that bring buildings, outlets and guest services into one view for the people who run them.
ERP synchronisation
Orders, invoices, stock and payments kept in step with SAP S/4HANA, Oracle Fusion or NetSuite, Microsoft Dynamics 365, Odoo or Sage.
E-invoicing mandates
Clearance with UAE PINT-AE, Saudi ZATCA Phase 2 and Oman, connected directly to the ERP.
Payments and POS
Gateways, acquirers and card networks over ISO 8583 or ISO 20022, with settlement files processed automatically.
Building IoT and edge
Device data collected and processed at the edge, then passed on to the platforms that need it.
CRM and service platforms
Guest and tenant records in Salesforce, ServiceNow or Microsoft Power Platform, linked to every channel.
Data residency and privacy
Guest and tenant data kept where the law requires, and designed for GDPR and the MENA personal data protection laws (PDPL).
Tax mandates
E-invoicing built to the clearance rules of each tax authority, with every submission and response kept for audit.
Building and device security
Smart-building and IoT networks secured with zero-trust access and micro-segmentation, so one device cannot reach the rest.
Accessibility
Guest and tenant apps designed to WCAG accessibility requirements, so every guest can use them.
How we work
We start from what you already run. We map the systems, design the connections and their failure paths, then build the guest apps, digital twins and operations tools on top. Giga-projects in the Gulf also bring e-invoicing and data-residency rules, which we design in from the start.
Map what you run
We inventory the systems, their interfaces and the data each one owns.
Design the connections
We design the integration layer and its failure paths before any build starts.
Build in stages
Guest apps, digital twins and operations tools are delivered in staged releases, each demonstrated live.
Scroll sideways to see the whole drawing.
POS to ERP: every sale posted once
Sales flow from the tills to the ERP as events, and prices and stock flow back. A store that goes offline keeps selling and catches up. A posting that fails is retried, then handed to a person.
- Primary flow
- Asynchronous
- Exception path
The flow in 8 steps
The flow, step by step
- From POS terminals to Store or POS cloud server: Sales, returns and voids (primary flow).
- From Store or POS cloud server to Integration layer: Sales events and end-of-day totals, through an event queue, over REST/JSON (asynchronous).
- From Integration layer to ERP: Sales and stock movements posted, over OData · REST/JSON (primary flow).
- From ERP to Integration layer: Prices, promotions and item data, by API or file export, over REST/JSON (primary flow).
- From Integration layer to Store or POS cloud server: Price and stock updates, over REST/JSON (primary flow).
- From Integration layer to Retry queue: Posting failed (exception path).
- From Retry queue to Integration layer: Retried (exception path).
- From Retry queue to Store operations team: Still failing: alert with the details (exception path).
Technologies and standards
The platforms and mandates property and hospitality work connects to, as the documents behind this page name them.
- 3D and digital twins
- NVIDIA Omniverse
- Unity
- Unreal Engine
- Design and accessibility
- WCAG 2.2
- ERP systems
- Microsoft Dynamics 365
- Odoo
- Oracle Fusion Cloud ERP
- SAP S/4HANA
- CRM and workflow platforms
- Salesforce
- ServiceNow
- Payments
- EMV
- SoftPOS
- Standards and regulations
- GDPR
- MENA PDPL
- UAE PINT-AE
- ZATCA Phase 2 (FATOORA)
Track record
Selected enterprise brands represent historical and ongoing systems, platforms and digital products architected or delivered by XSIS, KONG GROUP, our CEO and our principal engineering leadership across their careers. All third-party trademarks are the property of their respective owners and are named strictly for factual portfolio identification.
How to start
What happens next
Agreeing a time
Our team emails you to agree a time for the session.
Pre-consulting session
A free 30-minute online pre-consulting session: we go through your goals, systems and constraints.
Readiness review
In a free 48-hour readiness review, a Principal Architect checks your project against the 6-point Definition of Ready and recommends the track that fits.
Choosing the track
Scope-ready projects receive a binding proposal within 3–5 business days. Concept-stage projects start in the Blueprint Studio. A live system that is failing, undocumented or needs integration starts with a diagnostic of 1–2 weeks. The Blueprint Studio and the diagnostic each have a fixed fee, quoted in the proposal.
AI-native product teams
Managed, cross-functional pods of senior engineers, equipped with agentic coding and QA harnesses.
Fixed-outcome projects and round-the-clock managed services
Fixed-scope, milestone-driven delivery with named delivery leads, and round-the-clock application managed services under SLA governance.
The quickest way in is the Mandate e-invoicing and ERP readiness sprint package, one of our rapid engagement packages.
Questions and answers
What is a digital twin, and when is it worth building?
A digital twin is a live 3D model of a building, resort or district, fed by the data of its devices and systems. It is worth building when many teams must plan, operate or train on the same large estate. We start with the questions it must answer, then decide which data it needs.
Can you work with the property and hotel systems we already run?
Yes. We start by mapping the systems you have and the interfaces their vendors provide, then connect them through APIs, events or files. Replacing a system is a choice we make with you, never the default.
How do you protect guest and tenant data?
Each system keeps only the data it needs, in the region you choose, encrypted in transit and at rest. Access follows roles and is logged. We design for GDPR and the MENA personal data protection laws that apply to you.
Do you handle e-invoicing for property and hospitality groups in the Gulf?
Yes. We connect your ERP to UAE PINT-AE, Saudi ZATCA Phase 2 and Oman's e-invoicing, with automated validation and an exception path for rejected invoices. Our e-invoicing and ERP readiness sprint is a common place to start.
Where should a project start?
With a free readiness review led by a principal engineer. If your requirements are clear, it leads to a fixed-price proposal. If they are not, a Blueprint Studio engagement turns the goal into an architecture and a specification first.
Start with a conversation, not a contract.
Tell us what you need to build, connect or secure. An architect goes through it with you, then recommends where to start.