Places · Hospitality
Guestenza
Managers see the operational cause behind each guest moment, act in time and measure the result.
01The problem
Hospitality does not lack systems; it lacks one operating truth. Reservations, point of sale, delivery apps, kitchen screens, stock sheets and review sites each hold a fragment. When an evening goes wrong for a guest, the cause usually lies elsewhere, in a late station, a missing ingredient or an overbooked hour. Feedback arrives after the table has left, and recovery depends on who happens to notice.
02The system
Hospitality experience and operations intelligence.
Guestenza is one operating layer across guests, teams, operations, finance and intelligence, built on one data model, one access model and one audit chain. It is organised as connected products: Passport for guest memory, Command for the view across brands and branches, Kitchen for station and stock readiness, Recovery for complaint cases, Channel for reservations, dine-in, pickup and delivery, and Twin for decision modelling.
03Why it matters
Every guest moment is connected to the live operation behind it, so managers see the cause, act in time and measure the result.
Built for
- Multi-brand restaurant groups
- Hotel and resort food and beverage
- Food courts and shared venues
- Institutional dining at hospitals, universities and workplaces
04What it does
- 01
Passport: consented guest memory
Preferences, allergies, occasions and visit history, held with the guest's consent and available to the team serving them.
- 02
Kitchen: station and stock readiness
Station load, prep timing, stock on hand, waste and variance in one view of kitchen and supply readiness.
- 03
Recovery: closed-loop complaint cases
Each complaint becomes an owned case with a proposed action, a second person's approval and a recorded outcome.
- 04
Command: brands and branches
One view across brands and branches: what needs attention, what changed and where a branch is drifting from plan.
05Product in action
Screens are unedited captures of the public website of Guestenza. Where the venture labels an example as illustrative or synthetic, that label is kept.
06How it works
- 01
Guest signal
A preference, a wait, a complaint or a return visit is captured with the guest's consent.
- 02
Operational cause
The signal is set beside what was happening at that moment: kitchen load, stock, staffing and channel.
- 03
Action
The right manager receives the context and a clear next step, within their permissions and approval limits.
- 04
Outcome
The result is recorded, so recovery, service and cost can be measured rather than assumed.
07What makes it different
Guestenza keeps the guest, the operation and the decision in one record, and works alongside existing systems as an overlay, a hybrid or the full system. It is strict about what it does not know: a measured zero, missing data, an unavailable provider and denied access are each shown as different answers.
08Trust and governance
Each person sees only what their role and branches allow, and each organisation's data is separated in the database itself. Sensitive actions are recorded and cannot be edited afterwards. AI stays off unless an organisation turns it on. Pilot results appear only once measured, and no third-party certification is claimed.
09In the portfolio
Places
Guestenza brings the Places orbit into hospitality, where a building becomes a service that guests experience every evening. It follows the shared method closely: start from the guest's real problem, show evidence rather than guesses, keep a second person approving recovery, and work in English and Arabic from the start.
Also in this orbit
10Where it stands
In private rollout. Pilots by arrangement.
The venture’s own website has the full product story.
Visit Guestenza (opens in a new tab)