Skip to content
European companyFounded in 2014Built and operated in EuropePayments secured by Stripe
System statusSupportFree assessment
Gradax

Covers, not clicks

Websites, booking and ordering for restaurants, built around filling tables on the nights that are not full.

Get a free quote Book the free review
Sold as
One contract
Starts with
A free review

The vendors we build on, operate and resell.

  • Cisco
  • HPE
  • Dell
  • Lenovo
  • Veeam
  • WordPress
  • WooCommerce
  • Google
  • Stripe
  • Zoho
  • Atlassian

A restaurant's website has three jobs and usually does none of them: show the real menu, take a booking, and be correct about opening hours. Menus published as a PDF that will not open on a phone are still, somehow, the most common failure in the trade.

The commercial problem underneath is that Friday fills itself and Tuesday does not. Every marketplace and delivery platform will happily sell you Friday covers at a commission; nobody helps with Tuesday, and Tuesday is where the margin is lost.

The search side is not separate from that. "Restaurants near me", cuisine plus a neighbourhood, and "open now", almost entirely on a phone within an hour of eating. Ranking for those means the pages exist, the business is verified where it operates, and the reviews are real and recent.

What we build for restaurants

How a booking moves through a restaurant

A table is won on a phone in the afternoon and lost if anything between the booking and the bill goes missing.

  1. Booking taken

    Phone bookings during service go unanswered, so online booking keeps taking them while the floor is busy.

  2. Reminder before the night

    No-shows leave tables empty on full nights, so a reminder the day before lets guests cancel and the table be resold.

  3. Service

    Allergies noted on the booking never reach the kitchen, so dietary notes travel with the booking onto the ticket.

  4. After the meal

    Guests leave and are never heard from again, so the booking becomes a contact you can message with permission.

Services that go with it

What usually comes next, once the first piece is running, and why it matters in this trade.

Software we built for businesses like yours

A product we are building now, shown here as the work we do.

HoReCa POS (in development)

HoReCa POS, our till and back office for restaurants, is in development and is built to keep selling through internet and printer outages.

See how it works
A waiter taking an order at a restaurant table

What people in this trade ask us

Why not just use a booking platform?
Use one for discovery if it genuinely brings new guests. Do not pay a commission on regulars who searched for your name, which is what most restaurants are doing without noticing.
Is a PDF menu really a problem?
Yes, twice. It is unreadable on a phone, and its contents are invisible to search, so you rank for nothing you actually cook.
How do we fill a Tuesday?
With a list you own and permission to message it. That is slower to build than buying covers and it is the only version that keeps working.
Should we take deposits for bookings?
For large tables and peak nights, yes. A deposit is what makes a group of twelve call to cancel instead of simply not arriving, and it should stay off ordinary tables for two.
Can online orders go straight to the kitchen?
Yes, if your till accepts them, otherwise to a kitchen printer. We check what your till supports before quoting.

The infrastructure under it

Managed by the engineers who build the software, on the same contract and the same bill.

Application Hosting

Booking and ordering peak in the same two hours every evening, and an outage then empties the book.

See how it works
Hands typing application code on a laptop.

Cyber Security

Card payments and guest contact lists are what attackers look for in a restaurant's systems.

See how it works
Two monitors showing security logs in a dark room.

Priced and ready to order

A fixed scope and the price on the card. The line on each one is why it matters in this trade.

What one contract covers

  • One contract. The build, the infrastructure and the work that brings people to it, on one invoice.
  • A named team. The person on the first call stays on the project. No account managers, no handoffs.
  • Operated, not delivered. We keep it running after launch: patching, backups, monitoring and the phone when it breaks.
  • European hosting. Servers in Europe, run by us, with the data staying where you expect it to.
  • Monthly reporting. What changed, what it cost and what it produced, in language you can forward to a board.
  • No lock-in. The code, the domains and the accounts are yours. Leaving is a handover.

What keeps it running

More in retail, food and property

See what is costing you customers before you spend anything.

A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first.

Book the review See what we have built
  1. 01You tell us what is not working
  2. 02We review the site, the search presence and the enquiry path
  3. 03You get the three fixes worth doing, and what each is worth