The Complete Consulting Case Interview

Prep Guide
Everything you need before you start practicing cases and before you sit for
interviews

How to use this guide. Read Parts 1–3 first to understand what a case is and how to think.
Then internalize the frameworks in Part 4 and the case-type playbooks in Part 5. Memorize
the numbers and math in Parts 6–7. Learn the business vocabulary in Part 8. Then and only
then start doing practice cases, using Parts 9–11 to refine delivery and behavioral answers.
The single biggest mistake candidates make is memorizing frameworks and skipping the
thinking. Structure beats frameworks. Logic beats memorization.

TABLE OF CONTENTS
1. What a case interview actually is (and what it tests)
2. The two formats: interviewer-led vs candidate-led
3. The universal case-solving process (the meta-approach)
4. The core frameworks (and how to build your own)
5. Case-type playbooks (profitability, market entry, pricing, M&A, growth, ops, etc.)
6. Guesstimates & market sizing — full method + numbers to memorize
7. Business math & mental math
8. The complete business terms glossary
9. Delivery: how to communicate during a case
10. The behavioral / fit interview
11. Practice plan, common mistakes, and red flags

PART 1 — WHAT A CASE INTERVIEW

ACTUALLY IS
A case interview is a simulation of a client problem. The interviewer plays the client (or the
engagement manager), gives you a business situation, and you have to structure the problem,
ask for the right data, do some analysis, and arrive at a recommendation — usually in 20–40
minutes.

Consulting firms use cases because the job is solving ambiguous business problems with
incomplete information under time pressure while communicating clearly to a client. The
case tests the job directly.

What is actually being evaluated

Interviewers are scoring you on a small number of dimensions. Know them cold, because
everything you do should serve one of them:

 Structure / problem-solving. Can you break a messy problem into clean, logical,
non-overlapping pieces? This is the #1 thing. A structured wrong answer beats an
unstructured right one.
 Business judgment / intuition. Do your ideas make commercial sense? Do you know
what drives profit, what a customer values, what a competitor would do?
 Quantitative ability. Can you set up and execute math cleanly, interpret numbers,
and not panic at arithmetic?
 Communication. Are you clear, concise, and easy to follow? Do you signpost?
Would a client trust you in a room?
 Creativity / synthesis. Can you generate ideas and, crucially, pull everything into a
crisp "so what" recommendation?
 Poise & coachability. Do you stay calm, take hints gracefully, and drive the case
without being rigid?

You are not being tested on whether you reach a specific "correct" answer. Most cases have
several defensible answers. You are tested on how you get there.

The mindset shift

Think of yourself as a partner solving a real problem, not a student answering a quiz. That
means:

 You lead. Don't wait to be spoon-fed. Propose a structure, state a hypothesis, drive
toward an answer.
 You are client-facing. Speak in plain language, be confident but not arrogant, and
always connect analysis to a business decision.
 You are hypothesis-driven. Form an early point of view and test it, rather than
boiling the ocean.
 You are comfortable with ambiguity. State your assumptions out loud and move
forward.

PART 2 — THE TWO CASE FORMATS

You must know which format you're in, because your behavior changes.

Interviewer-led (e.g., McKinsey style)

The interviewer drives. They ask you discrete questions in sequence: "How would you
structure this?" → "Here's some data, what do you make of it?" → "Now estimate X" →
"What's your recommendation?" You answer each question excellently, but you don't choose
the path. Depth per question matters most. Answer the exact question asked, be MECE, be
crisp.

Candidate-led (e.g., BCG, Bain, most others)

You drive the whole case. After the prompt, you lay out a structure, you decide which branch
to explore first, you ask for the data you need, and you steer to a recommendation.
Ownership and flow matter most. You must proactively ask "Can I get data on X?" and
narrate where you're going and why.

In practice most firms blend the two. The safe default: always structure first, always drive,
always narrate your logic, and adjust based on how much the interviewer is steering.

PART 3 — THE UNIVERSAL CASE-

SOLVING PROCESS
Almost every case follows the same five-beat rhythm. Master this rhythm and you can handle
any prompt, even one that fits no framework.

Step 0 — Listen and take notes (during the prompt)

