Case Drill: Entering a New City in Quick Commerce

In the previous concept, Case Drill - Pricing Strategy for a SaaS Product in India, the challenge was to match pricing to customer willingness to pay and adoption friction. This case raises the difficulty: as the growth lead at a quick-commerce company like Blinkit or Zepto, you now need to launch Jaipur from zero presence in 90 days. It matters in interviews because it tests whether you can combine market sizing, operations, local consumer behaviour, unit economics, and metrics instead of listing disconnected marketing tactics.

The Big Picture: A 90-Day Quick-Commerce City Entry Playbook

Quick commerce means rapid delivery of daily-use products, typically through a dense network of nearby dark stores. In this case, the goal is not just to acquire users in Jaipur, but to build a city launch system where supply, rider capacity, assortment, demand generation, and retention metrics work together.

Market Assessment: Decide Whether Jaipur Is Worth Launching

The first step is to assess whether Jaipur has the demand density and supply readiness needed for quick commerce. The source gives four essential inputs: a metro population of approximately 4 million, a large student and young professional base around University of Rajasthan and IIHMR, existing but not saturated competition, and usable supply from Muhana Mandi and FMCG distributors.

This matters because quick commerce is highly local. A city entry case is not solved by saying, "launch ads and discount heavily." The interviewer is looking for whether you can read the city's demand profile and translate it into store placement, assortment, rider hiring, and metrics.

The nuance is that Jaipur should not be treated like Mumbai. The lower expected AOV of ₹250-350 changes how offers, delivery fees, and subscription thresholds are evaluated. A candidate who ignores this and assumes metro-city behaviour will lose points on localisation and unit economics.

Pre-Launch: Build the Minimum Viable Operating Network

Weeks 1-4 are about creating operational readiness before demand is switched on. In quick commerce, a dark store is a small fulfilment centre located close to customers rather than a customer-facing retail store. The source plan starts with 3 dark stores in Malviya Nagar, Vaishali Nagar, and Mansarovar, with the goal of covering 90% of the target population within a 15-minute delivery radius.

The operating model has three linked components: store location, assortment, and rider supply. If any one of these fails, marketing demand turns into a poor customer experience. For example, a 10-minute delivery promise shown in an influencer reel is only credible if dark store location and rider availability support it.

The practical interview use is to show that city launch is a systems problem. You can say: "I will not start with app installs. I will first ensure that the top zones, rider supply, and catalogue are ready to deliver the promise." That answer sounds more operator-like and less like a generic marketing plan.

Assortment Localisation: Start Narrow, Then Expand from Search Data

Assortment is the set of products available to order. In this case, the recommended starting point is 2,000 SKUs, much smaller than the 5,000+ SKUs seen in mature cities. That is a deliberate choice: early assortment should cover high-frequency needs while avoiding operational overload.

Jaipur's starting basket should include dairy, fruits, vegetables, staples, personal care, and beverages. Local preference items like namkeen, chach or lassi, and dal bati mixes make the catalogue feel relevant. This is especially important in a market with high kirana dependency, because customers need a reason to shift from familiar local stores.

The scale phase uses data-driven assortment expansion. In Weeks 9-12, the team analyses the top 100 searched-but-not-found items and adds them to the catalogue quickly. This is a strong case move because it turns user behaviour into an operating decision rather than relying only on assumptions.

Demand Generation: Create Trial Without Losing the Local Lens

Weeks 5-8 form the launch sprint. The goal is to generate first orders fast enough to test the operating model while introducing Jaipur customers to the convenience of quick commerce. The recommended offer is: First 3 orders - free delivery plus ₹100 off on orders above ₹299.

This offer is connected to the expected AOV. Since Jaipur's AOV is likely ₹250-350, an order threshold of ₹299 sits within the likely basket range while nudging users to build a viable basket. The source also says aggressive CPA is acceptable in the launch phase, but only because the goal is first-order adoption and learning.

The nuance is that growth tactics must match city context. In Jaipur, residential societies and colleges are specific channels in the source. A generic "run digital campaigns" answer is weaker because it misses the hyperlocal nature of the case.

Unit Economics: Show That Growth Has Operational Discipline

Unit economics means the economics of one order or one customer interaction. The source does not provide a full profit-and-loss statement, but it explicitly says the interviewer is testing understanding of dark store costs, rider costs, and AOV targets. Therefore, the answer should discuss these levers without inventing numbers.

For this case, the economic tension is clear. Jaipur's likely AOV is ₹250-350 compared with ₹450 in Mumbai, so the team cannot simply copy mature-city spending or catalogue depth. At the same time, the launch offer and CPA can be aggressive during the launch phase because the objective is to build trial and learn which zones, SKUs, and cohorts retain.

In an interview, this section separates strong candidates from tactic-heavy candidates. You do not need to calculate exact profitability if data is not provided. You do need to show which variables would determine whether the launch can scale responsibly.

Worked Example: 90-Day Jaipur Launch Decision

This worked example is powerful because every recommendation links back to the city facts. It uses Jaipur's population, student clusters, competition, supply sources, and order-value reality to make the launch plan specific.

Metrics: Define Success Before You Launch

A 90-day plan needs measurable success criteria. The source gives three Week 12 targets: 5,000 Daily Active Orders, average delivery time below 15 minutes, and repeat rate above 40%. Daily Active Orders, or DAOs, means the number of customer orders placed per day.

These metrics cover demand, service quality, and retention. DAOs show whether the city is generating order volume. Delivery time shows whether the operating promise is being met. Repeat rate shows whether launch incentives are converting into habit.

The nuance is that metrics should not be treated independently. For example, a high order count with weak repeat rate may indicate discount-led trial but poor habit formation. Similarly, strong demand without delivery speed can damage the quick-commerce proposition.

Structuring a Case Drill Interview Answer

Conclusion

A Jaipur quick-commerce launch is a 90-day operating case, not a campaign calendar. The winning answer assesses the market, builds a tight dark-store and rider network, localises assortment, creates disciplined trial, and judges success through DAOs, delivery speed, and repeat rate.