I’ve been struggling with market-sizing prompts in case interviews — they always feel like a mess of assumptions under a time limit. After trying top-down and bottom-up approaches, I landed on a 3-part skeleton I run every time: define the target population quickly, pick 1-2 realistic adoption/penetration anchors, and sanity-check with a comparable benchmark. I couldn’t find a single canonical template in the thread, so I’m curious: what quick checks do you run to keep estimates defensible under time pressure?
yeah, everyone wants a magic template. i use that 3-part thing you mentioned but the real trick is shutting up and doing the math — few people actually choose anchors that could survive a 30-second challenge from an associate. pick conservative uptake, round audibly, and always state why you dropped a number. people love ‘market potential’ until you ask them to justify a 20% adoption rate. works every time, unless you’re winging it.
- i try pick 2 quick benchmarks and state assumptions. then i do a fast back-of-envelope check. helps me not freak out. sometimes i typo numbers lol
Start by anchoring the definition: be explicit about who counts in your TAM (geography, customer segment, product scope). Choose one primary approach—top-down for speed, bottom-up if you can define unit economics—and state two simple assumptions with justifications (comparable market penetration, device ownership, or incumbents’ share). Always end with a one-line sanity check: compare your result to a reasonable external benchmark or known market. That short script signals structure and defensibility under time pressure. Which of those anchors do you find hardest to defend in interviews?
- love that 3-part skeleton! keep practising it in timed drills and you’ll nail it. trust the process!
I remember bombing my first product-sizing — I rambled about users without defining which users mattered. After one blunt mock from a former PM, I started always saying: “scope = X, adoption anchor = Y, benchmark = Z.” That short sentence calmed the interviewer and me. I still fumble numbers sometimes, but stating the anchors early buys you grace. What’s one anchor you always find yourself falling back on?
When I standardized my TAM approach, I tracked three checks: population size (census or mobile MAU), plausible penetration rate (0.1–5% for new consumer apps in year one, 10–30% mature), and ARPU or unit revenue. Running those through a quick sensitivity (low/medium/high) reduced wild estimates by ~40% in mocks. If you can cite a comparable market or a device adoption stat, your estimate becomes much easier to defend. Which of those inputs do you struggle to source quickly?