PM guesstimate framework for daily active user estimates
Start your DAU guesstimate with a clear target definition, segment users explicitly, and use transparent, checkable assumptions. Choose a calculation path that balances realism and simplicity. Identify the riskiest unknowns, and propose a small validation experiment to reduce uncertainty before scaling your recommendation.
PMMockr.comClarify the DAU definition and scope first
A common mistake is to launch into calculations without confirming what 'Daily Active User' means in the context of the question. DAU could refer to anyone who opens the app, those who perform a key action, or unique logins. Start by asking for or stating your definition, e.g., 'unique users who complete at least one session per day.' This disambiguation sets the stage for a focused estimate and avoids wasted effort.
Also, clarify the platform (e.g., mobile-only, web, or both), the geography, and any product restrictions. For example, estimating DAU for a niche B2B SaaS tool in North America will yield a very different process than for a global consumer social app.
Segment users to reduce guesswork
Jumping straight to a single population number often leads to hand-waving and large errors. Instead, break down the user base into logical segments: by geography, age group, platform, or use case. This approach lets you assign more realistic, checkable assumptions to each segment.
For example, estimating DAU for a language learning app, you might segment by language (English, Spanish, etc.), then by age group (students, professionals). For each, you can make smaller, more reasoned guesses about adoption and frequency.
Lay out explicit, checkable assumptions
Weak reasoning often hides behind vague assumptions: 'Let's say 10% of people use this daily.' Instead, state each assumption, label it as such, and explain your rationale. For instance, 'Assume 50 million adults in the US are interested in fitness apps (assumption: 20% of the 250 million adults).' If you cannot justify a number, flag it as the riskiest input.
This transparency lets the interviewer easily see your logic and challenge any step, which is far more valuable than an opaque calculation.
Choose a calculation path: top-down or bottom-up
There are generally two calculation approaches: top-down (start with a large population, filter down) and bottom-up (start with a core group, extrapolate up). Choose the one that best fits the product and your knowledge.
For a mass-market app, top-down usually works: start from total population, apply penetration rates, then estimate daily frequency. For niche or B2B products, bottom-up (e.g., number of companies × average employees × usage rate) may yield more believable numbers. State your choice and why it makes sense for this scenario.
Worked example: estimating DAU for a US-based fitness tracking app
Suppose you're asked: 'Estimate the daily active users for a mobile fitness tracking app in the US.'
First, define DAU as 'unique users who open the app and log an activity.' The US has about 250 million adults (assumption).
Segment by age: assume 18-34 (30%), 35-54 (35%), and 55+ (35%). Fitness app users skew younger, so estimate the following adoption rates: - 18-34: 25% use fitness apps (assumption, based on app popularity) - 35-54: 15% - 55+: 5%
Calculate total potential users: - 18-34: 250M × 30% × 25% = 18.75M - 35-54: 250M × 35% × 15% = 13.125M - 55+: 250M × 35% × 5% = 4.375M - Total: ~36M potential users
Next, estimate how many are active daily. Assume 40% are 'active' (log at least one activity per day; assumption based on fitness habits). So, DAU = 36M × 40% = 14.4M
Alternative approach: Estimate total fitness app downloads (say, 50M in the US; assumption), then estimate retention (e.g., 30% monthly active, 50% of those are daily active): 50M × 30% × 50% = 7.5M DAU. This is significantly lower; the difference highlights the sensitivity to retention and active use assumptions.
To resolve this, propose a validation: check public app store rankings, compare reported DAU from major apps, or survey a sample of users. If data shows actual DAU for top apps is closer to 5M, revise your estimate downward, noting that your earlier assumptions were optimistic.
Prioritize assumptions by risk and impact
Not all assumptions are equally risky. The assumption about daily activity rate often drives the most uncertainty in DAU estimates, as it converts potential users to actual daily actives. In the worked example, the 40% daily activity rate could easily be off by a factor of two.
Flag this as the primary risk. Suggest ways to test or validate it first, such as referencing published engagement metrics or running a quick user survey. This focus demonstrates judgment in where to invest effort.
Compare trade-offs: simplicity versus realism
Using fewer segments or broad averages makes calculations quicker but risks hiding important nuances. Over-segmenting can slow you down and introduce too much detail. The best approach is to segment just enough to capture major behavioral differences, then sanity-check your results.
In the example, segmenting by age group captures the likely variance in app usage, but adding gender, region, or income level may not materially change the estimate unless the product is highly targeted.
Weak reasoning: a cautionary example
Suppose you say: 'There are 250 million adults, let's say 10% use fitness apps, so 25 million. Assume half are daily users, so 12.5 million DAU.' This skips segmentation and uses arbitrary percentages without justification.
A better alternative is to explain each percentage, tie it to a plausible behavior or external reference, and segment at least once. This not only produces a more credible number, it also shows structured thinking, which is the real skill being tested.
Validate with a practical experiment or data check
Before committing to your estimate, describe a concrete way to check it. For instance, compare your DAU estimate with public reports for similar apps, cross-check with app store download rankings, or propose running a brief survey of your target segment.
State what new evidence would prompt you to change your recommendation. For example, if you learn from a reliable source that the largest fitness app has 3 million DAU in the US, and your estimate is 14 million, this suggests your adoption or activity rate assumptions are too high. Revise accordingly, and explain the adjustment.
Timed practice and self-review checklist
Set a timer for 10 minutes. Choose a product (e.g., a US high school homework app). Estimate its DAU using explicit assumptions, at least one segmentation, and explain your reasoning at each step. Propose a validation method.
Checklist: - Did you state and clarify the DAU definition? - Did you segment the user base and explain why? - Are all assumptions explicit and checkable? - Did you choose a calculation path and justify it? - Did you identify the riskiest assumption? - Did you compare at least one alternate approach or trade-off? - Did you propose a practical validation or experiment?
Practice this cadence 2-3 times per week. Use PMMockr or similar tools for additional prompts and feedback.
FAQ
How many segments should I use in a DAU guesstimate?
Use as many as needed to capture major behavioral differences, but not so many that the calculation becomes unwieldy. Typically, 2-3 meaningful segments (such as age and platform) are sufficient for most interview questions.
What if my estimate is way off from real-world numbers?
Acknowledge the discrepancy, revisit your assumptions, and update your estimate. Explain which assumption was most likely the source of error and how you would gather better data before making decisions based on the estimate.
Should I always use both top-down and bottom-up methods?
Not always, but briefly contrasting both can strengthen your answer. Choose the method that fits the product and your knowledge best, but mention the alternate approach and explain what it might reveal about your confidence in the numbers.