← All posts

The best AI in your venue is the AI your guests never see

Research shows AI in hospitality gets embraced when it works invisibly in the background, and distrusted the moment it stands between guest and maker. That is exactly what moonies is built for.

aioperationshospitality
A quiet kitchen pass with plates and prep laid out, the work behind the door the guest never sees.

Food Inspiration recently ran a good piece on AI in hospitality: Volop kansen voor restaurants bij slimme inzet artificial intelligence. It draws on research by final-year students at Hotelschool Maastricht, and it contains one finding that lands right where we think every day.

The core of it: whether AI gets embraced depends almost entirely on whether you can see it. Applications that speed up or improve a process without the guest noticing are widely accepted. Systems that place themselves between guest and maker meet resistance. Invisible wins. Visible gets distrusted.

That sounds obvious once you read it, yet most AI stories in hospitality are about the visible part: the ordering kiosk, the QR code, the chatbot that takes reservations. And that is precisely where the problem the research names begins.

A restaurant runs on contact

A venue runs on people receiving other people. That is not the packaging, it is the product. Anything that organises distance between the guest and the person who made the thing chips away at exactly the reason someone went out instead of staying home.

Under efficiency pressure that distance creeps in on its own. The kiosk saves a trip. The QR code saves a quick word. On their own each looks like a gain, but added up they push contact into the background, in a trade that lives on that contact. No wonder most operators, and their guests, eye front-of-house AI with suspicion. They feel the distance, even when nobody names it out loud.

The opportunity is behind the room

The research flips it around. The room for AI is not in the dining room, it is in the kitchen and the little office behind it. In the work the guest never sees, and never needs to.

That is the work that eats the most time and earns the least credit. Keeping track of which supplier you call when the delivery comes up short. Remembering how a dish was built when the regular cook had the night off. Handing the shift over cleanly to the crew coming in after you. None of it is glamorous, but it is what an evening stands or falls on.

AI that lightens that kind of work costs the guest nothing and gives the maker time back. Nobody at the table notices, and that is exactly why it works.

Where moonies sits

moonies is built on that invisible side on purpose. It is the back office of the venue: the work that happens out of view to keep the place running. We never touch the guest. There is no moonies screen on the table, no moonies voice on the phone, nothing from us standing between you and the person you are serving.

What we do do happens behind the door. Recipes and prep that hold up even when the regular cook is away. The knowledge of the house in one findable place instead of one person's head. A handover that genuinely sets the next shift up. Dull, important work, and precisely the work that swallows the time.

And once that work lives in one place, AI can actually do something with it. Not at the table, but in the background. An analysis of where your margin leaks, or which dish barely earns anything at today's supplier prices. The kind of work you would otherwise spend half a Sunday on with a spreadsheet, if you got to it at all. The guest notices none of it, and that is exactly the point.

The point is not that AI takes over the contact. The point is that AI clears the mess underneath it, so the people in the venue can keep their attention where it belongs: on the guest in front of them.

The question that matters

So the question is not "where do I put AI in the dining room." Guests answered that one long ago, and the answer is reluctant. The question is: which invisible work can I make disappear, so more time is left for the visible?

We worked the same idea out from two other angles: start small and start with your own data, and capture your venue's knowledge before it leaves with a departing colleague.

That is exactly the side the research points to, and it is the only side we want to be on. Curious what that looks like in practice? Take a look at the kitchen, or read how we think about the venue.

Give your restaurant's knowledge a fixed home.

Get started