10 Product Management & Market Sizing Guesstimate Questions [Solved] // Unstop

Product management is a dynamic field that requires a blend of analytical thinking and strategic decision-making. One of the key skills for a product manager is the ability to estimate market size, forecast demand, and make data-driven decisions without complete information. This is where guesstimates and market sizing questions come into play. These problems test a product manager’s ability to break down complex questions logically and arrive at a reasonable estimate.

In this article, we’ll explore 10 common product management guesstimates and market sizing questions, providing structured solutions.

Basic Framework for Solving Product Management Guesstimates

To approach any guesstimate or market sizing problem, follow this framework:

Clarify the Question: Ensure you understand the problem. Define key parameters such as geography (India, city-specific, global), demographics, and product category.
Make Logical Assumptions: Use real-world references, common sense, and known industry trends to make reasonable assumptions.
Break Down the Problem: Divide the larger question into smaller, more manageable parts to simplify calculations.
Perform Stepwise Calculations: Solve each step using multiplication or percentage-based estimations.
Cross-Check for Accuracy: Validate your answer by comparing it with known data points or industry benchmarks.

10 Product Management & Market Sizing Guesstimates For Your Practice

Let's take a look at the 10 guesstimate questions with step-wise solutions.

1. Number of Users of a Food Delivery App in a Tier 2 City

Assumption: Tier 2 city population: 500,000. Internet penetration: 70%. Smartphone penetration among internet users: 80%. Percentage of smartphone users using food delivery apps: 20%.

Solution:
1. Internet users: 500,000 * 70% = 350,000
2. Smartphone users: 350,000 * 80% = 280,000
3. Food delivery app users: 280,000 * 20% = 56,000
Explanation: This helps a PM understand the potential user base for their food delivery product.

2. Impact on App Usage if a Key Feature is Improved (e.g., faster delivery)

Assumption: Current app usage: 100,000 daily active users. Assume 20% of users are primarily concerned about delivery speed. Assume a 50% improvement in delivery speed leads to 50% of those concerned users becoming more engaged, leading to a 20% increase in their usage frequency.
Solution:
1. Users concerned about speed: 100,000 * 20% = 20,000
2. Users with increased engagement: 20,000 * 50% = 10,000
3. Increased usage per user: 20%
4. Overall increase in daily active users: 10,000 * 20% = 2,000 (additional sessions, not necessarily new users)
Explanation: This helps product managers to estimate the potential return on investment for improving a specific product feature.

3. Number of Monthly Active Users of a New Language Learning App

Assumption: Target market: 10 million people interested in learning a new language. Marketing reach: 50% of the target market. Conversion rate from marketing to app downloads: 10%. Percentage of downloaded users who become monthly active users: 30%.

Solution:
1. People reached by marketing: 10,000,000 * 50% = 5,000,000
2. App downloads: 5,000,000 * 10% = 500,000
3. Monthly active users: 500,000 * 30% = 150,000
Explanation: This helps the product manager project the user base for a new product.

4. Effect of a Price Change on Sales Volume of an E-commerce Product

Assumption: Current price: ₹1,000. Current sales: 10,000 units/month. Price decrease: 10%. Assume price elasticity of demand is -1.5 (meaning a 1% decrease in price leads to a 1.5% increase in quantity demanded).

Solution:
1. Percentage change in price: -10%
2. Percentage change in quantity demanded: -10% * -1.5 = 15%
3. New sales volume: 10,000 * 1.15 = 11,500 units
Explanation: Helps understand the impact of pricing decisions on sales.

5. Number of Customer Support Tickets a Company Receives Daily

Assumption: Number of customers: 1 million. Percentage of customers who contact support monthly: 5%. Average number of support tickets per customer per month: 2.

Solution:
1. Customers contacting support monthly: 1,000,000 * 5% = 50,000
2. Total support tickets per month: 50,000 * 2 = 100,000
3. Daily support tickets: 100,000 / 30 = approximately 3,333
Explanation: Helps plan for customer support resources.

6. Market Share of a New Feature in an Existing App

Assumption: Total app users: 500,000. Assume 20% of users are likely to use the new feature. Of those, assume 60% become regular users of the feature.

Solution:
1. Potential users of the new feature: 500,000 * 20% = 100,000
2. Regular users of the new feature: 100,000 * 60% = 60,000
3. Market share (among app users): (60,000 / 500,000) * 100% = 12%
Explanation: Helps assess the adoption rate of a new feature.

7. Number of Users Clicking on a Specific Ad in an App

Assumption: App users: 100,000. Ad visibility: 50% of users see the ad. Click-through rate (CTR): 2%.

Solution:
1. Users seeing the ad: 100,000 * 50% = 50,000
2. Users clicking the ad: 50,000 * 2% = 1,000
Explanation: Helps evaluate the effectiveness of in-app advertising.

8. Impact of a Redesign on User Retention

Assumption: Current user retention rate: 50% (meaning 50% of users come back after a week). Assume the redesign improves user experience, leading to a 10% increase in retention.

Solution:
1. Increase in retention: 50% * 10% = 5%
2. New retention rate: 50% + 5% = 55%
Explanation: Helps measure the success of a redesign effort.

9. Number of App Downloads from an Influencer Marketing Campaign

Assumption: Influencer's followers: 1 million. Engagement rate (likes, comments, shares): 5%. Click-through rate on the campaign link: 2%. Conversion rate from clicks to downloads: 10%.

Solution:
1. Engaged followers: 1,000,000 * 5% = 50,000
2. Clicks on the link: 50,000 * 2% = 1,000
3. App downloads: 1,000 * 10% = 100
Explanation: Helps estimate the effectiveness of influencer marketing.

10. Market Size for a Niche Product Feature (e.g., in-app language translation)

Assumption: App users: 1 million. Percentage of users who might use the feature: 10%. Percentage of those users who would be willing to pay for it: 20%. Average monthly price for the feature: ₹50.

Solution:
1. Potential users of the feature: 1,000,000 * 10% = 100,000
2. Paying users: 100,000 * 20% = 20,000
3. Monthly market size: 20,000 * ₹50 = ₹1,000,000
Explanation: Helps assess the revenue potential of a niche feature.

Want to become a product manager? Take these Role-Based Mock Tests to assess your skills!

Conclusion

Guesstimates and market sizing questions are crucial for product managers to make data-driven decisions with limited information. By following a structured approach - defining assumptions, breaking down numbers, and cross-validating results - you can develop logical estimations that guide business strategies. Whether estimating smartphone sales, food delivery revenue, or OTT platform growth, these calculations serve as valuable tools in product management. Start practicing.

Suggested Reads: