AI assistant · N5 Complete system
Menu Engineering Tool Creator for Restaurants
Turns your POS sales, your menu and your costing —as they are— into an interactive menu-engineering report in a single file: what each dish leaves, what to protect, what to fix and what to push, with the month's three decisions in money and their assumption.
N5Complete system
Several chained pieces you install and operate over time, with their review cadence. It changes how the business runs, not one decision.
◆ This assistant 117 of the 170 published assistants are at this levelIs this for you?
What it does and what you get
- Most menus are judged by what sells most, and the best seller is almost never the dish that leaves the most.
- This assistant has your AI, with the tool's folder (the Menu Engineering Kit), organize your data into a case, and the folder's template does the rest with the house engine: the menu matrix, popularity within each category, cost with its date, the menu and its descriptions, and the minutes of an expert board.
- The AI does not write the figures: the engine calculates them, the same way every time.
- What is missing from your data is not invented: it is stated, with what it changes and how to ask for it.
What you end up with
An interactive single-file report: a dashboard with a headline, four traffic-light figures and the month's three decisions in money; the menu matrix with every dish's card and simulator; cost, mix by daypart and channel, menu copy, seal and a 12-week roadmap; the board's minutes and the technical annex. Plus the list of what is missing from your data.
EXAMPLE This is what you getAn example built with Tizón Norte, one of the house's fictional businesses.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: «Here is the POS export from May to September, the menu and the chef's costing spreadsheet, which is half done. I want to know which dishes hold me up, which ones eat the cost and what I do this month.»
Deliverable A · REPORTE_tizon-norte-2026-10-01.html, built with the folder's motor/armar_reporte.py: the case meets the schema and the five guardians come out green. This is how it opens:
Tizón Norte, a northern Mexican grill in Mexico City (fictional case). Sales from May to September since the menu change: 31 dishes, 585 POS rows, incomplete costing.
Your menu leaves $1,483,620 in contribution margin a month, and the grill is both what holds it up and what eats the cost.
| Figure | Value |
|---|---|
| What the menu leaves a month (before payroll and rent) | $1,483,620 |
| How much cost eats (theoretical food cost) | 33.4 % · house ceiling 32 % |
| Sales in star dishes | 21 % |
| Data confidence | 87 out of 100 |
The month's three decisions, in order of money:
- Lower the cost of the 300 g Skirt Steak to $126.40 — its food cost is 36.2 %: portion and supplier before price · $11,975 a month (assumption: same units).
- Lower the cost of the 400 g Rib Eye to $220.80 before pushing it — 37.5 %: the dish you promote does not go over 32 % · $11,379 a month (same units).
- Push the Charcoal Picanha from the menu and the server — it meets the ceiling (30.2 %) and sells little · $9,932 a month (assumption: +15 % units).
Figures in Mexican pesos, illustrative. The report interface is in Spanish today; the figures, dish names and your texts stay in your language.
The eight dishes that leave the most a month. The engine decides the quadrant with the averages of the food menu.
| Dish | Units/mo | Price | Cost | Leaves each | Leaves a month | Food cost | Quadrant | Data |
|---|---|---|---|---|---|---|---|---|
| 300 g Skirt Steak | 722 | $395.00 | $143.00 | $252.00 | $181,846 | 36.2 % | Star | B · June costing |
| 400 g Rib Eye | 302 | $690.00 | $258.43 | $431.57 | $130,507 | 37.5 % | Leaves and sells little | A |
| Half Charcoal Chicken | 446 | $265.00 | $91.20 | $173.80 | $77,549 | 34.4 % | Star · anchor | A |
| Skirt Steak Taco | 1,365 | $89.00 | $37.90 | $51.10 | $69,753 | 42.6 % | Sells and leaves little | A |
| Tomahawk for Two | 72 | $1,590.00 | $625.50 | $964.50 | $69,444 | 39.3 % | Leaves and sells little | A |
| Charcoal Picanha | 209 | $455.00 | $137.60 | $317.40 | $66,211 | 30.2 % | Leaves and sells little | A |
| Northern Cecina | 260 | $345.00 | $110.80 | $234.20 | $60,845 | 32.1 % | Leaves and sells little | B · no date |
| Molcajete Guacamole | 601 | $145.00 | $44.25 | $100.75 | $60,508 | 30.5 % | Sells and leaves little | A |
Reading: the skirt steak taco is the best seller and the one cost eats most; the lever is its portion and the supplier, not raising the price of the dish that brings people in. The rib eye and the tomahawk leave a lot per unit, but neither is pushed while it is over the ceiling.
The report does not fill in what is missing: it says so, with what it changes and how to ask for it.
| Missing | Dishes | What it changes | What to ask for |
|---|---|---|---|
| Costing | Beef Rib Crackling, Pastor-style Kid Goat, Grilled Corn | Their margin is an ESTIMATE and they are not recommended for pushing | The standard recipe with the latest invoice price |
| Current costing | 5 dishes older than 60 days, among them the grill's skirt steak | The cost used may be below the real one | Re-cost with today's purchase price |
| Costing date | 3 dishes | Nobody knows whether the cost is current | The price date of each ingredient |
| Complexity | 8 dishes | It does not break ties in the matrix | Six answers from the head chef per dish |
Eight seats of the expert board read the case and vote. They are AI agents, and the report says so.
| Seat | Vote | Decision |
|---|---|---|
| Supply chain and food cost | Conditional | Re-cost the grill this month |
| Financial | Conditional | Execute in order of money |
| Consumer behaviour | Yes | Do not remove the chicken or the enchiladas |
| Market and competition | Conditional | Tell the northern seal on the menu |
| Operations | Conditional | Protect the grill at peak hour |
| Marketing and launch | Conditional | Push only what already meets the ceiling |
| Brand and IP | Yes | Shield the house cecina |
| Technology | Conditional | Monthly POS export |
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 4 of 5 parts. Behind the wall is how it is built with YOUR data: **the POS mapping** row by row reconciled to the cent, **the to-do list** with what each missing piece of data changes and **the six chat lines** with the owner, the week and the indicator of each decision. The Tizón Norte report is fictional and shown whole: it is exactly what your AI builds for you with the folder.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 12 of the 24 fields in «My Restaurant», among them Restaurant name, Cuisine or concept and City and country. It does not ask out of curiosity: these are what make the answer speak about YOUR scale instead of an industry average — the same calculation on a business of another size returns a number you cannot decide with.
You fill them once and they apply across the library, so the second assistant you open already starts with them in place. Whatever you leave blank, the assistant asks for one thing at a time instead of inventing it, and says so before answering, so you know what it is working from.
Always up to date
Every assistant carries a visible version and date. When an AI changes how it works, the assistant's version goes up and you see what changed.
v2.1.02026-10-08Renamed «Menu Engineering Tool Creator» (Diego's decision, 2026-10-08: creators that deliver a house engine's universal folder share one naming) and its kit is no longer the library's own template: it is now the _MR_IngenieriaMenuUniversal folder derived by the Menu Engineering Engine, with its engine, validator, templates and example, packed from the original behind the house privacy veto (docs/72). The body names that folder's paths. «archivos» becomes optional, as the package declares: without an AI that makes files, the caso.json is dropped into the template. Same slug and address.v2.0.02026-10-01Menu-engineering integration (docs/69), at Diego's request of 2026-10-01. The assistant stops drawing the matrix in the chat: it builds the case for the Menu Engineering Kit, whose template carries the house engine unchanged. «Where to start» selector with four focuses; two of them are what the Sales Mix Analyzer and the Recipe Costing Builder did. Example: Tizón Norte, a fictional house from the roster.v1.1.42026-08-28Becomes FREE. The home page offers three freely readable assistants and two of its three links had been dead since the 2026-08-26 merge: MPV-0219 was absorbed and MPV-0217 retired, and nobody moved the `es_gratuito` flag to their heirs — the catalogue was left with a SINGLE published free card. This card is the heir the showcase copy already describes, so it takes that slot. From today `_QA/prueba_gratis_del_home.py` watches it: it reads the `data-slug` values from both home pages and requires each to be published AND free, so the next merge goes red before it reaches production.v1.1.32026-08-26TASK now uses the restaurant's data instead of naming it only in the header. Raising the version pushed the card past the cut-off of `motor/arraigo.py` and the gate exposed a debt that predates it: zero fields inside TASK.v1.1.22026-08-26Declares what it does NOT do. `motor/alcance.py` had flagged it as high risk —its title names a role, or its body promises to act on a system— and with no `limites_es`/`limites_en` the public page was promising by omission.Same method, another variant
Inside the app this is a single control: you press it and the assistant reframes itself, including the variants that don't appear here because they don't have their own page yet.
More assistants in this category
Names your new dishes and rescues the ones nobody orders: twelve candidates, four verifiable discard criteria …
N4 · Executable planRewrites your menu descriptions with the house four-phase formula, picks the register each dish needs and cuts…
N3 · Analysis with a verdictReads your sales mix like a consultant would: concentration per dish, popularity index by category, daypart an…
This assistant is free with an account
Create it and read the whole thing, adapted to your AI and personalised with your restaurant's data. No card, no plan: the free account opens every assistant marked as free.
