Ask your restaurant anything. It has been paying attention.

Atlas reads every service — every dish opened, every hesitation, every bill — and answers in the words you would use on the floor, with the number behind it and the change already drafted.

Book a demo See the insights it sends

Answers from your own data
Drafts the fix
Says when it is not sure

Atlas findings: a supplier price rise that has pushed a dish under its gross-profit target, and an unrostered peak — each with the action already drafted — AtlasA real screen, not a mockup

One guest, one dishExample service

1
On the table
Truffle Risotto
£24
Sea Bass
£22
Burrata
£14
Tartare
£18
2
What AtTable recorded
- Opened the Truffle Risottothree times · 22 seconds
- Read it for 8sclosed without adding
- Ordered the Sea Bass+£22 to the ticket
3
What Atlas made of it
Atlas
Your most-opened dish is your least-ordered one, and guests are stopping at the price.
Opened
156
Ordered
12
Converts
7.7%
Category
15%
A two-week test at £21 with a description that leads with the truffle — drafted and waiting for you to launch it or bin it.

What you can ask

In your own words.

“How did this week go?”Takings against the same week last month, split by table, pickup and the till.

“Which dishes get looked at but not ordered?”Every dish where opens and orders are far apart, ranked by the money in the gap.

“Why isn’t the Truffle Risotto selling?”Where guests stop — the price, the description, or where it sits on the menu.

“Which regulars have stopped coming?”How many guests have gone quiet, why, and what a typical one spent.

“Did the midweek offer make money?”What the discount gave away against what the orders carrying it were worth.

How it answers

Three moves, one of them yours.

You ask
In whatever words you would use on the floorNo report to build, no filters to set, no dashboard to learn. A question typed the way you would ask a manager.
It fetches
Atlas goes and gets the data itselfIt has tools for revenue, dishes, guests, discounts, campaigns and recommendations, and picks the ones the question needs.
You get
A number, a plain-English read, and a draftNot a chart to interpret. The figure, what Atlas thinks is causing it, and the change already built and waiting for you to approve.

What it watches

Everything the rest of the system records.

Your menuWhat guests open, how long they read it, and where they put it down. The half of your menu a till has never been able to see.

Your guestsWho comes back, how often, what they order and when the pattern breaks — built from real visits, with consent on the record.

Your moneyWhich pound came from a campaign, a code, a recommendation or ordinary trade, credited once and never twice.

Its own adviceWhich insights you acted on and what happened next, so a suggestion that never works stops being made.

Against a dashboard

Including the row a dashboard wins.

A dashboard is not wrong, it is just answering a different question. It can tell you what happened. The rows underneath are the ones you would otherwise have to work out yourself, between services, from numbers that do not volunteer them.

What a reporting dashboard can do compared with Atlas
Capability	A dashboard	Atlas
Tells you what sold	Yes	Yes
Tells you what almost sold	No	Yes
Answers a question you type	No	Yes
Explains why a dish underperforms	No	Yes
Names the guests who stopped coming	No	Yes
Writes the fix and waits for approval	No	Yes
Says when the evidence is too thin to act on	No	Yes

It reads all of it

Atlas has nothing of its own to record.

Atlas is only as good as what the rest of the system sees — which is why it lives on top of the ordering, the tickets and the till rather than beside them.

Revenue & insights

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