The Catering Order You Lost Was a Slow Reply

Someone emailed you on Tuesday about feeding 40 people at an office on Thursday next week. You read it between the lunch push and a delivery, thought "I need to sit down and work that out properly," and got back to it Wednesday night. By then they had booked someone else.

You did not lose that job on price. You lost it on speed. The person organizing that lunch is not a food person. They are an office manager with a task on a list, and they emailed three or four places at once. The first clear number that lands in their inbox becomes the default, and everything after it has to beat a decision that has already half-formed.

Restaurant catering orders are decided in the first few hours. The fix is not working faster. It is deciding the answers once, in advance, so the reply is assembly instead of arithmetic.

Why the quote takes you an evening right now

Every catering enquiry you answer from scratch makes you re-solve the same four problems. How much food per person. What that costs you. What you should charge. Whether you can actually do it that day.

That is a forty-minute job when you are fresh and a two-hour job when you are tired, which is why it slides to the end of the night and then to tomorrow. And because you are solving it fresh each time, your pricing drifts. The corporate lunch you quoted in March and the one you quoted in June are not built the same way, so you never learn whether catering is making you money.

The owners who win this work are not smarter. They have a sheet. The sheet was hard to make once and costs nothing to use.

Build the standing quote structure

Sit down on a slow afternoon and write down the following. It does not need to be pretty. It needs to be decided.

Per-head tiers. Three packages, not a menu. Something like a simple tier, a mid tier, and a full spread. Each one is a fixed price per person with a fixed list of what's included. The buyer does not want to build a menu. They want to pick one of three things and stop thinking. Price each tier off your real food cost the same way you price the à la carte menu — the logic in how to price a menu when food costs keep moving applies here, with one extra pressure: catering has labour spikes that dine-in doesn't, because it all gets made at once.

A minimum. A head count minimum, a dollar minimum, or both. Ten people is usually not worth the pans, the drive, and the setup. Write the number down so you are not negotiating with yourself at 9pm. A minimum also protects you from the slow bleed of tiny orders that eat prep time on a Friday.

A delivery radius and a delivery fee. Draw a circle. Inside it, one flat fee. Outside it, you don't deliver, or you deliver at a stated higher fee. In the GTA this matters more than people expect, because a 12-kilometre drive at 11:30am on a weekday is not a 20-minute drive. Decide once whether you are going up the Don Valley for a 30-person order, so you are not deciding it while a driver waits.

Deposit and cancellation terms. A percentage deposit to hold the date, a final head count deadline, and what happens if they cancel inside that window. Say it plainly in the quote. Corporate buyers expect this and will not blink. The awkwardness is entirely in your head — we wrote about that same fear in a different context in taking deposits without scaring off new clients, and the lesson transfers: clear terms stated up front read as professional, not pushy.

Lead time. How many days' notice you need for 20, for 50, for 100. Different numbers. Write all three.

What you don't do. Plated service. Staffed events. Allergy-free kitchens. Whatever is a no, make it a written no so you stop agonizing over each request.

The five-minute reply

With the sheet done, your reply becomes a short email with the three tiers, the delivery fee, the deposit terms, and one specific question: "Can you confirm the address and a final head count by the Monday before?"

Send it the same hour. Not the same evening. The same hour.

Keep it as a saved template in your email so you are pasting, not writing. Change the date, the head count, and the delivery fee. Done. If a request needs something custom, still send the standard reply first with a line saying you can adjust — get a number in front of them while they are still reading their inbox, then refine.

One more thing: put the tiers on your website. A page that lists per-head pricing, the minimum, the radius, and the lead time does two jobs. It answers half the enquiries before they arrive, and it filters out the ones that were never going to work. The enquiries that do come in are then from people who have already accepted your price, which makes closing them nearly automatic. This is the same principle as a real ordering page instead of a menu PDF — information the customer can act on beats information they have to ask about.

The trap: the order that lands on your worst day

Here is the part that costs real money, and it is not the quoting.

A 60-person drop-off at noon on a Saturday sounds like a great day. Then you realize your Saturday brunch starts at 10, your prep cook comes in at 9, and the pans for that catering job need oven time in the exact window your dine-in tickets are firing. You end up running two services out of one kitchen with one crew. The catering goes out late, brunch goes out late, and a table of four leaves a two-star review about wait times. You made money on the catering and lost it on the room.

Before you accept, check three things:

1. Oven and stove time. Not whether you have the ingredients — whether you have the equipment free in the two hours before pickup.
2. Bodies. Catering is a labour spike, and if it means an extra prep shift you need that cost in the quote before you send it. If you're not sure what an extra body actually costs you on a given day, your staff schedule is a labour cost decision walks through it.
3. The clock. Delivery at 11:45 means leaving at 11:15 means packed at 11:00 means out of the oven at 10:30. Work backwards and see what that collides with.

If the timing collides, don't decline — counteroffer. "I can do 11:00 or 1:30, not 12:00." Office lunches move more easily than you think. And build a simple rule for the dates you will not take catering at all: your two busiest services of the week. Writing that rule down means you stop losing the argument to a big number on a Tuesday night.

Don't let the enquiry sit in a place you don't check

Most catering enquiries arrive one of three ways: a form on your site, a phone call, or a direct email. The form and the email go somewhere you look once a day. The phone call happens at 12:40pm and nobody picks up.

That last one is the biggest hole. A corporate buyer who calls and gets voicemail usually does not leave one. They call the next place. We covered the arithmetic of that in the five minutes after a missed call, and catering is the highest-value version of it — a single missed call can be a thousand dollars of food.

Make sure calls get answered during service, even if you are not the one answering them. An AI phone agent that takes the name, the date, the head count, and the delivery address and texts it to you turns a missed call into a five-minute reply you can send from your phone while standing in the walk-in. That is the whole game. You are not trying to be better at catering than your competitors. You are trying to be first with a clear number.

If you want to see how the website, the ordering, and the phone side fit together for a restaurant, that's what we build on our restaurants page.

Start this week

Write the three tiers. Write the minimum, the radius, the deposit, the lead times. Save the email template. Block your two busiest services on the catering calendar. Then answer the next enquiry inside the hour and see what happens.

You will win some jobs you would have lost. More usefully, you will stop spending Wednesday nights doing arithmetic you already did in March.