Your Peers Aren't Betting on the World Cup.
They're Investing In Their Restaurant.

Every POS has a product mix (PMix) report, sometimes called an item sales report or product performance report. Pull three months minimum, longer if you've had a seasonal shift in that window. What you need is units sold per menu item. That's it for this step. The PMix gives you the volume side of the menu picture without any costing work, and that's enough to start scoping the rest of the refresh. Most operators haven't looked at this report carefully in months or years. Doing it now is the cheapest, fastest piece of clarity you'll get all week.

Now use the PMix to scope the costing work. Start with two lists. The first is your top twenty by volume, the items the matrix needs to see clearly. The second is a smaller list of low-volume items you suspect have decent margin: the chef special when you have the protein, the dish your regulars order knowingly. Without the second list you'll never identify your puzzles, because puzzles by definition aren't showing up in the volume numbers. For each item on both lists, document the recipe (ingredients and portion sizes) and then cost it out. For each ingredient, take the invoice price, divide by usable yield (the portion that ends up on the plate after trim, shrinkage, and waste), and multiply by the per-plate portion in the recipe. Sum across ingredients to get plate cost. This is the step operators put off, then put off again. Done once, it gives you the foundation for every cost conversation that follows.

You have the two numbers: units sold from the PMix, contribution margin from the costing work. Plot the items on a simple grid, units sold on the horizontal and contribution margin on the vertical, and draw cross-hairs at the menu averages. Items above both lines are stars. Below both lines, dogs. High volume, low margin: plowhorses, your bread-and-butter, keeping the lights on without moving the bottom line. High margin, low volume: puzzles, the ones that would make you money if more people ordered them. Most operators have never done this. Doing it once changes how you look at the menu permanently.

Dogs come off the menu. Puzzles get repositioned (better placement, better description, sometimes a small price adjustment) to see if they can become stars. Plowhorses get a margin look (can we adjust the recipe, the portion, or the price without losing the volume). Stars get protected. The cut is the hardest part because every dog has a regular who loves it. The math is the math.

When did you last cost out your menu against current vendor prices? If the answer is "more than six months ago," you're operating on stale margins. Re-cost your top twenty items minimum. The operators who do this regularly know exactly which items are quietly losing money. The ones who don't are guessing.

Do you have a structure for how prices move, or do you change prices when something forces you to? A pricing structure means you've decided when to revisit prices (quarterly, semi-annually), what triggers a between-cycle change (a vendor increase over X percent), and how price changes get communicated to the team and the guest. Without a structure, you're reactive, and reactive pricing tends to fall behind costs.

Once you can see your menu clearly, the LTOs surface on their own. A puzzle that's underperforming becomes the candidate for a featured promotion. A seasonal opportunity (PNW salmon in late spring, stone fruit in summer) becomes a deliberate add. An LTO calendar built from this kind of analysis is grounded; one built without it is guessing.

Pull your top five to ten items by weekly volume. For each one, list every ingredient with its current cost and the amount the recipe uses. This is the same costing pass that should be happening in a menu refresh; if you've already done it, you're starting here. The point is to see which ingredients are sitting underneath your highest-volume plates, because that's where a small per-unit savings turns into real money.

Walk through those costed recipes and mark the inputs the guest can't pick out individually. Fryer oil. Flour. Base stocks. Canned tomatoes. Most spices. Frozen vegetables in a soup. The ones the guest does identify (your steak, your bread, your house dressing if you're known for it) come off the substitution list; those are brand decisions, not cost decisions. What's left is the swap pile.

Bring the costed recipes and the swap pile to your rep. Ask two questions in order. First, where do they have an exclusive-brand alternative for what you're already buying? Exclusive brands are the same play as Kirkland at Costco; the savings come from cutting marketing spend out of the price, not from cutting quality. Second, where would speed-scratch beat scratch on total cost once labor and yield are in the math? On both questions, ask for the total cost picture, not just the unit price. A speed-scratch item that costs more per pound but saves twenty minutes of prep and runs at 100% yield can win on the plate.

