A headless Commerce Operating System for India's scaling
enterprise Direct-to-Consumer (D2C) brands — designed from a blank canvas to a shipped MVP.
As the sole product person in a 4-person pod, I took Etailify from a blank canvas to a shipped MVP in 11 months — owning market research, product strategy, information architecture, interface design, and written specifications end to end. I identified the enterprise pivot, defined all seven core system architectures, and authored the PRDs that served as the single source of truth for engineering and business development simultaneously.
Three parallel research tracks before a line of code was written: undercover competitor procurement cycles with Shopify Plus and Unicommerce, embedded field research with brands at opposite operational ceilings, and unique selling point definition against alternatives. The output was the commercial strategy and the product thesis — not a deck, but a buildable product vision.
Defined the complete structural blueprint across the entire Partner OS — catalogue architecture, supply chain logic, Order Management System (OMS) state machines, fulfilment workflows, multi-node inventory transfers, and reverse logistics. Every information architecture decision mapped directly to the backend database states the CTO's pod would build against.
Designed every screen, interaction state, and edge-case resolution across all seven core systems — from the Maker-Checker pricing approval flow to the Twin Wallet payout UI. Produced a tokenised design system that the frontend engineer could execute with zero ambiguity.
Defined the MVP boundaries and held the line on scope every sprint. Forced a phased rollout when the founding team's instinct was to ship everything at once. Authored PRDs, state-machine specifications, and Knowledge Transfer (KT) documentation that served as the single source of truth for engineering, business development, and onboarding simultaneously.
Partner OS · Products
Three parallel research tracks run before a single line of code was written.
Follow the money through a scaling brand's operations. Revenue enters healthy — then leaks at four joints. None of the four is individually fatal. At volume, the combination is.
7–14 day COD remittance locks working capital in transit.
Stock split across 3PLs, FBA & dark stores — stockouts and wrong-node freight.
Stacked discounts and GST errors surface only at reconciliation — after the order ships.
iOS14 and ad-blockers break Meta & Google attribution — scaling the unmeasurable.
Not gradual drifts — forced choices, each with a clear rationale, made before the build began.
(Forged through collective intelligence of the founding team.)
80%+ of GMV came from a minority of enterprise clients. SMB volume was noise.
Migration was the single biggest blocker in the sales cycle. Decoupling removed it.
Flat fees cap revenue at seat count. Revenue scales with GMV instead.
A prediction engine, not a database. Every new merchant compounds the moat.
Promotions dashboard
One commercial mandate, resolved into three non-negotiable filters. Each one killed a feature that otherwise looked perfectly reasonable.
Engineer every capital and operational touchpoint to protect merchant margins and monetise through the infrastructure itself — not software fees. This was the filter for every roadmap decision.
Every feature meets one test: does it directly protect or grow operating margin? If not, it is cut.
Real-time analytics, in favour of Maker-Checker pricing approval. Less visible, more margin.
Where a self-healing static model delivers 95% of live accuracy at a fraction of the cost, the static model wins.
Live carrier polling, for self-healing static rate cards — 90% infrastructure reduction, negligible accuracy loss.
Every system is an independently activatable module — the platform scales incrementally, never a full rebuild per stage.
A coupled revenue layer, for modules staged for post-MVP activation — decoupled from an external dependency on its own timeline.
Seven core systems across two release stages — five shipped in the MVP, two fully designed and staged for post-onboarding activation. Select a layer to explore.
Decoupling the sellable frontend product from the physical backend SKU — a structural flaw in legacy platforms that breaks during bundle sales, B2B cross-listing, and multi-variant operations.
A complete Order Management System (OMS) state machine — from order placement to post-delivery resolution — with granular intermediate states covering every conditional branching scenario.
The platform's transaction layer — engineered to execute the core commercial thesis of volume aggregation and spread capture. Activation is gated on Escrow infrastructure, not product readiness.
Moving beyond descriptive reporting. Cross-brand anonymised data becomes a prediction engine and the platform moat that compounds with every new merchant.
A modular UI framework that mirrors the decoupled backend — each micro-service independently toggleable without affecting global platform state.
Order management automation preferences
A single module to demonstrate the structural logic required beneath the macro architecture. This state-machine schema ingests a raw storefront payload and autonomously triggers multiple carrier dispatches — zero manual intervention.
* System runs on self-healing static rate cards — eliminating live carrier API dependency and reducing infrastructure overhead by 90% with negligible routing accuracy loss.
One order in · split across 2 inventory nodes · 5 delivery orders out across 4 carriers · each routed back to the customer.
Honest reflections from executing an enterprise OS with a 4-person founding pod. These are not lessons learned in theory — they are decisions that produced visible consequences on the build timeline.
I forced the pivot to a phased MVP — the right call. But continuous micro-additions throughout the build extended the timeline in ways that compounded before they were visible. Scope defence isn't a one-time decision; it's a weekly act of reviewing every addition against the defined core and making the trade-off explicit.
Carrier and PG negotiations moved slower than the build. Reprioritising was reasonable — but it compressed the QA window when contracts finally landed. The fix: sandbox carrier and PG endpoints from day one so engineering builds against dummy credentials throughout. Live keys swap in when BD closes. External timelines should never touch QA.
Next Steps
The deep product strategy, architectural trade-offs, and execution realities are best explored in a live conversation.