For professional kitchens
A dish should not leave when the chef does.
Record the person who owns the dish, once, while they are still standing at the pass. What they actually did, in their words — with the things nobody ever wrote down marked as questions instead of quietly guessed.
Four versions of one problem
The recipe was never the problem. The parts nobody wrote down are.
The chef leaves
Notice is worked, handover happens, and the dish still changes. The spec sheet has the ingredients and none of the judgement — how dark the roux goes, how the pan sounds when it is ready. That never got written down because nobody thought to ask while there was still somebody to ask.
The chef is off
One sick day and a signature dish is cooked by somebody reconstructing it from memory and a photograph. It goes out. It is not the same, and the person who would have noticed is at home.
The second site opens
The same dish on two menus, drifting apart from the day it launches. Not carelessness — the recipe only ever fully existed in one kitchen, and a copied document does not carry the parts that were never in it.
The new starter
Trained by whoever is on shift, which means trained slightly differently every time. The laminated card was written eighteen months ago by somebody who has since left.
Training the next shift
The chef is off. The dish still has to go out.
Sick, left, or on the other site. RecipeMirror is not a kitchens product yet — this is how the engine we already have would put a house method in a trainee’s hands without inventing the bits the chef never said.
Beat 1 of 5
When the chef is not there
Sick, notice served, or already gone — the dish still has to go out. The spec sheet has ingredients. The judgement never got written down.
Illustration on the demo dish — not a live kitchen, and not a product you can buy today.
Transcript
- When the chef is not there. Sick, notice served, or already gone — the dish still has to go out. The spec sheet has ingredients. The judgement never got written down.
- Record the house method once. The person who owns the dish, at the pass, while they are still standing there. Not a YouTube import. Their words, their timings, the bits nobody wrote down marked as questions.
- A station card for the next shift. A trainee follows how this kitchen does the dish. Amounts the chef never fixed stay questions — never filled in for them.
- Someone else can cook it tonight. The card is in their hands, not a video on a phone. One step at a time, with the cue the chef actually gave.
- One kitchen, one dish. That is the whole ask for a first pilot. There is no kitchens product yet — this is the shape we would build first.
What already works
The engine is built. It has been pointed at home cooking.
It reads a demonstration
Video, a recording of somebody talking through it, a page from a book. Steps, ingredients, timings and the reason behind a step — with a link back to the second of the source each one came from.
It scales without inventing
Ingredients scale by real arithmetic. Times do not, because a time multiplier is a made-up coefficient that gets believed precisely because it looks like arithmetic. The batch planner says what changes and what you have to judge.
It asks instead of guessing
An amount nobody stated arrives as a question. In a kitchen that means the questions get asked of the chef while the chef is still there, which is the entire point of recording them at all.
The first artefact
House method, then a station card. Not YouTube.
A trainee follows how this kitchen does the dish, after the chef who owns it has gone. Paste-a-link from the internet is the wrong door: liability, drift, and someone else’s method. Record the person at the pass once. Print a card a starter can cook from — amounts they never fixed stay questions for the chef, never filled in.
The buyer is the head chef or the trainer. The trainee uses the card. There is still no kitchens product — this is the shape we would build first, and you can see it on the demo dish.
See a station card of the demo dishWhat does not exist yet
There is no kitchens product today.
This page is here to find the first kitchen to build it with, not to sell you something. Being specific about that is cheaper than being found out later:
- No multi-site dashboard, no roles for a group, no per-location reporting.
- No billing, no contract, no published price.
- No pilot has run. No professional kitchen has used this.
- Nobody outside the founding team has yet cooked a dish end-to-end, in any kitchen.
What does exist is the ownership model underneath: a location belongs to an organisation, data belongs to a location, and access is enforced in the database rather than in the app. That was designed in from the start so a restaurant group is an addition, not a rewrite.
Talk to us
One kitchen, one dish, one chef who is thinking about leaving.
That is the whole ask for a first pilot. If it is useful you will know inside a week, and if it is not we would rather find that out from you than from a pricing page.
You can also write to hello@recipemirror.com.