Free tool · stays in your browser

Stop guessing which dishes pull their weight.

Last verified:

Paste your menu — name, price, food cost, units sold — and get a Stars / Plowhorses / Puzzles / Dogs matrix with one short action per item. The math runs in your browser; nothing uploads.

How we keep your numbers private · What is menu engineering?

Analyse: Per-category split runs the median within each section so a $38 entrée and a $6 side don't share an x-axis.
Need a worked example first?
Item Price Food cost Units sold Category (optional)
Add at least 2 items above to render the matrix. Or click to see how it works on a 12-item Italian fixture.
Plain English

What this does, in four sentences

  1. You enter your menu. Items, prices, food cost, and units sold over a chosen period — typed in or pasted from a spreadsheet. The data sits in your browser and never leaves it.
  2. You get a 2×2 matrix. Each item is plotted against the median contribution margin and the median menu-mix share, landing in one of four quadrants: Star, Plowhorse, Puzzle, or Dog.
  3. You get an action per item. Stars get protected, Plowhorses get re-engineered for cost, Puzzles get re-photographed and repositioned, Dogs get dropped or replaced. The action plan is the deliverable.
  4. You get four ways to take it with you. The Menu Card is a 1200×1500 PNG you can email or print. The CSV mirrors the per-item math. The JSON is structured for any downstream tool. The ZIP packages all four (PNG + CSV + JSON + README).

It is not a POS connector, a recipe-cost calculator, or a menu-redesign service. More on the limits below.

Lead by example

Your menu data stays in your browser.

No upload, no account, no localStorage writes. Close the tab and the form is empty. Open DevTools → Network and click Add item or Load sample menu — the request list won't grow. The whole math module is plain JavaScript at /tools/menu-engineering/menu-engineering.js; right-click View Page Source and read it.

Same architecture as Brand Suite — see how Brand Suite protects your logo for the same posture, point by point.

Honest framing

What this isn't

Menu Engineering Matrix runs the math on data you already have. It is sharp, but it is one specific tool — not a substitute for the harder work that turns a Dog into a Star.

Not a POS connector.

You type or paste your data; the math runs locally. Connecting to Toast, Square, or Lightspeed inverts that flow and breaks the privacy posture. Pulling a sales report manually each month is the price of keeping it client-side.

Not a recipe-cost calculator.

Plated food cost is your input, not your output. Inferring it from ingredient prices + portion sizes is its own legitimately complex problem. Until that tool exists, your chef's plate-cost number is the right input here.

Not a menu redesign.

The Matrix tells you what to act on — re-photograph this Puzzle, drop that Dog, re-cost this Plowhorse. Designing a new menu around that action plan is paid studio work. The output is a brief, not a final.

Not a single-snapshot conclusion.

A Dog at brunch can be a Star at dinner. A summer Plowhorse can become a winter Puzzle. Run the analysis once a quarter, separately for service periods that have meaningfully different traffic. Trend across periods is its own (planned) feature.

What this is: a 30-minute exercise that pays for itself.

Three audiences, three handoffs. Bring the Menu Card to your chef — the four quadrants are the action plan. Bring the CSV to your accountant — the contribution-margin column is what they actually care about. Bring the JSON to a developer building anything on top of your menu data. The Card is the file your non-technical partners can actually use.

When you want a redesign, hire the studio.

A menu redesign turns the action plan into a printed, photographed, on-brand menu. Bring your Menu Card to the kickoff call — that's 30 minutes of the engagement already done.

See Brand & menu identity