Why Batavia restaurants cater one office lunch and lose the next

It is 10:15 on a Tuesday morning in Batavia and lunch prep is just getting going. The phone rings. An office manager at a manufacturer off Kirk Road needs lunch for thirty on Thursday. It is the quarterly meeting, there are a couple of vegetarians and one person who cannot have gluten, and the food should come to the side door by 11:45.

Your kitchen pulls it off. Two trays of chicken, a pasta, salads, and the gluten-free plate labeled with a name. The driver comes back and says they were happy. The office manager paid with the company card, and the ticket goes on the spike with the rest of the day.

Three months later the next quarterly meeting comes around. Two weeks before it, she gets an email from a place across the river with their fall catering menu and a line asking how their last lunch went. She orders from them. Nobody at your restaurant knew her name, and nobody noticed she was gone.

Why the second order slips away

The second order is the cheapest one you will ever win, and nobody asks for it.

Think about how the office manager decides. Feeding a meeting is one of forty things on her plate, so she wants the order that takes the least effort and carries the least risk. Whoever reaches her at the moment she needs lunch, with her headcount and her gluten-free note already on file, is the easiest yes. She has nothing against you. She has a meeting on Thursday.

On your side, the order came in as a phone call, got written on a ticket, and got paid on a card. Her email, the occasion, the side door, the gluten-free plate: all of it lives on a piece of paper headed for the recycling bin. The manager who took the call did it between the lunch rush and a produce delivery. Following up on catering is nobody's job, because catering is extra money on top of the dining room.

Offices feed people on a rhythm. Monthly staff meetings, quarterly reviews, training days, the December lunch. A customer who ordered for a quarterly meeting will need lunch again in about ninety days. You knew that the day she called, but nothing in the building held on to it.

Nobody counts it either. Ask how many catering customers ordered once last year and how many came back, and unless someone keeps a list, you will get a guess.

What follow-up looks like when a system does the remembering

None of it is complicated. It just has to happen on a Wednesday afternoon when you are short a line cook, which is why it does not happen now.

• Every catering order becomes a customer record the moment it is placed: company, contact, phone, email, headcount, what they ate, the occasion, and the delivery notes. The side door and the gluten-free plate get entered once and stay.
• The afternoon after the delivery, she gets a short note under your name asking how lunch went and whether anything should change next time. Any reply goes to a person. A complaint reaches the manager that day.
• The occasion sets the next reminder. A quarterly meeting gets a note about two weeks before the next one. A monthly training gets a monthly one. A one-time retirement party gets none.
• The reminder carries a reorder link with last time's order filled in. She changes the date and the headcount, and the order lands in the kitchen's queue with the same notes the driver needed the first time.
• A few times a year the list gets a seasonal email, holiday lunches in November for example, with an easy way to opt out. Nobody gets a weekly blast.
• On Monday you get one list: catering customers, how many times each has ordered, the last order date, and which ones are past their usual rhythm with nothing new on the books.

None of this asks your staff to learn new software. It sits between the phone, the website, and the point of sale you already use. I built the tracking side of this pattern for a Chicago-area pool service company, where a lead is captured at first contact and followed until it becomes a job. A catering customer is the same kind of record. The difference is that the job can come back every quarter.

What stays with you

The food stays with you, and so does the phone call that matters. When the Monday list shows the office off Kirk Road is two weeks past its usual order, you pick up the phone. Five minutes talking to the owner will do more than a third automated note, and the system's only part in it is telling you who to call.

Complaints stay human. If the pasta showed up cold, the fix is a person apologizing and deciding how to make it right, and the system should hand that off the minute a reply sounds unhappy.

Pricing stays yours too: a better rate for the office that orders every month, a number for two hundred people at a company picnic, whether to take a Thursday order when the dining room is already booked. The system remembers who ordered and when. The relationship still belongs to you, and to the driver who knows the receptionist by name.

When this is not worth building

If you do a handful of catering orders a year, keep a list on paper and put reminders in your phone. If your catering menu and prices are not written down in one place, that comes first, because a reorder link can only offer what already exists. If the leak is earlier, at the inquiry that never got a callback, the post on catering intake covers that end. If it is later, at getting paid, see the one on catering invoices.

Builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable. There is more on the restaurants page and on what I build for businesses in Batavia.

Where to start

The first step is a free 20 minute process audit. We pull last year's catering tickets, count the customers who ordered once and the ones who came back, and put a number on the gap. If a system pays for itself, build it. If it does not, you keep the count. Start here.