Illustrative Scenario: Improving a Restaurant Menu Before Expansion

Illustrative scenario, not a client case study. The business and figures below are hypothetical. They show how TerraForce could structure a menu and operations review; they do not describe delivered work or achieved client results.

The starting point

Imagine a casual restaurant with a 28-item menu, dine-in and delivery orders, and plans for a second location. The owner sees uneven preparation times and rising waste but cannot identify which menu items cause the problem. Expansion at this stage could repeat the same operational weaknesses.

Step 1: Establish a useful baseline

For each item, record selling price, ingredient and packaging costs, orders by channel, preparation time, returns and waste. Use the same time period for every item. Separate delivery fees from in-store costs so margins can be compared fairly. Confirm the data with kitchen and finance teams before drawing conclusions.

Step 2: Examine contribution, demand and complexity

Contribution per order is selling price minus directly variable costs. For illustration only, an item priced at SAR 50 with SAR 18 in ingredients, SAR 3 in packaging and SAR 4 in channel fees contributes SAR 25 before fixed costs and other labour. A popular item with low contribution may need a recipe, price or channel review. A high-contribution item that is slow to prepare may create a service bottleneck. Decisions need both financial and operational evidence.

Step 3: Redesign and test

Group items by demand, contribution and preparation complexity. Keep items that support the brand promise, improve recipes where possible, and test removing items that create complexity without enough value. Pilot the revised menu in one controlled period. Train staff on recipes, portions, allergens, suggestive selling and delivery packaging. Document every change so it can be repeated at a second site.

Step 4: Decide whether the model is ready to scale

Review order accuracy, guest feedback, preparation time, waste, average order value and contribution by channel each week. Compare the pilot with the baseline while accounting for promotions and seasonality. A second location should follow only when the team can deliver the product consistently and the financial assumptions have been checked.

What a real project would deliver

• A menu performance map with data definitions and assumptions.
• Recommended recipe, pricing and assortment tests.
• Standard portions, preparation steps and training materials.
• A pilot scorecard and decision criteria for expansion.

This example explains a method, not a guaranteed outcome. For a review based on your actual data, explore our food and beverage services or contact TerraForce.