Menu Engineering · San Diego
Most menus get priced by taking the plate cost and multiplying by three. That gives you a number. It does not give you a profitable menu.
Menu engineering reveals which items drive true profit versus those that just look high-margin. By repricing and repositioning based on real performance, you unlock hidden revenue. Whether applied in a Michelin-starred dining room or a high-volume neighborhood spot, the financial blueprint remains identical
The core mistake
Food cost percentage tells you how efficient a dish is. It does not tell you how much money that dish puts in your account. Those are different questions, and the second one is the one that pays your rent.
Here is the arithmetic, using round numbers to make the point:
Dish A wins on food cost percentage. Dish B puts $1,000 more in the account on the same 100 covers.
Most operators know this in theory. Almost none have their menu built around it, because the reports they get back are organized by cost percentage, not by contribution. The number that matters is already in your POS. It is just not on the front page of the report. Pulling item-level mix out of Toast is the first thing I do.
Food cost is still worth controlling. It is one half of prime cost, and prime cost decides whether the year works. But controlling it and pricing against it are two different jobs.
How dishes sort out
Once you plot every dish by how often it sells against what it contributes, the menu sorts itself into four groups. What you do about each one is where judgment comes in, and where most advice gets it wrong.
Protect these. Do not touch the recipe, do not move them on the page, and do not let a cost increase quietly erode them. Most of the work here is defensive.
The common advice is to reprice or cut. Often wrong. This dish may be the reason a table walks in. The fix is usually in the plate cost or the spec, not the price.
The best opportunity on most menus. Nobody is ordering your most profitable dish because of where it sits and how it reads. Placement and description move these before price ever needs to.
Usually cut. Not always. Some of these exist so a specific guest at a specific table has something to order, and removing them costs you the whole cover.
The process
This is not exploratory work. The sequence is fixed, the inputs are things you already have, and the output is a repriced, repositioned menu with the reasoning attached so your team can maintain it after I am gone.
01
Item-level sales counts straight from your POS, covering enough weeks to see a real pattern rather than one good Saturday. No site visit needed for this part.
02
Yield-adjusted, not invoice-adjusted. A case price divided by portions on paper is not what the dish costs you once trim, waste, and actual portioning are in the number. If you want to see the difference on one dish yourself, the recipe costing calculator is free.
03
Every item plotted by popularity against contribution. This is the moment most operators find out their signature dish is carrying the kitchen and their highest-margin plate is buried in the bottom right of page two.
04
Pricing architecture across the whole menu rather than item by item, plus layout, sequencing, and how each dish reads. A good portion of the recovery comes from placement, which costs nothing and does not touch your prices.
05
Four weeks later, same report, same method. Either the mix moved or it did not, and if it did not we find out why. This is the step almost nobody does, and it is the one that separates a menu project from a menu opinion.
It is not a redesign. I am not touching your concept, rewriting your chef's food, or handing you a template that worked somewhere else.
It is not a blanket price increase. Some items come down. Some stay exactly where they are and simply move on the page.
I fix the plumbing. I do not touch the soul.
Before you call
What is menu engineering?
Menu engineering is the practice of analyzing every item on a menu by how often it sells and how much profit it contributes, then repricing, repositioning, or reworking items based on where they land. It treats the menu as a financial instrument rather than a list of dishes.
How is this different from menu design?
Menu design is about how the menu looks. Menu engineering is about what it earns. A designer makes your menu beautiful. This work makes it profitable, and the two are compatible as long as the design serves the sequencing rather than fighting it.
Do you need my POS data?
Yes, and that is most of what I need. Item-level sales counts plus your recipes and invoices. No site visit, no staff meetings, no project plan for your team to manage. If you run Toast, the export takes about five minutes.
Will you make me raise my prices?
Often the opposite. Some items are priced above where their quadrant supports, which is exactly why nobody orders them. Placement and sequencing move more contribution than price changes do, and they cost you nothing.
How long does it take?
Two to three weeks from data handoff to a repriced menu, then a re-read four weeks after it goes live. Your time in that is roughly one call at the start and one at the end.
Does this work on a bar program?
Same math, different inputs. Pour cost replaces plate cost and the mix moves faster, but the four quadrants behave identically. I wrote about why your best-selling cocktail is usually your worst margin if you want the beverage version.
Is this a standalone project or part of something bigger?
Either. It stands alone as a fixed-scope project. It is also one of the first things I look at inside a margin recovery engagement, because the menu is usually where the fastest recovery sits.
Next step
Thirty minutes on the phone and I can usually tell you where the obvious contribution is sitting before we ever talk about an engagement. If there is not enough on the table to be worth the work, I will say so on the call.