Corporate Catering vs Weddings: What Actually Changes

I spent years thinking a catering job was a catering job. You cost the food, you price the head, you show up and feed people. Then I took on a run of weekly office lunches for a software firm and discovered that almost everything I'd learned from weddings was the wrong instinct for corporate catering. Not slightly wrong. Structurally wrong — in how you get paid, how you plan, and where the money actually is.

If you're weighing whether to chase office and business catering work, this is the honest comparison. Not the sales-brochure version. What genuinely changes when the client is a company instead of a couple, and why the differences run deeper than the guest count.

One shot versus the long game

A wedding is a single, enormous, emotional transaction. The couple has been imagining this day for months. They will spend more than they should, they will second-guess every line, and then — win or lose — you never cook for them again. Every wedding is a fresh sale to a fresh stranger. Your marketing cost is baked into every single booking because there is no repeat.

Corporate is the opposite shape. The first office lunch is a nervous test. The tenth is a habit. By the time you're the firm's default caterer, nobody is comparing quotes any more — they're just emailing you the headcount for Thursday. The value of a corporate client isn't the first invoice. It's the eighteen months of Thursdays after it.

That single fact reorders your entire operation. In weddings you optimise for the wow — the thing that makes the couple book you over the caterer down the road. In corporate you optimise for reliability, because reliability is what gets you re-ordered. A wedding tolerates one spectacular showpiece and a couple of rough edges nobody notices in the champagne haze. A recurring lunch contract tolerates zero rough edges, because the same office manager will notice the same cold soup every single week.

How you get paid changes everything

This is the part nobody warns you about, and it's the biggest operational shift of all.

Weddings run on deposits. You take 25–50% up front to hold the date, the balance clears a week or two before, and by the time you're plating you already have the money. Cash-flow risk is low. If the couple vanishes, your deposit and cancellation clause cover the food you've committed to.

Corporate runs on purchase orders and invoicing. A finance department does not pay a deposit for a Tuesday sandwich platter. They issue a PO number, you deliver, you invoice, and then you wait — typically net-30, sometimes net-45 or net-60 if it's a large company that knows it can dictate terms. You have paid your suppliers, paid your staff, and delivered the food weeks before a cent lands in your account.

Work a real example. You deliver a $1,400 lunch on the 3rd. You invoice on the 5th. Terms are net-30, so payment is due the 5th of next month — but "due" and "paid" are different words to an accounts-payable team, and it actually lands on the 12th. Meanwhile your protein supplier is cash-on-delivery and your casual staff were paid that Friday. You've financed roughly 40 days of that job out of your own pocket. Do four of those a week and you're carrying five figures of other people's operating costs before you've made a profit.

The practical defences, learned the expensive way:

• Always get the PO number before you cook. No PO, no delivery. A verbal "yes, go ahead" from someone who isn't in finance is not a payment instruction, and you'll discover that when the invoice bounces around for approval.
• Invoice the same day you deliver, or the next morning at the latest. Every day you delay pushes the payment date further out. The clock only starts when the invoice is in their system.
• Negotiate supplier credit so your payables lag your receivables. If your suppliers give you 14 days and your client pays in 30, you've only bridged 16, not 30.
• Chase early and politely. A short "just confirming the invoice landed with your AP team" on day two isn't rude. It's the difference between net-30 and net-55.

None of this exists at a wedding. It's the single biggest reason a caterer with a full corporate order book can still run out of cash. Revenue is not the same as money in the bank, and corporate stretches the gap between them wider than any other work you'll take.

The margin profile is genuinely different

Weddings carry a higher headline price. A plated wedding at $95–140 a head looks far more lucrative than a $22 office lunch. But the wedding number is gross, and the gross hides an enormous amount of one-off cost: the tasting you cooked for free, the site visit, the bespoke menu design, the extra service staff for a formal dinner, the risk premium for a date you can never resell if it cancels.

Corporate is lower per head but leaner to produce, and the leanness compounds because you're making the same things repeatedly. Here's the shape of it laid side by side:

The insight buried in that table: corporate's true margin only reveals itself over time. A single office lunch, costed against the effort of winning the account and setting up the menu, looks mediocre. The same lunch delivered for the fortieth time — recipes standardised, prep list muscle-memory, supplier order a two-minute copy of last week's — is one of the most profitable things a small catering kitchen can do. The National Restaurant Association's industry research consistently shows off-premises and catered business as one of the more resilient revenue streams precisely because of this repeat-order stability — it smooths out the feast-and-famine cycle that makes event-only caterers miserable.

