Zomato restaurant insights product: design it, price it and plan its go-to-market

As a product manager at Zomato, you are asked to create a data product that restaurants would pay for. Propose what the product is and whom it serves, then lay out the complete go-to-market plan that would launch it and turn it into a revenue line. ### Clarifying Questions - Is the product sold only to restaurants already listed on Zomato, or also to restaurants that do not use the platform? - Must the product earn money directly through its own fees, or does indirect revenue count, such as more advertising spend or lower partner churn? - Which restaurant types matter most: single-outlet independents, delivery-only kitchens, or multi-outlet chains? - How much aggregated information about nearby competitors is Zomato willing to show its partners? ### Part 1 — Define the Data Product Decide which restaurants you are building for, which recurring business decisions the product helps them make, what it contains in a first version, and how it makes money. ```hint Start from data only Zomato holds A restaurant already sees its own sales in its billing system. Ask which questions an owner cannot answer from that alone, and what a marketplace sees that a single kitchen never does. ``` #### What This Part Should Cover - The chosen restaurant segment and the specific decisions the product improves for it - The platform data behind each insight, and how customer and competitor information stays protected - A scoped first version versus later additions - The revenue model, with a price anchored to the value restaurants receive ### Part 2 — Build the Go-to-Market Plan Plan how the product reaches its first paying restaurants and then scales: the launch segment and markets, packaging and pricing, channels and sales motion, rollout phases, and the metrics that decide whether each phase succeeded. ```hint Earn the first payment Think about which restaurants would pay first, what proof of return they would need before paying, and where in their existing workflow with Zomato they would meet the product. ``` #### What This Part Should Cover - A beachhead segment and a phased rollout with gates between phases - Packaging and pricing tiers, and the sales channel that fits each tier - How return on investment is demonstrated to restaurants - Adoption, monetization and impact metrics, with guardrails for platform health ### What a Strong Answer Covers - A clear reason why Zomato, rather than a generic analytics vendor, can win this market - Consistency between the segment, the product scope, the price and the channels - The trust problem: charging restaurants for insights built partly from their own activity, keeping competitor data anonymous, and keeping paid insights separate from search ranking - Metrics that show whether restaurants acted on insights and gained from them, not only sign-ups - Risks, trade-offs and the conditions under which the plan would be scaled back ### Follow-up Questions - Restaurants object to paying for insights derived from their own orders. How do you respond, and does your packaging change? - The pilot restaurants like the product, but their orders show no lift against a matched control group. What do you do next? - How would you stop restaurants from believing that subscribers get better placement in search results?