CaseKit

Profitability Framework

The most tested framework in consulting interviews. Master this one first.

Most common · 40% of cases

Profitability cases show up constantly, and they look deceptively simple. The math is easy: subtraction. The discipline is hard. Most candidates rush toward a solution before they’ve actually figured out what’s broken. This guide will slow you down on purpose, so that by the end you’re decomposing problems the way a real consultant does, not guessing the way a nervous student does.

If you’ve never done a case interview before, start here. You’ll leave this page able to run this framework cold.

Imagine your friend runs a lemonade stand. Last summer she made $500 in profit. This summer, she only made $300, even though she sold more cups of lemonade than last year. She’s confused. So is her business partner. They ask you to figure out what happened.

You have exactly one honest starting point: profit is just revenue minus costs.

PROFIT = REVENUE COSTS
The entire framework, at its core

That’s it. Every consulting profitability case, whether it’s a $2M lemonade stand or a $2B retail chain, is a fancier version of “figure out why this subtraction problem changed.”

The reason this framework exists isn’t to give you something to memorize. It exists because “profit went down” could mean a hundred different things, and if you don’t have a structure, you’ll either freeze or start guessing randomly (“maybe rent went up?” “maybe they have too many employees?”). A framework is just a checklist that guarantees you look everywhere important, in a sensible order, without missing anything or repeating yourself. Consultants call this MECE: Mutually Exclusive, Collectively Exhaustive. Don’t worry about the jargon yet; you’ll feel why it matters by the end of this page.

So: revenue went down, or costs went up, or both. That’s step one. Everything else is just zooming in.

Use it any time a company’s financial performance is declining, underperforming, or just confusing. The trigger is almost always “profit changed”, but the cause could be hiding anywhere.

Classic prompts that signal profitability

  • “Our client’s profits have been declining for two years despite growing revenue.”
  • “Margins are compressing and the CEO wants to know why.”
  • “Our client is less profitable than its closest competitor. Help us understand why.”
  • “Net income fell 20% last year. Where should we look first?”

One important nuance: profitability thinking doesn’t only show up in “profitability cases.” Market entry cases secretly ask “will this be profitable?” Growth cases ask “which lever improves margins?” M&A cases require synergy math, which is just profitability math on two companies at once. Learn this framework cold. It’s the foundation everything else is built on. Every other framework in this guide borrows from it.

Don’t memorize the tree below yet. First, walk through why it’s built the way it is. That’s the part that actually transfers to a live interview, where you won’t have the tree in front of you.

Step 1 Revenue or costs?

Profit = Revenue − Costs. So logically, a profit decline can only come from three places: revenue fell, costs rose, or both happened at once. This is always your first move, and it’s a question you can usually ask the interviewer directly (“Do we know if this is being driven by revenue, costs, or both?”). Never skip this step to jump straight into a subcategory. You wouldn’t know which half of the tree is even worth exploring.

Step 2a If it’s revenue, break it into Price and Volume

Revenue is a single number, but it’s secretly two numbers multiplied together:

Revenue = Price × Volume

Why does this matter? Because Price and Volume can move in opposite directions and hide from you. Imagine prices rose 8% but the number of units sold fell 7%. Total revenue looks almost flat, up about 1%. A sloppy candidate would see “revenue’s basically flat” and conclude nothing’s wrong. But something’s very wrong: the company is losing nearly as many customers as it’s gaining in price. That’s a business bleeding volume, disguised by a price hike. You only catch this if you split Price from Volume and check both.

Once you’re inside Volume, you can go one level deeper still. Volume itself is a function of how many customers you have and how often they buy:

  • Customer count, are we acquiring fewer new customers, or losing existing ones?
  • Purchase frequency, are existing customers buying less often?
  • Average order size, are the same customers buying less each time?

Step 2b If it’s costs, break them into Fixed and Variable

Fixed Costs  →  don’t change with how much you produce or sell
(rent, salaried staff, insurance, software, R&D)
Variable Costs  →  scale up and down with each unit produced or sold
(raw materials, packaging, sales commissions, payment fees)

Why split this way instead of, say, alphabetically, or by department? Because the split tells you something actionable. If fixed costs spiked, that’s usually a structural, slower-moving problem (a new lease, a hiring binge), often visible from one line in a budget. If variable costs spiked, that’s usually tied to volume or input prices, and it means something changed per unit, a supplier raised prices, or your product mix shifted toward cheaper, thinner-margin items. Diagnosing “fixed vs. variable” instantly tells you what kind of investigation to run next.

Putting it together

Now the tree assembles itself. Toggle a branch and decompose it until you hit a lever you can actually move.

