How to stand out in a case interview by nailing the ending
The last 60 seconds of your case interview matter more than most candidates think.
I see this all the time in mock cases. A candidate will crush the analysis, find the right insight, and then fumble the landing by going back to the beginning and narrating the whole thing. They walk through what they found, repeat their structure, and wrap up with something safe.
The interviewer already heard all of that. Repeating it doesn't add anything.
The instinct to summarise makes sense. You want to show you did thorough work. But a summary isn't what the interviewer is looking for at this point. They want to see whether you can take everything you've learned and turn it into something actionable. That's what consultants do every day when they present to clients.
Why the closing matters so much
Think about what happens in a real engagement. You've spent weeks doing analysis. You have a 30-minute slot with the client's CEO. You don't walk in and explain your process from the beginning. You lead with the answer, back it up with evidence, flag what could go wrong, and tell them what to do next.
The case synthesis is a compressed version of exactly this. The interviewer already knows what you found. What they want to see is whether you can think like someone who would actually deliver the recommendation to a client.
Most interviewers have already formed a view of your analytical ability by the time you reach the closing. What they're watching for now is judgment, clarity, and presence. A strong close can elevate an average case performance. A weak one can undermine a strong one.
The structure that works
There are four parts to a good synthesis. In this order:
- Lead with your recommendation. One clear sentence. Don't hedge, don't build up to it. Say what the client should do. "I would recommend that [Client] enters the market through an acquisition rather than organic growth."
- Give two or three supporting reasons. Pull these directly from your analysis. These should be the strongest pieces of evidence you uncovered, not a retelling of every branch you explored. Pick the reasons that most directly support the recommendation and state them concisely.
- Flag a risk. This is the part most candidates skip, and it's the part that separates good answers from great ones. Identify one risk or assumption that would need to hold true for your recommendation to work. "The main risk I'd flag is integration complexity. If the target company's operations are harder to absorb than our initial assessment suggests, the cost synergies may take longer to materialise."
- Define a next step. Tell the interviewer what you'd want to investigate if you had more time. This shows you know where the gaps in your analysis are and that you're thinking beyond the immediate question. "If I had more time, I'd want to do deeper due diligence on the target's customer retention rates to validate the revenue assumptions."
That's it. Recommendation, reasons, risk, next step. The whole thing should take 45 to 60 seconds.
What this sounds like in practice
Here's an example of a clean closing for a market entry case:
"Based on my analysis, I'd recommend that FreshCo enters the German market through a partnership with an established local distributor rather than building its own distribution network.
Three reasons. First, the upfront capital requirement for owned distribution is roughly three times higher and would stretch the company's balance sheet. Second, the regulatory environment favours local operators, and a partnership gives us immediate compliance. Third, the target partner, GreenLogistik, already has relationships with the top five retail chains, which would cut our time to market from 18 months to roughly six.
The key risk is dependency. If the partnership doesn't work out, switching costs would be high and we'd lose 12 to 18 months rebuilding. I'd want to negotiate strong contractual protections upfront.
If I had more time, I'd dig into GreenLogistik's financial health and customer satisfaction scores to make sure they're a reliable long-term partner."
Notice what's not in there. No "So, to summarise what I found..." No walking through the structure from the beginning. No restating the problem. The interviewer knows the problem. They want to know what you'd do about it.
Common mistakes to avoid
Starting with "So, to summarise..." This signals that you're about to repeat yourself. Start with the recommendation instead.
Hedging too much. "I think maybe the client could potentially consider..." is not a recommendation. Have a point of view. You're allowed to be wrong, but you're not allowed to be vague.
Skipping the risk. Candidates worry that flagging a risk makes their recommendation look weaker. It does the opposite. It shows you're thinking critically and that you understand real business decisions always involve uncertainty.
Making it too long. If your closing is running past 90 seconds, you're including too much. Be ruthless about what you cut. The interviewer can always ask follow-up questions if they want more detail.
Forgetting the next step. This is what separates a complete answer from one that just trails off. Defining a next step shows you know the analysis isn't finished, and you know what would make it better.
How to practise this
Don't just practise full cases. Practise the synthesis separately.
Take any case you've already worked through and close your notes. Then give yourself 60 seconds to deliver a recommendation, reasons, risk, and next step from memory. Record yourself if you can.
The first few times it will feel rushed and incomplete. That's normal. The structure becomes natural after you've done it 15 or 20 times. Eventually you stop thinking about what comes next and start focusing on making each part sharper.
The candidates who practise this separately are almost always the ones who deliver it cleanly under pressure. The ones who don't practise it assume they'll figure it out in the moment, and it rarely works out that way.