Skip to content
RANGE

02

Connect culinary creativity to margin reality.

A menu is both a creative statement and a financial instrument. When those two things are misaligned, the result is a kitchen that works too hard for margins that disappoint. We have built and executed menu programs across full-service, high-volume, and fast-casual formats, including pioneering seasonal concepts and developing entirely new culinary visions from financial pro forma through opening day. The food has to work in the kitchen and on the P&L.

The best menus aren’t the longest ones. Operators add items to capture the veto vote. A reasonable instinct that compounds into operational fragmentation. Every addition slows the line, fragments training, and raises the floor on food cost. Frequency of visit is driven by craveability, not variety. We work backward from what’s actually craveable, and cut everything that’s just covering a gap in confidence.

Tell us what’s breaking.

Take the Diagnostic

Thirty to forty-five minutes, with the Straight Read back within 48 hours.

Scope of Work

  • —Menu engineering and profitability analysis
  • —Recipe costing, food cost, and cost-of-goods analysis
  • —Seasonal and LTO program development
  • —Kitchen execution audit and throughput analysis
  • —Supplier and sourcing strategy
  • —Beverage program development and cost structure

Start with an install

Not ready for the full engagement? A fixed-scope install builds one system into your operation: defined start, defined end, priced up front.

Why a longer menu rarely fixes a food-cost problem.

Menu work becomes urgent at predictable moments: food cost has crept up without a clear cause, the kitchen can’t execute the current menu consistently at volume, or a concept is heading into new units and the menu has to travel. The instinct is usually to add (a new item to chase a slow daypart, a limited-time offer to manufacture news) when the higher-leverage move is almost always to subtract.

We start from the data: item-level margin, product mix, and what the line can actually execute at peak. First document on the table is the product-mix report: which items actually sell, and at what margin. Theoretical food cost gets built recipe-by-recipe and checked against the real number, and a prep-and-plate audit times execution at real volume, not on a quiet Tuesday. Most kitchens carry a gap of five points or more between theoretical and actual food cost without knowing it; the operators who run tight hold that gap under two to three points, and closing it is usually worth more than any single price increase.

We engineer the menu around profit per cover and throughput (pricing, placement, prep, and sourcing moved together) and document it so it holds as the concept travels. The output is a shorter, sharper menu that’s easier to train and more profitable per seat.

The record is on Selected Outcomes.

How it works

StepWhat happens
01Pull a full-cycle product mix: margin by item
02Cost every recipe from current invoices
03Time the line at a real Friday peak
04Re-engineer pricing, placement, and prep together
05Cut the menu; document specs so it travels

Before

The menu has grown to cover every guest request, food cost is trending up with no clear cause, and the kitchen can’t hit ticket times at a full house.

After

A shorter menu, priced and placed against real margin data, runs faster on the line and holds food cost inside a gap the kitchen can explain.

Further Reading

When a focused menu starts capping your growth

Common Questions

Will cutting menu items hurt my sales?

Usually the opposite. Frequency is driven by craveability, not variety. Most long menus carry items that exist to cover a gap in confidence, not to drive visits. Removing low-margin, low-velocity items that slow the line typically improves execution, speed, and food cost without measurably reducing traffic. We model the impact before anything changes.

How does menu engineering lower food cost?

By aligning the menu with both margin and the kitchen’s actual capacity. We cost every recipe, analyze product mix, re-engineer pricing and placement toward profitable items, and simplify prep so the line executes consistently. The savings come from fewer SKUs, tighter specs, better sourcing, and less waste, not from cheaper ingredients.

What do you need access to for a menu engineering project?

POS product-mix reports covering a full seasonal cycle where possible, current recipe costing or the invoices to build it, and a walk of the kitchen at a real peak, not a demo shift. The gap between what the numbers say and what the line can actually execute is usually where the biggest opportunity lives.

Will you cut the dishes our regulars actually come for?

No. The product-mix data protects them. An item with real velocity and guest loyalty stays even at a thinner margin, because it drives the visits that carry the rest of the check. What comes off the menu are the items nobody would miss: low-velocity, low-margin dishes that slow the line and pad the inventory. If a cut is genuinely debatable, we model it before it’s permanent.

Does the chef lose creative control in menu engineering?

The chef gains a sharper canvas. Menu engineering sets the commercial frame (margin targets, prep load, what the line can execute at peak) and the chef builds inside it; a shorter menu usually means each dish gets more attention, not less. The projects that go best are the ones where the chef sees the product-mix data early, because the numbers tend to confirm what a good chef already suspects.

What does R&D mean for a restaurant?

Research and development, applied to the menu, not a lab. In practice: costing a new dish or format against real invoices, checking it against product-mix data, and timing it on the line at a real Friday peak before it ever reaches a guest. The “research” is the numbers; the “development” is proving the dish holds at volume, not just on a quiet tasting.
PreviousOperational Excellence & SystemsNext Service Standards & Training