Run your property smarter — without changing the systems you already run.
Predictive maintenance, sentiment alerts, energy savings, occupancy flow, wellness personalisation. One operating picture for the GM, the maintenance manager, the spa director and the front desk — built on your PMS, POS, BMS, IoT and reviews. Not a replacement. A layer on top.
The numbers a GM tracks. Moved in the right direction.
Energy, downtime, maintenance cost, response time, guest-context quality, and cross-team visibility should be baselined before a pilot target is agreed.
Measure energy use by zone, occupancy state, weather, and operating schedule before setting a reduction target.
Track failure hours, guest impact, detection lead time, and avoidable emergency work against the current baseline.
Separate planned from emergency work, parts, labour, and repeat callouts before agreeing the pilot target.
Define how quickly material feedback should reach the responsible team and measure detection-to-response time.
Resolve only the guest context the approved workflow needs, with purpose, access, and retention controls attached.
Give each role the minimum shared operating view it needs; do not flatten every department into unrestricted access.
These are measurement categories, not performance claims. The baseline, target, evidence window, and acceptance threshold are set against the property's own systems and operating conditions during scoping.
Six things your team catches that yesterday would have missed.
Every event below is caught, classified and routed to the team that owns it — with the source attached. No reading dashboards at the end of the week to find out what happened on Monday.
Where it touches your property.
One system across every part of the operation — from the front desk to the engine room. Nine outcomes, plotted on the zones that own them.
Nine things your team stops doing manually.
Each card below is what the person who owns it sees on a Tuesday morning — not what an engineer would say it is. The data plumbing matters; how it lands on your team's screen is what changes the property.
Predictive maintenance
A ticket on Tower B Floor 4 at 04:12 — HVAC vibration spike.
Twelve rooms held back from sale until it's resolved. No more guest complaints about a unit that should have been replaced last month. HVAC, plumbing, lifts, kitchen equipment — anomalies caught the day they start.
Smart staff scheduling
Tomorrow's roster, built from today's bookings.
Occupancy, event load and historical demand resolve into a schedule a manager can approve, not assemble from scratch. Less overstaffing on quiet nights, less understaffing on event days.
Housekeeping prioritisation
Today's order, not yesterday's rotation.
Rooms sequenced by check-in time, guest profile, floor route and current sensor state. The early arrivals and the VIPs land in rooms that were ready for them — not the next room on a static list.
F&B & inventory forecasting
Tomorrow's covers, surfaced against today's bookings and the weather.
Kitchen inventory and bar stock reslotted before procurement orders ship. Food waste drops. Margin holds. The procurement order matches the night the property is actually going to have.
Live occupancy & crowd flow
Lobby, pool, dining — live density on a map of the property.
Bottlenecks flagged before they become guest complaints. Staffing rebalanced in real time when the lobby goes into peak at 08:30 or the pool fills up at 14:00.
Wellness personalisation
Spa and F&B see the same guest, not three fragments.
Sleep history, last spa visit, stated nutrition goals — one record. The same guest stops getting asked the same question by three different teams. Personalisation lands at every touchpoint, not just the one that captured the preference.
The returning-guest profile
The guest who arrives in two years is met as who they became.
Preference learning across stays. The personalised welcome matches who the guest is now — not who they were on their first visit. Loyalty stops feeling like a points program and starts feeling like a relationship.
Sentiment intelligence
A pool complaint surfaces in hours. Not the next NPS quarter.
Reviews, in-app chat, support tickets, voice and surveys — one stream. Dissatisfaction caught before it becomes a public review. The team responsible knows before the guest hits Tripadvisor.
Hidden operational patterns
Why is the spa empty when F&B is overbooked?
Patterns that span teams — slow F&B + low spa rebookings + mid-shift housekeeping delays — resolve into one root-cause brief on the GM's screen. The cross-team correlation no spreadsheet was going to find.
Pre-arrival to loyalty — one continuous record.
Operations is half the system. The guest is the other half — one record across stays, not five fragments across systems.
Pre-arrival
Past preferences resolved across stays. Personalised options sent without asking what the guest already told you.
Arrival
Room readied against current sensor state. Front desk briefed on context the PMS alone doesn't carry.
In-stay
Spa, F&B, wellness and activities adapt to live signal — what was used, what was skipped, what's busy.
Departure
Sentiment captured before the review goes public. Loyalty triggered against the stay that actually happened.
Between stays
The profile keeps learning. The next arrival is met as who the guest became, not who they were.
What changes for the team running the property.
Seven systems. Three spreadsheets. Weekly reconciliation meetings.
- Each team is right about its own data and wrong about the others.
- Maintenance issues surface from a guest complaint, not a sensor.
- Sentiment shows up in the quarterly NPS — after the review goes public.
- Spa, F&B and front desk each have a different version of the same guest.
- The GM sees Monday's numbers on Friday.
One screen. One record. Alerts that route themselves.
- Every team is working from the same underlying record.
- Maintenance issues surface from the sensor, before the guest notices.
- Sentiment shows up in hours, routed to the team that owns the fix.
- One guest. Spa, F&B and front desk see the same person.
- The GM's morning brief includes yesterday — by the time they read it.
Built on what you already run.
Djeed reads your existing systems — PMS, POS, BMS, IoT, CRM, reviews — and puts them into one operating picture. No migration. No vendor switch. The stack you already pay for is the foundation.
What you already pay for.
- PMS · POS · CRM · ERP
- Spa & activities booking
- Building Management Systems, BACnet / Modbus
- IoT sensors, MQTT gateways, ONVIF cameras
- Guest app, staff app, in-room tablets
- Reviews, social, support transcripts, surveys
Reads it. Resolves it. Runs the intelligence.
Djeed sits on top and turns the systems you already run into one operating picture. The same guest across PMS, POS, spa and reviews resolves to one record. Sensors, bookings and reviews flow into one stream. Predictive maintenance, sentiment, occupancy flow, wellness personalisation and the day-end brief all run from there.
For the technical reader: this is Djeed's five-solution flow — foundation → graph/spatial → predictive → operational → decision. Detailed on /solutions.
Their daily work, with less of the chasing.
- Tickets routed before the guest notices
- Briefs assembled, not built from scratch
- Alerts surfaced to the team that owns the fix
- Bookings personalised on actual history
- Reports updated, not exported
- The GM's 7am brief — already on the screen
Plugs into the systems you already run
A sample of the categories and systems we've worked with. Connectors are scoped per engagement; unfamiliar stacks are part of the discovery conversation.
Names and marks listed are trademarks of their respective owners. Inclusion describes integration capability, not partnership or endorsement.
For the curious — the system, running
One property. One operating picture.
An abstract view of what's running underneath. Sources stream in, outcomes fire. Continuous — not a quarterly snapshot.
Your data lives where you choose.
Cloud, hybrid, on-prem or at the edge — Djeed runs the same intelligence wherever the property needs it to sit.
Djeed-hosted in Switzerland
Fully managed on Djeed's Swiss VM. Fastest to start. Default for properties without strict residency constraints.
Cloud + at the property
Sensitive guest records stay at the property; intelligence ships to the cloud. Most common shape for international groups.
In your data centre
The whole layer runs on your hardware. For properties with sovereignty mandates or air-gapped requirements.
At the property
Sub-second decisions where they're needed — predictive maintenance, occupancy flow — on edge nodes inside the property.
| Layer | Cloud | Hybrid | On-prem | Edge |
|---|---|---|---|---|
| What your team sees — dashboards, alerts, briefs | ●default | ● | ● | — |
| The intelligence — predictions, decisions, recommendations | ●default | ● | ● | ◐some, on edge nodes |
| The structured guest + property record | ●default | ◐split — guest record on-prem, intelligence in cloud | ● | — |
| — Djeed sits on top of everything below — | ||||
| Read connectors to your existing systems | ● | ● | ● | ● |
| IoT, cameras, BMS, sensors | — | ◐stays at the property | ● | ◐always at the edge |
| PMS · POS · CRM · spa booking | ◐depends on vendor | ● | ● | — |
| Guest PII, financial, health records | ◐optional | ◐stays at the property | ● | — |
Ready to use, or built for your property.
Pilot one outcome. Add the rest later.
Start with the outcome that has a measurable baseline, an accountable owner, and safe access to the required systems. Agree the proof window and acceptance threshold before building; add the next outcome only when the first earns it.
- One outcome scoped to your stack, owner, baseline, and proof window
- Acceptance criteria agreed before a delivery date is promised
- You decide where the foundation goes next — or not
The full picture, built for your property.
All nine outcomes. Every team on one screen — delivered for your environment (hybrid, on-prem or edge) and integrated with the stack you already run. For groups whose compliance posture, scale or sovereignty needs go beyond a one-outcome pilot.
- Front desk, maintenance, F&B, spa, GM — one record
- Deploy shape chosen with your IT — cloud, hybrid, on-prem, edge
- Scoped engagement: discovery → build → handover → run
The agents at work
Named specialists, doing specific jobs.
We always used AI agents inside this — now we name them. Each is grounded in one slice of your world and makes one specific call: a wheel in the bigger system. How the agents work →
Maintenance Watch agent
Knows the building and asset signals and the work-order history.
Decides what needs attention before it becomes a guest-facing callout.
Concierge agent
Knows the shared guest record and what makes a stay effortless.
Decides what to anticipate, personalise, and book for each guest.
Sentiment agent
Knows reviews and feedback across every channel.
Decides what to flag to the GM today.
Day Brief agent
Knows what the GM acts on each morning.
Decides what goes in the day-end brief.
Questions GMs and owners ask first.
Do I have to rip out my PMS, POS or CRM?
+
Do I have to rip out my PMS, POS or CRM?
+No. Djeed reads what you already run. The systems of record stay where they are — Djeed sits on top and makes them legible together.
Where does guest data live?
+
Where does guest data live?
+Your choice. Fully cloud on Djeed's Swiss VM, hybrid with sensitive records staying at the property, or fully on-prem inside your own data centre. The same intelligence runs in all three shapes.
How fast does the first outcome go live?
+
How fast does the first outcome go live?
+Timing is scoped after the systems, data quality, access constraints, and baseline are known. The first engagement defines one outcome, one proof window, and the acceptance measures before a delivery date is promised.
Can I start with one outcome and add the rest later?
+
Can I start with one outcome and add the rest later?
+Yes. Start where the baseline is measurable and the required systems can be connected safely. Add another outcome only when the first has met its evidence, adoption, and operating criteria.
What's the difference between DjeedX and a custom build for our property?
+
What's the difference between DjeedX and a custom build for our property?
+DjeedX is the invite-only workspace for structuring and analysing connected records. A custom build is needed when the property requires live system integrations, automated operating workflows, specialized permissions, or a specific cloud, on-prem, or air-gapped boundary.
How are outcome targets set?
+
How are outcome targets set?
+We establish the property's own baseline first, agree the metric definition and proof window, then set a target that reflects the connected systems, occupancy mix, operating constraints, and data quality. This page does not present another operator's result as a promise for your property.
Run your property smarter. Start with one outcome.
Tell us about your property and the outcome you'd move first. We'll show you what the connected system would look like, end to end — and the numbers for your specific stack.