The thread that runs through every stay

The booking is a moment. The stay is a relationship. For decades, the tools we sold hoteliers optimised the moment and forgot the relationship — and the OTAs were only too happy to own what was left.

What we mean by a thread

A thread is continuity. It is the front-of-house manager who remembers that you take your coffee black, that last time the radiator was slow, that it’s your anniversary again.

Software has been very good at transactions and very bad at memory.

We think that’s backwards. The transaction is commodity; the memory is the moat.

The problem with fragmented tools

When a guest’s preference lives in one person’s head, it leaves with them. When it lives in a spreadsheet, it’s never read in the moment. When it lives in your PMS, it’s buried under twelve fields that no one checks on a busy check-in morning.

A thread means the information travels with the guest, not with the system.

What this looks like in practice

Mae remembers that the Okafor party always asks for a high floor. She knows that Eleanor Pryce has had a noise complaint before and should not be placed near the lift. She knows that the Khan party celebrating an anniversary might appreciate a quiet word about the spa.

None of this requires a meeting. None of it requires anyone to remember. It just happens, because the thread is there.