Pick two or three swaps with the biggest expected impact and run them on actual recipes before you commit. Recalculate the plate cost with the new ingredient in place. Cook the dish. Taste it side by side with the original if you can. The math is the math, and so is the plate; if either one breaks, the swap doesn't go in. The ones that hold across both become permanent, and you extrapolate the same logic across the rest of the order guide from there.

The reason most order guides stagnate is that nobody owns them on a recurring basis. Put a quarterly review on the calendar with your rep. Same conversation, same questions, against current costs. Vendors release new exclusive brands and new speed-scratch options regularly; the operators who catch them early get the savings, and the ones who don't pay full price by default.

The swaps above are about margin. Backups are about continuity. Walk your top items again, marking the visible ingredients. Ask the rep for the substitute options, the pack and price, and whether they'd hold a small standing reserve. Test the substitute on the actual dish before you need it. Document the swap so anyone in the kitchen can execute it. The list stays dormant until it doesn't, and that's the value.

Walk your roster. For every position, ask who can cover it if the regular is out. If the answer is "nobody," that's a gap. Cross-training a line cook to run expo, a server to bartend, a counter person to handle the prep window: each of those is a piece of resilience that pays off the next time someone calls in sick, surge or no surge.

If you're going to have retention conversations with your best people, have them now. Not after they've already accepted an offer somewhere else. A bonus tied to summer commitment, a path conversation, even just "I see you and I want you here" goes farther than most operators realize. The operators losing their best people are usually the ones who never had the conversation early enough.

If your operation is going to extend into late-night windows during the surge (and many will, in the path zones), your team needs to know what that looks like before they're standing in it. A trial run on a Friday or Saturday with extended hours and the late-night menu in place. Find the friction now, when the consequences are small.

Your best training already happens on the floor. The veteran server explaining timing to the new hire mid-shift. The cook showing another cook a technique that just clicks. The guest describing a dish in a way that would sell better than your menu copy. Most operators leave that learning accidental. The operators who do it deliberately ask one more question while it's fresh: "How did you know to do that?" The thinking behind the move is what travels; the move itself is just the symptom. Pair that with a brief post-shift moment where someone shares one thing they noticed (a peer technique, a guest line worth stealing, a question that opened up a useful conversation) and you've turned every shift into a training session that nobody had to schedule. The team you already have probably uses a group thread for scheduling. Add a separate thread for what people learned, and protect it from operational chatter. The point isn't a new system; it's making visible what's already happening.

The morning huddle is great when you can pull it off. The whole team rarely lands in the same room before service, and the notes on the bulletin board stop getting read by Wednesday. The consistency comes online now through the channels the team already checks. POS alerts at clock-in for the must-know items. A group thread for live notes during service. Scheduling apps with a built-in comms layer are the cleanest of the bunch, because the team is already in there to see their hours, so the messages land. Whichever you use, the discipline is the same: today's reservations, today's specials, today's known weak spots, in the channel they're going to read anyway.

Make the list of pieces you've been worried about. The compressor that sounds different. The fryer recovery time that's gotten worse. The hood that struggled on the last hot night. The electrical that tripped twice last month. Every operator has the list; most have never written it down.

For your fryers, your refrigeration, your hot-holding equipment: actual recovery times under load, measured against spec. A fryer that should recover to temperature in 90 seconds and is taking 180 is an oil-change-or-replace decision you should be making on your schedule, not the equipment's. Same for refrigeration that's not holding temp on a busy day, hot-hold that's drifting, freezers that are working harder than they should.

Whatever you've been deferring, schedule the service. Hood cleaning. Walk-in seal inspection. Fryer boil-out. Grease trap pumping. PM on the ice machine. Electrical inspection if you've had nuisance trips. The cost of preventive service is bounded; the cost of failure is not.

Walk your equipment list against what the operation demands at peak. Refrigeration capacity for prep volumes. Ice machine sized for peak service. Hood capacity for the hottest cooking day. Capacity that's "enough most of the time" fails the rest of the time. Knowing where you're under capacity is the conversation, even if the fix is for next year.

