I talk to food and beverage operators almost every day who tell me the same story with different numbers. "We did $1.2 million last year." Or $800K. Or $2 million. And then, quietly, almost embarrassed: "But I'm not sure where the money went."

The revenue is there. The top line looks healthy. If you looked at the sales reports, you'd think the business was thriving. But the owner is still pulling 60-hour weeks, still stressed about making payroll, still carrying credit card balances to cover the gaps between what comes in and what goes out. The bank account tells a different story than the POS system.

This is the revenue-rich, profit-poor trap. And it's one of the most common conditions in the food and beverage industry. Not because operators are bad at business — most of them are incredibly resourceful. It happens because the operation isn't designed to convert revenue into profit efficiently. The infrastructure between the top line and the bottom line is full of leaks.

The gap between revenue and profit is operational

Most operators think about profit as what's left over. Revenue minus costs equals profit. And in theory, that's true. But in practice, "costs" is not a single number you can control with one decision. Costs are the sum of thousands of micro-decisions that happen every day, every shift, across every station in the operation. And without systems governing those decisions, waste accumulates invisibly.

Here's a concrete example. A restaurant doing $25,000 a week in sales with a 30% food cost target should be spending about $7,500 on food. But if the prep cook is over-portioning proteins by 10% — and they usually are, because there's no portion guide posted at the station and no one is checking — that's $750 a week in excess food cost. Over a year, that's $39,000. From one station. One behavior. One missing system.

Now multiply that across every area of the operation. Over-ordering because the pars aren't set and nobody's tracking inventory velocity. Overtime because the schedule was built reactively instead of against a labor model. Comps and voids because the service system doesn't catch mistakes before they reach the guest. Supply runs at retail because the ordering cadence doesn't account for lead times. Every one of these is a leak. And none of them show up as a single line item that screams "fix me." They just quietly erode the margin, week after week.

Revenue growth makes it worse, not better

This is the part that catches operators off guard. They assume that if they can just increase sales — add catering, launch delivery, book more private events — the profit will follow. And for a brief window, it might. A new revenue channel brings in cash that temporarily papers over the gaps.

But here's what actually happens: every new channel adds operational complexity. Catering requires a different prep flow, packaging inventory, delivery logistics, and a separate order management process. Delivery platforms take 20-30% off the top and add ticket complexity to the kitchen. Private events pull staff from regular service and require a different coordination model. Without the infrastructure to manage that complexity, each new channel becomes a new set of leaks.

I watched a barbecue operation go from $600K to $1.1 million in 18 months by adding catering and wholesale. The owner was thrilled about the revenue growth — until the year-end numbers came in and profit had actually declined. In absolute dollars, not just as a percentage. They made more money and kept less of it. Because the operation was built for a $600K restaurant, and they tried to push $1.1 million through it without rebuilding the infrastructure.

The four profit leaks I see in almost every operation

Leak 1: No cost visibility cadence. Most operators check their food and labor costs monthly — when the accountant or bookkeeper delivers the P&L. That's 30 days of lag time. In an industry where margins are measured in single-digit percentages, finding out you had a bad month after the month is already over is like finding out about a leak after the basement is flooded. You need a weekly cost pulse at minimum. Ideally, you're tracking key numbers daily — sales per labor hour, covers per shift, waste log totals. Not because you need to obsess over data, but because you need to see the deviation before it compounds.

Leak 2: No menu engineering discipline. Most menus are built on intuition — what the chef wants to cook, what seems to sell, what the competition offers. Very few operators have done a rigorous contribution margin analysis on their menu. Which items actually make money? Which ones are popular but low-margin? Which ones are high-margin but never get ordered? Menu engineering isn't about eliminating items people love. It's about understanding the financial architecture of what you sell so you can make informed decisions about pricing, placement, and promotion. A single menu restructure — without changing a single recipe — can shift gross margin by two to four points.

Leak 3: No labor model tied to revenue. Most scheduling in food and beverage is done by feel. The manager looks at last week's schedule, adjusts based on what they think next week will look like, and posts it. There's no underlying model that connects projected sales to optimal staffing levels by position, by daypart. This leads to chronic over-staffing on slow shifts and under-staffing on busy ones. Both cost money — one directly through excess labor, the other indirectly through lost sales, poor service, and employee burnout. A proper labor model doesn't have to be complicated. It just has to exist.

Leak 4: No channel profitability analysis. When an operator tells me they do dine-in, takeout, delivery, catering, and wholesale, my first question is: "Which of those channels actually makes money after all costs are accounted for?" The answer is almost always a blank stare. They know the total revenue, but they've never broken it down by channel and allocated the true costs — platform fees, packaging, labor allocation, vehicle costs, insurance. I've seen operators lose money on delivery and not know it because the revenue looked good in aggregate. Channel profitability analysis isn't optional for a multi-channel operation. It's the difference between growing strategically and growing into a bigger version of the same problem.

The fix isn't more revenue

If your operation is revenue-rich and profit-poor, the answer is almost never to sell more. The answer is to install the systems that convert what you're already selling into actual retained profit. That means operational visibility — knowing your numbers in real time, not 30 days later. It means process controls — portion systems, waste tracking, inventory cadences. It means a labor model that matches staffing to demand. And it means honest channel analysis that tells you which parts of the business are worth growing and which ones are subsidized liabilities.

This is the operational work that nobody talks about on restaurant Instagram. It's not glamorous. It's not a new menu item or a beautiful dining room renovation. It's the infrastructure underneath the business that determines whether a dollar of revenue becomes seven cents of profit or gets lost in the gaps.

When someone runs a CoreScore assessment, one of the first things it reveals is the relationship between operational infrastructure and financial performance. Not in theory — in the specific dimensions of their specific operation. Where the visibility gaps are. Where the process controls are missing. Where the revenue is leaking before it ever reaches the bottom line.

Because the goal was never to do more revenue. The goal was to keep more of what you earn. And that's an operations problem.