
Aged Ribeye
45-day dry aged, bone marrow butter
A guest scans the QR code on the table, or taps the NFC tag it is printed on, and orders and pays from their own phone. Your own photography, their own pace. Nothing to install, no account, and no waiting for someone to come and take the order.

A server who is not carrying orders back and forth is a server who is reading the table. The software takes the order; your people do the part it cannot.

45-day dry aged, bone marrow butter

Shoulder, ginger, long chilli

Minced lamb, cumin, flatbread, pickles

On the bone, preserved lemon, herbs

Goes with the Aged Ribeye
Malbec, Mendoza
The bill is already open on the phone that ordered. A table settles up and leaves without anyone fetching a card machine, which is the last ten minutes of every service handed back to you.
The whole thing happens in the browser that is already on their phone. There is nothing to download, no code to type in and no sign-up before they can read the menu.
One tag on each table carries both an NFC chip and a printed QR code. A phone that will not read one reads the other, so nobody is left holding a menu that will not open.
Guests pick food they can see. Your own photography, at the size the food deserves, rather than a list of names and prices.
Card details go from their browser straight to the payment provider. We never see a card number and neither does your floor.
Their first name lives on their own phone, so the second visit opens with it. Nothing about them is kept on our side.

When a guest adds something, the menu offers the one pairing your chef set for that exact dish, at that moment. Not the house favourite and not whatever carries the best margin. A suggestion a guest can tell was chosen by a cook is the only kind that gets accepted twice.
Floor
Tonight, 6pm to midnight
Orders through service
Peak 33 at 9pm
Orders arrive in a live feed with the table on them. Mark a dish sold out and it goes grey on every phone in the room in about a second. It runs in a browser tab on the machine you already have behind the bar.

You send photographs and a menu. We build it, print the tags, come in and fit them, then check in twice during the first month. There is no dashboard for you to learn and no configuration to get wrong.
We are not in the payment chain. The venue is the merchant of record, so your name is the one on the guest statement and the money lands in your own account on your own payout schedule. We could not hold your takings even if we wanted to.
Card details go from the guest browser to the payment provider. They do not pass through our servers, and there is no card form anywhere in the product.
An order is only marked paid when the payment provider confirms it with a signed message. Never when the guest lands back on the thank-you screen.
Every order carries a key, so pressing the button twice on a bad connection cannot charge a guest twice.
No names, phone numbers or email addresses are stored on our side. There is no customer database here to leak.
One flat monthly figure that does not move with three tables or with ninety, plus a share of what the menu sells. Card processing is billed separately by the payment provider at their rate rather than ours, and every one of the three is in the agreement before you start.
$0
A month, per location. Stop whenever you like.
0
Days free at the start, with nothing to cancel.
$0
Setup, build and the visit to fit the tags.
We build one section of your menu from your own photography, fit the tags in person and run it for thirty days. No setup fee, no contract, and nothing to cancel at the end.