Profitability Framework
Profit = Revenue minus Cost. The one framework that finds where the money leaked, then where to get it back.
On this page
The gist
- →Profit = Revenue - Cost, run as a binary search: ask which branch broke, kill the other, go one level deeper. Never analyse the whole tree.
- →Customise the revenue model to the business (subscribers x ARPU, outlets x orders x bill) and name real industry cost lines, not generic Fixed/Variable boxes.
- →Segment until the average breaks — a mix shift to a low-margin product or channel can halve profit while price and unit costs stay unchanged.
- →Always check firm vs industry, then quantify: your root cause must explain most of the rupee gap before you recommend sized fixes with named risks.
The framework at a glance
When to use it
Reach for this framework the moment the prompt contains a fall, a squeeze, or a gap in any money metric. Classic triggers: profits have declined 20% over two years, margins are shrinking while revenue grows, our client earns less than competitors, EBITDA is flat despite volume growth, or this business unit is loss-making and the board wants to know why. It also fits forward-looking versions: the client wants to double profit in three years, or improve margin by 300 basis points. Use it as a sub-framework inside bigger cases too - a market entry case usually ends in a profitability calculation, a turnaround case starts with a profit diagnosis, and a pricing case is a zoom-in on one branch of this tree. Do not use it when nothing about profit is broken: a pure market-sizing question, a make-versus-buy decision, an organisational or M&A synergy question, or a should-we-launch-product-X question where the real issue is demand and capability rather than a leak in an existing P&L.
What it is
The Profitability Framework is the diagnostic tool consultants use when a business is making less money than it used to, or less than it should. It rests on one equation every student already knows: Profit = Revenue - Cost. What makes it a framework rather than an equation is the discipline of breaking each side into layers until you reach a driver small enough to actually fix. Revenue splits into Volume times Price. Cost splits into Variable (moves with every unit you make or sell) and Fixed (rent, salaries, depreciation - which show up whether you sell one unit or a lakh). Keep splitting and you get a tree, what practitioners call an issue tree or profit tree.
Keep reading ↓Show less ↑
The framework is fundamentally about elimination, not exploration. You are not meant to analyse everything on the tree. You are meant to ask one question at each level - which branch is the problem in? - get an answer from the interviewer or the data, kill the other branch, and go one level deeper on the survivor. A well-run profitability case is a binary search: profit fell, is it revenue or cost, it is revenue, is it price or volume, it is volume, which product line, which region, which channel. Six questions and you are at the root cause. Candidates who instead recite the whole tree and analyse every twig run out of time and never find the answer.
The second thing that separates a strong candidate is customising the tree to the actual business model. Price times Quantity is a default, not a law. A supermarket is better read as number of transactions times average basket value. An app is users times ARPU. A hospital is beds times occupancy times revenue per occupied bed day. A consulting firm is billable consultants times utilisation times rate. Choosing the revenue model that matches how the company really earns money is what makes the rest of the case feel intuitive, and it is exactly what interviewers watch for. On the cost side, a generic Fixed plus Variable box is weak; naming the four or five real cost lines of that industry (for a QSR: food cost, rent, staff, delivery commission, packaging) shows business sense rather than memorisation. Profitability cases are the single most common archetype in MBB and Indian consulting interviews - roughly a fifth to a third of all cases - so this is the framework to master first.
How to apply it, step by step
- 1
Nail the objective and the numbers before you draw anything
Ask what exactly declined, by how much, and over what period: absolute profit or margin percentage, and versus last year or versus plan. Ask whether it is the whole company or one unit, and confirm the client's target (restore FY25 profit, or hit 12% EBITDA). A case where profit fell 40% in one year is a shock with a single cause; a case where margin drifted down over five years is structural. Write the baseline and current numbers down - you will use them in every calculation later.
- 2
Choose a revenue model that matches the business
Before you split Revenue into Price times Quantity, ask how the company actually makes money. Retail chain: stores times average daily sales. Telecom: subscribers times ARPU. Ed-tech: enrolments times fee times renewal rate. Airline: seats times load factor times yield. Say your choice out loud and flag the assumption. This single move is what makes your tree look like a consultant's and not a textbook's.
- 3
Build the cost side with real line items
Split cost into variable and fixed, then immediately name the four to six actual cost lines of that industry rather than leaving abstract boxes. A useful mental checklist is Make, Sell, Support: production and raw material; sales, distribution and marketing; then overheads like rent, admin, technology and interest. Do not agonise over whether a cost is truly fixed or variable - what matters is describing how it behaves as volume changes.
- 4
Isolate the branch: revenue problem, cost problem, or both
Ask for revenue and total cost in the base year and the current year, then compute both changes. If revenue is flat and costs are up, the entire case lives on the cost side and you should say so and drop the revenue branch. If both moved, quantify which explains more of the gap. Announce the elimination explicitly: revenue actually grew 15%, so the profit fall is being driven by cost or by mix, let me go down that branch.
- 5
Segment until the average breaks
Averages hide problems. Cut the surviving branch by product line, geography or store, customer segment, channel (own store vs marketplace vs distributor), and time period. Usually one segment causes most of the damage while the rest are fine - that is your root cause. Ask for the mix in percentage terms, not just totals, because a shift towards a low-margin product or channel destroys profit even when every individual price and cost is unchanged.
- 6
Check whether it is the firm or the whole industry
Ask whether competitors' margins moved the same way. If the entire industry is down, the cause is external - input cost inflation, a new duty or GST change, a price war, a substitute technology - and the recommendation is about repositioning or cost structure, not fixing an internal failure. If only the client is down, the cause is internal: their specific pricing, procurement, capacity utilisation, or channel decisions.
- 7
Quantify the leak and size the fix
Convert the root cause into a rupee number: the mix shift to delivery cost us roughly Rs 96 crore of contribution, which is more than the Rs 51 crore profit gap. Then size each recommendation the same way, so the interviewer sees which lever closes the gap and which is noise. Always sanity-check that your identified drivers roughly add up to the total decline - if they explain only 20% of it, you have not found the real cause yet.
- 8
Recommend, then stress-test
Close with a clear answer first, two or three prioritised actions with expected rupee impact and time to impact, and then the risks. Standard levers: raise price or improve mix, reduce variable cost per unit through procurement or process, spread fixed cost through higher volume or utilisation, and exit or fix the loss-making segment. Name the risk on each - a price rise can cost volume, a cost cut can hit quality or brand, an exit can strand fixed costs.
Worked example
Your client is a listed Indian quick-service restaurant chain with 400 outlets across tier-1 and tier-2 cities, selling biryani and North Indian meals. In FY25 it did Rs 1,200 crore of revenue and Rs 120 crore of EBITDA, a 10% margin. In FY26 revenue grew to Rs 1,380 crore but EBITDA collapsed to Rs 69 crore, a 5% margin. The CEO is confused: sales are up 15%, so why has profit halved? The ask is to restore FY25 profit levels within 18 months.
Frame the tree for a restaurant, not a generic factory
Model revenue as number of outlets times orders per outlet per day times average order value, rather than a vague Price times Quantity. Costs for a QSR are food cost, rent, store staff, aggregator commission, packaging and delivery, marketing and discounts, and corporate overhead. Stating this structure up front already signals that you understand the business.
Split the gap: revenue or cost?
Revenue rose Rs 180 crore while EBITDA fell Rs 51 crore, so total cost rose Rs 231 crore against a Rs 180 crore revenue increase. Costs grew far faster than sales. This kills the naive sales-are-falling hypothesis. The case lives on the cost side, or on a mix shift dragging revenue quality down.
Segment: where did the extra cost come from?
Ask for the split of orders by channel. Dine-in was 70% of sales in FY25 and only 50% in FY26; delivery through food aggregators went from 30% to 50%. Total orders went from about 2.4 crore to about 2.76 crore at a steady average bill of Rs 500. So volume genuinely grew, but the growth came entirely through the delivery channel.
Compute unit economics per channel
A dine-in order: bill Rs 500, food cost Rs 160, contribution Rs 340. A delivery order on the same Rs 500 bill: aggregator commission at 22% is Rs 110, the client's share of platform discounts is Rs 40, packaging and delivery materials are Rs 25, food cost is Rs 160, so contribution is Rs 165. Every order that moves from dine-in to delivery destroys Rs 175 of contribution.
Quantify the leak and check it adds up
The mix shift is 20 percentage points of 2.76 crore orders, roughly 0.55 crore orders moving to a channel worth Rs 175 less each, about Rs 96 crore of contribution lost. Against that, the extra 0.36 crore orders of volume growth added roughly Rs 45 crore. Net effect is about minus Rs 51 crore, which matches the EBITDA gap exactly. The mix shift is the root cause, not inflation and not weak cost control.
Check the second-order effect
Confirm the fixed-cost side too. Rent and store staff did not fall even though 20 percentage points of demand moved out of the dining room, so the client is paying full dine-in real estate to serve delivery orders. Also check the 40 new tier-2 outlets added in FY26 - if their average daily sales are below the network average they dilute margin further while adding fixed rent.
Recommend with sized impact
One, price the delivery menu 8-10% above the dine-in menu, an industry-standard practice, recovering roughly Rs 35-40 per delivery order. Two, shift 15% of delivery volume to the client's own app and WhatsApp ordering where there is no 22% commission - each point of channel shift is worth roughly Rs 8 crore. Three, stop funding deep discounts on the aggregator and renegotiate the commission slab using the volume the client now brings. Four, convert dining space in the 40 weakest dine-in outlets into smaller delivery-first kitchens to cut rent per order. Risks: an aggregator can de-prioritise your listing if you raise prices or cut discounts, and own-app adoption in India is slow without a real loyalty hook.
Takeaway: Revenue growth can hide a profit collapse. When margin falls while sales rise, the answer is almost always mix - a shift towards a lower-contribution product, customer or channel - and you find it by computing unit economics per segment instead of staring at company totals.
More worked examples
Worked example: Intel's margin collapse (2021 to 2024) — a fixed-cost absorption case+
Intel is the classic case of profit falling while the industry around it boomed. On publicly reported figures, Intel's revenue slid from roughly $79 billion in 2021 to roughly $53 billion in 2024, and gross margin fell from the mid-50s percent to the mid-30s. In 2021 it earned about $20 billion of net income; in 2024 it reported a GAAP net loss of roughly $19 billion after impairments and a tax valuation allowance. Meanwhile the semiconductor industry as a whole was in the middle of the biggest boom in its history on the back of AI. All figures below are approximate, drawn from public filings and press reporting, and are used illustratively to show the framework working — not as precise audited numbers.
Revenue 2021 → 2024 (approx.)
~$79B → ~$53B
Gross margin (approx.)
~55% → ~mid-30s%
Intel Foundry 2024 (approx.)
~$17.5B revenue, ~$13B operating loss
Capex per year, 2022-24 (approx.)
~$24-25B
Announced 2024 headcount cut
~15% (~15,000 roles)
Nail the objective and the baseline numbers before drawing anything
Two things need pinning down: what fell, and over what period. This is not a one-year shock with a single cause; it is a three-to-four-year structural slide, roughly $26 billion of revenue and about 20 percentage points of gross margin. That immediately tells you not to go hunting for a one-off event like a bad quarter or a customer loss. State the objective as the client would: restore double-digit operating margin, and decide whether the manufacturing business is worth keeping. Write down the two anchor numbers — revenue down about a third, gross margin down about 20 points — because every later calculation is checked against them.
Choose a revenue model that matches a company that owns its own factories
Price times Quantity is useless across thousands of SKUs from laptop chips to server CPUs. The right model has two layers. Revenue equals units shipped times average selling price, split by segment: client PC chips, data-centre chips, and external foundry work. But the cost model has to be wafer-driven: wafers started times die per wafer times yield, against a fab cost base that is overwhelmingly fixed. Saying this out loud sets up the whole case, because in semiconductors gross margin is mostly a story about how full the fabs are, not about what you paid for raw silicon.
Isolate the branch — and find that both branches are bleeding
Revenue fell about $26 billion, which at a 55 percent gross margin is roughly $14 billion of lost gross profit on its own. Separately, gross margin percentage fell about 20 points, which on the current $53 billion base costs another $10 billion or so. So this is not a revenue case or a cost case; it is a revenue case that mechanically caused a cost case. That link is the whole insight: fewer wafers through a fab whose depreciation, cleanroom, and staffing do not shrink means the fixed cost per unit rises. A fixed-cost-heavy business gets punished twice by a volume decline — once in lost contribution, once in unabsorbed overhead.
Build the cost side with real semiconductor line items
Do not leave two boxes labelled fixed and variable. The real lines are: wafer and materials cost (semi-variable), fab depreciation on roughly $25 billion a year of capex (fixed and rising), start-up costs for each new process node before it produces sellable volume (fixed and painful), R&D at roughly $16 billion a year, plus SG&A. Note the direction of travel: Intel was building five new nodes in four years and multiple new fabs, so depreciation and pre-production start-up costs were climbing at exactly the moment volume was falling. A candidate who names start-up costs and depreciation, rather than saying 'costs went up', is demonstrating industry knowledge.
Segment until the average breaks — Products versus Foundry
The company-level margin is a blended average that hides two completely different businesses. Once Intel began reporting Foundry separately, the picture was stark: in 2024, Intel Products did roughly $47-49 billion of revenue and still earned around $11-12 billion of operating income, a perfectly respectable design business. Intel Foundry did about $17.5 billion of revenue (mostly internal transfers) and lost roughly $13 billion. Cut Products further and the damage concentrates again: the PC segment was soft post-Covid, but the data-centre segment is where share was genuinely lost, as AMD moved from single-digit to roughly a quarter of server CPU units and, more importantly, data-centre budgets shifted from CPUs to Nvidia GPUs. So: one loss-making manufacturing arm, plus one structurally shrinking end-market inside an otherwise profitable products arm.
Check whether it is the firm or the industry
This is the step most candidates skip, and here it flips the whole recommendation. Over the same period TSMC's gross margin stayed in the 50s, Nvidia's ran around 75 percent, and AMD was gaining share — the industry was up, not down. Therefore the cause is internal, not an input-cost shock or a sector-wide price war. Trace it back and the root cause is a process-technology delay: missing the 10nm and 7nm timelines meant losing product competitiveness, which lost volume, which left expensive fabs underloaded, which crushed gross margin. One internal technical failure propagates through the entire profit tree — that is what a root cause looks like.
Quantify the leak, size the fix, and stress-test it
The two sized levers match the two segments. On Foundry, roughly $13 billion of annual operating loss can only be closed by filling the fabs with external customers or by shrinking the fab footprint — which is precisely why Intel separated Foundry into a subsidiary, courted external customers, cut capex, and slowed or shelved fab projects. On the fixed-cost base generally, the announced roughly 15 percent headcount reduction, a roughly $10 billion cost-reduction target, and suspending the dividend are all about buying time. The stress test is uncomfortable and worth saying aloud: the capex you cut to fix this year's margin is the same capex that funds the process node that restores competitiveness in three years. Cutting fixed cost in a technology race can be the move that guarantees you keep losing.
Takeaway: In a business where most costs are fixed, a revenue decline is charged to you twice — lost contribution plus unabsorbed overhead — so 'cost control' can never close the gap. The only real answers are fill the capacity or shrink the capacity, and the framework's job is to tell you which segment's capacity is the problem. It also shows why the firm-versus-industry check is not optional: because every peer's margin rose while Intel's fell, no external explanation survives, and the diagnosis has to be internal.
Worked example (India case-interview style): a two-wheeler NBFC whose profit fell two-thirds while its loan book grew 25%+
Your client is a mid-sized non-banking financial company headquartered in Pune that finances two-wheelers, largely through dealership tie-ups across Maharashtra, MP, UP and Bihar. Assets under management grew from about Rs 4,500 crore (FY24 average) to about Rs 5,600 crore (FY26 average). Over the same two years profit after tax fell from roughly Rs 179 crore to roughly Rs 59 crore. The promoter's framing in the room: 'The book is growing 25 percent, disbursements are at an all-time high, and my profit has fallen by two-thirds. Where is the money going?' Target: get PAT back above Rs 150 crore within six quarters. All figures are illustrative and constructed for the case.
Average AUM FY24 → FY26
Rs 4,500 cr → Rs 5,600 cr
NIM (yield minus cost of funds)
12.7% → 9.8%
Credit cost (% of avg AUM)
2.8% → 3.6%
PAT
Rs 179 cr → Rs 59 cr (illustrative)
Problem cohort
~30% of book, ~70% of credit losses
Nail the objective and the baseline before touching the tree
Confirm the shape of the decline: PAT down about Rs 120 crore, which at a 25 percent tax rate is a pre-tax gap of roughly Rs 160 crore, over two years, while AUM grew about 24 percent. Confirm there is no one-off — no fraud write-off, no merger, no accounting change. Confirm the metric the promoter actually cares about: he is talking in absolute profit, but the right lens for a lender is return on assets, and on these numbers RoA has fallen from roughly 4.0 percent to roughly 1.1 percent. Say that out loud early; it reframes the case from 'we lost Rs 120 crore' to 'every rupee of book is now earning a quarter of what it did', which is a very different problem.
Throw away Price times Quantity — build a lender's profit tree
A lending business has no units and no price in the manufacturing sense, and a candidate who draws P times Q here loses the room in minute two. The right tree is: Profit before tax = Net interest income + Fee income − Operating expenses − Credit cost. Net interest income itself equals average AUM times net interest margin, where NIM is yield on advances minus cost of funds. Flag the simplification honestly — cost of funds strictly applies to borrowings, not the whole book, so treating NIM as a spread on AUM is a working approximation. Now every line is something you can ask a number for, and each maps to a different real-world failure: pricing, funding, productivity, underwriting.
Bridge the Rs 160 crore pre-tax gap line by line
Ask for each driver in both years. Net interest income: 12.7 percent of Rs 4,500 crore is about Rs 572 crore in FY24, versus 9.8 percent of Rs 5,600 crore, about Rs 549 crore, so NII is down about Rs 23 crore despite a much bigger book. Fee and insurance-commission income fell from about 0.9 percent to about 0.4 percent of AUM (Rs 41 crore to Rs 22 crore), costing about Rs 18 crore after the client stopped aggressively bundling insurance. Operating expenses rose from 5.5 percent to 5.2 percent of AUM in ratio terms but from Rs 248 crore to Rs 291 crore in absolute terms, costing about Rs 44 crore. Credit cost went from 2.8 percent to 3.6 percent of AUM, Rs 126 crore to about Rs 202 crore, costing about Rs 76 crore. Total: about Rs 161 crore against a Rs 160 crore gap — the bridge closes, so you have found all the drivers and can now rank them.
Decompose the NIM line into a volume effect and a rate effect
NII barely moved in total, which naively looks harmless — but that is an average masking two large opposing forces, and this is where most candidates stop too early. Holding the old margin constant, growing the book by Rs 1,100 crore should have added about 12.7 percent of Rs 1,100 crore, roughly Rs 140 crore of extra NII. Instead, spread compression of 290 basis points on the full Rs 5,600 crore book destroyed about Rs 162 crore. So the growth the promoter is proud of did earn Rs 140 crore — it was simply handed straight back through pricing and funding. Splitting further: yield on advances fell from about 21.5 percent to 20.0 percent because of aggressive OEM-subvented schemes and competition from bank captives, while cost of funds rose from about 8.8 percent to 10.2 percent as the rate cycle turned and the client's credit rating stayed put.
Segment credit cost until the average breaks
Rs 202 crore of credit cost across a Rs 5,600 crore book averages 3.6 percent, which sounds survivable — but averages hide the problem. Ask for delinquency cut three ways: by sourcing channel (direct and repeat customers versus dealer-DSA sourced), by geography, and by disbursement vintage. The answer: loans written in the FY25 growth push through dealer-DSA channels in tier-3 UP and Bihar, at loan-to-value ratios above 90 percent and to first-time borrowers with no bureau history, are about 30 percent of AUM but generate about 70 percent of the losses — roughly 8 percent credit cost against about 1.7 percent for the rest of the book. Compute the contribution of that cohort properly: on Rs 1,700 crore it earns roughly 22 percent yield, but after about 10 percent cost of funds, about 8 percent credit cost and heavier collection opex of about 6 percent, it is earning close to nothing and consuming capital. The client grew its way into a loss.
Split the causes into external and internal — the recommendation depends on it
Test each driver against the industry. Cost of funds rising roughly 140 basis points is largely external — the rate cycle plus tighter bank lending to NBFCs hit every peer, so the recommendation there is about funding structure, not blame. Credit cost is the opposite: peer two-wheeler financiers were running roughly 2.5-3.0 percent, so the client's 3.6 percent blended and 8 percent on the problem cohort is firm-specific and therefore fixable. Yield compression sits in between: sector-wide competition is real, but the client chose to chase volume in the thinnest-margin schemes. That split matters because it tells you which levers are genuinely in management's control, and stops you recommending a cost-cutting exercise for a problem the whole market shares.
Recommend answer-first, with sized impact and named risks
Headline: the profit fall is not a growth problem, it is that roughly a third of the new book was underwritten at prices that never covered its risk — fix that cohort and about Rs 90-100 crore of pre-tax profit comes back. One, stop new dealer-DSA sourcing above 85 percent LTV for no-bureau customers and let that book run down by half; at roughly 8 percent credit cost on Rs 850 crore, that alone saves about Rs 65 crore a year and frees capital. Two, reprice what you retain in that segment by 150-200 basis points, worth roughly Rs 25-30 crore, since these borrowers are rate-insensitive and payment-EMI-sensitive. Three, attack cost of funds with co-lending and direct assignment with a bank partner on the prime slice of the book — moving 20 percent of AUM off balance sheet at a 150 basis point funding advantage is worth roughly Rs 17 crore, plus capital relief. Four, cut collection opex by pushing e-NACH and UPI autopay penetration, since field collection cost per case is what drove opex up in absolute terms. Risks to name: dealers may push volume to a competitor if you tighten, so protect relationships with faster sanction turnaround instead of loose credit; and shrinking the book raises the fixed-cost-per-rupee-of-AUM ratio, so the opex action has to run alongside the de-risking, not after it.
Takeaway: Growth is not the same as profitable growth, and in lending the two can move in opposite directions for two full years before the P&L shows it — because interest is booked immediately while credit losses arrive 12 to 18 months later. The framework's payoff here is twofold: customising the tree to a lender (NIM, fee, opex, credit cost) instead of forcing Price times Quantity, and refusing to accept the flat net-interest-income line at face value — splitting it into a +Rs 140 crore volume effect and a −Rs 162 crore rate effect is what turns 'nothing happened here' into the real story.
Common pitfalls
- •Reciting the whole tree instead of using it to eliminate. Analysing revenue and cost and every sub-branch burns your 30 minutes and finds nothing. Ask one question, kill one branch, go deeper on the survivor.
- •Using a generic Price times Quantity model for a business where it means nothing. An average price across 8,000 supermarket SKUs, or across a hospital's procedures, is a meaningless number and sends your analysis nowhere.
- •Leaving cost as two empty boxes labelled Fixed and Variable. Interviewers read that as zero industry knowledge. Name the actual cost lines the client incurs.
- •Jumping to solutions before locating the root cause. Suggesting a price increase in minute four, before you know whether the problem is even on the revenue side, is the most common reason candidates fail this case type.
- •Ignoring mix. If price is unchanged and unit costs are unchanged, most candidates conclude nothing is wrong, while a shift towards a low-margin product, channel or customer quietly eats the entire margin.
- •Never checking the external environment. If every competitor's margin fell the same way, an internal cost-cutting recommendation is the wrong answer and you look naive for missing the industry-wide shock.
Interview tips
- •Say the equation and the two branches out loud, then immediately ask a splitting question: do we know whether revenue or cost drove the decline? This gets you data in minute two instead of minute ten.
- •Always ask for the time period and whether the decline is absolute profit or margin. A 20% profit fall on flat revenue is a cost case; a 20% margin fall on 15% revenue growth is almost always a mix case.
- •Anchor every hypothesis in a number. Costs rose Rs 231 crore against Rs 180 crore of extra revenue is worth ten qualitative sentences and shows you are actually driving the case.
- •When you find the culprit segment, verify it explains most of the gap before recommending anything. If your driver accounts for only a fifth of the decline, keep digging.
- •Keep a running MECE check on your tree: every rupee of cost should sit in exactly one box. Interviewers probe for overlaps like counting delivery commission under both marketing and distribution.
- •Close answer-first: recommendation in the first fifteen seconds, then two or three sized actions, then risks. Indian MBB and Big Four interviewers are strict about this and will cut you off if you build up to the answer.
Test yourself
Best video explainers

