moonmoot

The complete restaurant playbook: structure and stack for a restaurant that survives its good months

Operating playbook · by the Moonmoot team · updated 2026-07-04

A restaurant that only watches its bank balance is flying by feel. The ones that last are built around one weekly number, prime cost, and structured so the kitchen holds its standard when the owner is not on the pass.

The diagnostic companion, how this trade really works and where it breaks, is on the Moonmoot for restaurants page.

How to structure it, in order

The moves that let the business grow beyond you, sequenced. Each is one step toward a business that runs, and sells, without its owner.

1
Install a weekly prime-cost rhythm before anything else

Food plus labour as a share of sales, every week, is the vital sign. Structure the week around producing it, or you will discover problems a quarter too late.

2
Write the recipes and specs down as costed, repeatable standards

A costed recipe is both a margin control and the thing that lets a second chef reproduce the dish. It is operations and transferability in one document.

3
Give the reservation book an owner and a no-show policy

Covers per shift and no-show rate are revenue you control. Deposits and confirmations turn a fatalistic loss into a managed one.

4
Treat delivery as a separate business with its own P&L

At platform commission, dine-in economics do not survive delivery. It needs its own menu and its own maths, or it quietly funds a loss.

5
Keep licence, lease, and food-safety evidence transfer-ready

An alcohol licence that will not transfer or a short lease can wipe out value a buyer would otherwise pay. This is checked first in any sale.

The complete positioning stack

Every capability the business needs to fully see and grow. The point is not owning tools, it is having them connected so nothing leaks between them. Each is tagged with what it drives.

POS with costed recipes

Dish-level margin from a POS where cost recipes are actually entered, so you can engineer the menu on data.

Revenue + Profit
Prime-cost reporting

Weekly food and labour as a share of sales, the single number that predicts survival.

Profit
Reservations + no-show control

A book that reports covers and no-show rate, with deposits or confirmations built in.

Revenue
Inventory + variance

Theoretical versus actual usage, where theft, waste, and over-portioning hide.

Profit
Connected accounting

Real books fed from the POS, so profit is provable in diligence, not reconstructed.

Profit + Value
Compliance + lease vault

Licence, lease assignability, food-safety records, dated and ready.

Value

The order to work it: revenue, then profit, then value

Doing these in the wrong order wastes effort. Here is the sequence that compounds for this trade.

Revenue

Engineer the menu and tighten no-shows first: both lift takings without a marketing spend.

Profit

Then run prime cost weekly and measure inventory variance. Most of the money is here, not on the top line.

Value

Then make the books provable and the licence and lease transfer-ready. That is what a buyer actually pays for.

The edge most owners miss

The restaurant that watches prime cost weekly is playing a different game

Two restaurants can look identical from the street and live on opposite sides of the survival line, decided entirely by whether someone is watching food and labour cost every week rather than every quarter. The structure and stack here exist to make that one number impossible to ignore, and to make the standard survive the owner's night off. Everything else in a restaurant is downstream of those two things.

Get this running on your restaurant

The playbook is the map. Your board reads your real tools and works it with you, week by week. Try the free read, talk to us, or just ask.

Get your free instant readTalk to us

Not ready for either? Just ask us a question. No card, no signup, ever for the read.