How to Clarify the Question Before You Calculate in Guesstimates
Most weak guesstimate answers do not fail because the final number is slightly off. They fail because the candidate starts calculating before confirming what is actually being sized. In interviews, clarification is the first scoring move: it shows that you can lock the geography, time period, unit and definition before building the math.
- Start every guesstimate by clarifying scope before choosing numbers or formulas.
- The minimum scope lock is geography, time period, unit and definition.
- Use the template: "To clarify, I am sizing X in [geography] for [time], in [units]."
- Clarification prevents common errors like mixing daily and annual numbers or confusing users, orders, revenue and market size.
- In product-management guesstimates, clarify the metric layer before estimating: users, funnel actions, per-action value or feature impact.
- A strong answer invites pushback after presenting the range, because guesstimates are judged on structure, assumptions and sanity checks.
Why Clarification Is the First Scoring Move
Board Infinity's universal guesstimate recipe starts with scope: "To clarify, I'm sizing X in [geography] for [time], in [units]." This step comes before top-down or bottom-up thinking because it decides what the root of the tree actually is.
A guesstimate is a rapid order-of-magnitude estimate made with limited information. It often uses Fermi estimation, meaning a structured approximation based on reasonable anchors, named after Enrico Fermi. The interviewer is not expecting audited precision, but they are expecting you to solve the right question.
Use this scope-lock table before any calculation, whether the problem is market revenue, daily users, feature adoption or operational volume.
"To clarify, I'm sizing X in [geography] for [time], in [units]." If X can mean more than one thing, define X before moving to the tree.
The Four Clarifications You Must Lock
Every guesstimate should begin with four checks. They sound simple, but each one prevents a different type of error.
Geography determines the base. For example, daily passenger movement at all Indian airports combined starts from annual passenger traffic at Indian airports of approximately 37-40 cr, domestic plus international. A city-only or airport-only version would need a different base; the source cross-check notes Delhi IGI alone handles around 1.9 lakh passengers per day.
Time period determines the divisor or multiplier. Daily UPI failed transactions use total UPI transactions of approximately 67-70 cr per day, while organised diagnostic labs are sized annually using approximately 300-350 cr diagnostic tests per year. If you mix daily UPI logic with annual diagnostics logic, the answer can be off by a factor of 365.
Unit determines whether you stop at volume or continue to value. Electric two-wheeler penetration can be expressed as units, share or revenue. The source first estimates FY28 EV-2W units at approximately 38 lakh units, then converts to revenue using ₹1.1 L average selling price, giving about ₹42,000 crore.
Definition determines what counts. WhatsApp Business catalog views are not all WhatsApp messages, all business chats or all product purchases. The source defines the situation as someone tapping into a business product catalog within a chat, which makes the correct funnel: WhatsApp monthly active users, business interactors, daily interactors, catalog tappers and views per session.
How Clarification Changes the Structure
Once scope is locked, choosing the approach becomes much easier. A top-down approach starts from a macro figure such as population, total users or total traffic and narrows through filters. A bottom-up approach starts from a unit such as one customer, outlet, transaction, MW or vehicle and multiplies up.
A cross-check means solving the same problem another way, such as demand versus supply, to validate the estimate. A sanity check compares the final answer with an external benchmark, such as a comparable company target or per-capita result.
The nuance is that no approach is universally better. In many interviews, you may start top-down and then sanity-check bottom-up, or start bottom-up and test it against a known macro anchor. The right move depends on the unit you clarified.
Worked Example - Clarifying Before Estimating FY28 EV-2W Revenue
This example shows why clarification is not a formality. If the interviewer wanted only EV-2W units, the answer would stop near 38 lakh units. If they wanted revenue, the answer needs the ₹1.1 L average selling price. If they wanted FY26 instead of FY28, the penetration anchor would be around 7%, not 18%.
Clarifying Product-Management Guesstimates
Product-management interviews at Microsoft, Google, Flipkart, Meesho, Swiggy and PhonePe use guesstimates differently from management-consulting interviews. The source notes that they are not testing only market-sizing rigour; they are testing whether you can size a feature, a user segment or a revenue lever within a known product.
That makes clarification even more important. You must first identify the metric layer: total addressable users, behaviour funnel, per-action value or feature impact.
DAU means daily active users, while MAU means monthly active users. ARPU means average revenue per user. GMV means gross merchandise value, or the total value of transactions on a marketplace; it is not the marketplace's own revenue.
The WhatsApp Business catalog example demonstrates the right PM clarification. The source starts with WhatsApp MAU India of approximately 55 cr, then narrows to users interacting with a business account in the past 30 days at approximately 35%, giving 19 cr monthly interactors. Applying DAU/MAU of approximately 60% gives 11.5 cr daily interactors; 8% tap into catalog on a given day, giving 92 lakh tappers; with 4 catalog views per session, total catalog views are approximately 3.7 cr per day, with a range of 3 to 5 cr per day.
The interview signal is the funnel shape. The source explicitly warns that product managers who size a feature as "DAU × ₹" miss the intermediate stack. Strong candidates clarify the user action and move through exposure, adoption, activation, retention and revenue impact.
Reusable Clarification Script
Use a short script at the beginning so you do not sound like you are interrogating the interviewer. The goal is to confirm the frame, not delay the math.
"Before I calculate, I will clarify the scope. I am estimating X for [geography], over [time period], measured in [unit]. I will treat X as [definition]. If that works, I will choose a top-down or bottom-up structure and then sanity-check the answer."
This script fits the Board Infinity 8-step universal recipe: clarify scope, choose approach, sketch the tree, state each assumption with an anchor, calculate with rounded numbers, sanity check, present a range and invite probe. The final step matters because it signals that you welcome follow-up rather than fear it.
Structuring a How to Clarify the Question Before You Calculate Interview Answer
"Estimate the annual revenue of all data centres in India."
The number one way candidates get this wrong is by jumping to a formula before confirming whether the interviewer wants capacity, occupied capacity or annual revenue. Clarify the unit first, then choose the math.
Conclusion
Clarification is not a warm-up line; it is the foundation of the entire estimate. Lock geography, time period, unit and definition first, and your structure will be easier to follow, easier to sanity-check and much harder to derail.
The most frequent error is calculating before defining the metric. It costs points because even neat arithmetic becomes irrelevant if you size annual revenue when the interviewer wanted daily users, or total WhatsApp activity when the question was only about WhatsApp Business catalog views.