How would you decide whether to build office meal subscriptions or improve ad-hoc group ordering first for a Swiggy-style product?

Problem Statement Description

Product context: Swiggy is an Indian food delivery and quick-commerce company; its products include restaurant delivery, Instamart grocery delivery, dining discovery, Genie, subscriptions, and partner tools.

Swiggy is evaluating where to invest next in food delivery experiences for office lunch occasions. Two potential directions are on the table: building an office meal subscription product for recurring weekday meals, or improving ad-hoc group ordering for teams that coordinate lunch together when needed.

The target users include office lunch coordinators, employees ordering together, restaurants fulfilling clustered lunch demand, and delivery partners operating in busy weekday time windows. The current workflow may involve collecting preferences across colleagues, managing payments, choosing restaurants that can serve groups reliably, coordinating delivery timing, and handling substitutions, delays, or cancellations.

This is a strategy decision, not a feature design exercise. You should frame how you would compare the two opportunities, what evidence you would seek, what trade-offs matter for Swiggy’s marketplace, and how you would decide which bet to pursue first to drive repeat group orders.

The experience should consider:

- Market size and frequency of office lunch use cases across Indian urban workplaces

- User pain points for coordinators, individual employees, restaurants, and delivery operations

- Strategic options: recurring subscriptions, improved one-time group ordering, hybrid approaches, or phased bets

- Swiggy’s right to win given restaurant density, delivery network, payments, loyalty, and existing consumer behavior

- Trade-offs across demand predictability, operational complexity, restaurant prep variability, delivery batching, and customer trust

- Risks around failed deliveries, low subscription retention, payment splits, privacy, data quality, and customer support load

- Decision gates such as pilot criteria, adoption signals, repeat behavior, unit economics, and operational reliability

- Competitive and ecosystem considerations, including employer involvement, restaurant partnerships, and alternative lunch solutions

Your goal is to describe a clear decision-making approach that helps Swiggy choose which opportunity to prioritize first, while showing how you would evaluate business impact, customer value, operational feasibility, risks, and learning milestones before committing significant product and engineering investment.