Menu Engineering: Mathematical Models to Restructure Your Offering by Popularity and Marginal Profitability

Chapter 1 — What menu engineering really means at scale

Menu engineering is a two-variable optimization model —popularity and dollar contribution margin— that decides which dishes carry your EBITDA when you move from one location to a network. It is not a pretty color chart. The mistake I see again and again: scaling a menu designed by the chef's intuition. In 2026, with input inflation that has shifted prime cost by 4 to 9 points in 18 months, replicating that bias multiplies the leak. Treat each dish as a portfolio asset: it has a return (absolute margin per guest) and a demand (menu index). The goal of a restaurant group leader is not the most profitable dish by percentage —a classic trap— but the mix that maximizes absolute margin per guest, replicable across 5, 10 or 40 units. That is where the real money begins, and where most operators quietly bleed it. Percentage margin lies when you scale; dollar contribution margin is what pays payroll and rent.

Chapter 2 — Why percentage margin is a trap

A real cash example: dish A sells at 12 USD with 68% margin, leaving 8.16 USD per unit; dish B sells at 24 USD with 55% margin, leaving 13.20 USD. The chef's intuition pushes A because its percentage shines, but B generates 62% more dollars per guest. Multiply that by 180 covers a day across 30 units: roughly 27,000 USD/day of added contribution that the pretty menu leaves on the table. Diego F. Parra repeats it in every Masterestaurant audit: the board does not collect percentages, it collects dollars. Restructure the offer so the dish with the highest absolute margin is also the most visible and the most ordered, not the one the cook defends out of pride. That single shift changes the unit economics of the entire network for good. Correct classification crosses two measurable axes: popularity index (threshold above 70% of the expected category average) and absolute contribution margin above the menu average.

Chapter 3 — The four-quadrant matrix as a portfolio model

That yields four quadrants. Star: high popularity, high margin —protect it, it is the 20% of dishes that usually delivers 60-70% of total margin. Workhorse: high popularity, low margin —redesign the recipe or raise it 0.80-1.50 USD without touching volume. Puzzle: low orders, high margin —give it visibility, reposition it on the menu, train the server to suggest it. Dog: low popularity and low margin —cut it or redesign it; under intuition it survives through the chef's emotional attachment, in the model it is decided by its quadrant and price elasticity. On a 40-item menu, purging 6 Dogs typically frees 11-14% of kitchen complexity without touching sales. The inherited approach freezes the pilot menu and copy-pastes it into the franchise manual; the MTIE model documents the algorithm so each franchisee restructures with the same criterion, not their own. The difference is operational and measurable.

Chapter 4 — The documented algorithm, not the franchisee's judgment

When a franchisee in another city faces an input 15% more expensive, they do not guess: they apply the same reclassification formula and move the affected dish to the right quadrant. I have seen it in dozens of operations: without a written algorithm, the second kitchen improvises and theoretical vs real cost diverges 3-6 points in 90 days. With the documented algorithm and a quarterly recalculation, that variance stays under 1.5 points. Diego F. Parra brings a single table to the board: each dish, its quadrant, its dollar margin and its action. That is what a CFO signs off, not a color chart. Standardizing the criterion is what makes quality scalable. The traditional menu does not measure the variance between theoretical and real cost per kitchen; the model turns it into the KPI that catches margin leaks before they contaminate the network's EBITDA. Operational definition: theoretical cost is what the recipe card dictates; real cost is what the inventory yields.

Chapter 5 — Theoretical vs real cost variance as a network KPI

A healthy gap lives between 0.5 and 1.5 percentage points. When it exceeds 3 points in one unit, you have waste, theft or inconsistent portioning —and across 30 units, 3 points of leak on 4 million USD of annual sales is 120,000 USD that vanish with no explanation. The model forces you to measure this variance per Star and Workhorse dish every week, because those move volume. Diego F. Parra insists: restructuring does not end at menu design, it lives in the weekly dashboard that compares the two figures and triggers the corrective action before month-end close. Before replicating the menu, run it against three measurable stress scenarios, not against a hunch. Scenario one: input inflation of +12% on the three main proteins —how many dishes drop from Star to Workhorse? If more than two, the menu is not ready to scale. Scenario two: actual vs planned sales mix with a 15% skew toward lower-margin dishes —recalculate the weighted margin per guest.

Chapter 6 — Stress-testing the menu before opening the second unit

Scenario three: rent and payroll rising 2 points on sales —does the break-even hold with the current mix? At Masterestaurant, Diego F. Parra uses this stress table as a board filter: no second unit opens unless the menu survives all three blows with a weighted margin above 68%. Restructuring here, in the model, costs 2 weeks; doing it with the network already open costs 6 months of eroded EBITDA and a franchise manual you have to rewrite from scratch. Price elasticity tells you how much you can raise a dish before volume falls more than the per-unit gain. Practical cash rule: on Workhorses —high popularity, low margin— a 4-7% increase usually moves volume less than 2%, so total contribution rises. If a dish sells 900 units/month at 14 USD and you take it to 14.90 USD, even losing 20 units you gain roughly 780 USD extra per month per dish; across 25 units, nearly 19,500 USD/month.

Chapter 7 — Price elasticity: raising prices without losing the guest

The mistake I see: raising the whole menu by a flat percentage, which punishes elastic dishes and gives away margin on inelastic ones. The model prescribes surgical increases by quadrant and by measured elasticity, not blanket ones. A Dog is not raised: it is cut or redesigned. A Puzzle is not raised: it is made visible. This price discipline, applied equally in every network unit, turns a profitable menu into a replicable margin machine. The intuition menu optimizes percentage margin; the mathematical model optimizes contribution margin in dollars per guest, which is what actually pays payroll and rent at scale. The inherited approach freezes the pilot menu and replicates it; the MTIE approach documents the classification algorithm so each franchisee restructures with the same criterion, not their own. In intuition, a 'Dog' dish (low popularity, low margin) survives out of emotional attachment; in the model it's removed, redesigned or repositioned based on its quadrant and price elasticity.

Chapter 8 — The differences that decide whether your network scales or bleeds margin

The traditional menu doesn't measure theoretical vs actual cost variance across kitchens; the model turns it into the KPI that detects margin leakage before it contaminates the network's EBITDA. Restructuring by popularity and marginal profitability shields unit economics: without that shield, every expansion CapEx amplifies a business that was quietly losing money.