Profitability Case Interview Guide: Framework and Worked Example

The profitability case interview is one of the most common case types in first rounds at McKinsey, BCG, and Bain. Mastering it is non-negotiable. This guide walks you through the core framework, a full worked example on a retailer with declining margins, and the mistakes that separate offers from rejections.

Analytics dashboard showing revenue and margin trends
Margin pressure is a common client problem. Operating margin compression, driven by input cost inflation and discounting, is a recurring theme in profitability cases.

What is a Profitability Case?

A profitability case asks you to diagnose why a company's profits have declined, stagnated, or failed to meet expectations, and to recommend a path forward. The prompt usually sounds like: "Our client's margins dropped 300 basis points last year. Why, and what should they do?"

These cases reward structured thinking, clean quantitative decomposition, and the ability to drive to a root cause rather than list generic ideas. They also test your instinct for which lever matters most.

The Core Profitability Framework

Every profitability diagnosis starts from the identity Profit = Revenue minus Costs. The power comes from decomposing each side into drivers that you can investigate with data.

Branch Driver Sub-driver
Revenue Price Mix, discounts, list price, realised price
Revenue Volume Market size, market share, channel mix
Costs Variable costs COGS per unit, logistics, raw materials
Costs Fixed costs Rent, salaries, marketing, depreciation

Pro Tip: Always split revenue into Price times Volume before you talk about segments. It forces you to ask whether the drop came from fewer units or lower realised price, and the interviewer will nod.

Tailor the Tree to the Industry

A generic tree will not win offers. A retail profitability case should mention same-store sales, basket size, and footfall. A SaaS case should mention ARPU, logo churn, and gross margin per seat. An airline case should mention yield, load factor, and fuel cost per available seat kilometre. Tailoring signals commercial awareness.

Do Not Forget Product Mix

A margin can fall even when every individual price and unit cost holds steady, simply because the company is selling a higher share of its lower-margin products. If shoppers trade down from full-price apparel into low-margin basics, the blended margin drops without any single product getting cheaper to make or sell. Always ask whether realised price fell because of true discounting or because the sales mix shifted toward cheaper lines, because the two have very different remedies. Separating a genuine price cut from a mix shift is one of the fastest ways to reach the real root cause, and it is exactly the kind of non-obvious driver interviewers plant to see whether you decompose carefully.

Step-by-Step Walkthrough: Declining Margins at a Retailer

Consider this prompt. "Our client is a European mid-market fashion retailer. Revenue grew around 5% last year, but operating margin fell from 12% to 8%. Find the root cause and recommend actions."

Step 1. Clarify and size the problem. Revenue grew, so the issue is on the cost side or on realised price. A 400 basis point margin decline on, say, two billion euros of revenue is roughly 80 million euros of lost profit. That is the prize.

Step 2. Split revenue first. Ask for price and volume trends. Suppose volume grew 10% but average selling price dropped 5%. That points to heavier discounting rather than a demand problem.

Step 3. Split costs. Break into COGS, store operations, marketing, and overhead. Suppose COGS per unit rose around 8% because of higher cotton prices, while store operating costs stayed flat as a percentage of sales.

Step 4. Quantify and isolate. The two biggest effects are the 5% price erosion and the 8% COGS inflation. Together they explain the bulk of the margin compression. Everything else is noise.

Step 5. Synthesise with conviction. "Margins fell because the client absorbed input cost inflation while discounting more aggressively. I recommend selective price increases on inelastic categories, renegotiating with top suppliers, and tightening promotional depth on best sellers."

For more on delivering the close, see how to structure a synthesis in 60 seconds.

Consultants reviewing a profitability tree on a laptop in an office
The tree, not the answer, wins points. A generic profitability tree loses points early, because it signals that the candidate is reciting rather than diagnosing.

Common Levers to Consider

Once you have identified the root cause, you need ready-made levers to recommend. Interviewers expect more than "cut costs".

  • Raise price on low-elasticity SKUs or premium segments
  • Shift mix toward higher-margin channels such as direct-to-consumer
  • Consolidate suppliers to unlock volume discounts
  • Automate or offshore back-office functions
  • Rationalise the tail of unprofitable SKUs, stores, or customers
  • Renegotiate long-term fixed contracts such as leases

Fixed Versus Variable Costs

Knowing which costs are fixed and which are variable changes the recommendation. If the client has high fixed costs, volume recovery is the fastest route back to margin. If costs are mostly variable, price and mix levers dominate. State this distinction out loud and your structure score will climb.

Common Mistakes to Avoid

  1. Reciting a generic revenue and cost tree with no industry colour
  2. Jumping to recommendations before quantifying the problem
  3. Ignoring mix effects and treating the business as a single product
  4. Forgetting to compare with competitors or the industry benchmark
  5. Refusing to commit and hiding behind "we need more data"

Strong candidates pick the two or three levers that matter, quantify the impact, and move on. Weak candidates list ten levers with equal weight.

Practice Cases and Next Steps

The fastest way to internalise the profitability framework is repetition under time pressure with feedback. Drill the decomposition until you can build a tailored tree in under 60 seconds. You can find broader structural drills in our guide to case interview frameworks and sharpen your estimation with our market sizing worked examples.

If you are targeting a specific firm, the McKinsey interview guide covers the interviewer-led style you will face on profitability prompts.

FAQ

How long should a profitability case take?

Expect 25 to 35 minutes end to end. Budget 60 to 90 seconds for the framework, 15 to 20 minutes for analysis and math, and around two minutes for synthesis.

Should I always split Revenue into Price and Volume?

Yes for almost every profitability case. Price and volume have very different diagnoses and remedies, so separating them early is non-negotiable.

What if the interviewer gives me only cost data?

Acknowledge it, size the cost side first, and flag that you will circle back to revenue if time allows. Do not force an artificial balance when the data clearly points one way.

How important is industry knowledge?

You do not need deep expertise, but a few tailored drivers per industry go a long way. Know the basic profit levers for retail, SaaS, banking, airlines, and consumer goods.

Is profitability tested at all firms?

Yes. McKinsey, BCG, Bain, and most Tier 2 firms use profitability prompts heavily in first rounds because they quickly reveal structure and quantitative skill.

Further Reading

  1. McKinsey & Company, Featured Insights, operating performance and margin pressure analyses.
  2. McKinsey Quarterly, Latest articles, strategy and profit decomposition perspectives.
  3. Harvard Business Review, Strategy topic archive, long-form essays on profit pools and competitive position.
  4. Bain & Company, Bain Insights, practitioner write-ups on margin recovery programmes.
  5. Financial Times, Companies coverage, corporate earnings and margin reporting.

Ready to start preparing? CasingLab offers adaptive case interviews with a McKinsey-style AI interviewer, 6-dimension scoring with proof points, and 150+ drills. CasingLab opens soon. Join the waitlist to get early access at launch.