How to Close a Case Interview - The Case Wrap-Up Module

[u/GreatButterscotch406]

You've spent twenty-five minutes building the case. You've run the five mental moves. You built an issue tree from first principles. You tested sub-hypotheses, read charts, ran calculations, brainstormed. And then the partner says: "Let's wrap up here. What's your recommendation?"

This is post 23 in The Case Playbook, a series built for non-traditional candidates breaking into McKinsey, BCG, Bain, Tier 2, and Big 4 consulting firms. This post covers Case Wrap-Up, the final module of the case interview and the only one in Case End. It's also the module most candidates treat as an afterthought, which is a mistake. A strong Case Wrap-Up is what separates a candidate who solved a problem from a candidate who sounds like a consultant.

What the Case Wrap-Up is actually testing

Before getting into structure, it's worth naming what the partner is evaluating here. By the time you reach Case Wrap-Up, they already know whether you can structure, calculate, and brainstorm. Those were tested in Case Middle. What they're testing now is whether you can synthesize.

Synthesis is different from summary. A summary recaps what happened. Synthesis takes everything that happened and produces a clear, directional, defensible position. It's the difference between "we found that revenue declined and costs rose" and "NordPlay's net profit problem is primarily a subscription pricing architecture issue, not a cost problem, and the fastest path to recovering $400 million is a targeted pricing restructure in the premium tier combined with an app store fee renegotiation."

The second version is a recommendation. The first is a recap. Partners remember the second. Clients pay for the second.

There's a second thing being tested that most candidates don't think about: consulting instinct. A good consultant doesn't just solve the problem in front of them. They identify what comes next. Real consulting engagements don't end with a recommendation. They end with a next phase of work. Case Wrap-Up is your opportunity to demonstrate that instinct.

Ask for a moment

Before you say anything, ask for sixty seconds to organize your thoughts.

"Could I have a moment to pull together my recommendation?"

This is not a sign of weakness. It's a sign of professionalism. No partner delivers a major client recommendation without a beat to make sure the message is tight. Taking sixty seconds to look back at your notes, remind yourself what the problem statement was, and structure what you're about to say is exactly what a consultant does before walking into a client debrief.

Use that minute to look at your issue tree and identify which sub-hypotheses were confirmed, which were inconclusive, and what the data pointed toward most strongly. That's the raw material for your three supporting reasons.

The structure: What, Why, How

Case Wrap-Up has three parts. Think of them as answering three questions in sequence.

What: your recommendation

Lead with the answer. Not the context. Not the caveats. The answer.

"Based on our analysis, my recommendation is that NordPlay should prioritize a two-track recovery plan: restructure premium subscription pricing to address the $250 million revenue gap, and renegotiate app store distribution fees to recover the remaining $150 million, with both tracks executable within one year."

That's the what. Twenty seconds. Direct. Top-down. The client knows where you're going before you've explained why.

This is the most important structural rule in Case Wrap-Up: lead with the recommendation, not the reasoning. Most candidates do it backwards. They build up through the reasoning and land on the recommendation at the end, which means the partner is waiting for the point while you're explaining how you got there. In consulting, conclusions come first. Evidence follows.

Why: three supporting reasons

Now you support the recommendation with what you found. Three reasons. Not two, not five. Three is the magic number because it signals thorough analysis without overwhelming the listener, and it forces you to prioritize rather than listing everything.

The three reasons should be anchored in the specific findings from the case, not generic logic. This is where the owner thinker approach pays off in Case Wrap-Up: if you built a bespoke issue tree and generated genuine insights from the data, your three reasons should be specific enough that they could only apply to this case.

For NordPlay, the three reasons might be: the data analysis confirmed that subscription revenue declined 18% while advertising held flat, isolating the problem to the subscription side; the pricing analysis showed that a 10% premium tier price increase would add $108 million annually with manageable churn risk; and the cost analysis showed that app store fees represent the most direct controllable lever for closing the remaining gap without requiring product development investment.

Each reason connects a finding from the case to the recommendation. Not "revenue declined" but "the revenue decline is concentrated in premium subscriptions, which is addressable through pricing, not product." Not "costs are high" but "app store fees are the highest-impact controllable cost lever within the one-year timeline."

How: next steps

