A diagnosis of the cross-vertical adoption gap — why 65% of Swiggy users are stuck on one service, and three specific interventions to close that gap.
Swiggy has built something unusual — a platform where you can order dinner, get groceries in 10 minutes, and book a restaurant table, all from one app. They have invested so heavily in Instamart that it now exists both as a feature inside the Swiggy app and as its own standalone app. The intention is clear: Swiggy wants to be present in every moment a user thinks about food — whether cooking at home, ordering in, or dining out. Yet despite this investment, the majority of their food users have never opened Instamart once.
Based on publicly available data, approximately 65% of Swiggy users use only one service. Most of them are food delivery users — they open the app, search for a restaurant, order food, and close it. Instamart is right there, one tap away, but they never try it.
Converting an existing user to a new service costs almost nothing compared to acquiring a brand new user from scratch. If just 10% of Swiggy's food-only users placed one Instamart order in the next 60 days, that would add hundreds of thousands of orders — without spending a single rupee on new user acquisition.
This case study diagnoses why that crossover is not happening and recommends three specific, testable interventions to close the gap.
Before diagnosing the problem, we need to define exactly how we will measure success — and what we must not break in the process.
A user who tries Instamart once because of a discount and never returns is not a win — it is a false signal. The supporting metric catches this. And the guardrail ensures we are growing the pie, not just moving slices around.
To understand why food users are not crossing over, I opened the Swiggy app as a regular user and observed the experience firsthand.
The first thing you see when you open Swiggy is food. The homepage is built entirely around food delivery — restaurants, cuisines, offers. Instamart, Dineout, and other services appear as tabs below the address bar, but they require a deliberate tap to reach. A user who opens Swiggy to order food will scroll through restaurants, place an order, and close the app — without ever naturally encountering Instamart.
This is not a user behaviour problem. It is a design and placement problem. Users are not ignoring Instamart — they are simply never being shown it at a moment when it is relevant to them.
The only moment Swiggy currently attempts to introduce Instamart to a food user is after they have placed a food order — with a ₹50 discount offer. The intention is right, but the timing is wrong. A user who has just ordered dinner is not thinking about groceries. They are thinking about when their food arrives. The offer gets ignored not because users do not want groceries — but because Swiggy is showing it at the wrong moment.
H1 — Low visibility: Most food users never actively notice Instamart because the app never surfaces it to them naturally.
H2 — Wrong trigger moment: Swiggy attempts to convert food users at the least relevant time in their day — right after they have just ordered food.
H3 — No habit-building mechanism: A single ₹50 offer can create a one-time transaction, but not a lasting behaviour change.
Swiggy currently shows food as the default at all hours. The fix is simple: between 7am and 11am, surface Instamart prominently on the homepage — this is when people think about groceries, breakfast, and what to cook for the day. Between 6pm and 8pm, show it again when dinner cooking decisions are being made. Outside these windows, food remains the default. Show the right service at the right moment.
When a user searches for a dish on Swiggy food — say "chicken noodles" — show a secondary option below the restaurant results: "Cook it yourself — get all ingredients delivered in 10 minutes via Instamart." Show the ingredient list, estimated cost, and number of servings. This turns a food search into a natural Instamart discovery moment without interrupting the ordering flow for users who still want to order out.
When a user is about to confirm their food order, show one relevant Instamart item — a cold drink, a dessert, or a snack that pairs naturally with what they ordered. "Complete your meal — add a Coke from Instamart, delivered in 10 minutes." This reaches the user when they are already in buying mode, making the addition feel natural rather than intrusive. Since approximately 50% of users enjoy something sweet after a meal, even a 20–25% conversion on this prompt would drive a significant number of first-time Instamart orders daily at zero acquisition cost.
Combined across the three touchpoints — morning homepage surfacing, cook-it-yourself during food search, and add-on at checkout — a conservative estimate is that 20–25% of currently food-only users would place at least one Instamart order within 60 days. At Swiggy's scale of tens of millions of food users, a 20% crossover rate represents hundreds of thousands of new Instamart orders generated without any new acquisition spend.
The most important number after launch is not the 60-day crossover rate — it is the 7-day repeat rate on Instamart. If users who try Instamart through any of these three interventions come back within a week, the habit is forming. If they do not, the interventions created transactions but not behaviour change — and the approach needs to be reconsidered before scaling.