I completely understand how to get the calculations and the justification behind increasing vs decreasing price for certain segments but I am a bit confused on how to know what type of additional information to ask the interviewer for. For example, I was able to get to the initial estimates of yearly revenue but it did not occur to me to calculate or ask for elasticity. In this case, would it be something I have to explicitly ask for, or would saying "I need more information to calculate how price affects demand" work fine?
Knowing what information to ask for


Hey there, Great question!
In general, you want to ask for information that are drivers to the problem you want to solve. Also for variables that are inter-related (as in with this example between sales volumes and price). Try to think as deep and wide as you can of relevant drivers, and put this in a formulaic approach to give your thoughts and answers structure and precision. You clarify this with the interviewer as they may or may not have it.
And with pricing elasticity, this is important because it is too often candidates make an implicit assumption that customers have an inelastic price elasticity. It may be the case that revenues can go down if prices go up (or vice versa) - and even if you didn't explicitly call for price elasticity, you could have asked for what the impact on sales volumes would be if price changes
Also, you don't want to ask for information that is not relevant. This will make you look like you don't know how to prioritise what's important or know what's important to think about
All the best

Hi,
When you request information to the interviewer, it's very important to state why you would like this information and how this will help you to solve the case. If the interviewer does not give you the exact information; you can do a proposal to estimate yourself or break it down first to parameters that are more easy to estimate.
Feel free to reach out if you would like additional info and/or want to practice this skills.
Mattijs

Hey!
It's important to strike a balance between being specific and demonstrating structured thinking. Instead of asking broadly for "more information," it's better to indicate the specific factor you're considering. A good approach would be to say something like:
- "To better understand the impact of a price change, I would need information on price elasticity of demand. Could you provide insights into how sensitive our customers are to changes in price?"
This shows that you know what you're looking for and why it's relevant. If you're unsure what exactly to ask, framing it as a hypothesis can help, e.g.:
- "I assume that demand might be elastic for this segment, but I would need more data on past price changes and their impact on sales to confirm. Could we explore that?"
This way, you're demonstrating both structured thinking and curiosity without appearing to lack knowledge.
Alessa

Hey,
Is seems that you lack business sense at this point, which is the hardest area to develop since there's just a critical amount of data your brain needs to process and internalize (industry / problem types) before you more confident in your case solving process and know what information to ask for.
To progress quickly, I suggest you take an active learning approach (in the following order):
1. Getting coaching when you are a complete beginner to learn the basics;
2. After you've learned the basics, practice cases with peers to polish your case solving process and acquire understanding of a wide range of industries and problem types;
3. Before the interview, ask a few acting consultants to give you cases in a mock-interview format to assess your readiness.
Hope this helps.
Good luck!
Nick

You need to build out your frameworking ability. You cannot predict the exact data. However, you can know the 2-4 possible pathways.
That's how you drive a case forward.
You use MECE thinking and frameworking throughout the case to eliminate pathways and move along the tree.
Unfortunately a Q&A can't really teach this. I highly highly recommond coaching to get case leadership down (it's one of the hardest parts of casing and fundamental to actually being a consultant)
My frameworking course is in here:
End-to-end case interview training – from beginner to advanced









