By Matt Wampler, CEO of ClearCOGS
On a recent intro call, we met a woman with an unusual vantage point on this industry. Her day job is vice president of asset management at a real estate firm. Her family business is restaurants: her in-laws started the first one, her brother-in-law and his wife opened the second, she and her husband partnered on the third, and two more concepts are on the way. She was brought in, in her words, because expenses at the first two were running too high. She came looking for systems.
And she offered the sharpest one-line diagnosis of restaurant economics we have heard in a long time. In her real estate world, revenue moves once a month: rent comes in, expenses are contractual, and reviewing the numbers monthly matches how the business actually behaves. A restaurant, she said, is the opposite: an endless stream of tiny transactions, and just as many tiny ways to fritter away the income.
That sentence deserves a framework around it, because it explains why so many capable, financially literate people feel like restaurants leak money through their fingers.
The Cadence Mismatch
Nearly every tool of traditional financial control runs on a monthly rhythm. The P&L closes monthly. The bookkeeper reconciles monthly. Plenty of operators, including the chef and operator in this family, are more honest than that: they look hard at the books around tax time, once a year, and discover they made less than they thought.
But a restaurant’s margin is not decided monthly. It is decided hundreds of times a day, in decisions too small to feel like decisions. How much to prep. Whether to open another bottle. How heavy the portion runs when the kitchen is slammed. Whether to cut a server at nine or nine-thirty. Each choice moves a few dollars. None of them appears anywhere until they have been made ten thousand more times and congealed into a food cost percentage on a statement nobody reads until spring.
This is why the leak feels mysterious and is not. The landmark research on restaurant failure, the Cornell Quarterly study by Parsa and colleagues, found that about 26 percent of independent restaurants fail in their first year, a far cry from the folklore figure, and its deeper finding was that internal and managerial factors weigh more heavily than previously believed. Restaurants rarely die of one dramatic wound inflicted from outside. The game is won or lost inside the four walls, in exactly the small recurring decisions that monthly review is structurally blind to.
The Twenty Bottles
Her family had a perfect emblem of this, and it is the detail we cannot stop thinking about. Every weekend, bottles of wine that had been opened but not finished came home from the restaurant, sometimes twenty of them. And here is the important part: her mother-in-law was delighted. Free wine, week after week. A perk of the family business.
Then the asset manager looked at it and said the quiet part: this is not a gift, it is a leak with a bow on it. Every bottle in that trunk was opened, often a sixty-dollar bottle, to sell a single glass. Nobody did anything wrong on any given night; a guest ordered a pour, and the bartender served it. The loss only exists in aggregate, which is precisely why nobody saw it. Leaks at daily cadence do not look like losses. They look like leftovers.
What the family did at the new restaurant is a small masterpiece of operational thinking: they cut the by-the-glass list from around thirty options to six. Notice what that fix is. It is not more training, more discipline, or more counting. It is decision design: they removed most of the situations in which the expensive mistake could occur. The best fix for a decision made badly a hundred times a day is often to stop requiring the decision at all.
The Person Who Is the System
The other thing this family sees clearly is where all those daily decisions currently live: in two people. The chef in the kitchen, the operator on the floor, both talented, both making calls on the fly, and, as she put it, in a vacuum, without all the information. When the operator covers one location, the other wobbles. The family’s ambition to keep growing runs straight into the fact that she is one person.
What struck us most was the spirit of what they want. Not surveillance, not a dashboard to catch anyone out. They want the two people who make the place great to get their jobs back: the chef cooking, the operator touching tables, and the behind-the-scenes arithmetic happening somewhere else, reliably, without either of them having to become the spreadsheet. That is the correct ambition, and it is worth stating plainly because operators often hear “systems” as an accusation. It is the opposite. A system is how you protect your best people from carrying the whole business in their heads.
Match the Control to the Cadence
The principle underneath this whole story: match the frequency of your information to the frequency of your decisions. A once-a-month business can be run off a monthly statement. A three-hundred-decisions-a-day business cannot, and no amount of month-end discipline fixes that, because by the close of the month the decisions are all already made. Daily decisions need daily numbers: what today is likely to sell, what to prep for it, what to pour, who to schedule. This is, candidly, the entire reason ClearCOGS exists as a daily product rather than a reporting tool: a forecast that arrives every morning meets the decisions on the schedule the decisions actually keep.
The audit this operator would run in your building takes one honest hour. List the five decisions your team makes most often in a day. Next to each, write down how often real information touches it: daily, monthly, or tax time. Every mismatch on that list is a place the business is frittering, one pour, one portion, one guess at a time. And then ask the question her family finally asked: what is coming home in the trunk every weekend that everyone still celebrates?
Sources
- Parsa, H. G., Self, J. T., Njite, D., and King, T. Why Restaurants Fail. Cornell Hotel and Restaurant Administration Quarterly, 46(3), 304-322. 2005. Via University of Denver Daniels College of Business. daniels.du.edu
