Reading the menu as a dataset
Every dish carries a margin and a demand signal. Here is how we read the menu the way an analyst reads a portfolio.
F&B Tech — Hospitality Operations Consultants
Most menus are arranged by tradition: starters, mains, desserts, in the order the kitchen learned them. That structure is comfortable, but it tells you nothing about which items are actually carrying the room.
When we treat the menu as a dataset, every item gets two coordinates — how much it sells and how much margin it holds. Plot those together and the menu stops being a list and starts being a map of where your money is made.
The interesting work is at the edges: popular low-margin items that need re-costing, high-margin items hiding at the bottom of a section, and the long tail of dishes that neither sell nor earn. None of that is visible from the pass; all of it is visible in the data.
The point is not to run the floor from a spreadsheet. It is to walk onto the floor already knowing where to look.
Related services
Menu Engineering →Working on something like this? Start a conversation →
Further reading
- Procurement
Cost stability without a crystal ball
You cannot control the market, but you can design a supply structure that absorbs its shocks. A look at procurement as risk engineering.
- Customer Insights
What guests tell you in the aggregate
A single review is an anecdote. Ten thousand reviews, normalised and mapped to the journey, are a strategy.