The short version
The same facts as the rest of this section, in the order you would read them once. There is no file to download and no separate story: a deck that says something the product does not is a deck somebody has to correct later.
The short version
-
What it is
One web product for places that serve food and drink: you write a menu, publish it, print a code for each table, and guests read the menu in the browser already on their phone. No app for the guest, no account for the guest.
Measured: The journey has 6 steps, and each step names the controller that runs it.
-
What is built
Menu, publication, printable codes, photos, branding, languages, branches, reports, ordering from the table, a team and ratings live in one account, not as separate products.
Measured: 12 parts, each read from the product inventory.
-
What is not built
The product is not a point-of-sale system, does not take money from a guest, does not do reservations, has no third-party integrations and has no in-store app. Those are stated as plainly as the capabilities are.
Measured: 7 stated limits, carried on the public home page as well as here.
-
What it costs
The base journey costs nothing and plans add capability on top of it. Every price shown on this site is read from the plan catalogue, never typed into a page.
Measured: Prices are read from the plan catalogue and published at /pricing without an account.
-
What has been committed
The commercial commitments a buyer asks for — availability, incident notice, service credit — are written as terms but left without values, on purpose, until something measures them.
Measured: Empty on purpose, in config/sla.php: availability_target_percent, measurement_source, incident_notification_minutes, service_credit_percent
-
Where it runs
One virtual server carries the application, the database and the uploaded files. Everything else that touches customer data is named, and named only while it is actually switched on.
Measured: 6 entries, read from configuration and the credential vault at render time.
-
How it is checked
Claims are tied to files and behaviour is tied to gates. A capability that disappears from the product cannot keep being sold on a page, because a red test says so before a reader does.
Measured: 25 claims tied to a file, 10 gate scripts present.
-
What nobody knows yet
Demand, what a restaurant will pay, whether a restaurant keeps using it after the first month, and what it costs to serve one at scale. None of that is measured anywhere in this code, and this section does not pretend otherwise.
Measured: Not measured. The honest answer to an unmeasured question is that it is unmeasured.
Talking to us
Questions about what is built, what is not, and how a claim is checked are answered from the same inventory these pages are drawn from.