The POS reflects the menu and the operation as both stood the last time someone took the time to organize it. Open the menu screen and look. Items that don't sell anymore. Modifiers that no longer apply. Categories that grew bloated. Buttons in the wrong place. Order entry should match how the kitchen runs today, not how it ran two years ago. An hour of cleanup here saves friction on every shift.

The connections between your tools break quietly. Online orders that should auto-flow into the POS get hand-keyed instead. Tips that should route to payroll get reconciled manually. Inventory counts that should pull from sales get rebuilt by hand. Most operators have at least one of these and have learned to work around it. The check is asking each tool: what's it supposed to talk to, and is it talking?

Pick two or three points that matter and verify they work. Place a dummy online order and follow it through to the receipt. Pull yesterday's labor report and see if it matches what you'd guess from the shift. Test a comp through the POS to see if it lands clean in the daily summary. The point isn't to test everything; it's to confirm the things you rely on are still doing what you think.

Most operators are paying for features they never turned on and tools that overlap with features already in the POS. Both add up. Pull up your POS provider's feature list once a year and ask what's included in your tier. If there's overlap with another subscription, decide which one stays. If there's a dormant feature that would save a step, turn it on. This pass usually finds money on the table.

Every contract renewal date on a calendar you actually look at. Auto-renewal pricing exists because operators don't see it coming. Putting renewals on a calendar with a thirty-day lead time turns auto-renewals back into negotiations. The same calendar entry is where you ask: what's working, what's quietly stopped working, what's changed in the operation since the last look.

Your primary category is the most important field on the entire profile. Get it specific. "Restaurant" is too broad; "Mexican restaurant" or "Coffee shop" or "Sandwich shop" is specific enough that Google can match you to the right searches. Attributes (outdoor seating, takeout, dog-friendly, accepts mobile payments) tell Google how to rank you against filtered searches. Walk every attribute and confirm it's accurate.

Your hours on Google are what Google tells the guest. If they're wrong by an hour, you're either turning away covers who showed up too early or annoying guests who showed up to a closed door. Special hours for holidays matter too; a "closed" status when you're open kills the entire decision.

The cover photo and the first three to four photos do most of the work. They should look like the operation looks now, not how it looked at the soft open. Food photos that match what's on the menu. Interior photos that show the room as it is. If your photos are five years old, your discoverability is tied to what the room used to be.

Every review gets a response. Positive ones get a short thanks. Negative ones get a measured, professional reply that acknowledges the issue without arguing. Google reads response rate. So do guests scrolling through. An unresponsive profile reads as an inattentive operation.

Most operators don't know Google has a Q&A section on their profile. Anyone can ask a question; anyone can answer it. If you don't answer first, someone else will, and they might be wrong. Walk through the questions, answer them, and seed the most common ones yourself.

Pull out your phone, search yourself the way a stranger would, and walk the path. Did the site load fast? Is the menu readable without zooming? Are the prices current? Can you find your hours without hunting? Can you tap to call without three steps? Most operators have never done this on their own site, and the gaps are obvious the first time you do.

Your menu lives in three or four places: your website, your Google Business Profile, your delivery platforms, and the wall inside your operation. They need to match. A menu on the website that doesn't reflect last quarter's price changes is a guest who shows up expecting one number and finds another. That's the wrong moment to surprise someone.

If you take online orders, count the taps from "I'm hungry" to "order placed." Industry research is consistent: every additional tap drops conversion. Seven taps where three would do is a lot of orders walking away. Look at where the flow asks for information you don't need, where it offers upsells that interrupt the path, where it forces account creation. Each of those is a friction point you can probably remove.

Your online ordering should be talking to your POS. Your reservation system should be talking to whatever you use for guest data. When systems don't integrate, somebody has to manually bridge them, which means errors and delays and a guest experience that doesn't feel like one operation. Map what you have. Note what doesn't connect. That's a punch list.

[Pending editorial pass]