Capex comparison
| Line | Cloud kitchen (₹L) | Casual dining (₹L) |
|---|---|---|
| Equipment | 5-9 | 12-18 |
| Interiors | 2-4 | 14-22 |
| Deposit | 1-3 | 6-12 |
| Licences | 1-2 | 2-3 |
| Working capital | 1-3 | 4-8 |
| Total | 10-21 | 38-63 |
Monthly fixed cost
Cloud kitchen: ₹1.0-3.0 lakhs/month (small footprint, lean staff). Casual dining: ₹2.8-7.5 lakhs/month (higher rent, larger staff, utilities scale). On the surface cloud wins by a wide margin.
Variable cost — where casual dining wins
This is the part most cloud-kitchen pitches gloss over. Cloud kitchens are 90-100% aggregator-dependent. At a 22-25% commission rate, that's 22-25% of revenue gone to Zomato/Swiggy. Add packaging (5%), variable labour (5%), food cost (30%) and you're at 62-65% variable cost rate — versus 42-46% for a dine-in heavy casual-dining.
Break-even revenue
| Format | Fixed (₹L/mo) | CM | Break-even revenue (₹L/mo) |
|---|---|---|---|
| Cloud kitchen (mid) | 2.0 | 37% | 5.4 |
| Casual dining (mid) | 5.0 | 55% | 9.1 |
The cloud kitchen needs ~₹18,000/day to break even. The casual dining needs ~₹30,000/day. Cloud wins on absolute number — but the question is whether the cloud kitchen can sustain ₹18,000/day given its dependence on a small set of aggregator listings, ad-budget compounding, and a tougher refund profile.
Hidden lines for cloud kitchens
- Ad spend — many cloud kitchens spend 6-12% of revenue on Zomato/Swiggy ads to stay visible.
- Refund drag — packaging breakage, missing items, late deliveries lead to 2-4% revenue losses through refunds.
- Listing cost — multi-brand cloud kitchens incur per-brand listing fees, not always offset by volume.
- Brand fragility — a one-week rating drop below 4.0 can permanently shrink discoverability.
When cloud kitchen wins
- You have an existing brand and just need a delivery node.
- You're testing a cuisine before committing to a dine-in format.
- You can hit ₹2.5L+/day from one brand by month 3 (rare; possible with strong product + city).
- You're under-capitalised — opening a casual dining underfunded is worse than a well-capitalised cloud.
When casual dining wins
- You can secure rent at <8% of expected revenue.
- You're confident in dine-in catchment (footfall, parking, visibility).
- You have a chef and a tested menu.
- You can run with no aggregator presence for the first 60 days while you build dine-in repeat customers.
Operating compliance (Maharashtra 2026)
Cloud kitchens are explicitly in scope under FDA Order 716/2026 — premises licence, RUCO oil, staff certificates, and packaging rules apply equally. See cloud kitchen FDA compliance and the line-by-line cloud kitchen capex guide.
Run the numbers for your format →