01
One customer profile
The concept is built around a shared guest identity rather than separate records for restaurant, wellness, stay and events.
PRODUCT CONCEPT · BABOU / KAIF
One guest account across a multi-format hospitality ecosystem
BABOU / KAIF is a product concept for connecting restaurant, wellness, memberships, events, stays, payments, bookings and personalised communication in one customer journey.
FUNCTIONAL CONCEPT
The digital layer follows the business ecosystem
The underlying KAIF 2.0 working concept combines wellness spa & sauna, panoramic restaurant, lounge and view terrace, spa services, gym, kids space, apartments and villas. The product concept turns those separate physical experiences into one connected guest account.
Guest IDone identity across services
Bookings & wallettransactions and reservations
Loyaltymemberships and personalised communication
WHY THIS PRODUCT
A multi-format venue should not make the guest start over in every department
02
Connected transactions
Bookings, payments, memberships and service usage can sit inside one product logic and customer history.
03
Personalised communication
A unified account creates the foundation for relevant recommendations, loyalty mechanics and cross-selling between business lines.
PRODUCT LOGIC
From physical ecosystem to digital ecosystem
01
Restaurant & hospitality
Guest account, reservations, service discovery and transaction history.
02
Wellness & spa
Booking logic for services, memberships and repeated wellness usage.
03
Stay & accommodation
A shared customer identity across apartments, villas and other on-site experiences.
04
Retention layer
Loyalty, memberships and personalised communication designed around the combined customer journey.
CURRENT STATUS
A product concept, not a claim of completed deployment
This page describes the current functional product concept and its connection to the KAIF 2.0 business model. It does not claim that every module has already been built or deployed. Final UX, integrations, payment stack, data model and implementation scope remain subject to product specification and development.
NEXT STEP