The Seoul Sandwich Co. launched with eight items. Not because they did not have more ideas — they had a menu of twenty-two items ready before opening. Eight is what we launched with. The decision was deliberate, and it was the right one.
Every operator I have worked with has felt the pull toward more. More options feel like more value to the customer. More items feel like insurance — if someone does not like one thing, there is always something else. More variety feels like ambition.
All of that logic is wrong, and the consequences of acting on it are measurable.
What a long menu actually costs you
A menu item is not just a recipe. It is an ingredient procurement decision, a storage decision, a prep schedule decision, a staff training decision, and a waste management problem. Every item you add multiplies complexity across the entire operation.
At launch, when your kitchen crew is still learning the choreography of the space, when your prep timings are estimates rather than certainties, when your vendor relationships are untested — this complexity is not manageable. It looks manageable on paper. It does not feel manageable at 1pm on a Saturday when the line is backed up and the second cook has not come in.
Increases mise en place — more ingredients mean longer morning prep, which means either earlier starts or a rushed kitchen going into service.
Raises food cost variance — more SKUs means more opportunities for waste, over-ordering, and spoilage from unpredictable item popularity.
Slows ticket times — staff working across 20 items are less fluent than staff who know 8 cold. Speed is muscle memory. Muscle memory needs repetition.
Dilutes your identity — a customer who can identify what you are famous for is a customer who comes back. A menu of 25 items tells them you haven't decided yet.
The Seoul Sandwich case
Eight items. Four sandwiches, two sides, one drink option, one dessert. That was it for the first six weeks.
What that short menu gave us: the team hit consistent ticket times by week two. By week four, the prep schedule was running twenty minutes shorter than the opening week because the crew had found the efficiencies that only repetition reveals. Food cost variance — the gap between theoretical and actual food cost — closed from 6.2% over theoretical to 1.8% over by week six.
None of those gains would have been possible with a twenty-item menu at launch. The complexity would have absorbed all the learning energy.
When to expand — and how
Short does not mean short forever. It means short until the core is solid. The question is: how do you know when the core is solid?
When all four of those are true — expand by two items at most. Not five. Not a seasonal menu refresh. Two items, run them for four weeks, measure the same metrics again.
The temptation after the first few weeks
It comes reliably, usually around weeks three to five. A customer asks for something you do not have. A competitor adds an item that generates noise on Instagram. Your own team has suggestions. All of this pressure points in the same direction: add more.
The operators who resist this pressure are the ones who have internalised something important: the menu is not for the customer's convenience. It is for operational integrity. A customer who wants something you do not have is a data point. Twelve customers who want the same thing is a signal worth acting on. Three customers asking for three different things is not.
The test is not "could we make this?" It is "can we make this consistently, at speed, without degrading what we are already doing?" That is a harder question. It is the right one.
The practical rule
At launch: the number of items you think you need, divided by two. That is your launch menu.
First expansion: only after hitting all four operational benchmarks above. Add two items maximum. Measure for four weeks.
Growth menu: once the concept is operationally stable — typically three to six months in — you can begin thinking about a full menu engineering exercise. By then you will have real sales data to inform it, rather than guesses.
What the short menu signals to the customer
There is a second benefit that operators often miss. A short, confident menu signals expertise. It tells the customer: we know what we do, and we do it well. We have not tried to be everything.
Think about the food businesses you trust most. The idli shop that does three things. The filter coffee place that does one thing. The biryani restaurant where every table orders the same biryani. Their brevity is not a limitation. It is a position.
A twenty-item launch menu signals the opposite. It signals uncertainty. It says: we are not sure what we are, so we have offered everything and hope something lands.
Customers read this, even if they cannot articulate it. The menu is the first argument you make about what you are. Make it a confident one.