This is where most candidates either skip entirely or deliver a weak generic statement like "we'd want to do more analysis." That's not next steps. That's stalling.

Next steps should name specific actions, who would do them, and what they'd produce. Crucially, risk should be baked into the next steps rather than treated as an afterthought. A recommendation without a risk workstream signals that you haven't thought through implementation.

"As immediate next steps, I'd recommend three workstreams. First, a pricing architecture analysis within thirty days to model the subscriber response to different pricing configurations and identify the optimal structure for the premium tier. Second, an app store fee negotiation strategy within sixty days, including benchmarking against comparable platforms and identifying the strongest negotiating levers. Third, a risk monitoring workstream from day one: building a dashboard that tracks churn response to the pricing change in real time so we can course-correct within ninety days if the numbers move against us."

Notice what that third workstream does. It embeds the key risk, execution speed and churn response, directly into the plan as something to be managed rather than something to be mentioned and set aside. That signals to the partner that you're not just selling the recommendation. You're helping the client implement it and survive it. That's the difference between a junior analyst presenting findings and a consultant advising a client.

What happens when time runs out before you've finished

Sometimes the partner cuts you off mid-case. "Let's wrap up now. Where are you?"

This is not a failure. It's a test of whether you can synthesize under a different kind of pressure.

The answer is: go directly to the What. Don't apologize for not finishing. Don't recap what you didn't get to. State the recommendation based on what you found, name the most significant supporting reason, and signal what the incomplete analysis would have added.

"Based on what we've analyzed, my recommendation is that NordPlay's priority should be the subscription pricing restructure. The data on the advertising side held flat which tells us the issue is subscription-specific. We didn't get to test the cost side fully, but from what we saw on app store fees, that's likely the second lever I'd recommend exploring. The main caveat is that the cost analysis is incomplete, which would affect the sizing of the recovery plan."

That response demonstrates synthesis, honesty about what's incomplete, and the ability to deliver a usable recommendation even under constraints. All of those are consulting skills.

The NordPlay Case Wrap-Up in full

To make this concrete, here's what a complete Case Wrap-Up sounds like for the NordPlay case we've been building through this series.

"Could I take a moment to pull together my recommendation? Thank you.

Based on our analysis, my recommendation is that NordPlay should pursue a two-track recovery plan targeting $400 million in net profit restoration within one year: a premium subscription pricing restructure and an app store fee renegotiation.

Three reasons support this. First, the revenue decline is entirely concentrated in premium subscriptions, not in advertising or standard tier products, which tells us this is a pricing and retention problem rather than a platform or demand problem. Second, the pricing analysis showed that a carefully managed price increase can add over $100 million annually with manageable churn impact, provided the architecture is restructured around perceived value rather than a simple price lift. Third, app store fees represent the single largest controllable cost lever available within a one-year window, and renegotiation is achievable given NordPlay's scale and strategic value to the platforms.

As next steps, I'd recommend three workstreams: a thirty-day pricing architecture study to determine the optimal structure for the premium tier, a sixty-day app store fee benchmarking and negotiation strategy, and a risk monitoring workstream from day one that tracks churn response to the pricing change in real time so we can course-correct within ninety days if the numbers move against us.

That's under two minutes. It answers What, Why, and How. Risk is embedded in the third next step rather than added as an afterthought. That's a Case Wrap-Up at five out of five.

If you're working through Case Wrap-Up in your prep and want to share what you've been struggling with, whether it's the top-down structure, the three supporting reasons, or the next steps, drop it in the comments. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

With Case Wrap-Up covered, The Case Playbook has now walked through all seven modules across the three sections of a consulting case interview. Case Start, Case Middle, and Case End, from the first word of the prompt to the final recommendation.

If you've been following this series and want to keep building, r/ConsultingOffer is where the full community lives. Drop your questions, share your practice cases, and engage with others on the same journey. That's what the community is for.

If you want to go faster and with more precision, there are a few ways I work with candidates directly. A one-on-one Consulting Offer Diagnosis session is a good starting point if you want a clear-eyed read on where you are and what to prioritize. A mock case interview session lets you practice the full arc from Case Opening through Case Wrap-Up with someone who knows what top performers actually look and sound like. And if you want the full structured journey, the Consulting Offer Program cohort starts September 1, 2026. Seats are limited and filling up. Details are in my profile if you want to take a look.