Home / About

A restaurant should own the people it feeds.

GetMenu exists because the software a small kitchen relies on had started charging like a partner while behaving like a landlord.

Why we built it

The order arrives. The relationship does not.

A delivery platform is very good at bringing a stranger to your door once. What it will not do is tell you who that stranger was, so the second visit has to be bought all over again — at the same rate.

Meanwhile the actual work of a small kitchen happens on WhatsApp. Orders, riders, the family group chat where somebody asks whether the machine is fixed. We did not think restaurants needed to be moved off the thing that already works. We thought the ordering should be moved onto it.

So GetMenu gives a restaurant its own storefront, sends every order into the WhatsApp groups the team already lives in, and charges a flat monthly fee that does not grow when the restaurant does.

What we will not do
  • Take a percentage. Not of an order, not of a delivery fee, not of a tip.
  • Own your customers. The list is yours, exportable, on any day including your last.
  • Sell your data. We are paid by you, so we work for you. There is no second customer.
  • Hold card details. Payment happens at the door, in cash or on your machine.
  • Lock you in. No minimum term. Tell us to stop and we stop.
How it is built

Four rules we hold ourselves to

These are not marketing lines. They are decisions in the code, made because the alternative costs a restaurant money on a busy night.

The price shown is the price charged

The checkout preview and the real charge are produced by the same calculation, not two that are meant to agree. A total is always the sum of the lines printed above it — never a separate sum that might disagree by a fils.

A locked-out kitchen is worse than a free feature

If our billing system is ever confused about what you have paid for, it lets you through. Wrongly allowing a feature costs us a little money. Wrongly denying one stops a restaurant serving dinner.

Order messages never queue behind marketing

Transactional and marketing messages travel in separate lanes that cannot merge. A promotional blast can never delay the ticket that tells your kitchen an order came in.

One restaurant can never see another

Every restaurant's data is separated at the database level, not by a filter in the application. There is no query in the system that can return another kitchen's orders by accident.

Where we are

Honest about the stage we are at

RUNNING IN PRODUCTION
  • Ordering, end to end
  • WhatsApp order fan-out
  • VAT invoicing and PDF receipts
  • QR print packs for tables
  • Loyalty tiers and stamp cards
  • Google Wallet cards that update themselves
  • Self-serve trial signup
BUILT, NOT YET BATTLE-WORN
  • Prize games and scratch cards
  • Referral programmes
  • Group ordering at a table
  • Building-level campaigns
  • Ramadan mode
  • Apple Wallet, awaiting a certificate

Tested and ready, but no restaurant has leaned on them in a real service yet. We would rather say so than pretend otherwise.

We are early on purpose. If you sign up now you will get more of our attention than you would in a year, and your requests will shape what gets built next.
The company

Who you are dealing with

Registered entity

ANUNZIO INTERNATIONAL FZC

Tax registration number

104239743800003

Where we operate

United Arab Emirates, all seven emirates.

Where your data lives

Hosted in the Dubai region, on infrastructure that keeps each restaurant separated from every other.

Getting in touch

Send us a message

See whether it suits your kitchen

Fifteen days with everything switched on, and no card details asked for.

Chat with us