The retreat that changed how we feed teams was a five-day stay at a rented house in Charleston. Eighteen people, mostly engineers, no on-site kitchen staff. The original plan was the standard one: catering company brings trays in for lunch and dinner, sets them on the long table, refreshes the chafing dishes, leaves. We've done that a hundred times. It works. The food is fine. Nobody loves it.
Two days before the retreat, the catering company canceled. We had forty-eight hours to figure out feeding eighteen people for five days, and the only Charleston option that picked up the phone was a local weekly meal service. We figured it'd be a stopgap. It ended up being the best decision we made on that whole trip.
What changed when the food got local
The first dinner was a slow-cooked low-country dish from a restaurant in West Ashley. The team was sitting around the table, someone said "wait, where is this from?", and the conversation shifted. Suddenly we were talking about the city. The engineers from Brooklyn were asking the local team where to get breakfast the next morning. Two attendees made plans to go back to the source restaurant on the last night.
The food was the conversation. That doesn't happen with chafing dishes. The catering tray is invisible — fuel, not experience. Whereas a meal that came from a place forty minutes from where you're sitting carries a story, and stories get the team talking to each other.
Why a weekly meal service works for retreats
We've been using Lilac in Charleston ever since. It's a weekly meal subscription that rotates through real local restaurants — pick a delivery day, pick the meals, the food shows up. It was built for households, but the same flow works beautifully for retreats. Five-day stay, four delivery windows, zero catering coordination.
The math works too. Catering quotes for that retreat were running between $45 and $65 per person per meal. The local meal route landed somewhere around $22, with portion sizes that the team actually preferred. Catering portions are designed for buffet logic — too much, served lukewarm. Restaurant portions are designed for a person sitting down to eat. Different goal, better outcome.
What you lose, and why it didn't matter
Catering gives you presentation — the chafing dishes, the staffing, the silver-platter effect. We lost that. What we got back was every meal feeling like the team had wandered into a small restaurant together. People served themselves. The kitchen counter was where the conversation happened. It felt like a vacation house with friends, not a corporate function with a hot bar.
We also lost the "one menu, eighteen plates" uniformity — which sounds like a downside until you realize that letting people pick their own meal in advance solved the dietary-restriction nightmare we usually spend hours on. Vegetarians got vegetarian. Gluten-free got gluten-free. Nobody ended up with sad rice and a side of regret.
Where this works (and where it doesn't)
Local meal service works beautifully for multi-day retreats in a rented house or a venue with even a basic kitchen. It works for teams of eight to forty. It does not work for a hotel ballroom on a single night where the whole point is the formal dinner. Use the right tool for the right occasion.
We've since recommended this approach to four other retreats, all in cities where local meal services exist. Every one of them has come back saying the same thing: the food felt like the place, the team talked more, and the catering line item went down. That's a rare combination.
Planning a retreat in Charleston? We feed our teams through Lilac — local weekly meal subscriptions from restaurants you'd actually choose yourself. It's the easiest catering swap we've found, and it changes how the team eats together.