REVENUE = Price × Volume Price ├── Has average selling price changed? ├── Are we discounting more than before? ├── Have we changed our product/tier mix? │ └── (Mix shift: more low-margin SKUs = lower blended price) └── Are competitors forcing price down? Volume ├── Total units sold: up, down, or flat? ├── Customer count: acquiring fewer customers? ├── Purchase frequency: buying less often? └── Average order size: smaller baskets?
COSTS = Fixed + Variable Fixed Costs (don't change with output volume) ├── Rent / lease payments ├── Salaries and benefits (salaried staff) ├── Depreciation and amortization ├── Insurance, software subscriptions └── R&D, corporate overhead Variable Costs (scale with each unit sold) ├── Cost of Goods Sold (raw materials, manufacturing) ├── Packaging and logistics ├── Sales commissions ├── Payment processing fees └── Customer support (if per-ticket)

Diagnose before you prescribe. Whichever branch you explore, quantify the gap first. Never say the word “recommend” until you’ve named the dollar amount and the root cause.

How to actually run this out loud in an interview

  1. Ask whether the problem is revenue-side, cost-side, or both. Isolate the culprit bucket first.
  2. Within revenue: check Price and Volume separately, out loud, even if one looks fine at first glance.
  3. Within costs: separate Fixed from Variable, then go category by category within whichever one is moving.
  4. Quantify the gap as you go: how much of the total profit decline does each driver explain? Consultants think in dollars, not adjectives.
  5. Only once you can point to a specific number and a specific cause do you say the word “recommend.”

Diagnostic discipline: tap a card to flip

01
Diagnose before you prescribe
Flip

Don’t say the word “recommend” until you’ve identified the specific dollar amount and root cause. First instinct isn’t analysis; it’s guessing.

02
Revenue = Price × Volume
Flip

They can move in opposite directions and still net to flat revenue. Always decompose: price vs. volume, customer count vs. frequency, and watch for mix shift.

03
Isolate the bucket first
Flip

Revenue-side, cost-side, or both? Name the culprit bucket before drilling down. It stops you from boiling the ocean on a branch that isn’t the problem.

04
Sequence by impact
Flip

Lead your recommendations with the biggest driver. Quantify how much of the decline each lever explains, then address the largest dollar gap first.

Reading the framework is one thing. Hearing it applied out loud is what makes it click. Here’s a short exchange showing how a strong candidate opens a profitability case. Notice they’re narrating their thinking, not just their conclusion.

Interviewer
“Our client, a national coffee chain, has seen profit fall 15% this year even though revenue grew 3%. They’ve asked us to figure out why.”
Candidate
“Got it, so revenue is actually up slightly, which tells me the problem is probably concentrated on the cost side, but I’d like to confirm that before I rule revenue out entirely. Do we have a breakdown of how costs have moved year over year, split between things like rent and salaries versus things like ingredients and packaging?”
Interviewer
“Good instinct. Costs are up 9% overall. What would you want to know next?”
Candidate
“I’d want to know whether that 9% is concentrated in fixed costs, like new store leases or corporate hires, or in variable costs, like coffee bean prices or cup packaging, since those point to very different root causes. I’d also want to sanity-check revenue isn’t hiding something, for instance if price per cup rose but transaction volume fell, that could still show up as ‘3% revenue growth’ while masking a real customer problem.”
Notice what the candidate didn’t do: they didn’t guess a cause (“maybe rent went up”), and they didn’t recommend anything yet. They asked a structured question that would let them isolate the right bucket first. That’s the entire skill this framework is training.

RetailCo is a mid-size specialty apparel retailer with 200 stores across the US. Two years ago they earned $80M in operating profit on $800M in revenue. This year, operating profit is $40M on $820M in revenue. The CFO is alarmed: revenue is up slightly but profit has halved, a drop of $40M. You’ve been called in. What’s going on?

Step 1 Revenue or costs?

Revenue went from $800M to $820M, up $20M (2.5%). That’s not the problem. So the $40M profit decline is entirely cost-driven. We can set revenue aside for now and focus on the cost structure.

Step 2 Fixed vs. variable?

The interviewer shares a cost breakdown:

Cost category2 years agoThis yearChange
COGS (variable)$440M (55%)$492M (60%)+$52M
Store rent (fixed)$120M$126M+$6M
Corporate overhead (fixed)$80M$82M+$2M
Marketing (semi-variable)$40M$38M−$2M
Other$40M$42M+$2M
Total costs$720M$780M+$60M

Revenue up $20M. Costs up $60M. Net effect: −$40M. Every figure on this page is operating profit, pre-tax — keep one basis and the reconciliation is exact.

Decompose it yourself with the builder below. The sliders start at this year’s troubled numbers. Drag the drivers and watch profit, margin, and the diagnosis react. Notice which lever actually moves the needle.

Baseline: two years ago RetailCo earned $80M profit on $800M (a 10% margin). Where did this year go wrong?

Revenue$820M
COGS (% of revenue) · biggest lever60%
Fixed costs (rent + overhead)$208M
Operating costs (marketing + other)$80M
Operating profit (pre-tax)
~$40M
Revenue$820M
− COGS$492M
− Fixed costs$208M
− Operating costs$80M
Operating margin4.9%
Margin under pressure
  • COGS at 60% of revenue, compressing the margin
  • Operating margin of 4.9% (vs. ~10% two years ago)
  • Operating profit of $40M (vs. $80M baseline)

Step 3 COGS is the smoking gun

COGS jumped from 55% to 60% of revenue, a 500 basis point margin compression. On $820M revenue those 5 points are worth $41M. COGS actually rose $52M in total — the extra $11M is simply the cost of selling 2.5% more goods, which isn’t a problem. It’s the $41M rate effect that explains the decline.

You ask the interviewer: “What’s driving the COGS increase?” They tell you:

  • Raw cotton and polyester prices spiked 18% due to supply chain disruptions after flooding in key manufacturing regions.
  • RetailCo’s contracts with suppliers are spot-priced (no fixed-rate agreements), so 100% of the increase was passed through.
  • RetailCo also shifted product mix toward lower-margin basics this year to compete on price with fast-fashion entrants. This reduced average gross margin per unit even before the input cost increase.

Step 4 Quantify each driver

  • COGS +$52M, which splits three ways: input cost spike ~$28M, product mix shift toward lower-margin items ~$13M, and ~$11M of ordinary volume growth on 2.5% more revenue.
  • Store rent +$6M (lease renewals at higher market rates, largely unavoidable short-term).
  • Corporate overhead +$2M, other +$2M, marketing −$2M.
  • Costs therefore rose $60M against $20M of revenue growth, for a −$40M swing in operating profit. That ties exactly to the table — and tying exactly is the point. If your drivers don’t sum to the gap, you’ve either missed one or double-counted.

Step 5 Recommendations

Short-term (0–6 months)

  • Renegotiate supplier contracts to lock in fixed pricing for 12–18 months. Even at current elevated rates, certainty reduces planning risk.
  • Pause the push into basics. Price competition with fast fashion is margin-dilutive. RetailCo’s strength is premium product, not price.

Medium-term (6–18 months)

  • Diversify the supplier base geographically to reduce concentration in flood-prone regions.
  • Explore partial vertical integration for key materials (cotton blends) to improve cost control.
What not to recommend: cutting marketing further. It’s already down, and reducing brand investment in a competitive environment will hurt volume next.
Price and volume hiding from each other

JCPenney, 2012: when a “neutral” price change collapsed revenue

Worth knowing because it’s one of the most-cited cautionary tales in retail: JCPenney, under CEO Ron Johnson in 2012, eliminated the company’s constant coupons and “sale” events in favor of a simplified “everyday low prices” strategy. On paper, this looked like a clean win for the customer. The math said shoppers would pay roughly the same or less, without needing a coupon to get there. Revenue collapsed anyway, falling by roughly a quarter that year, and Johnson was gone within about 17 months.

What happened is a real-world version of exactly the trap this page warned about earlier: revenue isn’t one number, it’s Price × Volume, and the two don’t always move for the reasons you’d expect. JCPenney’s effective prices barely changed. But volume cratered, because a huge share of their customers weren’t actually shopping for the lowest price, they were shopping for the feeling of getting a deal. Remove the “60% off” sign and the same price tag underneath suddenly sold far less, even though nothing about the actual dollar amount had changed. A team looking only at “did we raise or lower price” would have missed this completely. The real driver was on the volume side, and it was psychological, not economic.

The lesson: always check price and volume separately, and don’t assume a change that looks neutral on paper will actually behave neutrally in the real world. Customers respond to more than the number on the price tag.

Mistake 1: Jumping to recommendations before diagnosing

The most common error in profitability cases. The candidate hears “profits are down” and immediately says “they should cut costs” or “raise prices.” That’s not analysis. That’s guessing. The interviewer wants to watch you think, not hear your first instinct. Diagnose the specific driver before you suggest anything.

A good rule: don’t say the word “recommend” until you’ve identified the specific dollar amount and root cause of the problem.

Mistake 2: Treating Revenue as a single number

Revenue = Price × Volume. These can move in opposite directions and still produce flat total revenue. The “8% price up, 7% volume down” trap from earlier in this page is a real pattern that shows up constantly. Always decompose. Ask about price trends and volume trends separately. Ask about customer count and purchase frequency separately. Mix shifts are invisible unless you go looking for them.

01

The streaming service with rising revenue, falling profit

A mid-tier streaming platform grew subscribers 15% last year, but operating profit fell 12%. Content spend, infrastructure, and licensing are all on the table. Diagnose the driver and quantify it before recommending anything.

How to crack it
1
Revenue’s up, so this is entirely cost-side

Subscribers grew 15%, so set the revenue line aside. The 12% profit drop has to be living in the cost structure.

2
Split costs into fixed vs. variable

Fixed: infrastructure, licensing minimums, corporate overhead. Variable: content spend per subscriber, payment processing.

3
Benchmark each cost’s growth against 15%

Anything growing faster than subscribers is a suspect. That one test ranks your buckets before you drill into any of them.

4
Prime suspect: content spend

Streaming budgets are committed in advance, so 15% more subs doesn’t fund proportional content. If content grew 25% on 15% subscriber growth, that delta explains most of the compression.

5
Then infrastructure, then licensing

Cloud scales with streaming volume, so if per-unit cost isn’t falling with scale, it’s architecturally inefficient. Licensing is usually fixed-contract, so only a swing factor if a major deal renewed higher.

Where you land

Quantify the dollars from each bucket, then recommend. Don’t jump to “cut content spend” before you’ve confirmed it’s the driver.

02

The coffee chain losing margin to its competitor

Your client runs 400 cafés and earns a 9% net margin; its closest competitor earns 14% on similar revenue. Same prices, same regions. Decompose price, volume, and cost structure to explain the 5-point gap.

How to crack it
1
Same prices, same regions → it’s cost structure

Identical pricing and geography rules out a revenue-side story. The 5-point margin gap equals roughly the same dollar gap in cost efficiency.

2
COGS first

If the competitor sources coffee, milk and packaging cheaper (scale purchasing, better supplier contracts, vertical integration), that alone is 2–3 points.

3
Labor second

Check revenue per employee and labor as a % of sales. More staff per location or higher overtime rates is roughly another point.

4
Occupancy third

Same region doesn’t mean identical real estate. A lease portfolio skewed to premium high-traffic sites pushes rent as a % of revenue up.

5
G&A last

400 cafés should fund a lean corporate function. Overhead that’s bloated relative to store count is the final lever.

Where you land

Present all four buckets ranked by likely magnitude, quantify what closing each gap means in margin points, and let the data point you. It’s almost never one thing.

Try it yourself first. Talk through your full structure out loud before you click to reveal the answers below. That’s where the real reps happen.
Q1A company's revenue grew 10% this year, but net profit fell 8%. Which is the correct first analytical move?
A Recommend a price increase to restore margins
B Decompose costs into fixed and variable to identify what grew faster than revenue
C Benchmark the company against its competitors
D Analyze whether the market is contracting
Answer: B. Revenue grew, so the problem is cost-side. The right first move is decomposing the cost structure to find what’s growing faster than revenue. You don’t prescribe (A) before you diagnose. Competitive benchmarking (C) and market analysis (D) are useful later, but not first.
Q2A retailer's total revenue is flat year-over-year. The head of sales says "nothing has changed." But gross margin fell from 45% to 39%. What's the most likely explanation worth investigating first?
A Customer count declined
B A shift in product mix toward lower-margin items, or an increase in input costs
C Fixed costs increased significantly
D The company cut prices across the board
Answer: B. Gross margin is Revenue minus COGS, so it’s not affected by fixed costs (C). Flat revenue means Price × Volume is unchanged, making an across-the-board price cut (D) unlikely to go unnoticed. Mix shift and input cost increases are the classic causes of margin compression with flat revenue. One of the most important patterns to recognize.
Q3You identify that 80% of a company's profit decline is explained by a spike in variable costs. The remaining 20% is from increased fixed costs. Which should you address first in your recommendations?
A Fixed costs, because they're easier to cut
B Variable costs, because they represent the bigger driver and may be recoverable
C Both equally
D Neither; focus on growing revenue instead
Answer: B. Prioritize where the problem is biggest. Variable costs are the dominant driver here, so that’s where your recommendation should lead. Fixed costs may also need attention, but sequencing recommendations by impact size shows consultants’ discipline. D is a deflection: you should address both the cost problem and explore growth, but don’t use growth as an excuse to avoid diagnosing costs.
Q4A candidate hears "our client's profits are declining" and immediately responds: "I'd recommend they cut headcount and raise prices by 5%." What's wrong with this response?
A Nothing, speed matters in interviews
B It skips diagnosis entirely; the candidate doesn't yet know whether the problem is revenue, costs, fixed, variable, price, or volume
C 5% is too small an increase to matter
D Headcount cuts are never a good recommendation
Answer: B. This is the single most common failure mode in profitability cases. Recommending a specific fix before isolating the actual driver isn’t confidence. It’s guessing. A strong candidate would ask clarifying questions and decompose the problem first, and only recommend once the dollar-and-cause is identified.

Ready to put this into practice?

Reading the framework gets you halfway. The other half is reps: practice cases that build the muscle memory interviews demand.

Start practicing