Size the UK market for a paid meal-planning app, and tell me whether you would build it.
A product market sizing case should define the revenue pool, work top-down from households to willingness to pay, sanity-check penetration, then turn the estimate into a build-or-don't-build recommendation. It also connects estimation to the point an interviewer is testing.
Answer
Short answer
Define the market you are sizing, choose the unit of demand, multiply through a transparent assumption chain, then sanity-check the implied penetration. For a paid UK meal-planning app, the consumer subscription market looks small enough that the better recommendation is usually a grocery or basket-building model rather than a standalone paid app.
Was this answer helpful?
Likely follow-ups
- Which of your assumptions would you spend a week checking first, and how?
- How does the answer change if the buyer is a grocery retailer rather than a consumer?
- Give me the same estimate for India. What changes structurally, not just numerically?
- What would make you revise this upwards by an order of magnitude?
Related questions
- A large retailer wants to white-label your product and sell it to their own customers. Do you do the deal?hardAlso on unit-economics and product-cases6 min
- Two customer segments each bring in the same revenue and you can only focus on one next year. How do you choose?hardAlso on product-cases and unit-economics6 min
- Name a product decision you think is bad. Now tell me why the team that made it might have been right.mediumAlso on business-model5 min
- How do you size and price an engagement when the scope is still uncertain, and what do you do when you are told to cut the number?hardAlso on estimation7 min