The corporate tiffin opportunity: what B2B meal subscriptions need that home delivery doesn't
The call comes from an HR manager at a Gurugram IT office. Fifty tiffins, five days a week, delivered by 12:30 PM. You do the math: that's the same weekly revenue as 50 individual residential subscribers, delivered to a single address, with one invoice and one point of contact. Every founder who gets this call feels the same thing — this is the break we've been waiting for.
Most founders who say yes without thinking it through wish they had waited.
A corporate client is not 50 subscribers. It's one. That distinction drives everything. When you have 200 individual residential subscribers and 8 cancel in a week, your revenue dips 4% and you barely notice. When your Cyber City office account cancels — because the company switched to catered lunches, because the HR contact quit, because a single batch of food was substandard — you lose 25% of your weekly revenue in one email. Concentration risk is the first thing to understand before saying yes.
The delivery window is non-negotiable. Residential subscribers in South Delhi might pick up their tiffin anywhere between 7 AM and 8:30 AM and manage fine. Offices do not work that way. Cyber City security has a vendor arrival window: 11:45 AM to 12:15 PM. Miss it by 20 minutes and your driver waits at the gate, the food cools, and the HR manager gets a Slack message from 50 unhappy colleagues. MealDispatch's per-zone cutoff windows let you assign a separate delivery window to the corporate account — different from your residential zones, locked in, not up for negotiation.
Menu rotation works against you in B2B. The rotating weekly menu that keeps residential subscribers excited is a friction point for corporate buyers. The HR manager who signed the contract wants to tell their employees "we get tiffin every day" — they do not want to manage a weekly selection process across 50 people. Most corporate clients want a fixed 2-3 option menu that stays consistent for months. This is directly at odds with the variety-driven model that drives residential retention. Decide before you sign whether your kitchen can run two parallel menus: a rotating menu for residential subscribers, a fixed menu for the corporate account.
Invoicing is not a Shopify problem. It's your problem. Shopify Subscriptions handles per-subscriber billing cleanly — each of your 200 residential customers has their own subscription, their own payment method, their own UPI auto-debit. A corporate client expects a consolidated monthly invoice sent to their accounts payable team on the 1st of each month, with a 15-30 day payment term. That is not how Shopify billing works out of the box. You can structure it as a single subscription for the full bulk order, but you will still need to generate a GST invoice manually (or via a GST-compliant billing tool) and reconcile payment separately. This is not insurmountable — but operators who assume their existing billing setup will handle corporate accounts intact are in for a surprise.
The upside is real, if you set it up correctly. A single-stop bulk drop for a 10-floor office tower in Noida Sector 62 takes 20 minutes for a driver who would otherwise spend 90 minutes making 50 doorbell runs across a residential colony. MealDispatch's society-level routing handles this exactly the same way it handles a gated residential complex — one delivery stop, one confirmed access procedure, orders grouped by the single drop point. The driver sees one entry on their route sheet, not 50. That logistics efficiency is genuine.
The billing model that works best in practice is prepaid. Ask the corporate client to prepay a month of tiffins at the start of the billing cycle. It protects you against the payment-term problem (you are not floating inventory costs for 30 days waiting for accounts payable) and it gives the HR manager a clean line item for their budget. For kitchens on the MealDispatch Brand plan — which handles up to 1,500 subscribers across unlimited zones — a corporate account can sit in its own zone with its own cutoff time and its own fallback rule, separate from the residential subscriber pool.
The smart move is to start with one. Not all corporate accounts at once. Take one 30-40 person office, run it for 8 weeks, understand the actual operations cost, and decide whether the margin holds. The kitchens that have done this tell us that corporate accounts are profitable when the menu is fixed, the delivery window is strict, and payment is collected upfront. They are not profitable when the kitchen treats them like a large residential subscriber — rotating menus, flexible timing, post-delivery invoicing.
If your operations are already running cleanly for 100+ residential subscribers — cutoff is automated, prep sheets are printed, drivers are on zone routes — adding a corporate account is an incremental load. If your residential operations are still being managed on WhatsApp, a corporate account will not fix the underlying chaos. It will amplify it.
The HR manager at the Gurugram IT office is still a good lead. Just make sure your kitchen is ready to take the call before you pick up.
If you want to see how MealDispatch's zone routing and per-zone cutoffs handle a mixed residential-plus-corporate model, book a demo and we'll walk through the exact setup Delhi kitchens use.