AI assistant · N4 Executable plan
Growth Plan Architect for Restaurants
Finds the growth levers your restaurant already has at hand — check size, visit frequency, slow dayparts, new guests — and orders them into a 90-day plan by how much profit they leave.
N4Executable plan
A plan with owners, deadlines and the metric you review. Not advice: an agenda someone can execute on Monday.
◆ This assistant 23 of the 164 published assistants are at this levelIs this for you?
What it does and what you get
- Growth does not always mean another location or an ad budget: almost every restaurant has hidden sales in tables that turn slowly, hours when the room sits half empty, guests who would come more often if someone invited them, and checks that rise with one well-asked question.
- This assistant estimates what each lever is worth in YOUR case, picks the three with the best effort-to-profit ratio, and builds the 90-day plan to pull them with your current team.
What you end up with
An inventory of growth levers valued in your currency, the three chosen with their rationale, and a 90-day plan in table form with biweekly actions, an owner for each, and the number that confirms whether the lever moved.
EXAMPLE This is what you getAn example built with Sazón de Origen, the house's fictional restaurant.Not your data: your result is built with YOUR restaurant's.See the full example →Sample result
The owner asked this: «I have already decided: this quarter I raise the lunch ticket and I move the platform orders over to my own delivery. Put that into a calendar that holds.»
A decision cannot go into a calendar. A deliverable can.
| What the owner decided | Translated into something observable | The number that confirms it |
|---|---|---|
| «Raise the lunch ticket» | Three written suggestive-sells on Bandeja de la casa, Sancocho de tres carnes and Trucha al ajillo, each with its two-sentence script | Average ticket for the 12:00–14:30 window, Tuesday to Friday, against today's 48,000 COP |
| «Move orders to my own delivery» | One WhatsApp message per order delivered, carrying the own channel and a reason to use it next time | Orders through the own channel over total delivery orders, week by week |
What falls out of the plan: the third location the owner mentioned in passing. It does not move the margin goal within 12 months and it does not start within 90 days. It goes back to the table with a date, not into a drawer.
The yardstick that orders the quarter: across the 4,458 tickets in the month, every 1,000 COP of average ticket is 4,458,000 COP of additional sales. That is not the goal: it is what each fortnight is measured with.
SUPUESTO: the commission the delivery platform charges today comes from the contract the owner has in front of him, not from a sector figure; here it stays as A FIGURE TO CONFIRM. The plan does not depend on its exact value: what decides the fortnight is how many orders migrate to the own channel, not what the platform charges. If the commission turned out lower than the owner believes, the lever still holds —the customer data becomes his— but it drops below the lunch ticket in priority.
| Fortnight | Action | Prerequisite | Owner (role) | Close | Confirming number |
|---|---|---|---|---|---|
| 0 | Sign the standard recipe for the 3 star dishes, with gram weights | — | Chef, location 1 | Day 14 | 3 signed sheets, not 2 |
| 0 | Define which dishes do NOT go out on delivery | Standard recipe signed | Owner | Day 14 | Exclusion list posted at the pass |
| 1 | Write and rehearse the 3 suggestive-sells with the floor team | Standard recipe signed | Floor manager | Day 28 | 6 servers say them without reading |
| 2 | Suggestive-sells live: location 1 only, lunch only | Fortnight 1 closed | Floor manager | Day 42 | Ticket for the Tue–Fri window |
| 3 | WhatsApp message on every delivery order | Exclusion list | Administrator | Day 56 | % of orders through the own channel |
| … |
The rule that holds the table up: two fronts per fortnight and one active lever per owner. With 24 people and one owner, the third front does not run late — it gets abandoned, and it takes the morale of whoever started it with it.
Why fortnight zero exists: growing on top of an operation run by eye spreads the disorder across the whole business. The three suggestive-sells push the three star dishes; if the standard recipe is not signed, each location serves them differently and the suggestive-sell teaches the customer to expect something that does not always arrive. Fortnight zero is not preparation: it is the first fortnight that can fail.
Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.
This is 2 of 3 parts. The six-fortnight calendar and fortnight zero can be read here. Behind the wall is the dependency matrix with the critical path —what takes the quarter down if it slips fifteen days—, the 30-minute meeting template that exists to kill actions, and the list of what does NOT get done, each line with its reason and its return date.
See the full example — free accountWorks with these AIs
How to use it
Which of your data it uses
This assistant works with 9 of the 23 fields in «My Restaurant», among them Your main guest, Main goal this year and Strong and slow dayparts. 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.
v1.2.02026-08-20Rooting: the sheet declared the house up top and then spoke to just any restaurant. The TASK now filters by meta_principal —a lever that does not move it in 12 months stays out—, lands the suggested dishes on platos_estrella, keeps the owner out of momentos_fuertes and bans judging the fortnight against ventas_mes; the checklist guards razones_consumo and the first fortnight starts with tamano_equipo. Swapped, not added: 799 words before, 798 after, and the duel is still 100.v1.1.12026-08-14Spelling: Spanish accents restored in the prose. No field marker, link or meaning changed.v1.1.02026-08-13Rewritten under the margin mandate: sequence and dependencies of what was already decided, a standardization fortnight zero, 6 numbered steps, 5 named output blocks with owner, date and progress number, trade traps and a verification checklist. Duel 48.4 -> 100.v1.0.02026-08-09Version inicial de la biblioteca viva.v1.3.02026-08-25Brought in line with the house doctrine in the 2026-08-25 batches: the response ladder and the rooting in My Restaurant's data. The version was bumped at the time and the note was NOT written; guardian G11 caught it on 2026-08-26 and it is declared here, with the gap acknowledged rather than covered up.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
Designs your restaurant's complete strategy on a single coherent page: who it exists for, how it intends to wi…
N4 · Executable planChoose at the top which plan you need and over what horizon. In this one —targets by period— it turns your goa…
N4 · Executable planIt builds the system that runs the business without you being everywhere: the calendar of daily, weekly and mo…
Included in the always-growing library
Access to every published assistant, adapted to your AI and personalised with your restaurant's data, updates included.