Who is this assistant for?

You know you have to move a price and the following Monday scares you. Someone told you to raise it 10% and nobody told you what happens if people buy less. You charge the same in the dining room as on the app, where they take a commission off you. Your goal for the year says lift margin without raising menu prices.

Moving a price blindly is scary, with reason: nobody knows how many guests can be lost before the raise turns into a bad idea. This assistant turns that anguish into comparable numbers: three scenarios with visible assumptions and the indifference point showing how much volume you can concede and still end ahead.

AI assistant · N3 Analysis with a verdict

◆ Included in the annual plan🧮 Costs, Pricing and Profitabilityv1.2.0 · 2026-08-20

Price Simulator for Restaurants

Simulates what happens to your total margin if you move a price, with three guest-reaction scenarios and the exact unit count where the raise stops paying off.

Depth

9/23

Your data

Compatible AIs

Steps to use it

Depth of the resulttap a level to see what you get

◀ Put out today's fireRun the year ▶

📊

N3Analysis with a verdict

Crosses YOUR numbers and takes a stand, with a table, units and currency. Not options: a recommendation you can defend.

◆ This assistant 24 of the 164 published assistants are at this level

Is this for you?

What it does and what you get

Moving a price blindly is scary, with reason: nobody knows how many guests can be lost before the raise turns into a bad idea.
This assistant turns that anguish into comparable numbers: three scenarios with visible assumptions and the indifference point showing how much volume you can concede and still end ahead.

What you end up with

A dish baseline, a conservative-middle-optimistic scenario matrix with each total cash margin, the indifference point in units and a recommendation with an explicit condition.

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

Sazón de OrigenFictional contemporary Colombian restaurant in Medellín, 2 locations, 6 years in business. Every sample result in the library comes from this same case. Fictional restaurant

The owner asked this: «I want to raise the Bandeja de la casa by 7%. How many customers can I lose before the increase stops being worth it?»

One dish, not the menu: the Bandeja de la casa, the highest-rotation of the three star dishes. Last 30 days, net price before consumption tax. Standard recipe signed 41 days ago — within the 3 months, so it can be simulated.

Dish	Current price	Recipe cost	Unit margin	Units this month	Total margin
Bandeja de la casa	60,500	22,400	38,100	620	23,622,000

Price to test: 64,700 (+6.9%), which on the menu with consumption tax lands at 69,900 — inside the 28,000-to-72,000 band, so this is still a price simulation and not a repositioning. New unit margin: 42,300.

The break-even point: 23,622,000 ÷ 42,300 = 559 units. Today it sells 620. You can lose 61 units, 9.8%, and end up exactly where you are today. That is the number, and it is the only thing this simulator asserts.

SUPUESTO: the three scenario drops —5, 10 and 15 points— are not measured elasticity: they are the three numbers the owner chose to read the risk, and they are declared as such. Source: the session itself. Confirmation comes from counting units for four straight weeks after the move, not from this table. If the real drop were 12 points, the move would lose 0.5 M a month instead of gaining.

SUPUESTO: the 32% food cost ceiling this assistant's costing rule carries is not an industry benchmark: it is the house's own cap. Source: the assistant's own body (MASTERESTAURANT® Methodology). The Bandeja runs at 37.0% today at the current menu price; if the ceiling the house wanted to defend were 37%, this simulation would have no reason to exist.

Scenario	Assumed drop	Units	Unit margin	Month's total margin	Difference vs today
Today	—	620	38,100	23,622,000	—
Optimistic	−5%	589	42,300	24,914,700	+1,292,700
Middle	−10%	558	42,300	23,603,400	−18,600
Conservative	−15%	527	42,300	22,292,100	−1,329,900

None of the three is a forecast: they are three readings of the same arithmetic under three written assumptions. The middle scenario gains nothing —it drops 18,600 pesos a month, practically sitting on the break-even point— and that is what to look at: the move is only worth it if the real drop stays below 9.8%.

A conditional recommendation, and its condition is not arithmetic. This house's declared goal is to lift operating margin from 8% to 14% in 12 months without raising menu prices. Under that constraint this move does not get executed, and there is no elegant way to say it. One way out remains that never touches the printed menu: move only the delivery app's uplift, from 15% to 23%. It is worth 0.3 M a month in the optimistic scenario and 0.06 M in the middle one. On the house's 214.0 M that is barely over a tenth of a point of the six the goal asks for. It is not the lever.

The same arithmetic, run backwards. To leave the margin of the best of the three scenarios —24.9 M— without touching the price, the Bandeja's recipe cost would have to fall from 22,400 to 20,315: 2,100 pesos a plate, 9.3% of the costing. That costs not a single customer. In this house the Bandeja's price is not the problem: the problem is the 22,400.

Illustrative example generated with a fictional restaurant. Not a promise of results, not a client case.

This is 2 of 3 parts. Behind the wall is the **same move read channel by channel** —dining room, own delivery and app, each with its own break-even point, because commission changes the arithmetic— and the **four-week reading board** that confirms the real reaction, with the assumptions checklist one per line.

See the full example — free account

Works with these AIs

Claude para Excel — the best for this assistant The only one that enters YOUR spreadsheet instead of working on a copy: it reads your tabs, calculates and leaves the result in a new dated tab without overwriting anything. Ask it for the sheet map before it calculates.

How to use it

Pick one dish to simulate and gather its current price, approximate cost and last month's units sold.

Paste the assistant into your AI and define with it one or two new prices to test.

Compare scenarios, note the indifference point and, if you move the price, measure units for the next four weeks.

Which of your data it uses

of 23

This assistant works with 9 of the 23 fields in «My Restaurant», among them Menu price range, Average check (with currency) and Best-selling dishes. 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.

Menu price rangeAverage check (with currency)Best-selling dishesAverage monthly salesApproximate food cost (%)Why they visit (consumption reasons)Active sales channelsStrong and slow daypartsMain goal this year

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.

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.

What triggers it

the input went upmy own decision