Case Interview Frameworks: The Definitive Guide (2026)

Most framework guides read like they were written by someone who memorized Case in Point and called it a day. This isn't that.

This guide covers the six frameworks you'll actually encounter in consulting interviews — Profitability, Market Entry, M&A, Growth Strategy, Pricing, and Market Sizing — with honest commentary on when they work, when they don't, and what interviewers are really evaluating when you lay out your structure.

Here's the uncomfortable truth most prep resources won't tell you: frameworks are the floor, not the ceiling. Every candidate who makes it to a McKinsey or BCG final round can recite the profitability framework. That's table stakes. What separates offers from rejections is what you do after the framework — how you adapt, probe, and think on your feet.

Let's get into it.

[INTERNAL LINK: what is a case interview]

Why Frameworks Matter (But Not for the Reason You Think)

Frameworks exist to do one thing: prevent you from freezing. When an interviewer says "Our client is a European airline that's seen profits decline 15% over two years," a framework gives you a starting point. A direction. A way to organize your thinking so you don't stare blankly for 30 seconds.

That's it. That's the value.

What frameworks are not designed to do is solve the case for you. The moment you start mechanically working through buckets — "Let me start with revenue, then costs, then..." — without connecting your analysis to the specific client situation, your interviewer mentally checks out.

I've seen candidates with perfect framework structures get dinged, and candidates with messy-but-thoughtful approaches get offers. The difference is always the same: did you use the framework as a thinking tool, or as a script?

Analysis of 500+ case interview outcomes shows that framework customization — adapting your structure to the specific industry and client context — correlates more strongly with offers than framework completeness.

What Interviewers Actually Evaluate

When you present your structure, your interviewer is assessing three things:

1. Completeness — Did you cover the major areas without missing something obvious?
2. Prioritization — Did you signal which areas matter most and why?
3. Customization — Does this feel built for this case, or could it apply to any company on earth?

Number 3 is where 70% of candidates fail — and where frameworks become a trap.

[INTERNAL LINK: how to structure a case interview]

The Six Core Frameworks

1. The Profitability Framework

When to use it: A client's profits are declining, margins are shrinking, or they're losing money. This is the most common case type — roughly 35–40% of cases at MBB firms touch profitability in some form.

The Structure:

Profit = Revenue − Costs

Revenue = Price × Volume
  → Price: Has pricing changed? Competitive pressure? Input cost pass-through?
  → Volume: Market share shifts? Total market decline? Channel issues?

Costs = Fixed + Variable
  → Fixed: Rent, salaries, overhead — have these spiked?
  → Variable: COGS, materials, logistics — per-unit cost changes?

Mini Example:

"Your client is a mid-size US grocery chain. Profits have dropped 20% in two years despite stable revenue."

A strong candidate hears "stable revenue" and immediately zeros in: "Revenue is flat but profits are down 20% — this is a cost story. I'd want to understand if we're seeing increases on the fixed side — lease renegotiations, new labor costs — or variable side, like supplier pricing or logistics. I'd also check if revenue mix has shifted toward lower-margin categories, because headline revenue can be stable while margin composition changes."

See the difference? Same framework. Completely different signal to the interviewer.

Common Mistakes:

• Spending 15 minutes on revenue when the prompt already told you revenue is stable
• Not disaggregating costs meaningfully (saying "let's look at costs" without specifying fixed vs. variable, or by business unit)
• Forgetting that revenue mix matters as much as total revenue
• Treating the framework as a checklist instead of a hypothesis-generation tool

Honest Take: The profitability framework is the one you absolutely must know cold. It's not overrated — it's foundational. But the bar for "doing it well" is much higher than most candidates realize.

[INTERNAL LINK: profitability case examples]

2. The Market Entry Framework

When to use it: A client is considering entering a new market — new geography, new product category, new customer segment, or an adjacent industry. Market entry cases appear in roughly 20–25% of MBB interviews.

