Guides
How to run a corporate meal provider
Corporate contracts look like the easy end of this business — one buyer, one address, one invoice. They are, until you notice that the count you cooked and the count you billed have not matched for three months.
The economics are different from consumer plans
A corporate contract concentrates revenue. One office can equal thirty household subscriptions, arriving at one loading bay in one drop, which is why the delivery economics are so much better than consumer meal plans.
It also concentrates risk. Losing one office is losing thirty subscriptions at once, usually at a contract renewal you did not know was being reviewed, and usually over service consistency rather than price.
The consequence is that the operational discipline that matters is different. For consumer plans it is handling many small changes. For corporate it is being precise about counts and being able to prove what you delivered.
What actually goes wrong
The count arrives informally
A message to somebody’s phone the evening before. If it is not recorded with a time and a sender, a dispute about it cannot be settled.
The cut-off is not enforced
Late changes are accepted to keep the relationship warm, and the cost of them is absorbed silently rather than being visible in a variance figure.
Invoicing is reconstructed
At month end somebody assembles the invoice from delivery notes and memory. Every reconstruction rounds in the client’s favour.
Nobody owns the relationship
The facilities coordinator who ordered your service leaves, and the replacement inherits a service nobody explained to them.
Dietary requirements arrive as a list
Sent once in an email, never structured, and impossible to check against a menu on a given day.
Fix the operation in this order
Give count changes one channel
Portal or a single recorded channel, timestamped and attributed. Verbal counts should be repeated back into that channel before they are acted on.
Put the cut-off in the contract
And enforce it. A cut-off that bends on request is not a cut-off, it is a preference.
Invoice from delivered counts
Built from what was recorded as handed over, with the contract variance shown rather than absorbed.
Structure the dietary requirements
As per-person data that can be checked against a menu, not as a list in an email thread.
Review the contract before they do
A quarterly conversation about counts, variance and any service failures. Renewals lost by surprise are usually renewals nobody discussed.
Growing without losing the ones you have
The temptation with corporate work is to keep signing offices, because each one moves the revenue figure sharply. The constraint is nearly always the delivery window rather than the kitchen — corporate drops cluster into a narrow lunch slot, and two offices ten minutes apart can be undeliverable if the window is tight.
Before adding a contract, check the stop against the existing window rather than against the day. A kitchen with plenty of production headroom can still be unable to serve one more office at noon.
And be wary of pricing new contracts off the marginal cost of the last one. Each additional stop in the same window is cheap only while the window has room; the one that forces a second vehicle is not.
Common questions
- Why do corporate contracts lose money despite good delivery economics?
- Usually because delivered counts and invoiced counts drift apart. Late changes get absorbed to protect the relationship, month-end invoices are reconstructed from notes, and each reconstruction rounds in the client’s favour.
- How should headcount changes be taken?
- Through one recorded channel that timestamps the change and attributes it to a sender. Verbal counts should be repeated back into that channel before anyone acts on them, or a later dispute cannot be settled.
- What limits how many offices I can serve?
- The delivery window, not the kitchen. Corporate drops cluster into a narrow lunch slot, so a kitchen with plenty of production headroom can still be unable to add one more stop at noon.
- How do I avoid losing a contract at renewal?
- Discuss it quarterly — counts, variance and any service failures — rather than waiting for the renewal date. Contracts lost by surprise are almost always contracts nobody was talking about.
Counts that reach the invoice intact
See how a headcount change moves production, purchasing, packing and the billing record together.
Related reading
- SolutionsSoftware for corporate meal providersCorporate meal programmes look like a bigger version of consumer meal plans and behave nothing like them. Three structural differences change almost every part of the operation.
- SolutionsSoftware for hospitality and staff meal programmesA hospitality contract is a standing order with a moving headcount. The commercial relationship is stable; the number of people to feed changes with rosters, occupancy and shift patterns — often the evening before.
- SolutionsSoftware for workplace lunch programmesA daily office lunch programme is not a corporate meal plan on a faster clock. The shorter cycle changes which parts of the operation are hard.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- GuidesBilling a meal plan that keeps changingBilling here is harder than a flat subscription because the thing being billed for is physical and intermittent. The invoice has to agree with a stack of boxes that may or may not have arrived.