Consulting frameworks you actually need for case interviews
Frameworks are thinking tools. They give you a starting structure when the interviewer throws a problem at you and you have 30 seconds to figure out where to start.
But here's what trips people up: frameworks are not recipes. You can't memorize "the profitability framework" and apply it identically to every profit case. The interviewer can tell. They've seen thousands of candidates do exactly that.
What works is knowing 5-6 frameworks well enough to adapt them. Pull the relevant pieces, combine them, add case-specific angles. Below are the ones that come up most often at McKinsey, BCG, Bain, and other top firms.
Profitability framework
This is the most common case type. A company's profits are declining, or they want to improve margins. The framework is simple:
Structure
Profit = Revenue - Costs
Revenue = Price x Quantity (broken by product line, customer segment, or geography)
Costs = Fixed costs + Variable costs
How to use it
Start by asking whether the issue is on the revenue side, the cost side, or both. Don't try to solve everything at once. Pick the side that seems more promising based on the data, dig into it, and quantify.
If revenue is the problem, break it down: is volume down, or is pricing dropping? Which products or segments are affected? If costs are the problem: which cost categories grew, and why?
Example application
A retail chain's profit fell 20% while revenue stayed flat. That tells you the problem is costs. You'd break costs into rent, labor, COGS, and marketing. Ask for data on each. If COGS went up 15% because of supply chain issues, you've found the driver. Now recommend: renegotiate supplier contracts, find alternative suppliers, or adjust product mix toward higher-margin items.
Market entry framework
"Should we enter this market?" is one of the most frequent case prompts. The answer depends on four things:
Structure
1. Market attractiveness — size, growth, profitability
2. Competitive landscape — who is there, how strong, barriers to entry
3. Company capability — do we have the skills, assets, brand to compete
4. Entry mode — build, buy, or partner
How to use it
Work through each piece in order. A common mistake is spending 15 minutes on market sizing and never reaching the competitive analysis. Balance your time. The interviewer often cares more about your competitive insight than the exact market size.
For entry mode, think about the company's risk tolerance, existing relationships, and time-to-market requirements. Acquisitions are fast but expensive. Partnerships reduce risk but share profits. Organic growth is cheap but slow.
M&A framework
M&A cases ask whether a company should acquire another company. Three questions matter:
Structure
1. Strategic rationale — why buy? (fill pipeline, enter market, gain capabilities, eliminate competitor)
2. Valuation — what is the target worth? (DCF, comparable transactions, revenue multiples)
3. Integration risks — what could go wrong post-deal? (culture, talent loss, operational complexity)
How to use it
Start with why the acquirer wants to do this deal. If the strategic rationale is weak, the valuation doesn't matter. Then estimate value — even if you can't do a full DCF, you can do a rough revenue or EBITDA multiple. Finally, address risks and how to mitigate them.
The best candidates structure the deal itself as part of their recommendation. Rather than just saying "buy" or "don't buy," suggest earn-outs, milestone payments, or integration approaches that manage the risk.
Pricing framework
"How should we price this product?" comes up regularly. There are three approaches, and you should mention all three before picking one:
Structure
1. Cost-plus — calculate costs, add a margin. Simple, but ignores what customers will pay.
2. Competitor-based — price relative to competitors. Works when products are similar.
3. Value-based — price based on the value the customer receives. Hardest to calculate, usually yields the highest price.
How to use it
Calculate cost-plus first to establish a price floor. Then look at competitors for market context. Finally, estimate the value to the customer — how much money or time does your product save them?
Also consider: should pricing be tiered? Should there be a free tier? What about annual vs. monthly pricing? These details show the interviewer you think about pricing as a business decision, not a math exercise.
Growth strategy framework
When a company asks "how do we grow?", there are four directions:
Structure (based on the Ansoff matrix)
1. Sell more of existing products to existing customers (upsell, cross-sell, reduce churn)
2. Sell existing products to new customers (new geographies, new segments)
3. Sell new products to existing customers (product line extensions)
4. Sell new products to new customers (diversification — highest risk)
How to use it
Start with the lowest-risk options. Can the company grow by selling more to its current customers? That's almost always cheaper than acquiring new ones. Then explore new customer segments or geographies. Only suggest new products or diversification if the existing avenues are exhausted.
Quantify each option when you can. "Entering the European market could add $50M in 3 years" is more useful than "they could expand internationally."
When to use which framework
| Case prompt | Framework | First question to ask |
|---|---|---|
| "Profits are declining" | Profitability | "Is the issue on revenue or cost side?" |
| "Should we enter market X?" | Market entry | "How large and fast-growing is this market?" |
| "Should we acquire company Y?" | M&A | "What is the strategic rationale for this deal?" |
| "How should we price this?" | Pricing | "What does it cost us to produce?" |
| "How do we grow?" | Growth | "Where is the current revenue coming from?" |
| "How many X are there?" | Market sizing | "Let me break this into a top-down estimate" |
Many real cases mix types. A market entry case might require you to size the market and then do a profitability analysis. That's normal. Use the relevant pieces from each framework.
Common mistakes with frameworks
Reciting instead of thinking
If you say "I'll use the profitability framework: revenue equals price times quantity, costs are fixed plus variable" and nothing else, you've just repeated a textbook. The interviewer knows the framework. They want to see you apply it to this specific case.
Forcing a framework that doesn't fit
Not every case maps cleanly onto one framework. If the prompt is "a hospital is overcrowded," don't jam it into a profitability structure. Think about what actually drives the problem and build your structure around that.
Listing every branch without prioritizing
Candidates sometimes lay out 8 branches of analysis and then try to cover all of them equally. Pick the 2-3 that seem most relevant based on the information you have, and investigate those first. You can always come back to the others.
Never leaving the framework
The framework gets you started. But the case often takes unexpected turns. If the data points somewhere your framework doesn't cover, follow the data. The best candidates use frameworks as launchpads, not cages.
Practice applying frameworks
Reading about frameworks is step one. Using them under pressure is step two. CaseXcel gives you daily case prompts that force you to pick a framework, build a structure, and work through the case — the same way you'll do it in the interview.
The app also tracks which case types you struggle with, so you can focus your practice where it actually helps.