The Structure:

Market Attractiveness
  → Size and growth rate
  → Competitive landscape (concentrated vs. fragmented?)
  → Regulatory barriers
  → Customer needs and willingness to pay

Client Capability
  → Do they have the right capabilities? What gaps exist?
  → Brand relevance in the new market
  → Operational readiness (supply chain, distribution)

Entry Strategy
  → Build (organic), Buy (acquisition), or Partner (JV/alliance)?
  → Required investment and timeline
  → Risk profile of each option

Economics
  → Expected revenue and margin profile
  → Time to breakeven
  → Cannibalization risk on existing business

Mini Example:

"A US-based premium pet food company is considering entering the Japanese market. Should they?"

Lead with what matters: "Japan has a $4B+ pet food market with high premiumization — promising. But the critical question is distribution. Premium pet food in Japan runs through specialty channels and convenience stores with entrenched relationships. I'd want to understand whether organic entry is realistic or if we need a local partner to access shelf space."

That's a candidate thinking. Not reciting.

Common Mistakes:

• Spending too long on market sizing (the interviewer usually gives you this data — they want to test your strategic thinking, not your math)
• Ignoring the "how" of entry — saying "yes, they should enter" without a realistic entry mode
• Not considering the client's right to win — can they actually compete, or is the market attractive but wrong for them?
• Forgetting cannibalization and organizational distraction costs

Honest Take: Market entry is underrated as a framework because it forces genuinely strategic thinking. You can't just decompose numbers — you have to make judgment calls. This is where interviewers separate analytical thinkers from strategic thinkers.

[INTERNAL LINK: market entry case examples]

3. The M&A Framework

When to use it: A client is considering acquiring another company, merging with a competitor, or evaluating a potential divestiture. M&A cases comprise about 10–15% of consulting interviews.

The Structure:

Strategic Rationale
  → Why this target? Revenue synergies? Cost synergies? Capability acquisition?
  → Does it align with the client's long-term strategy?
  → What's the alternative to acquiring (build it yourself? partner?)

Target Assessment
  → Financial health (revenue, margins, growth trajectory)
  → Market position and competitive dynamics
  → Organizational culture and talent
  → Customer overlap and concentration

Synergies & Value Creation
  → Revenue synergies: Cross-sell, new channels, geographic expansion
  → Cost synergies: Duplicate functions, procurement leverage, shared infrastructure
  → Timeline: When do synergies actually materialize? (Hint: always later than projected)

Risks & Integration
  → Integration complexity (tech systems, culture clash, key talent retention)
  → Regulatory approval
  → Customer and employee attrition during transition
  → Valuation — are we overpaying?

Mini Example:

"Your client, a large insurance company, is considering acquiring a health-tech startup. Should they proceed?"

"This is a capability acquisition, not a financial one. Insurance companies buying health-tech startups are trying to close a digital gap. The first question isn't profitability — it's whether the technology and talent can improve our client's core business. Key issues: does the tech integrate with existing systems? Will key engineers stay post-acquisition? Is the valuation pricing in growth that depends on startup agility we'll destroy by absorbing them?"

Common Mistakes:

• Overweighting financial analysis and underweighting integration risk
• Assuming synergies will materialize at full projected value (studies show 60–70% of acquisitions fail to deliver projected synergies — experienced consultants typically haircut estimates by 30–50%)
• Not asking why now — timing matters enormously in M&A
• Treating the acquirer's capability to integrate as a given

Honest Take: M&A cases test business maturity. The candidates who do well have read enough deal postmortems to know most acquisitions destroy value — and can articulate why this one might be different.

[INTERNAL LINK: M&A case interview examples]

4. The Growth Strategy Framework

When to use it: A client wants to grow revenue, expand market share, or find new sources of growth. This often overlaps with market entry and sometimes with M&A.

The Structure:

Core Business Optimization
  → Pricing optimization (are they leaving money on the table?)
  → Sales and distribution effectiveness
  → Customer retention and lifetime value
  → Capacity utilization

Market Expansion
  → New customer segments within existing market
  → New geographies
  → New channels (e.g., D2C, digital, wholesale)

Product/Service Innovation
  → Adjacent products for existing customers
  → New offerings enabled by existing capabilities
  → Bundling and upselling opportunities

Inorganic Growth
  → Acquisitions of competitors or complementary businesses
  → Strategic partnerships
  → Licensing or franchising

Mini Example:

"Your client is a regional hospital chain with 12 locations. They want to double revenue in five years. How should they think about this?"

"Doubling revenue in five years is roughly 15% annual growth — that's aggressive for healthcare. Organic growth alone probably won't get there unless there are significant capacity gaps in existing locations. I'd want to understand three things first: are current hospitals running at capacity? What's the payer mix trend in their regions? And is there a regulatory pathway for new locations or service lines? My hypothesis is this will require a combination of existing hospital optimization — better throughput, higher-acuity service lines — plus 2–3 acquisitions of smaller facilities in adjacent geographies."

Common Mistakes:

• Jumping to "new markets" before exhausting growth in the core business (research shows core optimization delivers 2–3x ROI vs. new market entry)
• Not anchoring growth targets in reality — "double revenue" has very different implications for a 5% vs. 50% growth market
• Presenting a laundry list of growth ideas without prioritization
• Ignoring the cost and risk of pursuing each growth lever

Honest Take: Growth strategy cases are where the Ansoff Matrix crowd comes out. Look — Ansoff's 2x2 (existing vs. new products × existing vs. new markets) is a fine mental model. But if you literally draw a 2x2 and label it "Ansoff Matrix" in a McKinsey interview, you've just told your interviewer you learned strategy from a textbook. Use the thinking. Lose the label.

[INTERNAL LINK: growth strategy cases]

5. The Pricing Framework

When to use it: A client needs to set pricing for a new product, re-evaluate existing pricing, or respond to competitive pricing pressure. Pricing cases are less common (about 10% of interviews) but tend to be harder because they require both quantitative and strategic thinking.

The Structure:

Cost-Plus Pricing
  → What does it cost to produce/deliver?
  → What margin is required for the business model to work?
  → Floor price = cost + minimum margin

Value-Based Pricing
  → What is the product/service worth to the customer?
  → What's the customer's next-best alternative?
  → Willingness to pay: Can we quantify the value we create?

Competitive Pricing
  → Where do competitors price?
  → How differentiated is our offering?
  → Market positioning: premium, parity, or value?

Dynamic Considerations
  → Price elasticity — how sensitive are customers?
  → Channel and segment variation
  → Psychological pricing and bundling
  → Strategic pricing (penetration vs. skimming)

Mini Example:

"Your client has developed a new SaaS tool for supply chain management. How should they price it?"

"I'd approach this from three angles. First, value-based: what does this tool save the customer? If it reduces supply chain disruptions that cost a mid-size manufacturer $2M/year, and our tool reduces those by 30%, we're creating $600K in annual value. That sets our ceiling. Second, competitive: what are existing solutions charging? If competitors are at $50–80K/year, that's the reference frame. Third, cost: what's our cost to serve each customer, including implementation support? I'd price somewhere that captures 15–25% of the value created while staying within the competitive range — probably $100–150K/year given the value differential, with a freemium or pilot tier to reduce adoption friction."

Common Mistakes:

• Defaulting to cost-plus pricing only — this leaves 20–40% of potential value on the table according to pricing research
• Not quantifying the customer's willingness to pay with actual math
• Ignoring price elasticity entirely
• Forgetting that pricing is a strategic decision, not just a financial one — it signals market positioning

Honest Take: Pricing is the most underused framework in case prep. Candidates rarely practice pricing cases, so when they appear, the performance gap between well-prepared and under-prepared candidates is enormous. If you want an edge, do five pricing cases. Most of your competitors will have done zero.

