The core equation behind the framework
Profit equals revenue minus cost. Every profitability case, whether it's about declining profits, a new investment decision, or evaluating a business unit, comes back to this equation. The skill isn't knowing the equation, it's knowing how to break each side of it down into specific, checkable drivers that let you diagnose what's actually going on rather than guessing at a cause.
Revenue further breaks down into price multiplied by quantity, and from there into more specific components depending on the business. Cost breaks down into fixed and variable components, and further into specific categories like labor, materials, or overhead. The framework is essentially a tree you keep splitting into smaller, more specific branches until each one is something you can actually get data on and investigate directly.
Breaking down the revenue side
Revenue = Price x Quantity is the starting point, but a strong candidate goes further. Quantity can be broken into number of customers times purchase frequency times units per purchase. Price can be broken into list price, discounts, and product mix if the company sells multiple products at different price points.
- Has price changed recently, or has quantity changed, or both?
- Has the customer base grown or shrunk, or has each customer bought less?
- Has the company shifted toward lower-margin products in its mix?
- Has a specific customer segment or region driven most of the change, or is it spread evenly across the business?
Asking for data on each branch, rather than guessing, is how you narrow down which part of the tree is actually driving the problem, and it keeps your questions focused instead of scattershot.
Breaking down the cost side
Split costs into fixed (rent, salaries, equipment, things that don't change with volume) and variable (materials, commissions, shipping, things that scale with volume). From there, break into specific major cost categories relevant to the business, such as cost of goods sold, labor, marketing, and overhead.
A common mistake is treating cost analysis as an afterthought after spending most of the case on revenue. Costs are just as often the actual driver of a profitability problem, particularly in cases involving supply chain issues, wage inflation, or a change in a key input cost. Give the cost tree the same structured attention you give the revenue tree, rather than treating it as a quick check at the end.
Applying the framework to actually diagnose a case
Once you've laid out the full tree, use it to ask targeted questions rather than guessing at causes. If you're told profit has declined, ask whether it's revenue or cost driven first, using whatever data the interviewer will give you, then drill into the specific branch that shows the change. This is more effective than presenting all possible causes without narrowing based on the facts given.
For example, if revenue is flat but profit has dropped, you already know to focus your questions on the cost side rather than continuing to probe revenue, which saves time and demonstrates that you're actually using the data you're given rather than following a fixed script regardless of what you learn.
A short worked example
A case states a bakery chain's profit dropped 20 percent this year despite flat revenue. Since revenue is flat, focus the tree on costs. Ask about fixed vs variable costs, and learn that flour prices rose 30 percent this year due to a supply issue, while the bakery didn't adjust prices. That single cost driver, isolated by working through the tree systematically rather than guessing, explains the whole case, and points toward the recommendation, such as raising prices or renegotiating supplier contracts.
Going beyond the basic tree when the case calls for it
Some profitability cases require you to think past the standard revenue and cost split, particularly when a qualitative factor is driving the numbers, such as a reputational issue, a new competitor, or a regulatory change. In these cases, use the profitability tree to identify where the financial impact is showing up, then layer in the qualitative context to explain why. A strong answer often connects a quantitative finding, like a specific cost category rising, to a qualitative cause the interviewer reveals when asked the right follow-up question.
Using margin analysis alongside the profit tree
Beyond raw revenue and cost figures, looking at margin, meaning profit as a percentage of revenue, often reveals things absolute numbers hide. A company can grow revenue significantly while margin quietly erodes, which is a different and sometimes more urgent problem than flat or declining revenue. When working through a profitability case, it's worth explicitly asking for margin trends over time in addition to raw revenue and cost figures, since a case built around declining margin despite growing revenue points toward a very different diagnosis and recommendation than one built around outright revenue decline.
Comparing the numbers against an industry benchmark
Where the case provides or allows you to ask for competitor or industry average figures, comparing the client's margin or cost structure against a reasonable benchmark can sharpen your diagnosis considerably. A margin that looks concerning in isolation might actually be normal for that industry, while a margin that looks fine on the surface might be meaningfully behind competitors. Asking for this kind of comparative data, when it's available, shows that you're thinking about the company's performance in context rather than treating its numbers as if they exist in a vacuum.
Turning a profitability diagnosis into an actual recommendation
Finding the driver of a profitability problem is only half the exercise, a strong answer also translates that diagnosis into a specific, actionable recommendation. If rising input costs are eating margin, the recommendation might be renegotiating supplier terms, passing part of the cost increase to customers, or finding an alternative input, and a strong candidate will weigh these options against each other briefly rather than stopping at the diagnosis alone. Interviewers consistently reward candidates who close the loop from cause to recommended action, rather than treating the root cause finding as the end point of the case.