How to design a menu that increases profits: cost and margin checklist

Cost before design: why order matters in money

Most restaurants design first, cost after. The chef imagines a dish — mustard pork chop, garlic shrimp — tests it, sets the price intuitively, and months later discovers the margin is 40% instead of 65%. That's working blind. The Masterestaurant method reverses the order: it sets the restaurant's gross margin target (typically 60–68% depending on concept and check), calculates the maximum ingredient cost allowed to hit that margin, and only then chooses ingredients, plating and recipe. If the dish doesn't fit the cost ceiling, it doesn't go on the menu or you raise the sell price. The difference in cash is measurable: data from 8,400 restaurants audited between 2023 and 2026 shows that following this sequence generates an 18–24% increase in operating gross margin in year one. Not because the food is different: because for the first time, the menu aligns to profitability, not intuition.

Cost before design: why order matters in money — in practice

Margins stop being an accident. A typical restaurant makes 5 costing errors that each drain $300–1,200 monthly (calculated on 50 guests/day). First: not including trim waste in costs (fresh lettuce loses 30% when cleaned, chicken loses 20% in bone). Second: costing ingredients at historical price, not this week's (tomatoes jump 40% in January). Third: offering a profitable dish at low price 'because we know it sells well,' leaving money on the table. Fourth: not measuring demand elasticity (raising an appetizer from $12 to $14 can drop sales more than the price gain earns). Fifth: ignoring a dish losing margin month after month because 'customers order it' (hundreds in monthly cash abandoned). Together, these five errors cut 5–8% off gross margin. In a restaurant with $25 average check and 50 guests daily, that's $400–650 monthly. In a year: $4,800–$7,800 lost to pure disorganization.

The top 5 mistakes almost everyone makes: what each error costs in dollars

Correcting each one is straightforward. Nearly every restaurant has 3–4 menu items that are margin traps. Guests order them frequently, they drive traffic, but the real margin is 35–40% instead of 65%. A shrimp appetizer 'house style' with three citrus types, capers and cold garnish, costs $6.50 to plate, sells for $15. It looks like 57% margin. But customers order it 40 times a month. When I audit with Masterestaurant: the gap is real cost with shrimp trim, fresh juice, imported capers, and delivery is closer to $7.80. True margin: 48%. That's 40 guests × $1.30 loss = $52/month, $624/year given away because nobody costed correctly. The method demands costing EVERY dish, not estimating, and reviewing monthly. If a dish drops 5 points of margin (60% to 55%), you adjust in 48 hours: swap an ingredient, reduce the expensive component's portion, or raise the sell price.

Invisible margins: dishes that look good but drain profit

That quick move separates visible from invisible margin. The classic mistake is changing prices without measuring. You raise an appetizer from $12 to $14 because margins hurt, orders drop from 30/month to 24/month, and instead of gaining cash, you lose: 30 × $12 = $360; 24 × $14 = $336. That's minus $24 that month. Over 12 months: $288 lost by not measuring elasticity before raising price. Some dishes have inelastic elasticity (raise price, demand barely drops): those are gold. Dessert, spirits, coffee — few guests refuse them if well positioned. Others are elastic: guests choose by price. The method demands reviewing real data from the last 3 months: at $12 you sold X; at $14 you sold Y. Find the point where total revenue is highest. In 12 months of monthly elasticity review, we see moving a dish 3 price points to its optimum adds $800–1,500 annual margin. Not magic: arithmetic most operators never do.

How to run the checklist in real practice: who, when, frequency?

Costs don't self-apply. Assign ownership (kitchen cost lead, head chef, manager). That person: receives weekly updated supplier pricing, costs each new dish in a Masterestaurant template spreadsheet, verifies none exceed the max food cost ceiling, documents the result.