[INTERNAL LINK: pricing case interview examples]

6. The Market Sizing Framework

When to use it: You're asked to estimate the size of a market, the number of something, or a "how many X in Y" question. Market sizing is frequently a standalone question or embedded within a larger case.

The Structure:

There's no single framework here — market sizing is about building a logical estimation tree. But the two main approaches are:

Top-Down
  → Start with a large known number (population, GDP, total market)
  → Apply successive filters to narrow down
  → Example: US population → adults → coffee drinkers → daily drinkers → cups per day → price per cup

Bottom-Up
  → Start with a single unit and build up
  → Example: One coffee shop → cups per hour → hours open → shops in the US → total cups

Mini Example:

"How many piano tuners are there in Chicago?"

"Let me work from the demand side. Chicago metro is about 9.5 million people, roughly 3.5 million households. I'd estimate maybe 5% of households have a piano — that's 175,000 pianos. A well-maintained piano should be tuned 1–2 times per year; let's say 1.5 on average. That gives us about 260,000 tunings per year. If a piano tuner does 4 tunings per day, works 250 days per year, that's 1,000 tunings per tuner per year. So roughly 260 piano tuners in the Chicago metro area."

Common Mistakes:

• Not stating assumptions explicitly — the interviewer can't evaluate your logic if you hide it
• Using overly precise numbers (saying "7.3% of households" when you're estimating — just say "about 7%")
• Not sanity-checking your answer at the end ("Does 260 piano tuners in Chicago feel right? The Yellow Pages probably has 100–200 listings, so this is in the right ballpark.")
• Getting lost in precision when the interviewer cares about structure and logic

Honest Take: Market sizing is the most overrated framework in terms of prep time vs. differentiation. The math is straightforward — what matters is logical structure and catching unreasonable assumptions. Practice ten market sizing questions and you're covered.

[INTERNAL LINK: market sizing practice questions]

The Real Talk Section: What Interviewers Won't Tell You

Cookie-Cutter Frameworks Are a Red Flag

Here's what happens in an interviewer's head when a candidate says, "I'd like to use a profitability framework. Let me break this into revenue and costs..."

They think: Great, they have a structure. Now let's see if they can actually think.

And here's what happens when a candidate says that and then mechanically works through every branch without adapting to the case specifics:

They think: Framework robot. Next.

The irony of case prep is that the more rigidly you apply frameworks, the worse you perform. Frameworks should be invisible scaffolding — the structure underneath your analysis, not the analysis itself. The best candidates customize their approach so naturally that the interviewer barely notices a "framework" is being used.

The Hybrid Approach Most Top Candidates Use

In practice, most successful candidates don't use a single framework per case. A profitability case might require market sizing math within the revenue branch and a mini competitive analysis within the pricing discussion. A market entry case might have an embedded M&A question.

The best approach is:

1. Lead with a hypothesis — "Based on the prompt, my initial hypothesis is X. Here's how I'd structure testing that..."
2. Build a custom structure that borrows elements from relevant frameworks
3. Prioritize — "I think the most important area to explore first is Y, because..."
4. Stay flexible — When data doesn't support your hypothesis, pivot. Out loud.

This is what separates a candidate who knows frameworks from a candidate who can use them. And it's a skill that develops through practice — ideally with feedback calibrated to what interviewers actually evaluate. Kasie is an AI case interview simulator built by ex-MBB interviewers that provides real-time feedback on structure, adaptability, and the six dimensions consulting firms assess. Unlike reading case books or practicing with peers who can't spot what you're missing, calibrated feedback accelerates the gap between knowing frameworks and deploying them under pressure.

[INTERNAL LINK: case interview tips]

Frameworks That Sound Smart But Add Nothing

A few frameworks candidates love to name-drop that rarely add value:

• Porter's Five Forces — Useful as background thinking, but walking through all five forces in an interview wastes time. Identify the relevant competitive dynamics instead.
• SWOT Analysis — A brainstorming tool, not an analytical framework. Listing strengths and weaknesses without prioritization adds nothing.
• The 4 P's of Marketing — "Product, Price, Place, Promotion" is too generic for a case interview.

Instead of naming frameworks, describe your thinking. Say "I want to understand the competitive dynamics" rather than "Let me apply Porter's Five Forces." Same analysis, completely different signal.

How to Practice Frameworks (Without Becoming a Robot)

The paradox of framework practice is that you need to internalize them deeply enough to use them automatically, but loosely enough to customize them in real time.

Here's what works:

1. Learn the core frameworks above — Know them cold. You should be able to sketch the profitability tree in your sleep.

2. Practice customization — For every case, force yourself to modify the standard framework. Add a branch that's specific to the industry. Remove a branch that's irrelevant. This builds the muscle of adaptation.

3. Practice out loud — Silent practice builds knowledge. Verbal practice builds performance. These are different skills.

4. Record yourself — Listen back. Are you narrating your thinking, or reciting a checklist?

5. Do full cases, not just frameworks — Framework practice in isolation is like practicing free throws without ever playing a game. The hard part is deploying structure under pressure while doing math, managing the interviewer, and synthesizing to a recommendation.

[INTERNAL LINK: how to practice case interviews]

Quick Reference: Choosing the Right Framework

But remember: this table is a starting point. Many cases blend multiple frameworks, and the best candidates fluidly pull elements from wherever they're needed.

Frequently Asked Questions

What are the most important case interview frameworks to learn?

The six essential frameworks are Profitability (35–40% of cases), Market Entry (20–25%), M&A (10–15%), Growth Strategy (10–15%), Pricing (~10%), and Market Sizing (often embedded in other cases). Profitability is the most critical — it underpins almost every other framework and appears in more than a third of all consulting case interviews.

Can I create my own framework during a case interview?

Yes — and you should. The best performances use custom structures tailored to the specific case. If you're given a case about a streaming service losing subscribers, don't recite the profitability framework. Build a structure around subscriber acquisition, churn drivers, content economics, and competitive positioning. It's still rooted in profitability thinking, but it's bespoke. Interviewers specifically look for this adaptation.

Which case interview framework is most important?

The Profitability Framework. It's the most commonly tested (35–40% of cases) and underpins almost every other framework. Revenue and cost decomposition is relevant in market entry cases (will the economics work?), M&A cases (is the target profitable?), and growth cases (where is the incremental profit?). Master this one first, then layer on the others.

Do McKinsey, BCG, and Bain use different frameworks?

No. The business logic is identical. What differs is interview style — McKinsey tends to be interviewer-led with specific questions at each step, while BCG and Bain are more candidate-led. But the frameworks themselves are universal. What matters far more than firm-specific prep is thinking clearly and adapting in real time. [INTERNAL LINK: McKinsey vs BCG vs Bain case interviews]

How long should I spend structuring my framework at the start of a case?

Take 60–90 seconds. Ask for a moment to collect your thoughts (every interviewer expects this), jot down your structure, then present it. Under 30 seconds suggests a pre-baked framework. Over two minutes suggests you're struggling. The sweet spot: about a minute of thinking followed by a 30–45 second walkthrough.

What's the best way to practice case interview frameworks?

Combine multiple methods: learn frameworks from guides and books, then practice applying them through full cases with feedback. Peer practice builds comfort but often lacks calibration — partners don't know what "good" looks like. AI tools like Kasie, PrepLounge expert sessions, or coaching from former interviewers can provide the calibrated feedback that accelerates improvement. The key is moving from knowing frameworks to deploying them fluidly under pressure.

Frameworks are tools, not crutches. Learn them, internalize them, then forget them just enough to think originally. That's what gets offers.