Most candidates learn case interview frameworks the wrong way: as a stack of templates to recite the moment a prompt sounds familiar. That instinct is exactly what costs people offers. The frameworks below are genuinely useful, but only as a starting logic. The skill that gets you through an MBB round is taking that logic and shaping it into a structure built for this problem.
Think of a framework as a checklist of the drivers a sharp problem-solver would naturally consider. You are not graded on naming the framework. You are graded on whether your case interview structure is clear, complete, and obviously tailored to the situation.
What a framework is actually for
A framework does three things, and nothing more:
- It buys you a clear opening. You get 60–90 seconds of silence to think, then you lay out how you will attack the problem. A framework keeps that opening organized instead of rambling.
- It makes sure you do not miss a major driver. Knowing the standard buckets means you are unlikely to forget cost when discussing profit, or competitive response when discussing entry.
- It gives the interviewer a map. When your structure is clear, the interviewer can follow your logic and steer you, which makes the whole case smoother.
What a framework is not: a finished answer. The buckets are raw material. Your job is to choose the ones that matter here, drop the ones that do not, and explain why each branch is worth investigating. For a fuller walkthrough of a case end to end, see our case interview examples.
Profitability
The profitability framework is the most common starting point because most business problems eventually reduce to it. The core equation is simple:
Profit = Revenue − Costs, and Revenue = Price × Quantity.
From there you branch:
- Revenue: Is the problem price, volume, or product mix? Has price moved? Has volume dropped, and if so, is it fewer customers or lower purchase frequency?
- Costs: Split fixed from variable. Which line moved? Is the change internal (a new plant, a wage rise) or external (input prices, a new tariff)?
The trap is reciting every possible cost line. Strong candidates isolate the change. If profit fell last quarter, something specific moved — find it. Start by asking whether the decline is a revenue problem or a cost problem, then drill into the one that is driving it. That single question saves you ten minutes of undirected analysis.
Market entry
The market entry framework applies when a company is deciding whether to enter a new market, launch a new product, or enter a new geography. The question is never just "can we enter?" — it is "should we, and how?" Useful branches:
- The market: How big is it, how fast is it growing, and how profitable is it? A large but shrinking or low-margin market may not be worth entering.
- Competition: Who already serves it, how concentrated is it, and how will incumbents respond when you arrive?
- The company's fit: Do we have a real right to win — a capability, brand, cost, or distribution advantage — or are we just another entrant?
- Entry mode and economics: Build, buy, or partner? What does the investment look like, and what is the expected return relative to the cost of entry?
The recommendation should hinge on the right to win and the economics, not just on whether the market is attractive in the abstract. An attractive market with no advantage is a fast way to lose money.
M&A / acquisition
An acquisition case asks whether a company should buy a target. The structure mirrors how a deal team actually thinks:
- Rationale: Why do this at all? Common motives are growth, capability or talent, market share, cost synergies, or defensive positioning. The rest of the case should serve this "why."
- The target and its market: Is the target a good business in an attractive market? This often borrows directly from the profitability and market-entry logic above.
- Synergies: Revenue synergies (cross-sell, new segments) and cost synergies (overlap, scale). Be skeptical — synergies are routinely overstated.
- Valuation and risk: Is the price justified by the standalone value plus realistic synergies? What could go wrong in integration, culture, or regulation?
Notice how M&A reuses the earlier blocks. That reuse is the point: the building blocks combine. Once you see that, you stop memorizing frameworks as separate objects and start treating them as a shared toolkit.
Market sizing
Market sizing (or estimation) shows up as its own question — "how many electric vehicles are sold in Germany each year?" — or as a step inside a larger case. It tests structured quantitative thinking, not trivia. The method is consistent:
- Pick a path. Top-down (start from a population and narrow) or bottom-up (build up from units of demand). State which you are using and why.
- Lay out the equation before plugging in numbers, so the interviewer can follow and correct your logic.
- Use round, defensible assumptions and say where each comes from. The number matters far less than the structure and the sanity checks.
- Sanity-check the result. Does the answer pass a smell test against something you know?
What interviewers reward here is a clean structure and calm arithmetic under light pressure — exactly what a live voice practice session forces you to do out loud.
Why memorized frameworks fail in real cases
Here is the uncomfortable truth: at MBB, a memorized framework is more likely to hurt you than help you. A few reasons:
- Real cases do not match the template. An interviewer might open with a profitability problem that is really an operations or pricing problem. If you force the standard tree onto it, you miss the actual issue.
- It signals the wrong thing. Reciting a memorized list tells the interviewer you pattern-matched instead of thinking. They are hiring for judgment, and a generic tree is the opposite signal.
- It misses the case-specific buckets. The branches that win cases are usually the ones unique to that business — a regulatory wrinkle, a channel conflict, a seasonality effect — and those never appear in a generic template.
- It is brittle under pressure. When the interviewer pushes back, a memorized structure has nowhere to go. A structure you built from first principles can flex.
Interviewers can usually tell within a minute whether your structure was built for their problem or pulled off a shelf. The fix is not more frameworks — it is more reps building structure from scratch. Our guide on how to prepare for case interviews covers how to sequence that practice over the weeks before a round.
Building a tailored, MECE structure
A good structure is MECE — Mutually Exclusive, Collectively Exhaustive. The buckets do not overlap, and together they cover the whole problem. Here is a way to build one on the spot, using the frameworks above as raw material rather than as the answer:
- Clarify the objective first. "Increase profit" and "decide whether to enter" lead to different trees. Pin down the goal and any constraints before you structure anything.
- Choose your building blocks. Pull the relevant logic — profitability, entry, M&A, sizing — but only the branches that fit this objective.
- Tailor each bucket to the business. Replace generic labels with the specifics of this company and industry. This is what makes a structure look bespoke instead of canned.
- Check it is MECE. No overlaps, no gaps. If two buckets could contain the same idea, redraw the line between them.
- Lead with a hypothesis. Say where you would look first and why. A structure that points somewhere beats a structure that just lists.
The only reliable way to get good at this is to do it out loud, repeatedly, and get specific feedback on whether your structure actually fit. That is what AI Mock Case is built for: you run a full live voice interview with an AI interviewer calibrated by two ex-MBB interviewers with 5+ years coaching, drawing on a library of 100+ cases. Minutes later, a five-dimension scorecard (Structure, Quantitative, Business Insight, Communication, Recommendation) is emailed to you, with the Structure score tied to your exact words — so you can see precisely where a generic framework would have cost you.
Frequently asked questions
How many case interview frameworks do I need to know?
Far fewer than most candidates think. The building blocks above — profitability, market entry, M&A, and market sizing — cover the underlying logic of the vast majority of cases. The goal is not to memorize twenty frameworks but to understand the few drivers each one rests on, then combine them to fit the problem in front of you.
Is the profitability framework still used at MBB?
Yes, but as a starting logic rather than a template you recite. Profit equals revenue minus costs, and revenue is price times quantity. Interviewers want to see you break that equation into the few drivers that matter for this business, not list every cost line you can remember.
Why do memorized frameworks fail in real case interviews?
Because real cases rarely match the template. A memorized framework makes you force a generic structure onto a specific problem, miss the buckets unique to this case, and sound rehearsed. Interviewers can tell within a minute whether your structure was built for their problem or pulled off a shelf.
What does MECE mean in a case interview structure?
MECE stands for Mutually Exclusive, Collectively Exhaustive. A MECE structure has buckets that do not overlap and together cover the whole problem. It signals clear thinking and makes the case easier to drive, because each branch can be tackled without double-counting or leaving gaps.
How do I practice building tailored structures instead of memorizing?
Practice out loud against live prompts and get specific feedback on whether your structure fit the problem. AI Mock Case runs a full voice case with an AI interviewer and emails a five-dimension scorecard — including a Structure score tied to your exact words — so you can see where a generic framework would have cost you. See the full MBB prep guide for how this fits into a complete plan.