Level B Solved Skeletons - 5 Worked Guesstimate References
After Level A Quick Drills - 20 Timed Self-Attempts, the natural question is not "What was the exact answer?" but "Was my structure interview-grade?" Level B solved skeletons answer that question by showing the tree, assumption set, range, and sanity check for five common guesstimate prompts. In interviews, this matters because strong candidates are assessed on scope clarity, segmentation, assumption logic, and defensible ranges rather than one perfect final number.
- Level B solved skeletons are reference structures: they show the estimation tree and assumptions, while keeping the final answer as a defensible range.
- Do not grade your answer by checking the final number first; check scope, tree granularity, and sanity-checking before the math.
- The five worked references use different tree types: top-down, compound, bottom-up, replacement-cycle, and segmented user-intensity estimation.
- Ranges are not a weakness in guesstimates; they show that assumptions are approximate and that the answer can move within a reasonable band.
- Sanity checks convert raw arithmetic into interview confidence, such as kirana revenue checked against store count or WhatsApp messages checked against global daily volume.
- The reusable habit is to compare trees, assumptions, ranges, and checks - not to chase a single exact number.
Big Picture: What Level B Solved Skeletons Teach
Level B sits between timed Level A attempts and harder Level C compound drills. It is designed as a structure-first reference: each skeleton shows how to break the market or usage question into drivers, pick explainable assumptions, compute a range, and test whether the answer is directionally reasonable.
A Level B solved skeleton is a reference answer that shows the guesstimate tree, assumptions, calculation path, final range, and sanity check, without treating any one final number as the only correct answer.
The five references below cover the main patterns a candidate should recognize quickly.
How to Read a Level B Skeleton
Start with the approach line. Terms matter: TAM means total addressable market, or the full revenue opportunity being estimated; FMCG means fast-moving consumer goods, such as frequently purchased grocery and packaged consumption items; 2W means two-wheeler; and MAU means monthly active users, or users active in a month.
Then read the assumption table like an interviewer would. Each assumption should have a value and a reason. A strong answer is not just "Indian FMCG market is ~₹19 lakh crore"; it also says why that anchor is used, such as IBEF (US$220 bn), and then adds fresh produce plus unorganised staples separately when the target is total grocery plus FMCG.
Finally, compare the range and sanity check. The range tells the interviewer you understand uncertainty. The sanity check proves you are not blindly multiplying numbers.
Reference 1: Annual Revenue of All Kirana Stores in India
This is a top-down market sizing problem: begin with the total grocery plus FMCG total addressable market, then apply the kirana share. The source skeleton estimates Indian FMCG at ~₹19 lakh crore for FY26, adds ~₹16 lakh crore for fresh produce and unorganised staples, and reaches a total grocery plus FMCG TAM of ~₹35 lakh crore.
The calculation is: kirana revenue ≈ ₹35 lakh crore × 77% ≈ ₹27 lakh crore. The defensible range is ₹24 - 30 lakh crore annually. The sanity check is powerful because it uses a different route: ~1.3 cr kirana stores × ~₹20 L/yr each ≈ ₹26 L cr, which lands near the top-down estimate.
The interview nuance is that the kirana share is not a tiny residual. If modern trade plus e-commerce is still ~20 - 25%, then kiranas still carry most of grocery. A common mistake is to estimate only formal FMCG and forget fresh produce plus unorganised staples, which would understate the market.
Reference 2: Annual Market for After-School Tuition in Mid-Sized Indian Cities
This is a compound estimate: multiple drivers must be chained in sequence. The tree starts with mid-sized city population, narrows to school-going children, applies tuition penetration, and then multiplies by annual spend.
The midpoint calculation is: tuition spend ≈ 1.25 cr × ₹17,500 ≈ ₹22,000 crore. The range is ₹18,000 - 28,000 crore. The sanity check compares this with the total India coaching market of ~₹70,000 cr and a mid-sized city share of ~30%.
The practical interview use is to show segmentation discipline. If you jump directly from total city population to revenue, you skip the children share, paid tuition penetration, and annual ticket. The nuance is that the result depends heavily on penetration and annual spend, so a range is more credible than a single number.
Reference 3: Daily Petrol Sales in Mumbai
This is a bottom-up usage estimate by vehicle category. Instead of starting from total fuel market, the skeleton estimates litres consumed by two-wheelers and petrol cars, then adds buses, autos, and commercials.
The two-wheeler calculation is 35 L × 0.40 × 15 ÷ 45 = 4.7 L litres. The car calculation is 6 L × 0.50 × 30 ÷ 12 = 7.5 L litres. Adding buses, autos, and commercials contributes ≈ 2 L litres, giving total daily sales ≈ 14 L litres and a range of 12 - 18 L litres.
The sanity check uses retail distribution: ~700 retail pumps × ~20,000 L/day ≈ 14 L L. This is a good example of triangulation because the pump-based check is independent of the vehicle stock tree. The mistake to avoid is mixing vehicle stock with active usage as if every vehicle runs every day.
Reference 4: Annual Helmet Sales in India
This skeleton combines installed base, replacement demand, and new demand. The core logic is that annual helmet sales are not just linked to new two-wheeler sales; a large part comes from existing riders replacing helmets over time.
Replacement demand = 20 cr × 70% ÷ 3 = ~4.7 cr/year. New-vehicle demand = 1.9 cr × 1.5 = ~2.9 cr/year, covering rider plus partial pillion demand. The skeleton gives total demand ≈ 9.5 cr helmets/year and a range of 8 - 12 crore.
The interview lesson is to separate stock from flow. Stock is the existing base of two-wheelers on road; flow is the annual new two-wheeler sales and the annual replacement cycle. If you use only new 2W sold/year, you miss replacement demand from the existing base.
Reference 5: WhatsApp Messages Sent in India Per Day
This is a segmented user-intensity estimate. WhatsApp has India MAU of ~55 cr based on a Meta-disclosed broad band, and the skeleton splits users into heavy, medium, and light message senders.
The calculation is: heavy users generate 13.5 cr × 100 = 1,350 cr messages, medium users generate 27.5 cr × 30 = 825 cr messages, and light users generate 13.5 cr × 5 = 68 cr messages. Total ≈ 2,250 cr messages/day, or ≈ 22 billion messages/day, with a range of 18 - 28 billion.
The sanity check is external but still within the skeleton: global WhatsApp volume is ~100 bn/day, and India share is ~20 - 25%. This supports an India estimate around 22 billion messages/day. The nuance is that average messages per user can hide intensity differences, so segmentation is stronger than one flat average.
Worked Example: WhatsApp Messages as a Full Interview Reference
This worked example shows the Level B mindset: once the tree is correct, the interviewer can debate assumptions without breaking the structure. If the heavy-user message count changes, only that branch changes; the overall answer remains auditable.
Tree Comparison: Choosing the Right Estimation Pattern
The five skeletons are valuable because they are not the same tree repeated five times. The fastest way to improve is to recognize which pattern the prompt demands before writing numbers.
Structuring a Level B Solved Skeletons Interview Answer
"You have attempted a 15-minute guesstimate. How would you compare your answer with a Level B solved skeleton before looking at the final number?"
The number one way candidates get this wrong is by checking whether their final number matches the skeleton before checking the structure. In Level B, the scoring signal is the quality of the tree, assumptions, and sanity check.
The most frequent error is treating the skeleton as an answer key instead of a reference structure. That costs points because interviewers care less about one exact final number and more about whether your scope, tree, assumptions, range, and sanity check can survive discussion.
Conclusion
Level B solved skeletons train you to think like a structured estimator: define scope, choose the right tree, justify assumptions, express a range, and sanity-check with a second anchor. The final takeaway is simple: compare the reasoning before the result.