Guesstimates & Market Sizing for Analytics Interviews: A Confident MBA Framework
A quick-commerce team can reject a dark-store location before running a full survey by doing one rough calculation: households in the catchment x likely order frequency x average basket x delivery capacity. That is the power of a guesstimate - not guessing wildly, but building a number when perfect data is not available.
- A guesstimate is a structured estimate: define the unit, break the problem into drivers, assume transparently, calculate cleanly, then sanity-check.
- Market sizing is usually either top-down or bottom-up: top-down starts from population or industry size; bottom-up starts from users, usage and price.
- The interviewer is testing thinking, not the final number: clear structure, realistic assumptions and self-correction matter more than exact accuracy.
- Always state scope first: geography, time period, customer segment, product definition and whether you are estimating volume, revenue or profit pool.
- Use the Fermi logic: convert a big unknown into smaller known-ish assumptions, then multiply or add them carefully.
- Sanity-check with another route: per-capita spend, supply capacity, comparable category, or replacement cycle.
- Common trap: jumping into arithmetic before defining the market - it creates a neat-looking but useless answer.
Big Picture: A Guesstimate Is a Mini Analytics Model
Think of a guesstimate as a five-minute model built out loud. You are not expected to know the exact number; you are expected to convert ambiguity into a logical equation, expose assumptions and test whether the answer feels commercially plausible.
Core Explanation: The Framework That Actually Works
The big idea is simple: market size = number of eligible buyers x usage x price. Most interview questions are variations of that equation. Your job is to make the equation fit the category.
For example, if asked to size the market for premium running shoes in Mumbai, do not begin with India population. First define: Mumbai only, annual revenue, shoes priced above a chosen premium threshold, consumers buying for running or fitness, not formal shoes or casual sneakers. Then build the estimate.
Step 1: Define the Scope Before the Number
Step 2: Choose Top-Down or Bottom-Up
Top-down sizing starts with a large base and narrows it. Bottom-up sizing starts with behaviour at the user, store, route or transaction level and scales it up. In analytics interviews, bottom-up often sounds more business-aware because it uses observable drivers.
Step 3: Use Segments, Not Averages
Averages hide the answer. If you estimate food delivery orders by saying every Indian orders twice a month, the model collapses. Segment by city tier, income, age, access, use case or price point.
For a Blinkit or Zepto-style dark store, a stronger estimate begins with households within a short delivery radius, then filters for app access, grocery ordering behaviour, order frequency and basket value. The primary driver is local demand density, supported by assortment fit, rider availability, inventory turns and delivery promise. So what: market size is not national population - it is reachable, repeatable demand within a serviceable radius.
Step 4: Calculate Cleanly Under Pressure
Round numbers deliberately. Use 10%, 25%, one-third and half where possible. Say, "I will round for ease and keep the logic visible." That is better than struggling with false precision.
Step 5: Sanity-Check the Answer
A good guesstimate ends with a short audit. Ask: does the number fit people's spending power, industry capacity, comparable markets and replacement cycles?
Worked Example: Size Bengaluru's Monthly App-Based Laundry Market
Assume the interviewer asks: "Estimate the monthly revenue opportunity for app-based laundry services in Bengaluru." Treat the numbers below as interview assumptions, not factual claims.
A better candidate would add: "If adoption is 5% instead of 10%, the market halves to about ₹5.4 crore per month; if average order value is ₹400, it rises to about ₹14.4 crore. So the sensitive assumptions are adoption and order value."
How to Evaluate Your Guesstimate Quality
You cannot know the exact answer in the room, but you can judge whether your estimate is robust. Use these measures when practising.
Definitions You Should Be Able to Say in One Breath
- Guesstimate: A defensible numerical estimate built from assumptions when exact data is unavailable.
- Market sizing: Estimating the volume or value of a defined market over a defined period.
- Fermi problem: A problem solved by decomposing an unknown quantity into smaller estimable parts.
- TAM: Total addressable market - the full revenue opportunity if every potential customer is served.
- SAM: Serviceable available market - the part of TAM reachable with the current business model and geography.
- SOM: Serviceable obtainable market - the realistic share a company can capture under competitive constraints.
Case Study: Ather Energy and the Real Meaning of Market Size
Ather Energy showed why market sizing for EV scooters is not "all two-wheeler buyers" - it is the reachable premium urban segment with charging access, willingness to switch and daily commute use cases.
Situation: India has a very large two-wheeler market, but an electric scooter start-up cannot size its opportunity by taking a percentage of all petrol scooter and motorcycle buyers. The real market depends on urban commute patterns, charging confidence, upfront affordability, state policy, service access and trust in EV performance.
The move: Ather focused on a more specific serviceable market: urban consumers willing to pay for a premium electric scooter, supported by experience centres, connected vehicle software, financing options and the Ather Grid charging network. The primary driver was a focused premium urban EV proposition; supporting drivers included charging infrastructure, product reliability, brand trust, digital ownership experience and policy tailwinds.
Outcome or lesson: The strategic lesson is not that EV scooters win only because fuel is expensive. A practical market size must narrow from total two-wheelers to the segment that is reachable, chargeable, financeable and behaviourally ready to switch.
Interview takeaway: When sizing a market for any new-age category - EVs, quick commerce, healthtech, edtech or fintech - do not stop at TAM. Show TAM, then SAM, then SOM. That is how a business actually sees the opportunity.
How AI Changes Guesstimates & Market Sizing for Analytics Interviews
AI does not remove the need for structured estimation; it raises the bar. By 2026, strong candidates are expected to know how AI helps create better assumptions without blindly outsourcing the answer.
- Faster source discovery: Tools like Perplexity can surface public anchors such as annual reports, investor presentations, regulator releases and credible industry articles. The student still must judge reliability.
- Scenario modelling: ChatGPT or Claude can generate assumption trees, sensitivity tables and alternate top-down or bottom-up methods. This is useful for practice, but you must correct unrealistic assumptions.
- Natural-language analytics: AI copilots can convert a market sizing logic into spreadsheet formulas or Python snippets, helping analysts run low, base and high scenarios quickly.
Use NotebookLM before an analytics interview: upload the company annual report, investor deck and this lesson, then ask, "Generate five market sizing questions this company might ask, with assumption trees and sanity checks." Use the output to practise aloud - do not memorise it.
Interview Relevance
"Estimate the annual market size for electric scooters in urban India. Walk me through your assumptions and tell me which assumptions matter most."
Always narrate your assumptions before multiplying. A sentence like "I am using households rather than population because scooters are bought at household level" signals business maturity.
Common Mistake
The mistake: treating guesstimates as mental-math contests and rushing to a number. Why it costs candidates: the interviewer cannot see your segmentation, assumptions or business logic, so even a decent number feels accidental. One-line fix: spend the first 30 seconds defining scope and writing the equation before doing any arithmetic!
What to Revise Next
Once this framework is clear, strengthen the two skills that make it perform under pressure: fast arithmetic and structured diagnosis.