All articles
How to run an employee meal program
For Employers
3 min read

At one o'clock, the office empties in ones and twos. Someone is downstairs in the heat, watching a delivery app recalculate an arrival time that keeps slipping. Someone else has given up deciding and is eating biscuits at her desk. A third has left for the place around the corner and won't be back for the better part of an hour. By two, everyone has eaten, more or less, and no one has said a word about it. This happens every day, in most offices, and almost no one thinks of it as a problem to be solved.
That's the strange thing about lunch at work. It is a universal need, and an invisible one. Because everybody sorts it out somehow, nobody notices the cost, the lost half-hours, the small daily drain of deciding, the colleague who's running on nothing by mid-afternoon. It never appears on a balance sheet. So it never gets fixed.
Start with two questions
But some companies do fix it, and the ones who do tend to discover the same thing: feeding people well is one of the quietest, most reliable ways to make a workplace better. Not a perk. A kind of care people can taste. The question is how to do it, and here the honest answer begins with two questions of your own.
The first is: who pays? If the company covers the meal, people eat it, participation takes care of itself, because a paid-for lunch becomes the natural default. If employees pay their own way, you are asking them to choose you, every day, over every other option including nothing at all, and now the food has to earn its place. Neither is wrong. But they are different programs, and you should know which one you're running before you run it.
The second question is quieter, and more people get it wrong: do you want variety, or do you want reliability? The instinct is to chase variety, to fear boredom. The truth is that dependability is what makes a meal program live. Food that comes at the same time every day becomes something people build their afternoon around. Food that dazzles on Monday and vanishes on Thursday teaches people not to count on it. Pick reliability. You can add variety later; you cannot add trust later.
Your options
With those settled, the options more or less choose themselves, and each tells its own small story.
There is the WhatsApp group, where most teams begin. It is genuinely clever, a working system built out of a chat app because nobody offered anything better. But it rests on one person, usually the most organised in the office, who never volunteered to spend their mornings tallying orders and chasing payments. It holds until the team grows, or until that person takes a day off, and then it doesn't.
There are the delivery apps, which solve everything except the things that matter for a team: the fees that pile up unseen, the absence of anything shared, the reliability you've quietly handed to a stranger on a motorbike. Fine for a one-off. Punishing as a habit.
There is the canteen you build yourself, the real thing, with its own kitchen and staff. It is wonderful, and it is why good canteens have always belonged to big companies. For almost everyone else, the space, the overhead, and the management are simply out of reach.
And there is the newer option, the managed platform, which exists precisely to hand a small company what used to require a large one: vetted caterers, ordering, delivery, all run for you, the canteen without the kitchen. It lives or dies on the quality of whoever runs it, so choose carefully. But done well, a team of fifteen can eat the way a team of five hundred does. This is the work we do at Kater.
What actually makes it work
Whichever path you take, the same four things decide whether it works, and they matter more than the choice itself.
Vet whoever cooks for your people, really vet them, for hygiene and handling, not just taste. It is the thing no one checks until someone falls ill, and by then it is a catastrophe rather than a precaution. Insist on reliability, because on-time every day is what turns a service into a routine. Keep the price predictable, so no one, employee or finance team, has to do arithmetic to know what lunch costs. And keep the admin light, because any program that depends on one hero quietly running it has an expiry date written into it from the start.
Just begin
None of this requires getting it perfect. It requires beginning. Pick the setup that fits your size and your budget, make it dependable, let your team learn that lunch is simply handled now, and improve it from there. The companies that feed people well are rarely the richest. They are the ones who decided it was worth not leaving to chance.
And if what you want is that older, better idea, a proper canteen for your team, without building one, that is exactly the gap we set out to fill.