Write down: the client (who they are, what industry, business model), the objective (what
does success look like — and get a number if possible: "grow profit by 20%," "decide yes/no
on entry"), and any constraints (timeline, budget, geography). Note figures exactly.

Step 1 — Play back & clarify the objective (30–60 seconds)

Repeat the problem in your own words to confirm you understood, then ask 2–4 sharp
clarifying questions. Good clarifiers:

 Objective: "When you say improve profitability, is there a specific target or

timeframe?"
 Business model: "How exactly does the client make money?"
 Scope: "Are we looking at one product/region or the whole company?"
 Success metric: "Is the goal profit, revenue, market share, or something else?"

Don't over-clarify (3–4 questions max). The goal is to remove ambiguity that would change
your structure, not to stall.

Step 2 — Structure the problem (the most important 60–90 seconds)

Ask for a moment: "Can I take about a minute to gather my thoughts?" Then build a
structure — a set of buckets (2–4 top-level, each with sub-points) that are MECE and
tailored to this problem. Draw it as an issue tree.

When you present it: give the headline first, then walk through each bucket, and end by
stating where you'd like to start and why (your hypothesis). Example: "I'd look at this
across three areas — the market, the company's economics, and the competitive/execution
risks. I'd like to start with the economics, because whether this is even profitable is the make-
or-break question."
Step 3 — Analyze (the bulk of the case)

Go bucket by bucket. For each: state what you want to investigate and why, ask for the
relevant data, do the math or interpret the chart, and — critically — say the "so what" after
every piece of analysis. Don't just compute; interpret. Update your hypothesis as evidence
comes in. Move on when a branch is exhausted; don't rabbit-hole.

Step 4 — Synthesize & recommend (the final 60–90 seconds)

When asked (or when you've gathered enough), deliver a top-down recommendation:

1. The answer / recommendation in one sentence ("Yes, enter the market" / "The profit
drop is driven by rising variable costs").
2. 2–3 supporting reasons from your analysis.
3. Risks / caveats to watch.
4. Next steps — what you'd analyze next.

This is the moment interviewers remember most. Lead with the answer. Be confident. Keep it
to ~45–60 seconds.

The four habits that run through every step

 MECE (see below) — keep your buckets clean.

 Hypothesis-driven — always have a current best guess and test it.
 Signposting — tell the interviewer where you are and where you're going ("I've
finished the cost side; now I'll look at revenue").
 "So what?" — end every analysis with its business implication.

MECE — the core principle

MECE = Mutually Exclusive, Collectively Exhaustive. Your buckets should not overlap
(mutually exclusive) and together should cover everything (collectively exhaustive). Profit =
Revenue − Cost is perfectly MECE. "Marketing, sales, and online channels" is not MECE
(online overlaps with sales/marketing). MECE is the quality bar for any structure you draw.

The issue tree

An issue tree is a diagram that breaks the problem into branches and sub-branches. It's the
visual form of MECE structuring. Two flavors:

 Factor tree (breaks something into its mathematical drivers): Profit → Revenue &
Cost → (Price × Volume) & (Fixed + Variable).
 Hypothesis tree (breaks a question into possible reasons): "Why did profit fall?" →
because revenue fell OR costs rose → each with sub-reasons.

Learn to draw one fast for any prompt. This single skill carries most of the interview.
PART 4 — THE CORE FRAMEWORKS
A warning before the toolkit: frameworks are starting points, not answers. Interviewers can
smell a memorized framework dumped on a problem it doesn't fit. The best candidates use
these as mental checklists to build a custom structure. Learn them, then learn to blend and
adapt them.

4.1 Profitability framework (the most important one)

Everything ultimately ties back to this. Profit = Revenue − Cost.

 Revenue = Price × Quantity (Volume).

o Volume can be broken into: number of customers × purchase frequency ×
units per purchase; or market size × market share.
 Cost = Fixed Costs + Variable Costs.
o Fixed costs don't change with volume: rent, salaries, equipment, insurance.
o Variable costs scale with each unit produced: raw materials, packaging,
shipping, sales commissions.

When profit falls, isolate which lever moved: Did price drop? Volume drop? Fixed costs rise?
Variable costs rise? Always split revenue and cost, then drill into the side that changed. Then
ask why (internal reasons like a new machine breaking down, vs. external reasons like a
competitor cutting prices or input prices rising).

4.2 The 3 C's (situation analysis)

A quick lens for "should we do X / what's going on in this business":

 Company — capabilities, cost structure, brand, financials, products, distribution.

 Customers — who they are, segments, needs, willingness to pay, size and growth of
segments.
 Competition — who else is in the market, their share, strengths, likely reactions.

Often extended to add Context (regulation, macro, technology).

4.3 The 4 P's (the marketing mix)

For product/marketing/go-to-market questions:

 Product — features, quality, range, branding.

 Price — pricing strategy and positioning.
 Place — distribution channels, coverage.
 Promotion — advertising, sales force, discounts, PR.

(Sometimes extended to 7 P's for services: + People, Process, Physical evidence.)

4.4 Porter's Five Forces (industry attractiveness)

Use to assess how profitable/attractive an industry is:

1. Threat of new entrants — how easy is it to enter? (barriers: capital, regulation,

brand, economies of scale).
2. Bargaining power of suppliers — few suppliers = they set terms.
3. Bargaining power of buyers — few large buyers = they squeeze prices.
4. Threat of substitutes — alternative products that meet the same need.
5. Competitive rivalry — intensity of competition among existing players.

High forces = low industry profitability. Great for market-entry and industry-analysis cases.

4.5 Value chain

The sequence of activities a company performs to deliver a product: Inbound logistics →

Operations → Outbound logistics → Marketing & Sales → Service, supported by
procurement, tech/R&D, HR, and infrastructure. Use it to locate where costs sit or where
value is added when diagnosing operations or cost problems.

4.6 The 3 C's for pricing / a simple pricing lens

Three ways to set price (see full pricing playbook in Part 5):

 Cost-based — cost + target margin.

 Competitor-based — benchmark against rivals/substitutes.
 Value-based — what the customer is willing to pay for the value delivered (usually
the most defensible).

4.7 BCG Growth-Share Matrix (portfolio)

Classifies business units on a 2×2 of market growth (high/low) vs relative market share
(high/low):

 Stars (high growth, high share) — invest.

 Cash Cows (low growth, high share) — milk for cash.
 Question Marks (high growth, low share) — decide: invest or exit.
 Dogs (low growth, low share) — divest/exit. Use for multi-product portfolio or
"where should we allocate resources" cases.

4.8 Ansoff Matrix (growth directions)

Four ways to grow, on a 2×2 of product (existing/new) × market (existing/new):

 Market Penetration — sell more existing products to existing markets (least risky).
 Market Development — existing products to new markets/geographies.
 Product Development — new products to existing customers.
 Diversification — new products to new markets (riskiest).

4.9 SWOT (quick internal/external scan)

Strengths, Weaknesses (internal) and Opportunities, Threats (external). Useful as a fast
situational scan, but too generic to be a primary case structure — use sparingly and only as a
supporting lens.

4.10 The 7 S's (organizational)

For org/change/post-merger integration cases: Strategy, Structure, Systems, Shared values,

Style, Staff, Skills. The hard S's (strategy, structure, systems) and soft S's (the rest) must be
aligned.

How to build your OWN structure (the pro move)

Don't reach for a canned framework first. Instead:

1. Anchor on the objective. What decision or number are we driving to?

2. Ask: what would have to be true for the answer to be yes/good? Those become
your buckets.
3. Make them MECE and tailored to the client's specifics (industry, business model,
the actual question).
4. Sanity check: does each bucket clearly help answer the core question? If not, cut it.

A bespoke three-bucket tree that fits the problem beats any textbook framework.

PART 5 — CASE-TYPE PLAYBOOKS

These are the recurring case archetypes. For each: how to recognize it, the structure to use,
the key drivers, and the "so what."

5.1 Profitability / declining profits

Recognize: "Profits are down," "margins are shrinking," "we're less profitable than
competitors." Structure: Profit = Revenue − Cost. Split both. Find which line moved and by
how much, then diagnose why.

 Revenue side: is it price or volume? Volume → is the whole market shrinking

(external) or is our share dropping (internal/competitive)? Price → did we cut, or did
mix shift to cheaper products?
 Cost side: fixed or variable? Which cost line specifically (raw materials, labor,
logistics, overhead)? Internal (inefficiency, a broken process) or external (input
inflation, new regulation)? Method: Always ask for the numbers to quantify the
change, then isolate the single biggest driver (an "80/20" mindset). So what: State the
root cause, then propose targeted fixes (raise price, cut a specific cost, win back
volume).

5.2 Market sizing / guesstimate

Recognize: "How many X are there / sold per year in Y?" (See Part 6 for the full method and
numbers.) Structure: Choose top-down (start from a large population, narrow with filters)
or bottom-up (build from a unit and scale up). State assumptions loudly, segment where it
matters, compute, then sanity-check the answer.

5.3 Market entry

Recognize: "Should client enter market/geography/segment X?" Structure (four questions):

1. Is the market attractive? Size, growth, profitability/margins, trends. (Use Five

Forces here.)
2. Can we win / do we have the right to play? Our capabilities, cost position, brand,
differentiation vs. incumbents. Competitive reaction.
3. How would we enter? Build organically, acquire, partner/JV, or license. Trade-offs
of speed vs. control vs. cost.
4. Do the economics work? Investment required, expected revenue and profit,
breakeven, ROI vs. our hurdle rate. So what: Yes/no, driven by attractiveness ×
ability-to-win × economics, plus the recommended entry mode and key risks.

5.4 Pricing
Recognize: "How should we price this new product?" "Are we pricing right?" Structure —
evaluate all three lenses, then choose:

 Cost-plus: floor = your cost; add target margin. Simple but ignores customer value.
 Competitor/market-based: what do rivals and substitutes charge? Are we premium,
parity, or discount positioned?
 Value-based: quantify the economic value to the customer (money they save or make
by using it) and capture a share of it. Usually gives the highest defensible price. Also
consider: price elasticity (how volume responds to price), pricing objective
(maximize profit vs. gain share vs. skim early adopters vs. penetrate), and
psychological/segmented pricing. So what: Recommend a price with a range and
rationale, tied to the objective.

5.5 M&A / acquisition / "should we buy this company"

Recognize: "Should our client acquire target T?" Structure:

1. Strategic rationale — why buy? (Growth, market share, new capability, geography,
eliminate a competitor, vertical integration.)
2. Is the target attractive on its own? Market, financials, growth, management.
3. Synergies — the heart of most M&A cases. Revenue synergies (cross-sell, wider
distribution, pricing power) and cost synergies (economies of scale, cutting duplicate
functions, better procurement). Be skeptical — synergies are usually overestimated.
4. Valuation & price — is the asking price justified by projected cash flows +
synergies? (NPV, multiples.)
5. Risks & integration — cultural fit, integration cost/complexity, regulatory approval,
financing. So what: Buy/don't buy, at what price, and the biggest integration risk.
5.6 Growth / "how do we grow revenue"
Recognize: "Client wants to grow by X%," "revenue has plateaued." Structure (use Ansoff-
style logic):

 Grow existing products in existing markets (penetration): more customers, more

frequency, larger basket, win share, raise price.
 New geographies/segments with existing products.
 New products to existing customers.
 New products + new markets (diversification) or inorganic (M&A/partnership).
Prioritize by size of prize, feasibility, and fit with capabilities. So what: The 1–2
highest-value, most-feasible growth levers, with a rough sizing of each.

5.7 Operations / cost reduction / process improvement

Recognize: "Costs too high," "plant is inefficient," "long lead times." Structure: Walk the
value chain / process end to end, find where cost or time concentrates, split each cost into
fixed/variable and driver, and target the biggest, most-addressable pool. Look for: capacity
utilization, throughput bottlenecks, waste/scrap, procurement, labor productivity, automation.
So what: The specific cost pools to attack and the expected savings.

5.8 New product / product launch

Structure: blend market sizing (demand), the 4 P's (go-to-market), competitive response, and
the economics (unit economics, breakeven, investment). Decide go/no-go and how to launch.

5.9 Competitive response

Recognize: "A competitor just cut prices / launched a product / entered our market. What do
we do?" Structure:

1. Understand the threat — what exactly did they do, why, how big is the impact on us
(quantify lost volume/margin)?
2. Understand ourselves & customers — how loyal are customers, what do they value,
can we differentiate?
3. Options — match/undercut price, differentiate (features, service, brand), bundle,
target a different segment, do nothing, or exit. Consider the competitor's likely
counter-move (game theory). So what: The response that best protects long-run
profit, not just short-run volume.

5.10 Turnaround / declining industry

Combine profitability diagnosis with strategic options: fix the core (cost + revenue),
reposition, divest weak units (BCG dogs), or exit. Assess whether the decline is cyclical or
structural.

5.11 Others you may see

  Make vs. buy / outsourcing — compare total cost, control, quality, and strategic
importance.
 Capacity expansion / build a new plant — demand sizing + investment economics
(NPV, payback).
 Private equity / investment screen — is this a good asset to buy and can we improve
it and exit at a profit? (market + company + value-creation plan + returns.)
 Bank/insurance/airline/telecom-specific — same first principles, different
economics (e.g., load factor for airlines, ARPU/churn for telecom).

PART 6 — GUESSTIMATES & MARKET

SIZING (with numbers to memorize)
Guesstimates (a.k.a. estimation or market-sizing questions) ask you to estimate a number you
can't look up — "How many cups of tea are sold in Delhi per day?" or "What's the market
size of air conditioners in India?" They test structured thinking under uncertainty, not trivia.
The number matters far less than the method.

6.1 The two approaches

Top-down

Start from a big known number (a population) and narrow it with a chain of
percentages/filters down to your answer.

Example — smartphones sold per year in India: Population 1.4B → ~300M households →
households that can afford smartphones (~60%) → phones per such household (~2.5) →
divide by replacement cycle (~3 years) → annual sales. Add new buyers.

Bottom-up

Start from a single unit (one store, one person, one machine) and scale up.

Example — coffee shop daily revenue: seats × turns per day × occupancy × avg spend →
daily revenue → × 365.

Rule of thumb: use top-down when a clean population anchor exists (people, households).
Use bottom-up when you can reason from a repeatable unit (a shop, a plane, a household's
consumption). When possible, do one and sanity-check with the other.

6.2 The 5-step method

1. Clarify & scope. Units? Geography? Per day or per year? New sales or installed
base? "By 'market size' do you mean revenue or units?"
2. Choose approach (top-down / bottom-up) and state it out loud.
 3. Build the equation and segment where segments behave very differently (urban vs.
rural, income tiers, age groups). Don't over-segment — segment only where it
changes the answer.
4. Plug in round numbers and compute. Use clean figures; you can refine later. Keep
units consistent.
5. Sanity-check the answer. Is the order of magnitude believable? Cross-check against
a known figure ("that implies every person buys 5/year — plausible?"). State the final
number clearly with your key assumptions.

6.3 KEY NUMBERS TO MEMORIZE

Round, defensible figures you can pull instantly. Interviewers care about reasonable
assumptions, not precision.

India — demographics

Figure Value to use

Total population ~1.4 billion (140 crore)
Number of households ~300 million
Avg. household size ~4–4.5 people
Urban : Rural split ~35% : 65%
Age 0–14 ~25%
Age 15–64 (working age) ~65–67%
Age 65+ ~7%
Median age ~28–29 years
Male : Female ~52% : 48%
Life expectancy ~70 years
Literacy rate ~77%
Working population (employed) ~500 million
Smartphone/internet users ~750–800 million

India — income segmentation (rough, for affordability filters)

Segment ~Share of population

High income / rich ~5%
Upper-middle ~15%
Lower-middle ~30%
Low income / poor ~50%

India — economy & geography

Figure Value to use

GDP ~$3.5 trillion
GDP growth ~6–7% per year
Per-capita income ~$2,500/year
Tier-1 / metro cities ~8 (Delhi, Mumbai, Bengaluru, Hyderabad, Chennai, Kolkata,
 Figure Value to use
Pune, Ahmedabad)
Cities with 1M+ people ~50
Metro population (a big
~10–20 million
metro)

World

Figure Value to use

World population ~8 billion
China ~1.4 billion
India ~1.4 billion
USA ~335 million
World GDP ~$105 trillion
USA GDP ~$28 trillion

Time & conversion (extremely useful)

Figure Value
Days in a year 365
Weeks in a year 52
Hours in a year ~8,760
Working days / year ~250
Working days / month ~22
Hours in a working day 8
1 lakh 100,000 (10⁵)
1 crore 10 million (10⁷)
1 million 10 lakh (10⁶)
1 billion 100 crore (10⁹)

Handy consumption/asset benchmarks (approximate, for reasoning)

 Life cycles / replacement: smartphone ~2–3 yrs, laptop ~4–5 yrs, car ~8–10 yrs, TV
~7–8 yrs, refrigerator ~10 yrs, mattress ~7–8 yrs, tyres ~3–4 yrs.
 Ownership logic: 1 phone per adult; ~1 car / TV / fridge per (owning) household; 1
water bottle per person per day, etc. — build these from first principles, don't just
memorize.

6.4 Segmentation dimensions (your menu of "filters")

When narrowing a population, segment by whichever matters: geography (urban/rural,
metro/tier-2/tier-3), income (affordability), age, gender, household vs. individual (some
goods are per-household: fridge, car; others per-person: phone, toothbrush), usage/occasion,
frequency, and B2B vs. B2C.

6.5 Two fully worked examples

Example A (top-down): Number of smartphones sold in India per year

1. Population ≈ 1.4B → households ≈ 300M (avg ~4.5/hh), but phones are per-person,
so work with people.
2. Filter to people who own smartphones: exclude very young/old and lowest-income →
say ~55% of 1.4B ≈ ~770M smartphone users (matches the memorized ~750–800M
— good sign).
3. Replacement demand: average replacement cycle ~3 years → 770M ÷ 3 ≈
~257M/year.
4. New users: market still growing; add new adopters, say ~30–40M/year.
5. Total ≈ ~290–300M smartphones/year.
6. Sanity check: ~300M on a base of ~770M users implies replacing roughly every ~2.5
yrs including new buyers — reasonable.

Example B (bottom-up): Daily revenue of a coffee shop in a mall

1. Seats ≈ 30. Operating hours ≈ 12. Average customer stays ~45 min → each seat turns
~1.3×/hour → ~16 turns/seat/day.
2. Occupancy ≈ 60% average → effective customers ≈ 30 seats × 16 × 0.6 ≈ ~290
customers/day.
3. Average spend ≈ ₹250.
4. Daily revenue ≈ 290 × ₹250 ≈ ₹72,000/day → ~₹2.6M/month → ~₹31M/year.
5. Sanity check: ~290 customers over 12 hours ≈ 24/hour ≈ one every 2–3 minutes —
busy but plausible for a mall café.

6.6 Guesstimate do's and don'ts

 Do state your approach and assumptions before computing.
 Do use round numbers and keep the math clean.
 Do sanity-check the order of magnitude at the end.
 Don't obsess over precision or hidden decimals.
 Don't over-segment — each segment must earn its place.
 Don't go silent doing mental math; narrate.

PART 7 — BUSINESS MATH & MENTAL

MATH
You must do arithmetic out loud, cleanly, and without a calculator. Slow, error-free math
beats fast, sloppy math. Interviewers forgive a pause; they don't forgive a wrong number
stated confidently.

7.1 Techniques that save you

 Handle big numbers with scientific-notation logic. Strip zeros, multiply the
significant digits, then re-attach powers of ten. E.g., 300M × 250 = (3×10⁸)(2.5×10²) =
 7.5×10¹⁰ = ₹75 billion. Track your zeros carefully — this is where most errors
happen.
 Round early, correct later. Use 1.4B ≈ 1.4×10⁹; treat 22% as ~20% for a first pass,
then adjust.
 Percentages: x% of y = y% of x (16% of 25 = 25% of 16 = 4). To grow by 20%,
multiply by 1.2. To find % change: (new − old) / old.
 Fractions ↔ percentages (memorize): 1/2=50%, 1/3≈33%, 1/4=25%, 1/5=20%,
1/6≈17%, 1/7≈14%, 1/8=12.5%, 1/9≈11%, 1/10=10%.
 Growth over time — Rule of 72: years to double ≈ 72 ÷ (growth rate %). At 8%/yr,
doubles in ~9 years. At 6%, ~12 years.
 Compounding vs. simple: for quick estimates, compounding at r% for n years ≈
multiply by (1+r)ⁿ; for small r and n you can approximate total growth ≈ n×r%.
 Weighted averages for blended segments: overall = Σ(segment share × segment
value).
 Breakeven volume = Fixed Costs ÷ (Price − Variable cost per unit) = Fixed Costs
÷ contribution margin per unit.

7.2 The formulas you should never fumble

Concept Formula
Profit Revenue − Cost
Revenue Price × Quantity
Gross margin (Revenue − COGS) ÷ Revenue
Contribution margin (per unit) Price − Variable cost per unit
Breakeven quantity Fixed cost ÷ contribution margin per unit
Market share Our sales ÷ total market sales
ROI (Gain − Cost of investment) ÷ Cost of investment
Payback period Investment ÷ annual cash inflow
CAGR (End ÷ Start)^(1/years) − 1
% change (New − Old) ÷ Old

7.3 Presenting numbers well

 Say the units and the "so what": not "75 billion," but "about ₹75 billion in annual
revenue — which is small relative to the ₹500 billion market, so we'd have ~15%
share."
 Write your working down so you (and the interviewer) can follow it.
 If you get a weird number, say so and re-check — catching your own error scores
points.

PART 8 — THE COMPLETE BUSINESS

TERMS GLOSSARY
You cannot structure a case without the vocabulary of business. Learn these cold — many
cases hinge on understanding one of these concepts.
8.1 Costs & profitability
 Fixed costs — costs that don't vary with output (rent, salaries, machinery, insurance).
Spread over more units as volume rises (→ economies of scale).
 Variable costs — costs that rise with each unit (raw materials, packaging, shipping,
per-unit labor, sales commission).
 COGS (Cost of Goods Sold) — direct costs of producing what you sell (materials +
direct labor).
 Overheads / SG&A — Selling, General & Administrative expenses: indirect costs
not tied to a single unit (admin, marketing, rent, HQ).
 Contribution margin — Price − variable cost per unit; what each unit "contributes"
toward covering fixed costs and profit.
 Gross profit / gross margin — Revenue − COGS (and as a %). Measures core
production profitability.
 Operating profit / EBIT — Earnings Before Interest and Taxes; profit from core
operations.
 EBITDA — Earnings Before Interest, Taxes, Depreciation & Amortization; a proxy
for operating cash generation, used to compare companies.
 Net profit / net margin — the bottom line after all costs, interest, and taxes (and as a
% of revenue).
 Break-even point — the volume (or revenue) at which total revenue = total cost;
profit = 0.
 Economies of scale — per-unit cost falls as volume rises (fixed costs spread out, bulk
buying, specialization).
 Economies of scope — cost savings from producing a range of products together
(shared inputs/channels).
 Sunk cost — money already spent and unrecoverable; should be ignored in forward-
looking decisions.
 Opportunity cost — the value of the next-best alternative foregone.
 Marginal cost / marginal revenue — the cost/revenue of producing one more unit;
profit is maximized where they're equal.

8.2 Financial statements & metrics

 Revenue / top line — total sales before any costs.
 Bottom line — net profit.
 CapEx (Capital Expenditure) — spending on long-term assets (factories,
equipment); shows up on the balance sheet and is depreciated over time.
 OpEx (Operating Expenditure) — day-to-day running costs, expensed immediately.
 Depreciation / Amortization — spreading the cost of a tangible (depreciation) or
intangible (amortization) asset over its useful life.
 Working capital — current assets − current liabilities; cash tied up in day-to-day
operations (inventory + receivables − payables).
 Cash flow — actual cash moving in/out (different from profit, which includes non-
cash items). "Cash is king."
 Free cash flow — cash left after operating costs and CapEx; what's available to
investors.
 Assets / Liabilities / Equity — what you own / what you owe / owners' stake (Assets
= Liabilities + Equity).
  P&L (Profit & Loss) / Income statement — revenue, costs, and profit over a period.
 Balance sheet — snapshot of assets, liabilities, equity at a point in time.

8.3 Returns & valuation

 ROI (Return on Investment) — (gain − cost) ÷ cost. General profitability of an
investment.
 ROCE (Return on Capital Employed) — operating profit ÷ capital employed; how
efficiently capital generates profit.
 ROE / ROA — return on equity / on assets.
 Payback period — time to recover an investment from its cash inflows. Shorter =
less risky.
 NPV (Net Present Value) — sum of future cash flows discounted to today minus the
initial investment. Positive NPV = value-creating. Reflects the time value of money
(a rupee today is worth more than a rupee tomorrow).
 Discount rate / cost of capital / WACC — the rate used to discount future cash
flows; reflects risk and the return investors require. WACC = Weighted Average Cost
of Capital (blended cost of debt and equity).
 IRR (Internal Rate of Return) — the discount rate at which NPV = 0; compared
against the hurdle rate.
 Hurdle rate — the minimum acceptable return for an investment to go ahead.
 Valuation multiples — quick valuation shortcuts: P/E (price ÷ earnings),
EV/EBITDA (enterprise value ÷ EBITDA). Used to value companies relative to
peers.
 Enterprise Value (EV) — market value of equity + debt − cash; the "whole
business" value.

8.4 Customers, marketing & growth

 Market size (TAM / SAM / SOM) — TAM = Total Addressable Market (everyone
who could ever buy); SAM = Serviceable Addressable Market (the part you can
realistically serve); SOM = Serviceable Obtainable Market (the share you can
actually capture).
 Market share — your sales ÷ total market sales.
 Market penetration — % of the potential market that currently buys the product.
 Segmentation — dividing customers into groups with similar needs/behavior (by
demographics, geography, behavior, needs).
 Targeting & positioning — choosing which segments to serve and how to occupy a
distinct place in customers' minds.
 Value proposition — the specific benefit/value a product offers a customer.
 CAC (Customer Acquisition Cost) — total sales+marketing spend ÷ new customers
acquired.
 LTV / CLV (Customer Lifetime Value) — total profit expected from a customer
over the relationship. Healthy businesses need LTV > CAC (rule of thumb ~3×).
 Churn rate — % of customers lost per period. Its inverse is retention.
 ARPU (Average Revenue Per User) — revenue ÷ number of users; common in
telecom/subscription.
 Conversion rate — % of prospects who become customers (or visitors who buy).
  Funnel — the stages from awareness → consideration → purchase → loyalty; each
stage loses some people.
 Price elasticity of demand — how much quantity demanded changes when price
changes. Elastic = volume very sensitive to price (cut price → big volume gain);
inelastic = volume barely moves (can raise price with little volume loss).
 Willingness to pay (WTP) — the maximum price a customer will accept.
 Cannibalization — a new product stealing sales from your own existing products.
 Cross-sell / up-sell — selling additional / higher-value products to existing
customers.

8.5 Strategy & competition

 Competitive advantage / moat — a durable reason customers choose you and rivals
can't easily copy (brand, cost, network effects, switching costs, IP, scale).
 Differentiation — competing on unique value (quality, brand, features) rather than
price.
 Cost leadership — competing by being the lowest-cost producer.
 Barriers to entry — obstacles that keep new competitors out (capital, regulation,
brand, patents, economies of scale).
 Switching costs — the cost/hassle for a customer to move to a competitor; high
switching costs lock customers in.
 Network effects — the product gets more valuable as more people use it
(marketplaces, social networks).
 First-mover advantage — benefits of being first (brand, learning curve, locking up
supply/customers). Fast-follower can also win by learning from the pioneer's
mistakes.
 Vertical integration — owning more of your supply chain (upstream = suppliers,
downstream = distribution/retail).
 Horizontal integration — acquiring competitors at the same value-chain stage.
 Synergy — the "1+1=3" value from combining two businesses (revenue synergies +
cost synergies). Usually overestimated — be skeptical.
 Commoditization — when products become undifferentiated and compete only on
price.
 Value chain — the linked activities that create and deliver a product (see Part 4.5).
 Core competency — what a company does distinctively well.

8.6 Operations & supply chain

 Supply chain — the end-to-end flow from raw materials → production →
distribution → customer.
 Inventory turnover — how many times inventory is sold and replaced per period;
higher = more efficient.
 Capacity utilization — actual output ÷ maximum possible output. Low utilization =
wasted fixed cost.
 Throughput — the rate of production/output through a process.
 Bottleneck — the slowest step that limits the whole process's output.
 Lead time — total time from order to delivery.
 Economies of scale in ops — bigger runs lower per-unit cost.
  Utilization / load factor — industry-specific efficiency metrics (e.g., airline load
factor = seats filled ÷ seats available; hotel occupancy rate).
 Just-in-time (JIT) — minimizing inventory by producing/ordering only as needed.

8.7 Macro & context

 GDP — total value of goods/services a country produces; a measure of economic size
and growth.
 Inflation — general rise in prices; erodes purchasing power and raises input costs.
 Regulation — government rules that can create barriers, costs, or opportunities.
 Fragmented vs. consolidated market — many small players vs. a few large ones;
consolidation is often a strategic opportunity.
 B2B vs. B2C — selling to businesses vs. to consumers; different buying behavior,
cycle length, and economics.
 Recurring vs. one-off revenue — subscriptions/repeat purchases (predictable, high-
value) vs. single sales.

PART 9 — DELIVERY: HOW TO

COMMUNICATE DURING A CASE
Two candidates with identical analysis get different scores based purely on delivery. This is
coachable.

9.1 Communicate top-down (the Pyramid Principle)

Always answer/headline first, then support. "My recommendation is to enter, for three
reasons: A, B, C." Not a slow build-up to a buried conclusion. Clients (and interviewers)
want the answer, then the logic.

9.2 Signpost constantly

Tell them the map before you walk it, and announce each turn:

 "I'll look at this in three parts — first X, then Y, then Z."

 "I've finished the cost side. Now I'll move to revenue."
 "That leads me to think it's a volume problem. Let me confirm with the data."

9.3 Think out loud — but organized

Silence makes interviewers nervous; rambling loses them. Narrate your logic in structured
chunks. When you need to compute or think, ask for a moment: "Give me a few seconds to
work through this math." Then share the result and its implication.

9.4 Drive the case

Especially in candidate-led cases: proactively ask for the data you need ("Could I see the cost
breakdown?"), decide where to go next, and keep momentum. Don't wait to be led.

9.5 Be MECE and "so what" every time

After each analysis, deliver the business implication before moving on. Numbers without
interpretation are worthless.

9.6 Handle data & exhibits well

When handed a chart or table: (1) take 15–20 seconds to read the title, axes, and units before
speaking; (2) state what the exhibit shows; (3) connect it to your hypothesis; (4) state the "so
what." Don't just describe the chart — interpret it.

9.7 Take hints gracefully

If the interviewer nudges ("Have you considered costs?"), that's a gift, not a trap. Incorporate
it smoothly: "Good point — let me factor that in." Rigidity and defensiveness score badly;
coachability scores well.

9.8 Stay calm and composed

If you get stuck: restate the objective, return to your structure, and pick the next logical
branch. It's fine to say "Let me step back and re-anchor on what we're solving for."
Composure under pressure is itself part of the evaluation.

9.9 Manage the clock

Don't rabbit-hole on one interesting branch. Keep an eye on covering the whole structure and
leaving time for a crisp recommendation.

PART 10 — THE BEHAVIORAL / FIT

INTERVIEW
Cases are usually paired with a fit/behavioral portion. Firms want to know you're someone
clients trust and colleagues enjoy. Don't neglect this — strong candidates are rejected on
weak fit answers.

10.1 Use a story structure (STAR / PARADE)

 STAR: Situation → Task → Action → Result.

 PARADE: Problem → Anticipated consequence → Role → Action → Decision-
making rationale → End result. Keep it tight, quantify the result, and make your
individual contribution clear ("I" not just "we").
10.2 Prepare stories for these themes (have 4–6 flexible stories)

 Leadership — a time you led a team/initiative.

 Impact / achievement — your proudest accomplishment, with measurable results.
 Overcoming a challenge / failure — what went wrong, what you did, what you
learned.
 Conflict / difficult person — resolving disagreement.
 Influencing without authority — persuading peers/seniors.
 Working under pressure / ambiguity.
 Teamwork — a time you were a strong team player. Reuse and reshape the same
core stories across questions.

10.3 The classic questions — and how to answer

 "Walk me through your resume / tell me about yourself." A 60–90 second

narrative: a through-line connecting your experiences to why consulting, why now.
Not a chronological list.
 "Why consulting?" Steepest learning curve, exposure to varied industries and
problems, working with smart people, real impact on important decisions. Make it
personal and specific, not generic.
 "Why this firm?" Do your homework — cite specific practices, values, culture,
people you've spoken to, or work they're known for. Show you're choosing them, not
just "a consulting firm."
 "Why should we hire you?" Map your strengths (analytical, structured, leadership,
communication) to the role with evidence.
 "What's your greatest weakness?" A real, non-fatal weakness + concrete steps
you're taking to improve. Avoid clichés ("I work too hard").
 "Tell me about a time you failed." Own it honestly, focus on the lesson and change,
don't blame others.

10.4 Questions to ask them

Always have 2–3 thoughtful questions ready — about the work, the team, career path, or the
interviewer's own experience. It signals genuine interest.

PART 11 — PRACTICE PLAN,

COMMON MISTAKES & RED FLAGS
11.1 How to practice (this matters more than reading)

1. Learn the theory first (this guide). Don't practice on top of a shaky foundation.
2. Do cases out loud, ideally with a partner who plays interviewer. Solo practice can't
replicate the pressure or the back-and-forth. Aim for 30–50+ live cases before real
interviews.
3. Alternate roles — interviewing others teaches you what good looks like.
 4. Record and review — note where you lost structure, fumbled math, or forgot the "so
what."
5. Drill weaknesses separately — do 20 guesstimates in a row if estimation is weak; do
timed mental-math sets daily.
6. Simulate real conditions — timed, dressed, no notes-cramming mid-case.
7. Keep an error log and review it before each session.

11.2 A 4–6 week ramp (adjust to your timeline)

 Week 1: Absorb this guide. Memorize frameworks, formulas, and the guesstimate
numbers. Do 5 easy cases to get the feel.
 Week 2: One case type per day (profitability, market entry, pricing…). Drill
guesstimates and mental math daily.
 Week 3: Mixed live cases with partners; start recording. Begin behavioral story-
building.
 Week 4: Full mock interviews (case + fit) under real conditions. Polish delivery and
recommendations.
 Weeks 5–6 (if available): Firm-specific practice, harder cases, refine weak spots,
mock with people at target firms.

11.3 The most common mistakes (avoid these)

 Dumping a memorized framework that doesn't fit the problem. Always tailor.
 Jumping into analysis without structuring first.
 Not being MECE — overlapping or incomplete buckets.
 Doing math silently and going dark.
 Forgetting the "so what" — computing without interpreting.
 Not driving (in candidate-led cases) — waiting to be led.
 Boiling the ocean — no prioritization, no hypothesis.
 Ignoring the objective — solving a different problem than the one asked.
 Weak recommendation — trailing off instead of a crisp, confident, top-down close.
 Being rigid — not taking the interviewer's hints.
 Panicking on arithmetic — losing composure over a number.
 Neglecting the fit interview.

11.4 What a strong candidate looks like (the bar to hit)

 Opens with a sharp playback and a couple of pointed clarifiers.

 Presents a clean, MECE, tailored structure with a clear starting hypothesis.
 Drives the case, asking for the right data at the right time.
 Does math cleanly and out loud, interpreting every result.
 Signposts throughout — the interviewer is never lost.
 Closes with a confident, top-down recommendation: answer → reasons → risks →
next steps.
 Stays calm, warm, and coachable throughout.

FINAL WORD
Frameworks are scaffolding, not the building. The candidates who succeed aren't the ones
who memorized the most frameworks — they're the ones who think clearly, structure
ruthlessly, do clean math, and communicate like someone a client would trust in the
room. Use this guide to build the foundation, then get to the real work: doing cases, out
loud, over and over.

Good luck.