Our story
Every printed menu is out of date by the time it reaches the table.
Not badly out of date. Just a little. A price that moved when onion doubled. A dish the kitchen stopped making in March. A seasonal section that ran for eight weeks and has been sitting there since.
Every venue we looked at was working around the same constraint. A printed menu costs real money to reprint, so changes get saved up until there are enough of them to justify the run. In the meantime the servers carry the corrections in their heads, and the guest reads a document that is quietly wrong.
The workarounds are familiar. A sticker over the old price. A laminated insert that goes missing. “Market price” written next to something that has a perfectly stable price, because nobody wants to commit it to paper. A dish left on the menu all year that the kitchen will talk you out of in April.
Seasonal menus made the problem obvious
In Gujarat the winter list is not a marketing exercise. Undhiyu, ponk and ubadiyu are available while the produce is available and not one week longer, and every kitchen in the state reorganises around that for about eight weeks.
A printed menu gives you three bad options: reprint twice a year, print an insert that gets lost, or leave the items up all year and disappoint people for ten months. Most kitchens pick the third. That is how you end up with an undhiyu on the menu in April that nobody intends to cook.
A menu that is wrong about what is available teaches diners to ask the server instead of reading. Once that habit forms, the menu has stopped working.
So we separated the code from the card
The QR code on your table encodes one address. The menu behind that address is yours to change whenever you like, from wherever you are, in as long as it takes to type a number. Nothing you do afterwards reaches the paper.
That is the entire idea. Everything else in the product exists to make the page behind the code worth scanning: 25 venues are live on it today, with 119 dishes priced.
What we decided, and why
- 01
The code is an address, not a menu
Your QR code encodes one URL and nothing else. Change a price, take the fish off, swap the whole design — the printed code is untouched. That is the difference between a card you reprint quarterly and one you print once.
- 02
A menu is a card, not a web page
We set dishes with dot leaders running to the price, the vegetarian mark before the name, and figures in the display face. Those are printed-menu conventions, and they exist because they work. Most digital menus throw them away and end up looking like a delivery app.
- 03
The guest installs nothing
No app, no account, no email capture before someone can read what the kitchen is cooking. A scan opens a page. That page is the whole product.
- 04
Fast on bad signal, or it does not count
A menu is opened on a phone, in a room full of phones, by someone who is hungry. We serve it as static HTML from a cache, so the page is painted before a heavier site has finished negotiating.
What we are not building
No ordering. No payments. No delivery, no POS, no table reservations, no loyalty scheme. Those are real products and other people build them well. Adding them here would mean a slower menu page and a guest who has to think about software before they can read what is for dinner.
We do one thing: the card behind the code, and the code on the table.
Browsing rather than listing? See the menus already live in Surat.