How to Solve a Business Case: A 6-Step Guide for High School Students
If you're a high schooler walking into your first business case competition, it can feel a lot like sitting a final exam for a class you never actually took. You're handed a dense packet about a company you've never heard of and asked to produce a recommendation in a few hours, with no lecture notes to fall back on. That gap, between never having done this before and being expected to perform like you have, is exactly where most students freeze.
The good news is that solving a case is a repeatable process, not a talent you're born with. This guide walks through six steps that work whether the company is deciding on pricing, weighing a new market, or trying to explain why profits are falling: how to read the prompt correctly, which framework to reach for depending on the type of problem, and how to turn your analysis into a deck a judging panel will actually follow.
Key takeaways
Covers a 6-step process for solving a business case: reading the prompt correctly, applying the right framework for profitability, market entry, or pricing problems, building a clear deck, and presenting it with confidence
Most points get lost by answering the wrong question or ignoring a stated constraint, not by weak math
Before building a single slide, write down the exact decision the case is asking for in one sentence, then check it against the budget, timeline, and other limits in the prompt
Useful for any student prepping for a first case competition, including students with no prior business background
Start by figuring out which of the three core frameworks, profitability, market entry, or pricing, actually fits your case, since that decision shapes almost everything else you build
What makes a case competition different from a normal class assignment?
A class assignment usually comes with a rubric and one correct path to the answer. A business case doesn't work that way. You're handed a messy, incomplete situation and asked to build a defensible recommendation under real constraints, then defend it out loud in front of judges who are allowed to push back. That's a genuinely different skill from anything a normal exam tests, closer to the kind of judgment you build by doing real work than by studying for one. It's also the same muscle a project-based internship builds: working on an actual deliverable for a real company, with a real deadline and a real manager reviewing your work, instead of a professor grading a rubric. A program like Ladder Internships is built around exactly that kind of experience, pairing students directly with real startups on live projects rather than simulated ones. More on that below.
How does this guide actually break down?
The six steps below split into two halves: the first four get you to a data-backed recommendation no matter what specific problem your case throws at you, and the last two turn that analysis into something a judging panel can actually follow. Steps 1 through 4 cover reading the prompt correctly and then applying whichever of the three core frameworks, profitability, market entry, or pricing, actually matches your case. Steps 5 and 6 cover building the deck and delivering it.
Step 1: Understand what the case is actually asking
One of the easiest ways to lose points in a case competition is to deliver a good solution to the wrong problem. When you first open a case brief, resist the urge to immediately brainstorm marketing campaigns or new app features. Your first job is to separate the surface-level symptoms from the actual business decision you're being asked to make. A case might spend three pages describing declining brand sentiment among a specific age group, when the real decision the CEO needs from you is whether to cut an underperforming product line or shift the marketing budget elsewhere. Pin down exactly what you're being asked to solve before you do anything else.
Next, highlight the constraints. Case prompts always come boxed in by rules: a specific budget, a fixed timeline, an unchangeable regulation. If the prompt states the company has a maximum capital budget of five million dollars and you propose a twenty million dollar supply chain overhaul, judges will tune out before you finish the sentence. Write down the decision you're being asked to make, what's actually causing the problem, what limits your recommendation, and what success would look like, in that order, before you touch a single slide.
Step 2: Apply the profitability framework if the case is about falling profit
Profitability cases are among the most common scenarios you'll run into in a case competition. At its core, profit is just total revenue minus total costs, so when a company's profitability is falling, your job is to isolate which side of that equation is actually causing the problem and recommend a targeted fix.
Start by diagnosing whether the revenue side or the cost side is actually driving the drop, then target your recommendation at that specific cause. On the revenue side, figure out whether a sales drop is coming from falling prices, a shrinking customer base, or a shift toward cheaper, lower-margin items. On the cost side, check whether fixed overhead has crept up, or whether variable costs like raw materials and shipping have risen per unit. Use whatever data the prompt gives you to work out whether the real cause is internal, like inefficient operations, or external, like a price war a competitor started. Once you've isolated the actual driver, aim your recommendation directly at it: renegotiating supplier contracts to cut variable costs, for instance, or adding premium features that justify a higher price, instead of a vague call to "increase profitability."
Step 3: Apply the market entry framework if the case is about a new product or market
When a case asks whether a company should launch a new product or enter a new country, your job is to prove the reward is worth the risk. A strong market entry recommendation answers four questions: how big the market actually is, who already dominates it and how hard they'll fight back, what's keeping new entrants out (high startup costs, strict regulation, technical hurdles), and how you'd actually get in (build from scratch, partner with a local distributor, or acquire a smaller competitor already there).
In most high school competitions you won't have complete market data, and that's fine. Use an assumption-based estimate, sometimes called a back-of-the-envelope calculation: start with a known anchor number, like a country's total population, narrow it down by your target demographic, estimate how often they'd buy, and multiply by an expected price. Judges aren't grading you on hitting the exact dollar figure. They're grading whether the logic behind each assumption actually holds up.
Step 4: Apply the pricing framework if the case is about setting a price
Setting a price means balancing what a product costs to make against what a customer will actually pay for it. Most pricing recommendations lean on one of three models: cost-based pricing, competitive pricing, or value-based pricing. Cost-based pricing adds a standard markup to your production cost. It's safe, but it ignores what customers are actually willing to pay. Competitive pricing benchmarks against rivals, letting you choose to price at a premium, match the market, or undercut it. Value-based pricing prices the product around the actual financial value it delivers to the buyer.
To justify a pricing recommendation, use whatever numbers the case gives you. If a prompt says a software tool saves a client twenty hours of labor a month at thirty dollars an hour, that tool is generating six hundred dollars of monthly value. Pricing it at one hundred fifty dollars a month captures real profit while still leaving four hundred fifty dollars of value on the table for the client, which is the kind of specific, data-backed reasoning that makes a pricing recommendation land.
Step 5: Design a deck judges can actually follow
Your slide deck is the visual backbone of your pitch, and judges review dozens of them in a single afternoon. A dense, text-heavy deck loses their attention before you've made your first point. Keep one core idea per slide, and write headers that state your actual conclusion instead of a generic label: "Expanding into Brazil generates four million dollars in year-two profit" beats "Brazil market financials" every time. Lean on short bullet points, structured tables, and bold callout numbers instead of paragraphs of small text.
Most strong decks also follow the same narrative arc consulting firms use: open with the situation, the market conditions and baseline performance the audience needs as context, then state the complication, the specific obstacle or shift that creates urgency, then deliver your recommendation as a clear, actionable choice, and close with next steps, the rough roadmap, timeline, and the biggest risks worth flagging.
Step 6: Deliver the presentation and handle Q&A with confidence
How you deliver the deck matters just as much as the analysis behind it. Stand confidently, keep eye contact with the judging panel, split speaking time evenly across your team, and never turn around to read straight off the screen. Your slides carry the data. Your voice carries the context.
The Q&A segment is often where competitions are actually won or lost. The most common mistake first-timers make is getting defensive when a judge challenges an assumption or finds a real gap in the model. Treat it as a stress test, not an attack. If a judge catches a genuine blind spot, acknowledge it, explain the reasoning behind your original choice, and describe exactly how you'd adjust the recommendation or find the data you'd need to close the gap. Judges tend to remember how a team handled being wrong far more than whether they were wrong in the first place.
What mistakes quietly cost teams the most points?
The biggest point-losers rarely show up as one dramatic error. Answering a different question than the one actually asked is the most common one: building a polished deck to launch a new product when the prompt explicitly asked how to cut supply chain costs. Close behind it is dumping raw data and market statistics on the judges without ever translating it into an actual decision, and ignoring the constraints stated in the brief by proposing something that blows past the stated budget, legal boundary, or timeline.
The rest tend to show up in the room itself. Vague financial claims like "sales will increase significantly" instead of an actual estimate, slides so crowded with text and charts that judges start reading instead of listening, and a presentation the team never once rehearsed out loud, so the handoffs and timing fall apart live. The safest-sounding recommendation, something like "conduct more market research," is usually the weakest one in the room. Judges are looking for a specific, defensible stance, not a way to avoid taking one.
Common questions about solving a business case
1. Do I need to know finance to solve a business case?
No. Most of what you need is arithmetic you already know: revenue minus costs, percentages, basic ratios. What actually separates strong teams is structuring the problem clearly, not running complicated math.
2. What if I can't figure out which framework fits my case?
Look at what the company is actually being asked to decide. If profit is falling, it's a profitability case. If they're deciding whether to launch or expand, it's market entry. If the question is what to charge, it's pricing. Some cases blend two of these, and that's fine. Just be explicit about which framework you're leaning on for which part of your answer.
3. How much of my recommendation needs to be backed by exact numbers?
Enough to show your logic holds up, not enough to be perfectly precise. Judges expect high schoolers to make reasonable assumptions when a case doesn't give complete data. What matters is stating your assumptions out loud and showing the math behind them.
4. Should every team member speak during the presentation?
Usually, yes. Judges notice when one person carries the whole pitch while teammates stay silent, and it tends to read as unequal preparation. Splitting speaking time also means more of the team can handle Q&A instead of one person fielding every question alone.
5. What if a judge asks something I genuinely don't know the answer to?
Say so directly, then explain how you'd find out. "We didn't model that, but here's the data we'd pull and how we'd use it" reads far better to a judge than a guess dressed up as a confident answer.
Where do you go from here?
Solving a business case comes down to a repeatable process, not raw talent or years of business classes: pin down the actual decision before you brainstorm solutions, pick the framework that matches your specific problem, back your recommendation with the numbers the case actually gives you, and build a deck that leads with your conclusion instead of burying it. The teams that place well aren't usually the ones with the most sophisticated math. They're the ones who answered the actual question, respected the stated constraints, and could defend their thinking out loud when a judge pushed back.
That kind of structured problem-solving under real constraints is worth building well before your next competition, and it shows up far beyond case rooms, in any situation where you're handed an ambiguous problem and expected to produce a defensible answer. If you want to build it on an ongoing basis rather than one competition at a time, a project-based program like Ladder Internships puts you inside a real startup's actual project, with a company manager and a dedicated coach, working through exactly this kind of open-ended problem over several weeks instead of a single afternoon.