The prep cook taps in.
She lets herself in the back door, taps her four-digit PIN on the kitchen tablet, and she's on the clock. No binder, no paper sheet. The schedule already knew she was coming.
Run the whole restaurant. From one login. Fancy Fork is a fine-dining room in Regina, Saskatchewan — and our first restaurant. One service, open to close. The screens are the shipped product; the day is a composite of real ones.
Play this epicShe lets herself in the back door, taps her four-digit PIN on the kitchen tablet, and she's on the clock. No binder, no paper sheet. The schedule already knew she was coming.
Table 5 orders the tasting menu. The ticket fires straight to the kitchen display — coursed, timed, allergy-flagged. The espresso machine hasn't even warmed up yet.
Every dish fired at lunch quietly consumed its recipe from stock. Now dinner prep starts, and the count says demi-glace is at 0.8 litres — with Friday's reservations heavy. It flags it now, not at 6:40 PM.
While the room is full, the AI that lives inside the system reads the same numbers the owner will see tonight — and speaks up on its own when something matters.
He counts the till against what the system already knows, closes the day in four steps, and locks up. By the time he's on his porch, Tuesday is on his phone.
Fancy Fork — Tuesday closed. $4,812 · 61 covers · labour 27% · till variance +$1.50
Orders land on the kitchen display the second they're sent — with allergy flags and course timing, no paper tickets to lose.
Recipes deduct ingredients as dishes fire — first-expiring stock first — so counts stay honest without a clipboard.
A four-step closeout counts the till against expected takings — variance shown to the cent before anyone goes home.
The line, where a missed ticket becomes a remake — and the close, where the drawer either matches or nobody ever finds out why. Everything else on this page is convenience. These two are the margin.
A ticket that sits is a table waiting, and a ticket that goes missing is a dish cooked twice and sold once. The screen sorts itself by how long each ticket has been waiting, so the oldest is never the one nobody noticed.
Most nights end with somebody counting cash and comparing it to a number they have to work out themselves. Here the till already knows what it took and how. You count once, and it tells you the variance — four steps, and none of them is arithmetic.
Review Z-report
Mia H. · closed 22:41 · Saturday
Three tiers, and no surprises in the bill: what every Mangrove product comes with, what dining rooms, cafés and takeaway needs on top of that, and what else you can switch on. Mangrove for Restaurants includes all of it — you never pay per tool, and there is no module you have to buy.
Add-ons cost nothing extra. They are separate only because most businesses of this kind do not switch them on in the first week.
Need something none of these do? The studio builds it — same team, and we have done it before.
Software demos well on the happy path. What decides whether you keep it is the hour it goes wrong. These are four that happen to a restaurant, and what happens next.
Every dish fired consumed its recipe from stock, so the count fell all afternoon in the open — flagged at 2:30, not at 6:40.
They ask for a manager PIN on the spot. The void goes through, and the manager’s name is the one on it.
The till keeps taking orders on the tablet it is already running on and settles up when the connection returns.
Takings by method are already known. You count once, and it tells you the variance instead of asking you to find it.
A dining room turns over its staff faster than almost any business there is. This is priced per person who logs in — at a rate mainstream restaurant software charges in about thirteen months — and there is no setup quoted on top of it.
Buy a year at a time and renew, or buy several years up front — renewal pricing is confirmed with you at renewal. The 24/7 option is the service previously called Premium, not a second charge on top of it. Your data exports whenever you want it.
What software like this is worth is not a number we get to invent. Below is what other people measured, with the source on every one — set against a $450 bill.
Read those as figures for this kind of software, published by other people — not as measurements of Mangrove for Restaurants. Two of the three come from companies that sell a remedy for the problem they measured; we have named all three, and dated them, so you can weigh that yourself.
$7.23 back on a dollar is a ratio, and the dollars underneath it were much larger dollars. Mainstream software at a typical $35 per user per month is about $420 a year for each person who logs in, and quotes the setup on top of that. We are not going to pretend the ratio multiplies cleanly onto a smaller bill; nobody has measured that. What we can say is which half of it we control. Per person, we made the denominator $450 — and there is no setup line under it.
Everything above · $450 per user / year · no implementation project