The Profitability Framework Beyond Revenue minus Cost
If your profitability tree only branches into revenue and cost, you are leaving the most interesting moves on the table. Here is what a partner-level structure actually looks like.
The default candidate response to a profitability case is some version of: "Profit equals revenue minus cost. Let me break each side down." That is true. It is also where most candidates plateau.
A profit-equals-revenue-minus-cost tree feels like structure but does not give you anywhere to go. You end up listing every revenue stream and every cost line until you run out of time, and the interviewer politely cuts you off and asks what you think the problem actually is.
What a strong profitability structure does
The job of the structure is not to be exhaustive. It is to give you a path: a sequence of buckets you can prioritize between, so that within 90 seconds of seeing the data you can say "the issue is X, here is why, here is what I would test next."
That means your tree needs three things:
- A unit-economics layer. Per unit, per customer, per transaction โ whatever the business actually sells in.
- A volume layer. How many of those units, and driven by what.
- A mix layer. What the unit looks like is not fixed โ it is an average of segments, products, or channels that may be moving in opposite directions.
The four-branch decomposition
For most cases, a cleaner tree looks like this:
- Price. List price, realized price after discounts/promo, price elasticity by segment.
- Volume. Customers ร frequency ร units per transaction. Each of those drivers has its own driver.
- Variable cost per unit. COGS, fulfillment, any cost that scales with volume.
- Fixed cost. Overhead, R&D, fixed marketing, rent. These do not scale per unit and behave differently in a downturn.
The reason this beats "revenue minus cost" is that price and volume move independently and often in opposite directions. A 5% price cut that drives 8% volume is a different conversation from a 5% price cut that drives 2% volume. If your tree merges them into "revenue", you cannot have that conversation.
Where mix breaks the model
Once you have the four-branch tree, the next move that separates strong candidates is asking about mix at every level. A few patterns you should be ready for:
- Customer mix. Are we losing the high-margin enterprise customer and gaining low-margin SMB?
- Product mix. Is the category growing because the cheap SKU is taking share from the premium SKU?
- Channel mix. Direct vs reseller margins differ by 15โ30 points in many businesses; a channel shift can move blended margin without anyone changing their price.
- Geographic mix. Same product, different willingness-to-pay and cost-to-serve.
The signal interviewers look for
At the partner round, what gets you noticed on a profitability case is not the framework itself. It is whether, after looking at the first slide of data, you can immediately go: "this is mix. Let me rebuild the analysis on a same-product, same-channel basis." That kind of pattern recognition only develops if your structure has room for mix in the first place.
One concrete drill
Take any cases you have already practiced and re-do the math with a deliberate mix shift baked in: the customer base added 30% SMB-tier accounts at 8% margin while losing 10% of enterprise accounts at 28% margin. Rerun the profitability story. You will find that "revenue is up, profit is down" stops being mysterious and starts being mechanical โ which is exactly the muscle the case is testing.
Why Most Candidates Botch Market Entry Cases
The next-most-tested case type, with the six failure modes that separate offer-getters from runners-up.
One short, useful email per week.
New case frameworks, mock interview tactics, and recruiting intel from the CaseGrade team. Built for serious candidates โ no fluff, no upsell every paragraph.
Unsubscribe anytime. We never share your address.
Keep reading
All articles โThe State of Consulting in 2026: AI Delivery, Flat Entry Pay, and What Candidates Should Care About
Six things are shifting at once inside the consulting industry. Most of them are being talked about loudly. A few are being talked about quietly. Candidates who only track the loud ones are missing the more important story.
McKinsey Solve in 2026: Red Rock, Sustainable Future Lab, and What Actually Improves Your Score
McKinsey's digital assessment got a third module in late 2025. The good news: the underlying skills haven't changed. The bad news: most of the prep advice on the internet hasn't caught up.
What AI Case Interviewers Can โ and Can't โ Evaluate
Several AI case-prep tools have launched in 2026. Some are genuinely useful. Some are thin wrappers. The difference is what they can score honestly and what they have to hand-wave through.