Running an e-commerce brand day to day — inventory, fulfilment, seasonal demand, customer support — teaches lessons that translate directly into how we build and operate software. The surface looks different. The underlying discipline is the same.
Operations are the product
For a physical brand, the product isn’t just the garment; it’s whether it arrives, fits, and can be returned without a fight. Customers don’t separate the object from the experience of getting it. Software is no different. The feature is not the product — the product is the feature plus onboarding, plus support, plus what happens when something breaks at the worst possible time.
Inventory is a feedback loop
Ordering stock forces a bet on demand you can’t fully know, then pays you back with brutal clarity: it sells or it sits. That loop trains a useful instinct — commit in increments, read the signal, adjust. It’s the same instinct a good roadmap needs. Ship a defined scope, watch what real usage says, and let the next commitment be shaped by evidence rather than the original plan.
Support is research
Every support ticket is a customer telling you where the product failed them, for free. Running an e-commerce brand makes that impossible to ignore, because a confused customer is a refund and a lost repeat sale. Carried into software, it reframes support from a cost centre into the cheapest research the business has. The teams that read their own tickets build noticeably better products than the teams that route them away.