Coming soon

Test the change before you commit to it.

Run two versions of a dish — a price, a description, a position — against real guests at the same time, and keep the one that actually won. A version that takes more money while making less of it does not count as a winner here. It is built, but not yet switched on for venues — this page describes how it will work.

  • Two live versions
  • Measured against each other
  • Checked against food cost
A full restaurant dining room during service
ExperimentsEvery table, a set of decisions
What it does

Know what sold, what almost sold, and what caused the difference.

  1. Both versions run at onceHalf your guests see the new version and half see the current one, during the same services, so the result is not really a story about the weather.
  2. Traffic is a real gateYou choose what share of guests takes part, and a holdout can sit outside it entirely. The current menu is one of the versions being measured, not an unmeasured default.
  3. It reports in money, with the guests behind itEvery result shows how many guests saw each version, and a winner comes with what it is worth a month at your current traffic — not just a percentage.
  4. And in the money you keepA discount comes off every plate, so a price cut can lift takings and still leave you poorer. Where the dish’s recipe is costed, the result carries gross profit per guest beside the takings — and a version that wins the first while losing the second is not offered as the winner at all.
  5. It waits for enough evidenceA result that has not seen enough covers is reported as unfinished instead of being called early because it looks good.
How it runs · in order

From the first step to the last.

  1. Day 0
    Pick the dish and the changeA price, a description, a photograph or where it sits on the menu. One change at a time, so the result means something.
  2. Day 0
    Choose how much of the room takes partSet the share of guests entering the test and hold the rest back entirely. Everyone who enters sees one of the two versions.
  3. Days 1–13
    Both versions run through real servicesNobody has to do anything. Guests are assigned as they scan, and the totals build against each version separately.
  4. Day 14
    Keep the one that paidThe result is reported in money against covers, and in gross profit where the dish is costed. If it has not seen enough covers to be sure, it says so instead of calling it — and if the version that won took more while making less, it says that instead of handing you a trophy.
A laid table before service
What the till never seesBefore the order
What changes

Tonight, versus tonight with it on.

Now: Change a price on a hunch and never find out whether it helped.
With AtTable: Change it for half the room and read the difference.
Now: A good month gets credited to the new menu and the sun.
With AtTable: The new version is compared against guests who saw the old one.
Now: A price cut lifts takings, gets called a win, and nobody ever works out the margin.
With AtTable: Takings and gross profit are both on the result, and the one that lost you money is not the winner.
Where it sits

Experiments is part of revenue & insights.

It runs on the same menu, the same tables and the same bill as everything else — nothing to integrate, nothing to reconcile.

Ordering

Take the order at the table, the counter or the kerb, and get it to the kitchen.

Bookings

Fill the diary — and give a forgotten table a chance to be sold again.

Food cost & stock

Cost the menu on what you are actually paying for the food.

Suppliers

Compare what you ordered, what arrived, and what you were billed for.

Team & shifts

Build the rota, publish it once, and know who did what on the floor.

See all twenty features
Start here

Stop guessing at prices.

Run it against half the room, and keep the version that made money — not just the one that took it.

45 days to go live · 21 days free once you're live · No card required · No minimum term