odel-labs

01The service list, each name arriving with what the house already knows about them.

Module

GuestIQ

Shape

SaaS, AI

Parts

Sync, memory, service notes

Runs

Live from the booking system

Built for

Hospitality

State

Live

It is a private internal app for a restaurant group, reachable only by named staff accounts. There is no guest-facing side and no public sign-in, which narrowed the build and removed most of the risk with it.

Bookings sync live from the group’s booking system and arrive with the visit count, the usual table, the dietary alerts and the dates worth marking. The host sees it before the guest is through the door, which is the only moment it is worth anything. After service, a host types 1 ordinary sentence about how it went and the system structures it. No form, no dropdowns, no tagging, because a host at 11pm will not fill in a form and every system that asked them to has been abandoned.

Consent is signed at the desk, and identity and preferences sit in separate databases. That separation is not a technical flourish. It is what lets the group hold a preference history at all, and it was the first question their lawyer asked.

The memory stays when the staff leave, and a regular at one venue is a regular at every venue. That is the whole point of it. Years of floor knowledge used to walk out of the door with the person who had it.

One sentence typed at the end of a shift, and what the system made of it.

Years of floor knowledge used to walk out of the door with the person who had it.

Screens

Drawn, not photographed. The captions say what each screen shows.

02Visit count, usual table, dietary alerts, and the dates worth marking.
03A sentence in plain English, and the structure it became.
04What was signed at the desk, and which database each field sits in.

What next

If years of floor knowledge leaves with the person who has it, that is the module.

Send an email