MarginMind™ Found 61 Loss-Making Dishes on a 130-Dish Menu in the First Session
A Park Street Bengali restaurant had no visibility into per-dish profitability. The first MarginMind™ session changed everything.
Results at a glance
61
Loss-making dishes identified
Of 130 dishes analysed, 61 were found to be loss-making or margin-negative when overhead was allocated.
80%+
Food cost on Biryani
The restaurant's most popular dish was discovered to have a food cost above 80% — actively eroding margin with every order.
130
Dishes costed to the paisa
Full recipe BOM built for every dish, with yield factors, purchase prices, and overhead allocation.
Per dish
Overhead mapped
Rent, utilities, staff cost, and packaging allocated to each dish based on preparation complexity and resource usage.
The challenge
Petuk is a well-regarded Bengali restaurant on Park Street — one of Kolkata's most competitive dining corridors. With 130 dishes on the menu, built over years of adding customer favourites and seasonal specials, the kitchen had never mapped the actual cost of a single dish.
Food cost was tracked as a blended percentage: total monthly ingredient spend divided by total revenue. At 41%, it looked uncomfortable but explainable — 'our ingredients are premium.' There was no way to know which dishes were profitable and which were actively losing money with every order.
The flagship Biryani — Petuk's most-ordered dish — was later discovered to have a food cost above 80%. Every order of the restaurant's most popular item was making the business poorer. The owners had no idea.
Overhead costs — rent, utilities, staff, packaging — had never been mapped to individual dishes. The menu was priced on intuition and competitive benchmarking, not economics.
The solution
This was a MarginMind™ managed service engagement. The KhanaOS team worked directly with the restaurant — not a self-service product. Learn about MarginMind™ →
MarginMind™ is a managed service engagement — the KhanaOS team works directly with the restaurant to build its cost intelligence layer. For Petuk, this began with a structured intake: every dish on the 130-item menu, its recipe, portion sizes, and current selling price.
The KhanaOS team built recipe cost cards for all 130 dishes, applied current market purchase prices, and applied yield factors to every ingredient. Overhead costs — rent, utilities, staff cost, and packaging — were allocated per dish based on preparation time and resource usage.
The output: a complete menu P&L showing the contribution margin, overhead-loaded cost, and fully-loaded food cost for every dish — with specific repricing recommendations for each.
"We thought we knew our food cost. We knew a number — we didn't know what was behind it. The first session showed us that our most popular dish was the one losing us the most money. That's not something a spreadsheet tells you."
Owner
Petuk, Park Street, Kolkata