For most of last year, I was running fourteen live digital properties. Different niches, different platforms, different margins. From the outside they looked like a portfolio. From the inside they looked like fourteen identical problems wearing different costumes.
The single biggest lesson — bigger than anything about ads, conversion, or product‑market fit — was this: the cost of running a store has almost nothing to do with the platform you chose, and almost everything to do with the operational drag you’ve allowed to accumulate.
What "operational drag" actually means
Operational drag is every small unit of friction in the path between a customer placing an order and that order becoming cash in your bank with a happy customer at the end. It’s rarely one thing. It’s the cumulative weight of every micro‑decision a human still has to make in your store.
- The 90 seconds you spend tagging an order so the right SKU goes to the right warehouse.
- The five minutes you lose copy‑pasting a tracking number into a customer email.
- The hour every Friday reconciling Razorpay against your accounting tool.
- The afternoon you burn making sure two stores haven’t over‑sold the same SKU.
None of these feel like a problem. Each one feels like a reasonable thing to do. The disaster is the sum.
If you can’t take a two‑week holiday and trust the store to behave, you don’t own a store. You own a job that pretends to be a store.
The five drag categories every store has
After the first three or four stores, I started noticing the same shape every time. New niche, same skeleton. The drag categories I now check for on every store I touch:
1. Order routing drag
Every order has to find its way to the right fulfilment path — a supplier, a warehouse, a dropship API, a manual pack‑and‑ship person. If a human is making that decision per order, you have order routing drag.
2. Inventory drag
Stockouts, oversells, "I thought we had ten left" emails. The deeper this drag goes, the harder it is to scale your top SKUs without breaking the rest of the store.
3. Customer comms drag
"Where is my order?" is the most expensive sentence in e‑commerce. Not because the question is hard, but because it shows up at the wrong time in the wrong inbox and pulls you out of the actual work.
4. Reconciliation drag
Payments don’t match orders. Refunds don’t match invoices. Your books and your store disagree. This is the drag that quietly makes your business legally and financially weaker the longer it stays.
5. Reporting drag
If you can’t see what’s happening in your store inside ten minutes a day, every operational decision after that is being made on vibes.
The cheap rule that changed how I work
Once I’d named the categories, I gave myself a rule that quietly reshaped almost every workflow in my portfolio:
If a task happens twice and a human did both, it gets a workflow before the third time.
Not "if it’s painful." Not "if it’s slow." Just twice. Because by the third time, the cost of automating it is almost always less than the cost of doing it again — and the compounding starts from workflow #3 onwards, not when the task finally hurts enough to fix.
That rule alone took me from a small set of automations to several dozen, distributed across stores. None of them are clever. All of them are quietly load‑bearing.
A worked example
Here’s a typical example from one of the stores. The pattern is intentionally small — that’s the point.
// pseudo-flow inside n8n
// 1. Listen for new order webhook from store
// 2. Branch by SKU prefix → route to supplier or warehouse
// 3. Generate the supplier-facing PO + customer-facing tracking template
// 4. Push to GSheet ledger
// 5. Trigger customer email when carrier confirms pickup
// 6. Daily 18:00 IST: reconcile against payment gateway, flag mismatches
Six steps. Maybe two hours to build the first time. Replaces something like 30–40 minutes of human attention per order across the lifecycle. Multiply by orders per month and the math gets uncomfortable in the best way.
The drag table I check every quarter
Once a quarter I run every active store through this table. It takes maybe twenty minutes per store and it has yet to fail to surface something worth fixing.
| Drag category | Symptom to look for | First fix |
|---|---|---|
| Order routing | Human decides per order | Workflow + rule table |
| Inventory | Manual stock updates | Sync API + alert thresholds |
| Comms | WISMO emails | Triggered status updates |
| Reconciliation | Books disagree weekly | Daily auto‑reconcile job |
| Reporting | You don’t look | One ten‑minute dashboard |
What this actually unlocked
The naive version of this story is "I automated everything and now I work four hours a week." That’s not what happened, and it’s not the point. What actually happened was much more useful:
- I stopped being the bottleneck for boring decisions, which freed up the only resource I can’t buy more of: attention.
- The portfolio stopped scaling linearly with hours. Adding store fifteen doesn’t cost me what adding store five did.
- I started actually noticing the strategic problems — the ones nobody else can solve for me — instead of drowning in tactical ones.
If you’re running even one store and any of this sounds familiar, the first move isn’t a new tool. It’s a quiet hour with a piece of paper, walking through the five drag categories above, and listing the first three workflows you’d build if someone forced you to choose. That’s usually the most useful hour of the quarter.
If you want me to actually build the workflows with you, that’s the kind of work I do over at digitalshijil.com. Otherwise — keep building, keep cutting drag, keep going.