All posts
🍱Tiffin

From 20 to 200 Tiffins: A Scaling Guide for Indian Meal Services

Routes, cutoffs, veg/non-veg day patterns, label automation, WhatsApp-to-portal migration, and unit economics at each growth stage.

9 min readOctober 20, 2025

Stage 1: 20-50 Tiffins (Hustle Mode)

You're cooking in a home kitchen or small commercial space, delivering yourself (or with one helper), and managing everything in a spreadsheet or WhatsApp group. Customers are mostly friends, family, and word-of-mouth referrals. Unit economics: $8-$12 per tiffin, 40-50% food cost, you're netting $4-6 per tiffin after ingredients.

The bottleneck at this stage: time. You're cooking, packing, delivering, and answering WhatsApp messages 12 hours a day. There's no system — it's all in your head. The first scaling move: get out of WhatsApp hell.

**How:** Set up a simple customer portal (even a Google Form works) where customers can skip a day, update delivery address, or pause. Stop answering "can I skip tomorrow?" texts at 9pm. Set a cutoff (48 hours before delivery) and enforce it. Most customers will adapt; the ones who don't are costing you sanity.

**Delivery:** You're still delivering yourself, but start optimizing the route. Use Google Maps or a free route planner (PlateOS has one built in). Group deliveries by neighborhood and set time windows ("all downtown deliveries between 6-7pm"). This saves 30-60 minutes/day.

Stage 2: 50-100 Tiffins (Systemizing)

You've outgrown your home kitchen and moved to a commercial space. You've hired 1-2 part-time kitchen helpers. You're delivering 5-6 days a week (or 3 days if you're doing bulk weekly plans). Revenue: $2,000-$4,000/month. You're profitable, but barely — most of the profit is your own labor.

The bottleneck: operational chaos. You're still managing orders manually, printing labels by hand, and forgetting who gets veg vs. non-veg. The scaling move: automate your kitchen workflow.

**Labels:** Stop handwriting names on containers. Use a label printer (Dymo, Brother, Rollo) and generate labels from your order list. Each label: customer name, delivery address, meal type (veg/non-veg), delivery day, any special notes ("no onions"). This saves 20 minutes/day and eliminates mistakes.

**Veg/Non-Veg Tracking:** Most Indian tiffin services have veg and non-veg options (and some customers alternate: veg on Tuesdays, non-veg on Fridays). Track this in a system (spreadsheet or PlateOS), not in your head. Tag each customer's preference and generate a daily prep list sorted by meal type. Your kitchen helper can follow it without asking you 10 times.

**Delivery:** Hire a delivery driver (gig worker or part-time) for 2-3 hours/day. Pay $15-20/hour or a flat rate per route. This frees you to stay in the kitchen or do sales/marketing. Make sure the driver has the route pre-planned (PlateOS auto-generates optimized routes) and a contact list in case of issues.

Stage 3: 100-200 Tiffins (Scaling for Real)

You're doing $8,000-$15,000/month in revenue. You've got 2-3 kitchen staff, 1-2 drivers, and you're cooking in a legit commercial kitchen (or cloud kitchen). You've hit the "real business" stage — but also the "real complexity" stage.

The bottlenecks: route optimization (200 tiffins across a city is 3-4 hours of driving if done poorly), inventory waste (you're buying for 200 meals but half your veggies spoil), and customer churn (you're too busy to notice when someone quietly cancels).

**Routes & Cutoffs:** Divide your delivery area into zones (Downtown, Suburbs North, Suburbs South). Offer delivery on specific days per zone (Downtown gets Mon/Wed/Fri, Suburbs North gets Tue/Thu). This clusters deliveries and cuts drive time by 30-40%. Enforce cutoffs strictly: 48 hours for skips, 72 hours for pauses. Late requests get politely declined.

**Inventory & Recipes:** At 200 tiffins, you're buying bulk (50 lbs of rice, 30 lbs of chicken). Start tracking recipes and portions in a system (PlateOS has recipe management built in). If you know Butter Chicken serves 40 tiffins and uses 8 lbs chicken, you can order exactly what you need and reduce waste from 15% to 5%. This alone saves $500-1,000/month.