Consulting Case Interview: A Profitability Case Study with ex-BCG Consultants
Prepmatter
A full end-to-end mock of a profitability case with an ex-BCG consultant - the best way to watch the tree used to eliminate branches in real time.

Hack the Case Process - Most Important Framework to Understand for Case Interviews (Profitability)
Essentials Explained
A tight, teaching-first explanation of the profit tree from an ex-Bain manager. Start here if you have never built one before.

Better Profitability Cases: 3 Alternative Revenue Models To Impress In Your Case Interviews
CraftingCases
Shows how to replace the default Price x Quantity with the revenue model the business actually runs on - the single move that makes your tree look consultant-built.

Profitability Case Study Interview Example - Solved by Ex-McKinsey Consultant
CraftingCases
A full auto-manufacturer case (margin 5% to 2.5%) solved end to end, including the follow-up questions that trip up most candidates after the diagnosis.

Profitability case interview: Fix Chili’s (w/ McKinsey & EY Consultants)
rocketblocks
A live restaurant-chain profitability case with real-time feedback - great for seeing segmentation and cost line items applied to a business you already understand.
Go deeper
Profitability Framework and Profit Trees: The Complete Guide
Crafting Cases
The deepest free guide on customising the tree to the business model - supermarkets, apps, mining, consulting - plus a four-step process for building one live.
Profitability Case Interview: Step-By-Step Guide
Hacking the Case Interview
Practical step-by-step walkthrough with worked numeric examples and a clear list of the questions to ask at each layer of the tree.
Profitability Cases - How to Approach One of the Most Common Cases
PrepLounge
Free basics article plus a large library of peer-practice profitability cases you can actually drill with a partner.
6 Variants of the Profitability Framework
MConsultingPrep
Shows how the same tree adapts across six different situations, and warns against going deeper than layer two before you know which branch holds the root cause.
Now use it on a real case
Reading a framework isn't the same as applying it under pressure. Practise with an AI interviewer that pushes back.
Practise a case free