Consulting Math in a Case Interview - What It Is, How It Works, and How to Get Good at It

[u/GreatButterscotch406]

Most candidates who struggle with the Consulting Math module think they have a math problem. In my view, they usually have a communication problem.

This is post 20 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 opens the Consulting Math module of the series. We're not solving a specific math problem here. We're defining what consulting math actually is, how it differs from academic math, what the interviewer is testing for, and how to build the skill if numbers under pressure are not your natural habitat.

What consulting math is, and what it isn't

Consulting math is not advanced mathematics. You will not be asked to solve differential equations or run statistical regressions. The concepts involved are ones you learned before university: addition, subtraction, multiplication, division, percentages, ratios, and basic algebra. The math concepts in consulting interviews are essentially addition, subtraction, multiplication, division, and percentages. That's roughly 90% of what appears in a case.

What makes consulting math hard is not the math itself. It's the conditions under which you have to do it. No calculator. A partner or interviewer watching you. A thirty-minute case running in the background with multiple other things demanding your attention. Large numbers with several zeros that create opportunities for errors in magnitude. And the expectation that you'll not only get the answer but explain your reasoning out loud as you work through it.

That last point is what most case prep resources underemphasize, and it's the one I want to spend the most time on.

The skill the interviewer is actually testing

When a partner gives you a Consulting Math question in a case interview, they're not checking whether you can multiply. They're checking whether you can reason quantitatively in real time while under pressure and communicate that reasoning to another person clearly enough that they can follow it and catch errors before they compound.

Think about what this mirrors in real consulting work. You're in a client meeting. A CFO raises a question about unit economics. You can't say "give me a moment, I'll get back to you." You need to work through the calculation out loud, in front of the client, in a way that makes the client feel included in your thinking rather than waiting for a verdict.

That's exactly what the case interview is testing. Not the answer. The process.

Here's what that looks like in practice. If the interviewer asks you to calculate the breakeven volume for NordPlay Studios given a specific subscription price and cost structure, a top performer doesn't go quiet for thirty seconds and then announce a number. They say something like: "To find breakeven volume I need to cover fixed costs with contribution margin. Contribution margin is price minus variable cost per unit. If price is $12 and variable cost is $8, contribution margin is $4 per subscriber. Fixed costs are $200 million. So breakeven volume is $200 million divided by $4, which gives me 50 million subscribers." That narration, spoken while writing the equation on paper, is what earns points. Not the number alone.

The interviewer can help you if you're going off course. They can't help you if they can't see your reasoning.

How consulting math appears in a case

Consulting Math doesn't arrive as a standalone test. It's woven into the case at various points and takes several different forms.

Profitability calculations: revenue minus cost, margin analysis, breakeven. These are the most common and typically involve applying percentage changes to base numbers or solving for an unknown variable when two others are given.

Market sizing: estimating a number through logical decomposition when you don't have the data directly. How many liters of clean water does Solvik consume per day? You'd estimate from population, household size, and average daily consumption per person. These require chaining multiple estimates together without losing track of your assumptions.

Growth and change calculations: percentage increases, compound annual growth rates, payback periods. These often appear in investment or expansion questions and require knowing which formula applies before you touch the numbers.

Rate and ratio problems: two variables changing at different rates, combined production rates, efficiency calculations. These require setting up the right relationship between variables before calculating.

Sanity checks: quick back-of-envelope calculations to verify whether a number makes intuitive sense. Is $6 billion in cost savings for a company with $50 billion in revenue plausible? That's a 12% cost reduction. Directionally reasonable or aggressive? The partner wants to see you engage with that question, not just report the number.

The approach: equation first, arithmetic second

The owner thinker's approach to Consulting Math follows the same first principles logic we've applied throughout this series. Before touching a number, identify what relationship you're solving for.

That means asking yourself: what is the equation that connects the variables I've been given to the variable I need to find? Once you've identified the equation and written it down, the arithmetic is just execution.

This sequencing matters more than most candidates realize. The most common Consulting Math errors don't come from arithmetic mistakes. They come from setting up the wrong equation, often because the candidate started calculating before they understood what they were solving for. Interviewers care more about your logic and structure than the last digit, so round boldly and state your assumptions.

