Profitability cases: find the leak before you build the tree
Profit equals revenue minus cost is arithmetic, not a structure. The candidates who win profitability cases narrow to where the money is leaking first, then build a tree around that leak. Worked dialogue and a drill.
- Profit equals revenue minus cost is arithmetic. Everyone in the room already knows it, so opening with it tells the interviewer nothing about you.
- The prompt almost always hands you three facts that narrow the search: when the decline started, whether revenue moved, and whether the industry moved with the client.
- Build a lopsided tree. Three levels deep in the branch your facts point at, one or two everywhere else, with the hypothesis said out loud.
- Most of these resolve on a pair of numbers: what share of the cost or revenue base this thing is, and how far it moved.
On this page
Profitability is the case type prep guides and school casebooks consistently put first, and the one candidates think they have solved. They have memorized that profit equals revenue minus cost, that revenue splits into price and volume, and that costs split into fixed and variable. So does everyone else in the room, including the interviewer.
That equation is arithmetic. It is true for every company that has ever existed, which is exactly why opening with it tells your interviewer nothing about you. The work in a profitability case is narrowing: figuring out roughly where the money is leaking from the facts you already have, then building a tree that goes deep on that part and stays shallow everywhere else.
The equation is not a structure
A structure earns its place by being about this client. If your opening would fit a hospital, an airline and a software company without changing a word, you have described accounting, not a hypothesis. This is the same failure as naming a framework instead of building one, and it costs you the same two minutes of interviewer attention.
The test is simple. Read your opening back and ask whether a competitor could hand in the identical page. If yes, it is not yet a structure.
Hear the difference a real conversation makes
Your first full voice interview is free. No sales call, just a case and a live interviewer.
The prompt already told you where to look
Before you draw anything, mine the prompt. Almost every profitability prompt hands you three facts, and each one narrows the search.
When the decline started, and how fast. A margin that fell off a cliff in one quarter is a different animal from one that has drifted down for three years. Sudden means something discrete happened, a contract, a competitor, a plant, an input price. Gradual means something structural, mix shifting, price eroding, a fixed cost base spread over falling volume.
Whether it is profit or margin, and whether revenue moved. Falling profit with flat revenue is a cost problem or a mix problem, and you can say so out loud in your first sentence. Falling profit with rising revenue is almost always mix or a cost that scales worse than the top line. Falling profit with falling revenue sends you to volume and price first.
Whether the problem is the client's alone. If the whole industry is down, you are looking at a market question and the recommendation will not be "cut costs." If only the client is down, something inside the company or its position moved.
Ask for whichever of the three the prompt withheld. Two clarifying questions here are what let you build a structure shaped by this client's facts rather than by a template, which is the whole difference the first four minutes can make.
Build around the leak
Now the tree. Name every bucket before you open any of them, then go deep where the evidence points and say why you are going there. Three levels, not two, in the branch you have prioritized.
Suppose the prompt says profit fell while revenue held steady, in a business that assembles and ships physical goods. That combination points at cost, so the shallow half of your tree is revenue and the deep half is cost. Under cost you separate what moves with each unit from what does not, then under the per-unit side you separate what you buy from what you do, and under what you buy you name the two or three inputs that actually matter for this product. That is three levels and it is specific to a manufacturer. It would be wrong for a software company, which is the point.
State the hypothesis with it. Not "let us look at costs" but "my hypothesis is that a per-unit input cost rose and was not passed through to price, and I would like to test that first." A named hypothesis gives the interviewer something to confirm or kill, and either answer moves you forward.
What this sounds like
Two things carried that dialogue, and neither was a framework. The candidate used the flat-revenue fact to make the structure lopsided on purpose. And the moment a number arrived, they said what it would mean before computing it, which is what turned an arithmetic step into an insight.
The two numbers that usually end it
Go looking for a pair. A share and a change: what fraction of the cost base or the revenue base this thing is, and how much it moved. Fifteen percent of cost of goods, up 25 percent. Fifteen percent of revenue, down by half.
Ask for both, in that order, and multiply. If the product is small relative to the gap you are explaining, that branch is not your answer no matter how interesting it looks, and you should say so and move on. Candidates lose whole cases by finding a real but minor effect and building the recommendation on it.
Where candidates lose these
Opening with the equation. Two minutes spent reciting revenue minus cost is two minutes the interviewer spends waiting.
A symmetrical tree. Equal depth on every branch means you have not formed a view. Lopsided is the signal that you read the prompt.
Chasing the interesting branch. The declining segment that turns out to be 4 percent of revenue is a distraction. Size the branch before you invest in it.
Cutting costs by reflex. Cost reduction is the answer when cost caused it. When a mix shift caused it, cutting costs makes the product worse and the mix shift faster.
Never naming the cause. Some candidates present five contributing factors and let the interviewer pick. Take the stand. Name the driver, quantify it, and then hedge specifically about what would change your mind.
Drill this
Fifteen minutes, out loud, once a day.
- Invent a client in an industry you do not know well. A regional bakery chain, a container port, a veterinary group.
- Give yourself one prompt fact and only one, for example "profit down 30 percent, revenue up 10 percent."
- Minute 1 to 3: say the two clarifying questions you would ask and why each one narrows the search.
- Minute 4 to 8: name all buckets, then go three levels deep in the one your fact points at. Out loud, no notes to read from.
- Minute 9 to 12: invent a share and a change, do the arithmetic explaining before calculating, and say whether it is big enough to be the answer.
- Minute 13 to 15: give the recommendation, the number behind it, and the one thing that would change your mind.
The rule that makes the drill work is the single prompt fact. It forces you to build a lopsided tree from thin evidence, which is exactly what the first four minutes of a real profitability case demand.
Frequently asked questions
Should I ever start with the profit equation?
You can name it in one clause on the way to something specific, the way you would name arithmetic. What loses points is stopping there, or drawing it out as though it were the structure. The interviewer is waiting for the part that is about this client.
How deep should the tree go?
Three levels in the branch you prioritize, one or two everywhere else. Two levels throughout reads as generic. Three levels everywhere burns your time and the interviewer's patience.
What if the prompt gives me nothing to narrow with?
Then your clarifying questions are the narrowing. Ask what happened to revenue and whether the industry moved with the client. If the interviewer declines to answer, structure around both possibilities explicitly and say which one you would test first and why, which still shows a view.
Is a profitability case always a cost case?
No, and assuming so is a common tell. Flat revenue hides mix shifts, price erosion and volume declines that offset each other. The revenue side deserves a real look whenever revenue is flat rather than growing, because flat is often two moving parts cancelling out.
What if the interviewer hands me a number that kills my hypothesis?
Say so immediately and name what it rules out. "That is smaller than I expected, so materials cannot be the whole story, and I want to look at mix next." Abandoning a hypothesis out loud with a reason is a strength. Quietly steering back toward the branch you already committed to is the failure interviewers are watching for.
Practice this on your own casebook
Upload the casebook PDF you already study with and run its cases as live voice interviews with exhibits and 8-dimension feedback.