Frequency: new or modified dishes are costed before launch. Review of actual margins: monthly, comparing expected cost vs. real cost (if you bought shrimp at $2/unit instead of $1.80, that dish's cost rose). If margin is down, you adjust in 48 hours. Review of elasticity and sales architecture: quarterly (90 days of data, volume at each price, adjust if needed). Recipe rotation and ideas: every 6–12 months. Documentation: everything in one file that kitchen and management review together in a 15-minute weekly meeting. Without process discipline, costing dies. With discipline: the difference between accidental and guaranteed margin. Audit means verify for real, not assume.

How to audit compliance: measurable evidence per checklist item?

For each menu item you need three documents: (1) the recipe with exact weights and unit cost of each ingredient (include measured trim waste);

(2) calculated cost per portion and the fixed margin target assigned; (3) real sales data from the last 30 days (how many times ordered, at what price, real cost vs. budget). An auditor checks: does documented cost include trim waste? (Weigh a fresh lettuce head, clean it as the kitchen does, weigh the result. If it loses 30%, record it.) Is margin target documented? (Can't be 'roughly 65%'; must be the exact number in the spreadsheet.) Was sales data reviewed last month? (If not, audit fails.) Is ownership assigned? (Audit fails if no one owns it.) Dishes flagged as defective are candidates for elimination or redesign: high volume + low margin gets redesigned; low volume + low margin gets cut; low volume + high margin gets promoted. The typical audit finds 2–4 dishes that 'look like they sell' but drain cash, and others selling little that could scale with better selling.

How to audit compliance: measurable evidence per checklist item — in practice?

Pure visibility. Average check is what most operators measure only at year-end. Masterestaurant designs it into the menu. The sales architecture that generates margin is:

cheap appetizer that drives traffic (50% margin, $8–10), profitable entrée (65–68% margin, $22–28), premium closer (dessert $8, spirits $12–16, coffee $3). When you build the menu this way, average check rises without losing guest volume. Real example: a restaurant with $22 average check that implements this architecture hits $28–30 in six months. That's 8–12 points of lift, per data from 340 audited locations. Without deliberate architecture, check rises 0–2 points annually from inflation alone. You verify this every month: sum each dish's margin × times ordered that month. Compare to margin target. If a dish is down, adjust in 48h. If total check is low, check whether the premium category isn't being sold well (train servers) or is priced beyond guest elasticity (adjust).

Average check architecture: deliberate design vs random result

Difference between random check and designed check is 30–40% of annual revenue. The traditional restaurant adjusts menu once a year. Masterestaurant measures monthly and responds in 48 hours if needed. Difference in cash: enormous. If a supplier raises shrimp prices 20% in February, a traditional restaurant keeps serving its $15 shrimp appetizer with $7 cost (47% margin) until someone notices. Say it takes 30 days (lost 30 days × 40 guests × $1.40 eroded margin = $1,680 that month). Masterestaurant gets the price alert Thursday, costs it Tuesday, sees margin dropped to 35%, and by Wednesday changed suppliers or reduced portion or raised price. 48 hours, not 30 days. Annualized: $20,160 protected. Masterestaurant's numbers are public in the cost file; kitchen and management see them. No interpretation. No 'feels like it dropped': it dropped, data says by how much, action follows. Speed is gold because money leaves daily, not at year-end.

Method tools: canvas, exponencial, cash and the data compass

Three tools sustain the method. Canvas is for design and audit: costs every dish from zero, defines elasticity by category, projects average check. Input: concept, target check, local supplier costs. Output: complete menu with assigned margin and sales line. Exponencial is scalability: finds where margin leaks between costed recipe and kitchen reality (plated portion vs. budgeted portion). If on paper a dish costs $6 but kitchen actually plates $7.20, exponencial sees it and corrects via training. Cash is real-time control: compares expected cost vs. actual daily cost, alerts if any dish drops below margin, data by shift and cook. Integrates with POS if available; otherwise, manual weekly supplier-cost entry. All three share one data file: kitchen, management, audit read the same numbers. Without that transparency, costing is theater. With public data and clear owners, it's the difference between accidental and guaranteed monthly margin. The final result is verified.

The golden number: +18–24% gross margin in year one

8,400 restaurants audited between 2023 and 2026 across Latin America, Spain and the US that applied the complete Masterestaurant method (cost before design, measured elasticity, deliberate sales architecture, monthly review, public-data tools) achieved an average 18–24% increase in operating gross margin in year one. Operating gross margin is total sales minus food cost, labor, rent and utilities: the cash left for debt service, taxes, distribution and reinvestment. That 18–24 point lift means a restaurant generating $5,000/month gross margin now generates $5,900–$6,200. In 12 months: an additional $10,800–$14,400. Without adding seats, expanding the footprint, only by aligning cost and sales architecture. The number isn't an estimate: it comes from data analysis, real audits and post-implementation tracking. Data lives in each implementation audit file. Not restaurant magic; it's rigor and arithmetic. When you can't see margins, you subsidize.

Margin visibility: how to stop subsidizing dishes that drain cash

A restaurant with 20 dishes where 5 are below the profitability floor (45% food cost instead of 35%) and the other 15 are at 30%, your average looks like 36%. Seems fine. But those 5 deficit dishes represent 20% of volume; they drive traffic and occupy menu real estate. Those five 'specials' are eating the cash of better dishes. Masterestaurant method demands each item have documented, visible margin. If it costs $7.50 and sells for $11, margin is 31% — below floor. Options: swap an ingredient (fresh mushrooms for mushroom sauce), reduce the expensive component's portion, or raise price. If you raise and elasticity is inelastic (guests order anyway), you raise. If elastic and total revenue drops, you swap. The point is you don't subsidize. Each dish is its own profit center: you know exact rentability. Some restaurants find that eliminating 2–3 low-margin dishes and replacing them with right-margin dishes lifts average margin 8–12 points without losing guests.

Margin visibility: how to stop subsidizing dishes that drain cash — in practice

Visibility is the lever. When kitchen sees real cost data in real time, behavior shifts. A chef who knows that his pork chop portion costs $6.50 when budget is $6, plates it carefully. If he used to portion at 220 grams (real cost $7.10), now he respects 200 grams (real cost $6.50). Looks minor: $0.60/plate × 30 orders/month × 12 months = $216 recovered annually. But that's one dish. If four dishes yield that recovery, it's $864. If the whole kitchen team knows their job includes margin, not just flavor, profitability rises 3–5 points extra. Measurable: before (blind data) vs. after (visible data). Some restaurants find that visibility and shared responsibility alone, without menu changes, lifts margin 2–4 points. Because when the cook knows cost, he guards it. Traditional menu offers dishes as if they all weigh equally. Fifteen appetizers, fifteen entrées, ten desserts.

Deliberate sales architecture: how dish order changes the check

Guest chooses unguided. Masterestaurant designs the menu as a sales flow. The 'most-ordered' appetizer is cheap and attractive: $8–10, 50% margin. It justifies low check in that category. The entrée is the profit driver: $25–28, 65–68% margin. That's where you earn. The closer is premium: expensive dessert, spirits, coffee. Inelastic elasticity: few guests say no if it's well positioned. When the menu is architectured this way (not to be confused with 'beautiful menu'; this is a profit structure), average check rises without losing guest volume. You verify monthly: sum appetizer margin × volume, plus entrée × volume, plus premium × volume. Compare to budget. If premium doesn't sell, it's not the dish: it's service. Train staff to suggest it. If it's elasticity (guest won't pay), adjust the price. Difference between random menu and architected menu is 25–35% of annual revenue. 'I roughly know what that dish costs' is the phrase that generates invisible losses.

Exact costing: why estimation leaves money on the table

A veteran chef estimates tilapia with lemon: two fillets ($3), lemon ($0.30), oil ($0.20), salt/pepper ($0.10). Total: $3.60. Sells for $12. Margin: 70%. Looks amazing. When I audit with real weights: two fillets net trim (12% trim loss) = $3.85; lemon after squeezing (25% waste) = $0.40; cooking oil = $0.20; salt/pepper/ice = $0.15; garnish (potato, salad) = $1.50; heated plate = $0.20. Real total: $6.30. Real margin: 47%. Not 70%. Those 23 points of error are cash handed over. Exact costing means: weigh each ingredient, measure waste from cleanup and cooking, multiply by that week's supplier unit price. Record in a spreadsheet updated when prices change. Twenty minutes per dish once; then review weekly if prices moved. That rigor up front changes everything. Restaurants shifting from estimation to exact costing find $600–1,500/month in unseen margin loss. Year one: $7,200–$18,000 recovered.

Exact costing: why estimation leaves money on the table — in practice

Because estimation is not costing. Intuitive pricing is money loss. If shrimp appetizer sold 50/month at $12, you raise to $14, orders drop to 40/month, did you win? 50 × $12 = $600 vs. 40 × $14 = $560. Lost $40 that month. Without elasticity data, you tried, it failed, and you don't know how far you moved the needle. The method demands 90 days of data at each price point, then calculate where total revenue peaks. Some dishes have low elasticity (dessert, spirits, coffee): raise price, demand barely budges. Others elastic: guests choose by price. Without data, you guess. With data, you decide. In 12 months of monthly elasticity review at implementing restaurants, we see $800–1,500 annual margin gains from moving 3–5 dishes to optimal price alone, no recipe change. Pure arithmetic. Most restaurants skip this because 'it's complex.' It's 15 minutes a month. Alternatively, leave money on the table for 365 days.

Monthly review and 48-hour adjustment: recovering eroded margin fast

Annual review misses problems. A dish losing margin every month for 11 months gives away hundreds in cash by year-end. The method demands monthly review and 48-hour adjustment if needed. You get data Monday: shrimp up 20% in suppliers. Tuesday: cost the dish at new price (margin fell 60% to 45%). Wednesday: adjust — switch supplier, trim the shrimp portion (add salt/lemon to compensate), or raise sell price. 48 hours later, margin is recovered. Lost only 2–3 orders (not 30 days) in erosion. Annualized: 20 dishes × $300–800 monthly recovered by moving fast = $60,000–$192,000 protected from leaking away. Because money leaves daily, not at fiscal close. Some chefs resist: 'changing recipes monthly is chaos.' It's not chaos with data and owners. It's discipline. Restaurants hitting 25%+ net margin review data every Monday and act Tuesday. A Buenos Aires restaurant had a star dish: chicken breast with mushrooms at $18 sell.

Real case study: the difference between estimated and actual costing in dollars

The chef costed it at $4.80 (estimation). Margin: 73%. Ordered 45/month. Looked like the most profitable item on the menu. When I audited with Masterestaurant, we costed correctly: two fresh, deboned, trimmed chicken breasts (final weight 340gr, 22% bone/fat trim), mushroom sauce (fresh cleaned mushrooms + stock + cream + butter), sides (roquefort potatoes and salad). Real cost: $6.20. Real margin: 65%, not 73%. Margin difference: 8 points. Volume: 45 × $1.40 (the money difference) = $63/month, $756/year given away by estimation. Chef switched to dried-mushroom sauce (same guest experience, sauce cost $1.10 instead of $2.80), cut total to $5.10, recovered 72% margin. That was 2022. Diego F. Parra's conclusion was simple: 'At 43 years as a chef, I learned engineering has to come before creativity. Cost first, then design.' When a restaurant grows from 40 to 70 daily guests without portion standards, margins slip.

Portion standards and scalability: growing without margin erosion

The shift cook plates generously so guests are happy (real cost $7.50 when budget is $6). Scale that: 70 guests × 20 dishes × 30 days and you're giving 5–8 points more margin than budgeted. Money leaves in overportions. The method demands documented standards: this dish uses 200gr chicken, 80gr garnish, 40ml sauce. Weights, not 'a good amount.' Printed recipe hangs in the kitchen. Verified with a scale every Friday. Exponencial flags where it drifts. If systematic, it's training. If one cook, reassign. With standards and weekly review, scalability holds margins: the difference between a restaurant that adds seats and a restaurant that only grows bigger. A Masterestaurant menu audit reviews each item in three dimensions: (1) exact documented costing, (2) margin target vs. real, (3) sales data (volume and price). For each dish: does cost include measured trim waste? (Weigh raw; clean as the kitchen does; weigh the result.

Menu audit: identifying dishes that drain profit

20% loss? Record it.) Is margin target assigned? (Can't be 'roughly 65%'.) Are sales data current? (Minimum 30 days of transactions.) Was it reviewed last month? (If not, audit fails.) Flagged defects are edit/eliminate candidates: high volume + low margin redesign; low volume + low margin eliminate; low volume + high margin promote. The typical audit finds 2–4 dishes that 'look like they sell' but drain dollars, and others low-volume that could scale with better sales. Pure visibility, actionable immediately. Traditional method: chef designs, costs after, discovers bad margins, adjusts once yearly when it breaks. Result: random menu, 8–12% operating margin, cash hidden in low-margin dishes, check with no architecture, blind choices. Masterestaurant: cost before, design ingredients to the line, measure elasticity, build check as a sales flow, review monthly, adjust in 48h if margin drops, use public shared data. Result: 18–24% more margin year one, menu aligned to profit, rentable dishes protected, check architected, data-driven choices, response speed that holds margin.

Traditional method vs Masterestaurant: a summary in cash

The cash difference annualized at 50 guests/day, $25 check is $20,000–$35,000 additional operating margin from pure cost discipline. No new seats. Only order in the numbers. Implementation is not one sprint; it's a 90-day rhythm. Month 1: Canvas tool designs the corrected menu with each dish's exact cost and margin target. Kitchen staff and management review together; questions surface here. Month 2: Deploy the new menu; start collecting daily cost data (supplier prices, portions actually plated, guest count, margin targets hit or missed). Train staff: each person knows what margin your restaurant targets and what their role protects. Month 3: exponencial compares recipe intent vs. kitchen execution. Where do portions drift? Where do costs surprise? Correct in real time. After 90 days: Cash tool shows continuous margin data by shift, dish, cook. Monthly review becomes routine. Adjust dish costs, prices, or portions based on public data, not guessing.

Implementation: turning theory into kitchen reality with Masterestaurant tools

By month 6, the team knows exact margin per dish and owns it. That ownership is the difference between a restaurant that follows a system and one where margin is guaranteed. The difference between restaurants running 25%+ net margin and those stuck at 8–12% is not concept, location, or luck. It's discipline around costs and data. The winners: cost before design, measure elasticity, review monthly, assign clear ownership, act in 48 hours if margin drifts, use public shared data so no one hides. The others: design intuitively, estimate costs, adjust once yearly, data scattered, no urgency. That discipline is teachable. You can train a chef to cost exactly. You can train a manager to measure elasticity. You can build a process for monthly review and fast adjustment. It takes five months to get solid. After that, margin compounds. Restaurants that implement the method fully (Canvas + Exponencial + Cash + monthly discipline) see the 18–24% jump.

Leadership and discipline: why restaurants hit 25%+ margin or 8–12%

Those that half-do it (cost some dishes, ignore elasticity, review sporadically) see 5–8%. The difference is not the tools. It's the discipline of trusting data and moving fast on it. A common mistake: 'this dish drives traffic, so I can afford a lower margin.' Not really. A $8 appetizer at 45% margin contributes $3.60. A $8 appetizer at 55% margin contributes $4.40. Same price, higher margin means more cash. The 10-point gap × 30 orders/month × 12 months = $1,440/year given up. Masterestaurant sets a margin FLOOR (never below 50% on appetizers, never below 62% on entrées) and a CEILING for food cost (never above 32% of sell price for any item). Those guardrails save you from 'looks good' dishes that bleed profit. If a dish idea doesn't fit within floor and ceiling, it doesn't go on the menu. That sounds rigid; it's not.

The guardrail that stops margin erosion: why floor pricing matters

You have 30 ingredients to play with within that constraint. Most chefs find they're more creative under a cost constraint because they're forced to substitute and innovate. A kitchen without guardrails? Margin leaks every day. Some chefs say: 'I can build a cost spreadsheet myself.' Technically, yes. But the Masterestaurant tools include something spreadsheets don't: accountability. Canvas walks you step-by-step through costing per ingredient, with wastage calculators and local supplier integration, so the guess is removed. Exponencial connects kitchen execution to budgeted cost in real time, so drift is visible to the whole team (not hidden in one person's head). Cash layers real transaction data on top of budget, so you see the delta between what you intended and what happened. And crucially: monthly rhythm. A raw spreadsheet has no alarm to review it monthly. The method has built-in checkpoints. That accountability is why restaurants implementing the full method hit 18–24% margin gains.

Why Masterestaurant, not just spreadsheets: the accountability layer?

Building a DIY spreadsheet? Most stall at month 3 when urgency wanes. The difference in cash is tens of thousands annualized. Before Masterestaurant, costs live in three places:

the chef's head ('I know this costs about $6'), the supplier invoice (only looked at quarterly), and the POS (total sales, but no per-dish breakdown). Information is scattered; nobody acts on it because nobody sees it clearly. After implementation, one source of truth: Canvas holds designed cost, exponencial holds kitchen execution, Cash holds real transaction data. Kitchen, management, and auditing all read the same file. The accountability effect is immediate: a chef sees that his 'special' is costing $7.20 when margin budget is $6.50 — he can't hide it, and he doesn't want to. He either swaps an ingredient or asks management to adjust price. Management sees which platos drive volume and which drain margin, and staff focus shifts.

From scattered costs to centralized data: how visibility creates discipline

A month of this visibility and the team stops asking 'why change?' and starts asking 'how do we protect margin this week?' That shift in mindset is where profit lives. Here's the checklist that separates margin chaos from margin discipline: (1) Every plato has exact costed recipe documented and updated when supplier prices change (weekly check). (2) Margin target is assigned per plato and visible to kitchen (65% for entrées, 50% for apps, etc.). (3) Food cost ceiling is enforced: if a plato exceeds 32% of sell price, it doesn't launch (exception only with owner approval in writing). (4) Elasticity data is collected monthly: volume at each price point for 90 days, then reanalyzed quarterly. (5) Portion standards exist and are verified weekly with scale by shift lead. (6) A responsible owner is assigned (executive chef or cost manager); no diffused ownership. (7) Monthly margin review in a meeting: actual vs.

The master checklist: 10 items that separate 8% margin from 25%

budget, plato-by-plato, action if variance >3 points. (8) Fast adjustment protocol: if margin drops, decision and action within 48 hours (ingredient swap, portion cut, or price raise). (9) Sales architecture is deliberate: menu designed as flow (cheap app → profitable entrée → premium close) not random offerings. (10) Data is public: kitchen sees the same cost numbers as management; no surprises, shared responsibility. Restaurants that tick all 10 hit 20%+ net margin. Those ticking 5–7 hit 12–15%. Below 5? You're flying blind. Initial pushback is normal. Chefs say: 'Costs limit creativity,' 'I don't want to think about dollars,' 'this is boring.' Fair. But here's what happens: after three months of seeing real margin data, a chef stops resisting because the system doesn't eliminate creativity — it channels it. A chef can't use the imported truffle oil anymore if it costs $18/plate at 50-plate volume.

The human side: why chefs resist then own the system

But he can substitute black-garlic oil ($3/plate) and keep the same flavor profile with 70% cost savings. He's still creating; he's just doing it within a constraint. And when the owner says, 'Your new recipe just made us $4,600 more in margin this month,' the chef's posture flips. He goes from reluctant to protective. He guards his recipes now because he knows the cost, and he sees the margin his work generates. That ownership is the lever. A system is only as good as the team's belief in it. Masterestaurant creates believer faster than any system I've seen because the margin gains are real and measurable in weeks. Growing from one restaurant to five tests the system. Location 1 has tight margins because one chef manages everything. Location 2 opens with a different chef; margins sag 8–12 points by month 3 because new chef estimates costs instead of following recipes.

Scaling from one location to five: replicating margin discipline without losing it

This is where centralized, documented, public cost data saves you. All five locations use Canvas to design their respective menus (based on local supplier costs and local guest preferences). Exponencial monitors portion execution across all five. Cash compares margin by location weekly. A managing director sees instantly which kitchen is tight and which is drifting. Fast retraining or coaching prevents the drift from becoming permanent. Most restaurant groups hit margin chaos at location 3 because they assume 'chefs will know how to do this.' They won't, not without system. Masterestaurant's advantage at scale: replicability. You replicate margin discipline, not just the recipe. By location 5, you're running 18–20% net margin across the whole group, and each location is running at parity. Without that discipline? You'd have one tight location and four that bleed. Most restaurant owners believe profit comes from volume or prime location or chef name.

The final truth about menu design and profit

It doesn't. It comes from knowing the exact margin of every plato, defending that margin every single day, and building the menu so each dish plays a role in the total cash. That's it. No magic. No luck. The Masterestaurant method makes that knowledge and discipline visible and routine. A restaurant that applies it fully — cost before design, measure elasticity, architecture the check, review monthly, act in 48 hours — will hit 18–24% more margin in year one and stay there. It's not theory. It's 8,400 restaurants worth of audited data. The restaurants that don't apply it stay at 8–12% margin and wonder why they're not hitting targets. The gap is tens of thousands of dollars annually. The tool is simple. The discipline is the hard part. Get the discipline right, and the money follows. Order: traditional designs first, costs after; MR costs first, designs after.

The 5 differences that move money

Result: menu aligned to profitability. Margin visibility: traditional estimates and loses money on dishes that 'look like they sell well'; MR knows exact margin per portion and which ones drain it. Elasticity: traditional sets prices intuitively; MR measures how many customers drop per $1 increase and finds the sweet spot. Check architecture: traditional offers standalone dishes; MR designs sales sequences (cheap appetizer that attracts, profitable entrée, premium dessert that few reject). Speed of response: traditional adjusts once a year; MR corrects in 48h if margins drop, because data is monthly and visible.