Dietary breadth: the corporate curveball

A wedding has a guest list. The couple hands you a spreadsheet: 4 vegetarians, 2 coeliac, 1 nut allergy, 3 no shellfish. You plan against known numbers. It's finite, and you cost the substitutions in.

A corporate lunch has an office — a shifting population where you rarely get names, only a rough headcount and the instruction "make it work for everyone." Modern workplaces run vegan, vegetarian, halal, gluten-free, dairy-free and multiple allergy profiles simultaneously, every single delivery, without warning. You can't plan against a list because there isn't one. You have to build breadth into the standing menu itself.

In practice that means every recurring corporate menu needs a genuine vegan option that isn't an afterthought, clear allergen labelling on every item, and enough naturally gluten-free and halal-friendly dishes that no one is left with a sad side salad. Get this wrong once and you don't lose one guest like at a wedding — you lose the office manager's confidence, and the office manager is the account.

Timing is a hard edge, not a window

A wedding runs on a loose timeline. Canapés drift, the speeches overrun, dinner slips twenty minutes and nobody minds — it's a party, not a schedule. You have slack.

A corporate lunch has no slack. If the working lunch is called for 12:30 because the board meeting resumes at 13:00, the food is on the table at 12:25 or it has failed. There is no "we'll start when everyone's seated." The meeting starts on the minute whether your platters are there or not, and a room of executives staring at empty trestle tables is the fastest way to lose an account. Breakfast catering is worse — a 08:30 delivery for a 09:00 kick-off means you're prepping in the dark and driving through commuter traffic with zero margin for a wrong turn.

This changes how you plan production. Weddings you build around the plating moment; corporate you build backwards from a delivery slot with traffic and loading-dock access factored in. Know which door, which floor, whether there's a lift, whether security needs your name on a list. The food being perfect is worthless if you're stuck at reception at 12:28.

Volume pricing and framework deals

Weddings are priced bespoke, one at a time. Corporate clients, once they trust you, want a framework: a fixed per-head rate across menu tiers so their finance team can budget without re-quoting every week. You'll be asked for a rate card — Tier 1 sandwich lunch at $18, Tier 2 hot fork buffet at $26, Tier 3 with dessert and staffing at $34 — and once agreed, that's the price for months.

This is a real commitment and you must cost it with headroom, because your ingredient prices will drift upward before the framework is up for renewal. Price the framework on next quarter's likely costs, not today's. A rate you set in spring against cheap-season produce will hurt by autumn if you locked it at the floor.

Relationship management, not event management

The final and biggest shift. A wedding is project management: a fixed scope, a fixed date, a defined end. You deliver the day and you're done. A corporate account is relationship management with no end date. The office manager who books you is a person with preferences, a boss to impress, and a Rolodex of other companies. Keep them happy and the account renews itself; keep them delighted and they recommend you to the firm across the hall.

That means remembering that the CFO is dairy-free, that they like the Tuesday menu rotated so it's not sandwiches three weeks running, that the Christmas function is the one event a year where they'll happily pay wedding-level margins. It means the occasional unbilled extra — a plate of good coffee cookies dropped in during a stressful week — because the lifetime value of that account dwarfs the cost of the gesture. Track this. The chef who remembers the client's standing preferences without being reminded is the chef who never gets put out to tender.

So which should you chase?

Both, but for different reasons, and with clear eyes about what each one is.

Weddings are your high-margin, high-effort, high-emotion showpiece work. They pay well per event, they let you cook at your best, and the deposit structure protects your cash. But every one is a cold start, they cluster into a brutal summer season, and they leave nothing behind — no recurring revenue, no compounding relationship.

Corporate is your baseload. Lower per head, unglamorous, timing-critical, and you finance the cash gap yourself. But it's predictable, it fills the dead midweek and the dead winter that weddings leave empty, and once an account is established it produces revenue on autopilot with near-zero acquisition cost. A catering business built only on weddings lives and dies by summer. Add a spine of corporate accounts and you have income in February.

The mistake is running them with one playbook. Price the wedding for the wow and the risk. Price the corporate account for the long game and cost the cash gap honestly. Rehearse the wedding; systematise the corporate lunch so the fortieth one is as good as the first and takes a fraction of the effort. Do that, and the two halves of the business cover each other's weaknesses instead of competing for the same tired attention.

"The wedding paid the best invoice this month. The office lunches paid the rent every month."

Both matter. But if I had to keep only one, I'd keep the boring one — because boring, reliable and repeat is what a business is actually made of.