How do veterans structure a market sizing as a series of go/no-go gates with real data?

I keep seeing strong case performers treat market sizing like a series of decisions, not a wandering estimate. I’m trying to build that muscle: open cleanly, lock scope, drop one hard anchor, choose a build path, and add quick “go/no-go” gates so I don’t chase dead ends.

What I’m missing is a concrete, veteran-style checklist for those gates. For example, start with one public, defendable anchor (population, units, or spend), cap the number of multipliers before a sanity check, and force a second triangulation (capacity, share-of-wallet, or comparable company data) if the number feels off. I’m also curious what “must-have” sources you grab in a real interview—things you can cite broadly (e.g., census-level figures or a 10-K line item) without sounding like you’re guessing.

If you’ve done this in the wild: what are your specific gates and when do you pull the ripcord? Bonus if you can sketch a quick example (say, sizing U.S. boutique fitness memberships) to show the step-by-step moves and where you stop for a reality check.

What’s your go/no-go gate sequence and the one or two real-world anchors you rely on to keep the estimate credible under time pressure?

you’re overcomplicating it. pick one anchor you could defend in front of a cranky VP: people, units, or dollars from a boring public source. apply two clean multipliers max, then sanity check with a second lens (capacity, utilization, or a peer 10‑K). if it’s off by an order of magnitude, you blew a definition, not the math. stop apologizing for “rough” numbers—interviewers want logic, not fantasy decimals. cite census.gov, bls tables, or company filings and move on.

go/no‑go gates: 1) can you define the buyer in one sentence? no = stop. 2) price × penetration × frequency or units × replacement cycle—pick one path. 3) second check: capacity or share-of-wallet. 4) if you can’t name two primary drivers without peeking, you don’t understand the market, bail. time it: 90s scope, 4 min build, 1 min cross-check, 30s risks/levers. sounds clinical because it is. interviews aren’t TED talks.

love the gate idea. i always run long tho. any quick trick for picking the anchor fast without second‑guessing?

i tried a capacity check on coffee shops (seats × turns) and it actually cleaned up my math. is that too nerdy for a 10‑min mock?

for sources, is it ok to just say “census-level stats” if i can’t cite exact year? or do interviewers expect the number?

A practical gate sequence that travels well: define the market in one sentence (buyer, geography, product). Anchor with one public number—population cohort, installed base, or spend—stated as a round figure. Select a single build path (incidence × frequency × price, or units × replacement cycle × ASP). After two multipliers, pause for a cross-check using a distinct lens: capacity constraints, comparable company revenue scaled by share, or a plausible utilization bound. State driver sensitivities explicitly (e.g., penetration ±5pp changes TAM by ~X%). Close with a crisp headline estimate and one risk to assumptions. Example for boutique fitness: adult population bracket × realistic membership penetration × average monthly price × months; cross-check against studio capacity (classes/day × seats × occupancy × studios) to ensure you’re not exceeding physical throughput.

Love this approach! Your gate mindset is solid. Keep it simple, anchor early, sanity check once, and close confidently. You’ve got this!

I bombed a sizing once by stacking six assumptions before any reality check. Next mock, I kept it boring: defined the buyer, anchored on a 10‑K unit figure, then did price × attach rate. At minute five, I sanity‑checked with capacity (staffed installs per day) and found I was 2x high. I said it out loud, corrected it, and the interviewer literally nodded. The gates weren’t fancy, just spaced well so I could catch myself before the math ran away.

A defensible sequence under time pressure: define the market boundary tightly; use one public anchor (e.g., adult population ~260M or a disclosed installed base) rounded for speed; choose a single build (incidence × frequency × price) and cap multipliers to two before a cross-check. Cross-check using an orthogonal lens: capacity (units × utilization) or company revenue scaled by share to ensure the estimate’s within 0.5–2.0x. Verbalize sensitivity on the dominant driver and finalize with a concise range rather than a point estimate.