**Portal Migration:** By now, 20-30% of your customers are still texting you on WhatsApp. Migrate them to a self-serve portal (PlateOS, or even a Shopify store with a subscription app). Send a message: "We're moving to a new system to serve you better. Here's your login link — you can skip, pause, and update delivery details anytime." Most will switch; the holdouts, you migrate manually.

Veg/Non-Veg Day Patterns (And Why They Matter)

Many Indian tiffin services offer both veg and non-veg, but the split isn't 50/50 every day. Common patterns: **All-veg Tuesdays** (religious observance for some customers), **Non-veg Fridays** (end of week, customers want something hearty), **Weekend veg preference** (lighter meals on Sunday).

Track these patterns in your system and plan your menu accordingly. If 70% of your customers go veg on Tuesdays, cook 70% veg tiffins that day (and prep less chicken). This reduces waste and improves freshness.

Some operators offer flexible plans: "Choose veg or non-veg per day" (customer picks each week). This maximizes satisfaction but adds complexity (you're cooking 2 menus every day). Others offer fixed plans: "All-veg" or "Non-veg 3 days/week." Simpler to prep, but less flexible.

The middle ground: offer 2-3 plan templates (All-veg, Mostly non-veg, Balanced) and let customers pick. Then, allow one swap per week. This gives flexibility without full chaos.

Unit Economics at Each Stage (The Real Numbers)

Let's talk money. Here's what typical tiffin service unit economics look like at each stage:

**20-50 tiffins:** Revenue/tiffin: $10. Food cost: $4 (40%). Packaging: $0.50. Delivery (your time): $2. Net: $3.50/tiffin. You're making $70-175/day, or $2,000-5,000/month. Mostly your labor.

**50-100 tiffins:** Revenue/tiffin: $10. Food cost: $3.50 (35%, you're buying smarter). Packaging: $0.40 (bulk discount). Delivery: $1.50 (driver cost split across volume). Labor (kitchen help): $1. Net: $3.60/tiffin. You're making $180-360/day, or $5,000-10,000/month. You're paying yourself a salary now.

**100-200 tiffins:** Revenue/tiffin: $10. Food cost: $3 (30%, bulk purchasing power). Packaging: $0.30. Delivery: $1. Labor: $1.20 (kitchen + driver). Overhead (rent, utilities): $0.50. Net: $4/tiffin. You're making $400-800/day, or $12,000-24,000/month. This is a real business with real profit.

The key insight: margins improve with scale, but only if you systemize. If you're still managing everything manually at 100 tiffins, your labor cost will eat your margin. Invest in tools (labels, route optimization, customer portal) early — they pay for themselves by month 2.

The 200-Tiffin Ceiling (And How to Break It)

Most tiffin services plateau at 150-200 tiffins. Why? Because you've maxed out your kitchen capacity (you can only cook so much in 6 hours), your delivery capacity (one driver can only cover so many stops), and your management capacity (you're still the bottleneck for decisions).

To break through, you need to make 3 shifts:

**Kitchen:** Move to a larger space, or add a second shift (morning prep + evening prep). Some operators add a second kitchen (north side + south side of the city) to reduce delivery distance.

**Delivery:** Add a second driver, or switch to a hub-and-spoke model (customers pick up from neighborhood hubs 2x/week instead of daily home delivery). This cuts delivery cost by 50% and lets you serve 300+ customers with the same driver headcount.

**Management:** Hire an operations manager (or promote your best kitchen helper). They handle scheduling, inventory ordering, and customer issues. You focus on marketing, menu planning, and growth. This is the hardest shift — but it's the only way to scale past 200.

Final thought: scaling a tiffin service is less about cooking skill and more about systems. The operators who grow are the ones who automate early, track metrics obsessively, and aren't afraid to invest in tools and people. Start small, systemize by 50 tiffins, and you'll be at 200 within 18 months.

Put this playbook to work

PlateOS runs subscriptions, meal passes, cook lists, routes, and renewals for food businesses — free to start, with an AI operations manager included.