Operator Truth No. 01. Not because chefs can’t do it. Because the chef job is already a full plate.
Your best chef shouldn’t be your buyer.
In almost every independent restaurant I’ve ever worked in or walked through, the chef is exactly who the buyer is. That’s the design, not the accident. Most chef roles include purchasing by default. Chefs know it’s there when they take the job, and most are perfectly capable of doing it.
The problem isn’t ability. It’s time. And the cost of asking one person to do everything is higher than most owners realize.
This is the first essay in a series I’m calling Operator Truths: short statements about the realities of running hospitality at scale, each one earning its own treatment in these pages. Twenty-eight of them prepared so far, and counting.
The chef I worked for
The chef at Landmark Cafe in Faneuil Hall was carrying everything.
Menu. Food quality. Prep. Staffing. Scheduling. Vendor communication. Purchasing. Price comparisons. Receiving. Substitutions. Kitchen maintenance. Cleaning standards. Training. Food cost. Administration. Parts of the bookkeeping and financial review.
He was running three restaurant spaces in the same building. That alone would have been three jobs. Everything else, including purchasing, scheduling, training, and food cost, was stacked on top.
I remember him locked in his office for stretches of 12, 14, even 16 hours a day. There were days I barely saw him in the kitchen because so much of his time was consumed by everything around the kitchen, not the work inside it.
None of that was unusual. The job of a chef has always included most of what he was doing. He knew that going in. He was capable of doing every piece of it. He was doing every piece of it.
But the cumulative load was crushing the parts that needed the most attention. The kitchen was the thing that suffered when something else demanded his time, and in any given week, something always did.
When he asked me if I wanted to manage purchasing (a story I told in Issue #1), it was not really a delegation. It was a reorganization. He was not handing me a task. He was creating dedicated capacity for a function that had grown too large, too important, and too time-consuming to be done well alongside everything else.
That distinction is the one I want to push on here. Asking someone else to do purchasing is not delegating a chore. It is redesigning the role.
Why purchasing loses the time war
The chef role, properly defined, includes menu design, food cost, quality standards, prep, line leadership, training, scheduling, hiring, food safety, cleaning standards, vendor management, purchasing, receiving, kitchen culture, and a long tail of administration. Each of those is legitimate. Each is part of the job. Most chefs can do each one well.
But every chef has the same twenty-four hours. And in any given week, something has to lose. The question is which one.
In most kitchens, purchasing is the function that loses first, because purchasing can be done badly without immediate failure. Service starts at 5 whether the new menu is ready or not. The staff meeting at 3 has to happen. The line cook hired Monday needs training tonight. The health inspector is coming Tuesday. Each of those has a hard deadline.
Purchasing’s deadline is more forgiving. You can wait until 4 in the afternoon, call the vendor, place the order, and product will probably arrive. Service will happen. The plate will go out. No one in the dining room will notice. Not until the food cost report at month-end, when margin has quietly drifted in a direction nobody can quite explain.
That is the trap. Purchasing is the function that absorbs the squeeze because it is the function that does not shout when it loses. It can run on habit instead of judgment for weeks before anyone catches it.
What it actually costs
The cost shows up in four places, and none of them are obvious.
Margin. Without dedicated time for comparisons, supplier strategy, credit recovery, and invoice review, prices drift, missed credits accumulate, and the cheapest line item is the one nobody noticed wasn’t cheap anymore. Habit buying takes over. Orders still go out, but active discernment has disappeared.
Culinary quality. A chef who is split-brained between vendor calls and the line is not running the line. Creativity erodes. Consistency erodes. The plate suffers in ways nobody can quite point to, because no single missed dish caused it.
Time. The 4 a.m. phone calls and the afternoon vendor follow-ups are stolen from cooking, training, mise en place, and menu development. Those hours have a real cost. They just don’t show up on the P&L line where the trade-off was made.
Retention. Chefs increasingly resent administrative work that crowds out the cooking. The market for talented chefs is brutal. When yours is spending three hours a day on vendor questions and invoice resolutions, somebody else is going to offer them a kitchen where they can actually cook.
The obvious objection
I know the objection. I can’t afford a dedicated buyer.
Fair. Most single-location operators can’t justify a full-time procurement hire. That isn’t the point. The point is that somebody, somewhere, needs to own this work with dedicated time, not as the fifteenth item on someone’s list.
That could be a regional purchasing role in a group. A shared service across locations. An outside partner who does the comparing, the audit, and the supplier management on your behalf. A redesigned role for someone you already employ, like a sous chef whose week formally includes a few hours of protected procurement time instead of bleeding into it.
The fix isn’t always headcount. The fix is deciding the work has an owner, and that the owner has actual time to do it well. Once both conditions are met, the work gets better. As long as either is missing, it stays expensive.
Why the right person matters
When my chef chose me for the purchasing role, he could have chosen someone purely administrative, purely systems-oriented, or purely organized. He didn’t. He chose someone who had worked inside the kitchen, someone who had cleaned coolers, organized walk-ins, cooked the line, expedited service, and understood what it cost the operation when the wrong product or wrong quantity arrived.
He also chose someone with a business mindset. I was studying marketing and business at the time, and that academic frame mattered. I could think about supplier programs, pricing structures, and process design, not only about today’s order.
And, most importantly, he gave the role real time. Purchasing wasn’t one item on a longer list. It was the list.
Kitchen fluency, business mindset, and protected time. Three conditions. Most operations underestimate how rare the combination is, and how valuable it becomes when you find it. The chef still owned the standards. I owned the process. When that division is clean, both jobs get done better.
What ChefMod was built to do
This is part of what ChefMod was built around. Not just to give operators software, but to give them the procurement function they could rarely afford or assemble in-house. People who know the kitchen. Process that catches what falls through the cracks. Platform that makes the whole thing visible. The chef keeps the standards. We carry the rest.
That is the shape of the support the chef at Landmark Cafe needed. It is the shape most kitchens still need today.
The deeper principle
Underneath this Operator Truth is a broader one. Some functions are too important to do part-time.
Procurement is one of them. So is hiring, when hiring is taken seriously. So is training. So is the financial review that connects food cost to margin. Each of these can be done part-time by someone juggling six other things, but each of them suffers when it’s done that way. The visible work continues. The quiet work degrades.
The chef role isn’t broken because chefs aren’t capable. It is strained because the role has expanded faster than the day has gotten longer. Asking the most senior person in the kitchen to also be the most senior person in procurement is asking them to do two full jobs and giving them time for one.
Worth asking, for your own operation
-
Who owns procurement in your operation, and what percentage of their week can they actually give it?
-
How many hours each week is your chef spending on vendor calls, pricing questions, and invoice issues?
-
If you removed those hours, where would your chef put them, and what would that time be worth?
-
When something has to give in a busy week, what gives first? Is purchasing the silent loser?
-
If purchasing were treated with the same priority and protected time as service or staffing, what would change?
The operators I respect most can answer those questions cleanly. The ones who can’t aren’t bad operators. They’re running roles that were complete before purchasing got added on top.
Close
Your best chef shouldn’t be your buyer.
Not because chefs can’t buy. Most can, and most have. But because the chef job is already a full plate, and purchasing is the function most likely to lose the time war when something has to give. The cost shows up in places that don’t get measured, and the operation pays it regardless.
If this is something you’re navigating in your own restaurant, club, hotel, catering company, or hospitality group, I’d love to hear how you’ve structured it. Reply, comment, or DM me. That’s the conversation this newsletter is for.
John
Related issues
Behind the Line goes out every Tuesday for multi-unit operators who would rather hold the line than explain where the money went.
Want to know what your own numbers look like? ChefMod runs procurement for multi-unit independents: the agreements, the price checks, the receiving discipline, and the weekly numbers underneath all of it.