Why most Indian D2C brands outgrow spreadsheets in their second year

I've been the ops lead at three D2C brands. I've also spent the last two years talking to founders running 40+ others. And the spreadsheet-to-WMS inflection point shows up everywhere, almost always at the same trigger: crossing ₹1 Cr/month in revenue, or about 2,000 orders/month, whichever comes first.

This article is the conversation I wish someone had with me at year one, so I didn't have to learn it the hard way at year two. It's three parts: the signs you're at the inflection, the actual cost of staying in spreadsheets, and what to do about it.

1. The four signs you've hit the inflection

You can rationalise staying in spreadsheets for a long time. "We know our data." "We're fast." "We're not like the big guys." All true — until they're not. Here are the four signs I see consistently:

Sign 1: Your ops team is a human API

The single biggest tell. If your ops manager is the person who pulls order data from Shopify, reformats it for Nykaa, pastes the AWB into a third tab, and uploads the tracking CSV to Myntra — they are your integration layer. They are doing what software should do, and they are the bottleneck for every other decision.

When this person goes on leave, the business slows down. When they quit, you have a knowledge transfer crisis. When they're good, you can't scale without hiring a second one of them at ₹8-12 LPA. None of those are great outcomes.

Sign 2: Your "inventory count" is a meeting, not a number

If you can't tell me, right now, how many units of SKU-WP-12 you have in your Mumbai warehouse, you don't have inventory. You have a guess backed by three different spreadsheets that disagree with each other.

For a brand doing ₹50L/month, this is fine — you can absorb 5-10% variance, and you can physically see most of the stock in the warehouse anyway. For a brand doing ₹1 Cr/month, the variance starts costing you real money: stockouts on bestsellers, dead stock on slow-movers, overselling that triggers RTOs.

Sign 3: Your marketplaces don't know what each other know

Shopify says you have 47 units. Myntra says 23. Amazon says 0 (out of stock). The actual count in the warehouse is 31. You sold 8 on Myntra this morning, but Shopify still shows 47, so the website is still taking orders you'll have to cancel in 2 days.

This isn't a tooling problem; it's a sync problem. And it's exponential — every new channel you add multiplies the combinations.

Sign 4: You can't answer "what's our RTO rate by pincode" in 30 seconds

If pulling this report takes longer than drinking a cup of chai, you don't have analytics. You have a data warehouse that requires a human to translate. And decisions made on gut feel in operations are costing you 1-2% of revenue — which at ₹1 Cr/month is ₹1-2 lakh/month, or ₹12-24 lakh/year. That's the cost of a senior ops hire.

2. The actual cost of staying in spreadsheets

Founders usually frame this as a tooling decision: "Do we spend ₹3L/year on a WMS, or stay free in Google Sheets?" The framing is wrong. The cost of staying isn't ₹0; it's the cost of the things you're losing to latency and human error.

Cost 1: RTOs from delayed shipping

Indian ecommerce RTO rates average 12-18%. Half of those RTOs are caused by operations: late dispatch, wrong address verification, courier allocation errors. A 2% improvement in dispatch TAT, which a WMS gives you almost for free, is worth ₹1.5L/month at ₹1 Cr GMV.

Cost 2: Overselling on marketplaces

Nykaa and Myntra penalise cancellations. Amazon hides you from search. Each oversell costs you 1-3 orders you'll never get back. At 50 oversells a month, you're losing ₹30-50K of contribution margin monthly.

Cost 3: Dead stock you don't know you have

The brands I've worked with typically have 8-15% of their working capital tied up in dead stock — SKUs that haven't sold in 90+ days, sitting in bins, blocking the cash flow for SKUs that could actually move. They don't know because there's no SKU velocity report. A WMS surfaces this on day one.

Cost 4: The founder's time

This is the biggest cost and the hardest to measure. If the founder is spending 4 hours/week reconciling data, that's 200 hours/year. At even a conservative ₹2,000/hour value-of-time, that's ₹4L/year. Plus, the founder isn't doing founder work.

The cheapest WMS in the world costs ₹3L/year. The cost of staying in spreadsheets is usually 5-10x that, you just don't see it on a P&L line.

3. What to do about it (the practical version)

If you've nodded along to the signs above, here's the playbook I've used with brands transitioning out of spreadsheets:

Step 1: Audit your current state (1 day)

List every spreadsheet, every Google Doc, every WhatsApp thread that's part of your daily operations. For each, write down: who owns it, who uses it, what decisions it enables, and what breaks if it's wrong. You'll end up with 15-30 artifacts. That's your operations surface area.

Step 2: Pick the first 3 things to automate (1 week)

Don't try to do it all at once. The three I always start with:

• Unified order inbox — all orders from every channel, in one place, with one status flow
• Single source of truth inventory — one number per SKU, synced to every channel, that updates on every movement
• Basic picklist + label print — paper or phone-based, replacing the WhatsApp-picklist workflow

These three take 90% of the pain out of daily ops. Everything else is optimisation.

Step 3: Run a 2-week pilot, not a 6-month rollout

The biggest mistake I see is treating a WMS implementation like an ERP rollout. Don't. Pick one warehouse, one channel, one SKU category, and run a 2-week pilot. If your pick rate goes up and your RTOs go down, you have your business case. If not, you've lost 2 weeks, not 6 months.

Step 4: Don't change your process, change your tool

Your ops team has spent 18 months building workflows that work in their head. A WMS that requires them to relearn everything will be resisted. Find one that fits your existing workflow first, and improves it second. (This is exactly why we built our platform with a "wave picking" workflow that mirrors what Indian 3PLs already do, rather than enforcing a rigid Western-style WMS process.)

Step 5: Keep one spreadsheet, kill the rest

For the first 60 days, let your team keep their familiar spreadsheet alongside the new system. Then, after 60 days of comparison, kill the spreadsheet. This builds trust. Forced cutovers breed workarounds.

The bottom line

Spreadsheets aren't bad. For a ₹10L/month brand, they're exactly right. The mistake isn't using them; the mistake is using them past the point where the cost of human error exceeds the cost of software. That point is almost always around ₹1 Cr/month, and almost always feels like it's 3-6 months later than it actually was.

If you're reading this and recognising yourself in it, the good news is: the inflection point is also the inflection opportunity. The brands that move at this point pull ahead of their spreadsheet-locked competitors by 2-3x within a year. It's not a cost; it's a moat.

If you want to see what a ₹1 Cr/month brand's operations look like in a system designed for that exact scale, start a 14-day trial. No sales call, no credit card. Or book a 20-minute demo and we'll walk you through it on your data.