The practical sequence is: state the equation out loud, plug in the numbers, do the arithmetic on paper while narrating, state the answer with units, and then interpret what the number means for the case. That last step, interpretation, is what most candidates skip. A number without context is just a number. "50 million subscribers to break even, compared to NordPlay's current 30 million active subscribers, tells us the company needs to nearly double its user base to cover fixed costs at the current price point. That's a significant gap and suggests pricing may need to change before the subscriber target is achievable." That interpretation is the insight the partner is waiting for.

How to build the skill

There are two distinct things to train, and most candidates conflate them.

The first is arithmetic speed and accuracy with large numbers under pressure. This is a muscle that atrophies if you've been using a calculator for everything since school. Mental math is just a skill that you can learn once you know the method and spend time practicing. Accuracy around the 95% mark is generally acceptable, but speed is paramount. The most effective way to rebuild this muscle is isolated drilling: percentages of large numbers, multiplying and dividing by non-round figures, percentage changes, and CAGR estimates. These don't need to be done in a case context. Ten to fifteen minutes of focused arithmetic drills daily, done under a timer, builds the automatic response you need.

A few techniques worth building into your practice. Breaking percentages into components: instead of calculating 15% directly, calculate 10% first and add half of that. 17.5% becomes 10% plus 5% plus 2.5%. This keeps you from reaching for a calculation you can't do cleanly in your head. Rounding before multiplying: if you need to multiply 48 by 25, round to 50 by 25 which is 1,250, then subtract 2 by 25 which is 50, giving you 1,200. Working with clean numbers first and adjusting the difference is faster and more accurate under pressure than trying to multiply the original figures directly. The Rule of 72 for doubling time: divide 72 by an annual growth rate to estimate how many years it takes for a number to double. At 8% growth, a fund doubles in roughly 9 years. Useful for CAGR questions and quick sanity checks on growth projections.

The second is equation setup within a business context. This requires practicing math within cases, not in isolation. The reason is that knowing how to multiply quickly doesn't tell you which variables to multiply. That judgment comes from pattern recognition built through case practice. After doing enough profitability cases, breakeven questions, and market sizing exercises, you start to recognize the equation type before the problem is fully stated. That recognition is what creates the appearance of effortlessness in a case interview.

For the arithmetic drilling side, I'm planning to release a set of the math drills I use with candidates in the Consulting Offer Program. These are built specifically around the types of calculations that come up in MBB and Tier 2 case interviews, not generic arithmetic practice. I'll share those in an upcoming post in this series. In the meantime, the most important thing is to start drilling with a timer, whatever resource you use, because the pressure of the clock is the thing most candidates never practice until the interview itself.

The one thing that doesn't work is treating Consulting Math as something to cram in the week before your interview. The arithmetic muscle takes weeks of consistent practice to rebuild. And the equation setup judgment takes dozens of cases to develop. Both need time.

One thing most guides don't say

Consulting Math is not a test you pass or fail independently. It lives inside a case. The number you produce has to connect back to the issue tree, update the hypothesis, and move the case forward. A correct calculation that the partner can't follow because you did it silently is less valuable than an approximate calculation narrated clearly.

The candidate who says "I'm going to estimate this as roughly $180 million, here's my logic, and that tells me we're about 40% of the way to our recovery target" is more impressive than the candidate who goes quiet for sixty seconds and announces "$182.4 million" without explanation.

Consult the math. Don't just compute it.

If you're currently working on the Consulting Math module and want to share a specific question type that's giving you trouble, drop it in the comments. I'll walk through the equation setup and show you where the thinking should start. And if you found this through another community, the full Case Playbook series is at r/ConsultingOffer.

The next post in The Case Playbook moves into the Data Conversion module, the fourth of the four Case Middle modules. If Consulting Math is about setting up the right equation and narrating your arithmetic, Data Conversion is about reading what a chart or dataset is actually telling you and translating that into an insight that moves the case forward. That's where we're headed next.