Hospitality

Sofiane Ghorbel wants guests, not platforms, to own the preference profile

Sofiane Ghorbel's first ask for luxury hospitality is client-controlled guest profiles. His argument is data quality, not ethics — and the order matters.

The client should own and control the preference profile, not the technology platform. Sofiane Ghorbel, founder and CEO of AL Hospitality Group, with more than twenty-five years across luxury hotels, resorts, travel, concierge services and destination management, named this as the first of the two things luxury hospitality needs built, and put it ahead of every workflow product.

His argument is not primarily ethical. It is about data quality.

What did Sofiane Ghorbel actually ask for?

Privacy-safe personalisation in which the client, not a platform, holds the preference profile. Asked what still needs to be built, Ghorbel led with this and returned to it repeatedly:

"Very important first of all is the privacy-safe personalization ... The future belongs to systems that allow personalization, privacy and client ownership [of] data."

The ownership point is the substance of it:

"Clients should control their own preference profiles, not technology platforms."

Why does client ownership produce better data?

Because a guest who controls the record will fill it in. Ghorbel's reasoning runs through accuracy rather than compliance:

"This point is very important because data will come from there, and accurate data — accurate data will come from that. Complete data about luxury clients."

That is the argument worth understanding. Ghorbel is not asking for privacy as a constraint on personalisation. He is arguing that client control is the only route to data complete enough for personalisation to work.

A client who owns a profile and can revoke it will populate it. A client who suspects a platform is accumulating a permanent dossier will not, and thin data is what produces confident, wrong output.

Galina Fendikevich summarised the architecture back to him: the keys stay with the client, who grants a business scoped access to their own profile and manages what is visible. Ghorbel's response was "Exactly, exactly. Not the technology platforms."

What would the product have to do?

Five requirements come straight from the interview:

Let clients hold and control their own preference profile
Give operators scoped, permissioned access rather than a copy
Keep ownership away from the technology platform
Produce data complete and accurate enough to personalise on
Preserve discretion, since discretion is part of what the client purchased

Note what is absent from that list. Ghorbel does not ask anyone to run software inside their own building, and he does not describe a hotel-side database with better permissions. He describes a profile that belongs to the guest and travels with the guest.

Why does the order of his two requests matter?

Because the second request runs on the first. Ghorbel's other ask is AI designed around the real hospitality workflow, which he names as eight stages: inquiry, discovery, curation, booking, travel, follow-up, loyalty and repeat business.

"AI designed for hospitality professionals. Most AI tools are generic currently, and hospitality needs workflow-specific solutions."

He was asked what needs to be built and did not begin with a product. He began with a data-ownership architecture, and only then described the eight-stage workflow that would run on top of it.

That order is correct, and it is almost universally inverted in practice. Most companies selling into luxury hospitality build stage-specific tools and assume the client data problem belongs to somebody else. It does not. A workflow tool built on withheld data inherits the accuracy problem no matter how well the workflow is modelled.

What should a builder do with this?

Treat the consent layer as the product rather than a settings page inside something else. A client-held preference profile, portable across the advisors and properties one person uses, with scoped and revocable access, is the input every other product in this category needs, and it is the only design that makes a private client more willing to contribute rather than less.

If you are already building a booking, itinerary or concierge product, the question to answer this quarter is narrower. Where does your guest data come from, who is recorded as owning it, and would a client with something to protect agree to that arrangement in writing? Ghorbel is describing infrastructure and calling it a wish.