Which dish on your menu is losing money?
You find out which dish is quietly losing you money, from your supplier invoices, without stock software.
Who picks up the phone during service?
The allergy question, the table for nine, the closing time on a bank holiday: answered while you are in service.
The bookings and the recurring questions land in the lab instead of on a notepad by the till.
For your own business, or as a service you charge other businesses like yours for.
Nobody runs this lab yet. Take it, give it your hours and your prices, and it is yours.
Every lab has its own page. That is the floor: these are what answers on top of it.
Le Comptoir
online
A table for nine on Saturday, yes, at 7:30pm or 9:15pm, the 8:30 is gone. On the allergy: the risotto and the beef cheek are gluten free as served, the bass comes with a crumb we can leave off. The kitchen is not gluten free, so I say it plainly rather than promise. Which slot do I hold?
12:31 pm
Le Comptoir
online
Tonight: sea bass with fennel, beef cheek in red wine, and the vegetable risotto. Starters, the tomato and burrata or the chilled courgette soup. Dessert is one thing only, an apricot tart, and there are twelve. The lunch formula is 21 euros, starter and main or main and dessert. The bass is the one that goes first on a Thursday.
11:05 am
Hello, Your table for nine is held for Saturday at 7:30pm, on the long table at the back. We keep it until 7:50pm. On the gluten allergy: the risotto and the beef cheek are gluten free as served, and the bass comes with a crumb we leave off. Our kitchen is not a gluten free kitchen and I prefer to say it plainly rather than promise something I cannot hold. Above eight covers we ask for a single set menu, 34 euros a head, so the kitchen can send nine plates at once. Choose two starters, two mains and one dessert from the card and reply with them by Friday midday. No deposit, but a call if you are running late, the table goes at 9:15pm. See you Saturday, Le Comptoir
| Question | Asked | When | What ends it |
|---|---|---|---|
| Are you open on Monday? | 38 times | Sunday evening | Closed Sunday night and Monday, on the door |
| Gluten free dishes | 26 times | Before booking | Two dishes, and the kitchen is not gluten free |
| Table for more than eight | 17 times | Thursday and Friday | Single set menu above eight, 34 € a head |
| Terrace available? | 15 times | Sunny days, 6pm | Fourteen covers outside, first come |
+ 1 more rows
The Monday question is asked 38 times a month and the answer is already on your door. It is asked because nobody reads a door at 9pm on a Sunday.
Ai for restaurants always fails in the same place. It answers opening hours fine and goes quiet the moment anyone mentions a dish, an allergen or a table for nine. That is not a technology problem: it is that nobody wrote down the card, the allergens and the booking rules anywhere except in the head of whoever is at the pass. A bistro that puts those three things in once gets something that answers customers during service, on WhatsApp as on its own page, and a record where the recurring questions finally write themselves down.
Put there once, read by every magik.
Put there once by you, read by every magik, corrected when reality moves. Full on day one, unlike the collections below.
Worth more in month six than in week one.
The collections belong to the lab, not to any single magik. Every magik reads them and every run adds to them, which is why this lab is worth more in month six than in week one.
| Question | Asked | Answer kept |
|---|---|---|
| Gluten free at lunch? | 41 times | yes, 3 dishes on the card |
| Table for 9 on Saturday | 23 times | yes, booked the day before |
| Open on 15 August? | 17 times | closed, back on the 18th |
Invented for this page. Your Questions already answered collection starts empty and fills as you work.
It wears your name, not ours.
The same lab, under your name, your colours and your logo. Your customers never see ours.
On the Pro plan, and not needed to take a lab. A fully bespoke theme exists as an upgrade, hand built rather than self-serve.
And whatever you already use: any tool available through an API or an MCP server, connected with your own account.
A tool built for exactly your job, and only that, will go deeper at that one job. This is for the jobs nothing covers, or the ones spread across three tools today.
A website chatbot answers from a page written months ago. Here the answer is read from your hours, your card and your booking rules at the moment somebody writes, so a bank holiday closure decided this morning is true tonight. And it answers where the customer already is.
No, and that is worth saying plainly: it answers written messages, on WhatsApp or from the page of the lab. What it changes about the phone is the volume, since the questions about hours, allergens and large tables are the ones that ring most and the ones it takes.
Not as it stands: this idea answers questions and handles booking requests. Taking orders is a different job, with your menu, your slots and your lead times, and it would be another magik added to the same lab rather than something already included.
What you wrote in your card and your allergen list, and nothing else. On a dish whose composition is not in there, it says it does not know and offers to put them through to you. That is the only acceptable behaviour on this subject, and it is a rule you set yourself.
It applies your booking rules and your table plan: what you take, from what size you ask for a deposit, what you never take. A request outside that comes back to you instead of turning into a promise made during service.
One line in your hours and exceptions. Since the answer to a customer reads that resource at the moment they write, the exception is true straight away, including at 7pm on a Sunday. A fixed greeting on a page does not do that.
No, and a free tool that answers your customers under your name would be worth being suspicious of. It runs on your account, each run has a cost that is announced before it starts, and there is no licence per table or per cover. What you spend follows what you use.
A tool built for exactly restaurants and bistros, and only that, will go deeper at that one job. This lab is for the jobs no tool covers, or the ones spread across three tools today, and it runs under your name.
Every audience is still open.
Nobody has taken a square on this idea yet. You declare your audience when you take the lab (“roofers in Brittany”, “plumbers around Paris”), and two people can start from the same idea on two different audiences without getting in each other’s way.
And it wears your name, not ours.
The bundle describes a lab that does not exist yet : the jobs it would do, and an example of each output.
Open Knowledge Format : plain markdown, re-importable into any agent. No account, no lock-in.
You find out which dish is quietly losing you money, from your supplier invoices, without stock software.
How much rib of beef for twelve, and is it ready Saturday. Answered without leaving the block.
Orders arrive written down, with the quantities already worked out and the pre-orders in one place.
Sixty guests, four vegetarians, one gluten allergy: the quantities, the price and what you need to know, before you commit.
The quote, the quantities and the day-before checklist come out of one conversation.
Still comparing tools? Best AI for a chatbot on your site.