A wedding, a rehearsal dinner, a pop-up, a venue night. Build the event, brand it, print the QR and let every guest ask the food their own questions instead of finding you during service.
It sounds like the hard part of an event isn't cooking it it's the forty-five minutes when the food goes out and suddenly you're the only person who knows what's in anything. Someone's aunt is asking about gluten. A groomsman wants to know if the chicken has dairy. The venue staff you met two hours ago are guessing on your behalf.
A printed card can't answer a follow-up. A server hired for the night can't know your recipes. And the one person who does know is carrying a tray.
A QR code on the table can answer all of it, all night, without you.
One account holds all of them. Each project is self-contained its own menu, its own look, its own code, its own night.
Name it, set the date, and upload the menu a photo of your prep sheet, a PDF from the client, a spreadsheet, whatever you have. Item fields stay light because an event menu is twelve dishes, not two hundred. Allergy detail stays unlimited.
Its own loading screen and its own colors the couple's photo, the family name, the birthday, the company logo. Guests open something that looks like the event they came to, not like a vendor's software.
Each project gets its own code. Put it on the tables, the bar, the buffet card, the program. Guests scan and ask. You track how many are chatting from your phone while you plate.
Built in an afternoon. Live for one night. Yours to clone for the next one.
A restaurant runs forever and wants to be found. An event runs for a day and wants to be private. Four things work differently because of that.
A project is built around its window the rehearsal, the day, the brunch after. It knows when it starts and when it's done.
An event never appears in any restaurant list or anywhere on the public site. The only way in is the code you handed out.
When the date passes, the chat closes politely with a thank-you instead of erroring out on a guest who scanned an old program in the car.
Most caterers run the same core menu with different names on it. Keep the finished project and copy it forward instead of rebuilding.
Three weddings and a corporate lunch in the same month, each with its own menu and its own client. Track which are live and how many guests are asking, across all of them, from one screen.
Coordinators, wedding planners, banquet halls, breweries and barns that host. The questions guests would have brought to you get answered at the table instead.
Supper clubs, food trucks at a festival, tasting nights, private chefs. Anything with a menu that won't exist tomorrow and doesn't deserve a permanent account.
One account. Every event you'll ever run.
Start free and set one up before you commit to anything. Pay per event when you need one, or subscribe if you're running them constantly.
The permanent version. Your full menu, allergens, calories, hours and specials, answered for every guest and every server plus chains and multi-location under one brand.
For Restaurants →The same line turned inward. Where things are, how they're made, notes on the food and the wine useful the night you're working with staff you just met.
For Training →