Anatomy of a Profitability Case: A Full Walkthrough
Reading about frameworks is one thing. Watching a partner-level candidate work a case from prompt to recommendation is another. A complete walkthrough of a coffee chain margin decline — including the moves an interviewer would actually grade.
Reading about frameworks teaches you the buckets. Watching a case played out turn by turn teaches you how the buckets actually work in real time — and where strong candidates diverge from average ones. This is a complete walkthrough of a profitability case at the difficulty level of an MBB round-2 interview.
The prompt
Setup: Our client is BrewHouse, a US-based chain of ~600 specialty coffee shops with revenue of ~$420M. Over the last 18 months their EBITDA margin has dropped from 17% to 11%. Same-store revenue has been flat.
Question: What is driving the margin decline, and what would you recommend?
Inflection 1: Clarification (60–90 seconds)
The candidate's first move is to clarify scope. Strong candidates ask 2–4 specific questions; weak candidates either skip clarification or ask vague questions ("can you tell me more about the company"). For this prompt the high-value clarifications are:
- "You said same-store revenue is flat — has the store count grown over those 18 months, or is the network stable?"
- "Is the margin decline uniform across stores or concentrated in a subset?"
- "Are we benchmarking the 17%→11% decline against industry peers, or is this BrewHouse-specific?"
For this case, the interviewer responds: store count has grown from 540 to 605 over the period, the decline appears across most stores, and peer chains have seen smaller (1–2 point) declines.
Two of three answers are informative. Store growth + flat same-store revenue means new stores are not yet performing, which is a separate margin pressure. Industry peers seeing smaller declines means there is an industry-wide cost headwind plus a BrewHouse-specific issue. Strong candidates immediately note both as parallel hypotheses.
Inflection 2: Structure (60 seconds of silence, then deliver)
Take 60 seconds. Write your structure on paper, top-down. Then deliver out loud, one branch at a time. Here is what a partner-level structure looks like for this case:
"I see three drivers I'd want to test: First, revenue per store — has price, mix, or volume per visit declined? Second, variable cost per drink — coffee bean cost, packaging, dairy, labor per cup. Third, fixed cost allocation — new-store buildout, headquarters overhead, underperforming new stores dragging the average. I'd start with revenue mix and cost-of-goods, since you mentioned peers are seeing smaller declines, suggesting an input-cost shock plus a BrewHouse-specific revenue mix issue."
Notice the candidate (a) names three branches, (b) decomposes one of them, (c) prioritizes the first branch with reasoning tied back to the clarification. This is the structure-with-a- point-of-view that interviewers grade as "partner-track." A weaker candidate stops at "let me look at revenue and cost," which sounds structured but contains zero new information.
Inflection 3: First drilldown — revenue mix
Interviewer: "Good. Let's start with revenue mix. Here is the data."
2 years ago: Specialty coffee 60%, brewed coffee 22%, food 12%, merchandise 6%
Today: Specialty coffee 48%, brewed coffee 27%, food 19%, merchandise 6%
Per-unit gross margin: Specialty coffee 76%, brewed coffee 70%, food 38%, merchandise 55%
Strong candidates do two things here: (1) immediately compute the blended margin shift, (2) identify the mix story.
Quick math:
- Old blended GM: 0.60 × 76 + 0.22 × 70 + 0.12 × 38 + 0.06 × 55 = 45.6 + 15.4 + 4.6 + 3.3 ≈ 68.9%
- New blended GM: 0.48 × 76 + 0.27 × 70 + 0.19 × 38 + 0.06 × 55 = 36.5 + 18.9 + 7.2 + 3.3 ≈ 65.9%
- Mix-driven gross margin decline: ~3 percentage points.
Out loud: "On the data: blended gross margin moved from about 69% to 66% — a 3-point decline driven entirely by mix. Specialty coffee, the highest-margin category, lost 12 points of share. That mostly went into food, which is half the margin. Before drawing conclusions, I'd want to know whether specialty coffee volume actually declined or just share-of-mix declined."
Inflection 4: Second drilldown — cost
Interviewer: "Specialty coffee volume is roughly flat — food and brewed coffee volume grew faster. Now let's look at cost."
2 years ago: COGS $0.95, labor per drink $1.40, total $2.35
Today: COGS $1.25, labor per drink $1.65, total $2.90
Average drink price: Both periods ~$5.40
Quick math:
- Old per-drink contribution margin: ($5.40 − $2.35) / $5.40 ≈56%
- New per-drink contribution margin: ($5.40 − $2.90) / $5.40 ≈46%
- Per-drink contribution margin decline: ~10 percentage points
Out loud: "Per-drink contribution margin dropped 10 points — much larger than the 3-point mix effect. COGS is up 32% and labor up 18%. Bean prices industry-wide are up roughly 25% per public reporting, so most of the COGS increase is probably input-driven. The labor increase is harder to read without knowing whether it's wage rate or labor-per-drink inefficiency."
The candidate connected the bean-price increase to public industry data, which is exactly the kind of "real-world context" partners grade as senior thinking. They also flagged labor as ambiguous and asked the right follow-up rather than guessing.
Inflection 5: Third drilldown — new-store drag
Interviewer: "Labor inefficiency has been a problem in newer stores — they take 12–18 months to reach steady-state labor productivity. Here's the new-store data."
540 stores open 18+ months: EBITDA margin 14%
65 stores open less than 18 months: EBITDA margin −2%
Weighted average: (540×14 + 65×−2) / 605 ≈12.3%
Out loud: "So the new-store drag accounts for roughly 2 points of the margin decline on its own. Combined with the 3-point mix shift and the per-drink contribution margin pressure (mostly bean-cost driven), we have a picture: about half the margin decline is industry-wide cost pressure, and half is BrewHouse-specific from new-store cannibalization and adverse mix shift toward lower-margin food."
Inflection 6: Recommendation
Interviewer: "Good. The CEO is in the room. What do you recommend?"
Out loud: "I'd recommend a two-track plan. First, on the cost side: BrewHouse should hedge bean exposure with 12–24 month forward contracts — peer chains have done this and recovered 1–2 points of margin within a year. Second, on the revenue mix: rather than pushing back on food, which customers clearly want, BrewHouse should reformulate the food offering toward higher-margin items — pastries with gross margins in the 50–55% range — and bundle them with specialty drinks. That should recover ~1–2 points of blended margin without losing the food traffic. Third, on new stores: pause expansion for 6 months and focus on driving the underperforming cohort to steady-state. We can revisit unit economics for new openings once the existing base recovers.
Combined, this gets us back to ~14–15% EBITDA margin in 12–18 months. The key risk is bean prices continuing to rise — if the hedge does not work, we revisit pricing. That's a difficult conversation in this category, but a 5–10% price increase is defensible if peers move first."
That recommendation has six parts: (1) specific actions, (2) mechanism for each, (3) expected magnitude, (4) timeline, (5) named risk, (6) contingency. This is the structure that turns "good case performance" into "offer." Most candidates stop at parts 1 and 2.
What an interviewer writes on the rubric
The interviewer's rubric (paraphrased from a real MBB evaluation form) typically scores on four dimensions:
- Structure (1–5): Clear branches, prioritized, supported by reasoning. Above-bar = candidate explicitly names a hypothesis.
- Math (1–5): Arithmetic accuracy, framing of the question, sanity-checking. Above-bar = candidate states assumptions and corrects rounding.
- Communication (1–5): Top-down, concise, follows interviewer cues. Above-bar = candidate paces with the interviewer rather than driving.
- Recommendation (1–5): Specific, hedged correctly, includes risk. Above-bar = candidate names what would invalidate the recommendation.
For this case, a candidate who delivers the analysis above would typically score 4/5 or 5/5 on all four — a clear pass. A candidate who skipped clarification, used a generic revenue/cost tree, did the math without framing, and ended with "I would investigate further" would score 2/5 or 3/5 — a clear fail.
How to use this walkthrough
Read it twice. The first time, follow the logic. The second time, run the case yourself out loud — pretend you are the candidate, narrate each step, then check against the walkthrough. The gap between your version and this one is your actual prep target.
The Profitability Framework Beyond Revenue minus Cost
The companion piece — the structural decomposition that powered this walkthrough.
One short, useful email per week.
New case frameworks, mock interview tactics, and recruiting intel from the CaseGrade team. Built for serious candidates — no fluff, no upsell every paragraph.
Unsubscribe anytime. We never share your address.
Keep reading
All articles →The State of Consulting in 2026: AI Delivery, Flat Entry Pay, and What Candidates Should Care About
Six things are shifting at once inside the consulting industry. Most of them are being talked about loudly. A few are being talked about quietly. Candidates who only track the loud ones are missing the more important story.
McKinsey Solve in 2026: Red Rock, Sustainable Future Lab, and What Actually Improves Your Score
McKinsey's digital assessment got a third module in late 2025. The good news: the underlying skills haven't changed. The bad news: most of the prep advice on the internet hasn't caught up.
What AI Case Interviewers Can — and Can't — Evaluate
Several AI case-prep tools have launched in 2026. Some are genuinely useful. Some are thin wrappers. The difference is what they can score honestly and what they have to hand-wave through.