2023-10-05
No Layers
What it really means to put the guest first — and why most operators never get there.
What it really means to put the guest first — and why most operators never get there.
There is a meeting that happens in almost every large corporate dining contract. It sits about three levels above the person actually responsible for the food. Someone from procurement, someone from facilities, someone from HR, and a regional account manager from the operator. No chef in the room. No one who touched a pan that morning. Just slide decks and scorecards.
I have sat in that meeting. I have been in the room when the decision about what 4,000 employees eat every day gets made by people who eat somewhere else.
That is the problem we built Rudy's to solve.
The conventional contract dining model is built on distance. A national operator wins a bid, assigns an account manager, and that account manager becomes the single point of contact between the client and a system that is structurally designed to optimize for margin, not food. Feedback travels upward through layers. Decisions travel downward through the same layers. By the time a guest's experience influences a menu change, six months have passed.
The guest experience is an output of that system. It is not the center of it.
This is not a criticism of the people in those organizations. It is a description of the architecture. When a company is built to operate at national scale, the systems that enable that scale are the same systems that create distance from the guest. That is not a bug. It is a feature — for that model.
It is just not our model.
When we say no layers between the decision and the guest, we mean it operationally. Not as a tagline.
It means that when a client tells us Tuesday's soup was too salty, that conversation happens with the person who scheduled the cook line that morning — not with a regional account manager who will log it in a CRM and flag it for the next quarterly review.
It means that when we see a participation drop on a particular station, we pull the numbers, walk the floor, and change the menu in the same week. We do not submit a change request through a concept approval matrix.
It means our Executive Chef knows the names of the guests at the companies we operate for. He knows what their people eat. He knows the culture of the building because the culture of the building shows up in what people choose for lunch.
Most operators would call that over-involvement. We call it the job.
We are independently owned. Founded in Clarkston, Michigan in 1933. That is relevant not as heritage marketing — it is relevant because ownership structure determines decision-making speed.
When a client needs something, the person they call has the authority to say yes. There is no escalation path because there is no one above us to escalate to. Robert Esshaki built this company. Chris Thomas has been in this industry for over 35 years. I have spent 23 years in hospitality operations. When we sit across from a client, we are not account managers. We are operators. We are owners.
That distinction changes everything about how fast you can move, how much you can customize, and how honest the conversation gets when something is not working.
We did not get into corporate dining because we wanted to serve institutional food. We got into it because we believed the workforce deserved what the restaurant guest gets — chef-driven menus, real ingredients, and a team that is proud of what comes out of the kitchen.
The 16 culinary concepts we operate are not branding exercises. They are working kitchens with their own identity, their own menu architecture, and their own standard of execution. Garden is not just salads. Flame is not just a grill station. Each concept represents a promise to the guest about what they are going to experience — and our teams are held to that promise every service.
That is harder to operate than a generic café line. We know that. We choose it anyway, because the alternative — a cafeteria that no one looks forward to — is not something we are willing to put our name on.
No layers is not a service promise. It is an operating philosophy. And the day we build a layer between the decision and the guest is the day we become the thing we set out to replace.
Refined dining hospitality for the modern workplace. 15 chef-driven culinary concepts, scratch-made daily. Independently owned, Michigan rooted.
