Before vs After: menu engineering in your restaurant
Before Masterestaurant you have a bloated menu with copied prices, dishes that sell but leave no margin, and a food cost you don't know per item. After, you have a 20-25-item optimized menu, food cost ≤32% on each one, and a menu strategy that pushes the dishes that actually build the business.
You've been building the menu for years. Every time a customer asked for something you didn't have, you added it. Every time the chef wanted to experiment, it went on the menu. Now you have 55 or 60 dishes, the kitchen is a labyrinth of ingredients, waste is driving up costs, and the customer takes ten minutes to decide. The worst part: some dishes sell very well and you celebrate them — but when you calculate the food cost you find that your star dish leaves pennies of margin or is actually costing you money. Your popular menu is silently destroying your profitability.
Menu engineering with the Masterestaurant method starts with data, not intuition or tradition. You cross sales volume with the contribution margin of each dish and classify them: stars, plowhorses, puzzles, and dogs. The ones that sell well and leave margin get pushed. The ones that do neither get cut. The result is a menu of 20 to 25 items where every dish serves a strategic function, food cost is controlled at ≤32%, and AI automatically recategorizes the menu when ingredient prices update.
| Before (no method) | After (with Masterestaurant) | |
|---|---|---|
| Menu size | ✕55–60+ items accumulated with no exit criteria | ✓20–25 items optimized by margin and sales volume |
| Basis for adding a dish | ✕Customer request, chef idea, or business tradition | ✓Contribution margin ≥ target + projected sales volume |
| Food cost per dish | ✕Unknown or estimated; some exceed 50% without anyone knowing | ✓Calculated and controlled: ≤32% hard ceiling per item |
| Dish classification | ✕Popular or not popular — nothing more | ✓Stars, plowhorses, puzzles, and dogs: different actions for each |
| Visual menu design | ✕Long list with no visual hierarchy to guide the customer's decision | ✓Menu designed to direct attention to the most profitable dishes |
| Updating after cost changes | ✕Manual, slow, and almost always forgotten until margin has already dropped | ✓AI automatically recategorizes the menu when ingredient prices change |
Analysis: before (A) vs after with Masterestaurant (B)
What it looked like beforeBefore
- 55+ dish menu with no idea which ones generate real margin
- Prices set by copying competitors or by habit
- Best-selling dish with 48% food cost: a 'success' destroying margin
- Kitchen with 200+ different ingredients, high waste, complex operations
- Customer paralyzed by the menu: too many options, slow decisions
What it looks like after the MR methodMasterestaurant
- 20–25-item menu where every dish has a strategic function
- Food cost ≤32% calculated and verified before going on the menu
- Stars identified and pushed with visual design and server suggestions
- Simplified kitchen: fewer ingredients, less waste, faster service
- AI recategorizes the menu when ingredient prices change
Why the method makes the difference
A long menu looks like a sign of abundance and expertise. It's actually a sign of lack of criteria and fear of cutting. Every dish that doesn't rotate occupies kitchen space, generates waste, complicates staff training, and splits the team's attention. When I analyzed the menus of 8,400+ restaurants across 43 countries, the pattern was consistent: the most profitable ones have fewer, clearer items, with better contribution margin per item.
Menu engineering isn't cutting for the sake of cutting: it's building a menu where every item works for the business. Visual design matters too: customer eyes follow hierarchies on the menu, and the MR method leverages that to guide them toward higher-margin dishes. With AI integrated, every time a key ingredient price updates, the system recalculates the food cost for every dish containing it and tells you if any exceeded the 32% ceiling.
The numbers that matter
“I went from 58 dishes to 22. The chef cried a little. Customers decided faster. Waste dropped 34%. And net margin rose 9 points in two months. The long menu was my biggest hidden cost.”
How to start your transformation this week
And with AI?
Optimize menu engineering, descriptions and the photos that sell most. Diego F. Parra is an expert in AI applied to restaurants.
Free tools to apply this now
Do it with Masterestaurant tools
The MR standard recipe and costing course are the two tools you need for real menu engineering: calculate food cost per item, classify it, and build a menu that works for the business.
Diego F. Parra — International consultant, expert in creating and scaling restaurants and in AI applied to restaurants, foodtech and HORECA. Methodology applied in 8.400+ restaurants across 43 countries · Expert in Artificial Intelligence applied to restaurants, hospitality and food businesses · 20+ years in restaurants, catering, large events and business growth · Author of the book «From Slave to Owner» (Amazon) · International keynote speaker for the HORECA sector.
Frequently asked questions about menu engineering in restaurants
How many dishes should an optimized menu have?
What do I do with dishes customers ask for even though they're not on the new menu?
How does AI categorize my menu items?
Does menu engineering mean raising prices on every dish?
Related content
Your menu can be your most profitable competitive advantage
With the Masterestaurant method you build a 20–25-item menu where every dish has food cost ≤32% and a clear contribution margin — backed by Diego F. Parra and 8,400+ restaurants across 43 countries.