Growth Is Easy to Announce. Operating Leverage Is Hard to Build.

A digital platform is not truly scaling when its order volumes rise. It is scaling when each additional order makes the underlying system more efficient.

Swiggy’s second-quarter FY27 results illustrate that distinction. Revenue grew 36% year on year and net loss narrowed 15.6%, while food delivery reported higher adjusted EBITDA. At the same time, Instamart expanded quickly, with net order value up 31.4% and 69 new dark stores-but its reported loss also increased.

The figures point to a larger strategic question: Can a platform turn growth into durable operating leverage across businesses with very different economics?

Scale is an architectural challenge

Food delivery and quick commerce may share an app, a customer base and parts of a technology stack. But their operating models are different. One coordinates restaurants, riders and customer demand; the other adds inventory, storage, replenishment and local fulfilment to the equation.

That distinction matters for enterprise architecture. Shared infrastructure can reduce duplication, but forcing different business models into the same operational logic can create hidden costs. Forecasting demand for a restaurant meal is not the same problem as deciding which products to stock in a neighbourhood store. Each requires its own data models, service-level expectations and measures of efficiency.

The real platform advantage is not simply a common interface. It is the ability to reuse what should be shared-identity, payments, customer support, observability and core data capabilities-while keeping the systems that need to differ appropriately modular.

Growth must become operational leverage

The food-delivery business’s reported adjusted EBITDA of Rs 341 crore, up Rs 101 crore over a year, is an important signal. It suggests that scale can be accompanied by improving economics in at least one part of the operation. But that progress should not obscure the investment still required elsewhere: Instamart’s revenue rose, yet its loss widened to Rs 764 crore.

These are not contradictory outcomes. They reflect different stages of maturity and different cost structures. The architectural question is whether investments in stores, inventory systems and fulfilment processes produce a repeatable path to better economics-or simply support expansion.

For technology leaders, this means treating operational metrics as first-class design inputs. Store throughput, inventory availability, substitution rates, delivery time and fulfilment cost should connect directly to product and engineering decisions. If data arrives too late, or teams optimise separate dashboards without a shared view of contribution economics, the organisation may scale activity faster than value.

A useful discipline is to distinguish growth metrics from health metrics. GOV, order value and revenue show reach and commercial momentum. Contribution, fulfilment efficiency, waste, retention and segment-level profitability help explain whether that momentum is sustainable. No single figure tells the whole story; together, they guide investment.

Build for density, not just expansion

Quick commerce depends heavily on local density. Adding stores expands reach, but each new location also introduces fixed costs, inventory complexity and operational dependencies. The challenge is to know where additional capacity improves the customer experience and where it dilutes efficiency.

This has a broader relevance for Indian digital businesses. In a country of varied settlement patterns, purchasing power and infrastructure, a model that works in one dense urban cluster may not transfer unchanged to another market. Expansion needs local data and adaptable operating rules-not just a repeatable rollout checklist. That is particularly important when platforms look beyond their most concentrated markets, including regions where geography and logistics can make service design more demanding.

For founders and CTOs, the lesson is practical: invest in systems that make unit economics visible at the level where decisions are made. Build modular platforms, but do not mistake modularity for uniformity. Automate where the process is understood; preserve human oversight where local conditions and exceptions matter.

The next phase of platform leadership will belong not simply to companies that grow fastest, but to those that learn how to make growth increasingly efficient.

---

About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.