The evening this is about
A recipe that lives in one head is a single point of failure with a holiday booked. The dish is right when that person cooks it and approximately right when anyone else does, and nobody can say what it costs, because nobody wrote down the yield.
- The sauce is different on the chef's day off and the regulars notice before the kitchen does.
- A new cook asks how much goes in and is told "you'll see".
- The same dish is plated three ways in one service.
- Nobody can say what a portion costs, because the base is a recipe inside a recipe.
What it actually does
- Holds every recipe with quantities, yield and loss — including recipes made of other recipes.
- Works out the allergens through the whole tree, so a sauce inside a dish inside a menu still declares its mustard.
- Shows the cook what the finished plate should look like, in the language they read.
- Takes the stock off when the dish is rung up, from the recipe rather than from a guess.
The detail that matters
The recursion is the point. A cake is a base, a ganache, an insert and a glaze; a bolognese is a stock that is itself a recipe. Systems that treat a dish as a flat list of ingredients cannot cost either one, and cannot tell you that the allergen came in two levels down.
What it does not do
- It does not teach anyone to cook. It writes down what your kitchen already decided, so the same thing comes out on Tuesday.
- It does not photograph your food. Where there is no photograph, it shows a drawing — and a drawing promises the guest nothing it cannot deliver.
We would rather you read this before the call than find out after.
Where it sits
Ordering, plating standards and the delivery chaos. Digital Chef is one of three tools in Kitchen & Supply, and it runs on the same guest, booking and menu data as the rest of the Suite — so nothing is typed in twice.
Fifteen minutes, no slides.
Tell us how your venue runs and we will say plainly whether Digital Chef helps — and which two or three tools to start with.