Pricing Power Case Interview: Elasticity Without Data

Pricing power in a case interview is the client's ability to raise, hold, or segment price without destroying the economics through lost demand, churn, trust damage, or competitive reaction. When the interviewer gives no elasticity data, your job is not to fake a demand curve. It is to turn elasticity into a hypothesis: which customers value the offer, what alternatives they have, how visible the price move will be, and what evidence would confirm or falsify the upside. A strong answer says where pricing may be available, where it is risky, and how the client should test the move before rolling it out. That means separating related ideas: pricing power is the room to move price, a price increase is a possible action, and price discrimination is charging different customers differently based on segment, product, channel, or contract logic. The interviewer is testing judgment under uncertainty, not textbook recall.

Pricing power in a case interview, without elasticity data

Economists use price elasticity of demand to describe how demand responds when price changes, but a case interview rarely gives you enough clean response data at the start. OpenStax explains price elasticity as a demand-response concept. In the interview, that means you can discuss what would make demand more or less sensitive, but you should not pretend to calculate true elasticity from nothing.

Pricing power is a condition. A price increase is an action. Price discrimination is a segmentation choice. A client may have pricing power and still choose to hold price because the timing is poor, the channel will resist, or the brand trust risk is too high. A client may also lack broad pricing power but still have room to raise price for a narrow segment, package, renewal cohort, or service tier.

That distinction matters because consulting firms are not looking for a memorized pricing formula. BCG describes case interviews as business problems where candidates structure the approach, ask thoughtful questions, analyze data, run quick calculations, and use business judgment in its case preparation guidance. For pricing power, judgment starts with saying: I need evidence on willingness to pay and substitutes before I can recommend the action.

HBS Online's value-based strategy material is useful here because it connects price, cost, margin, and customer value in practical terms. The client wants more margin, but customers pay because they perceive enough value relative to alternatives. Your case answer should sit between those two facts.

Questions that decide whether pricing is the right branch

Before you build a pricing branch, test whether pricing is actually the right lever. Pricing power often appears inside a profit case, where price, volume, mix, and cost all interact. If that connection feels fuzzy, review driver tree examples before drilling pricing cases.

Use these questions out loud:

• Objective: Are we trying to improve profit, defend margin, reposition the brand, protect retention, or respond to cost pressure?
• Customer segment: Which customers buy this product, and do they differ by urgency, use case, geography, contract status, or channel?
• Product type: Is this a commodity, a differentiated product, a recurring service, a regulated offer, or a bundled solution?
• Current price position: Are we already premium, at parity, or discounted versus the main alternatives?
• Alternatives: What substitutes can customers switch to, and how painful is switching?
• History: Have recent price moves changed volume, churn, complaints, or renewal behavior?
• Constraints: Are there contracts, regulation, distributor agreements, public list prices, or customer promises that limit what can move?
• Competitive response: Which competitors could undercut, match, bundle, or use the move to win accounts?

For consumer cases, ask about habit, urgency, promotions, brand trust, and substitute availability. For business customer cases, ask about mission criticality, procurement cycles, renewal timing, implementation friction, and customer concentration. For regulated-market cases, ask what price changes are allowed, who approves them, and whether service obligations limit the client's options.

A clean candidate phrasing could be: I would first separate whether the margin issue is price, volume, mix, or cost. If pricing is the main branch, I would test whether customers have enough willingness to pay and too few attractive alternatives for a targeted price move to work.

No-data pricing power proxy table

When elasticity data is missing, proxies do not prove demand response. They help you rank demand risk and ask for the evidence that would prove or disprove your hypothesis. HBS Online's willingness-to-pay guide is a useful anchor because it frames price headroom around customer value, perceived alternatives, and variation across customers rather than the seller's margin wish. The same logic also connects to market structure: substitutes, rivalry, and buyer power all affect pricing room, which is why the market attractiveness framework is relevant.

A proxy table is useful only if it changes your next move. If urgency and switching costs are high, ask for margin and churn data so you can size the upside. If substitutes are strong and price visibility is high, move toward segmentation, bundles, or cost actions instead of a blunt increase.

If you want to turn this proxy logic into interview behavior, Road to Offer helps by routing you through structure, math, and synthesis drills before you try to solve a full case.

Worked example: raising price when volume data is missing

Suppose a premium coffee chain faces margin pressure from higher input costs. The interviewer asks whether the client should raise prices. You are not given volume response data.

Start with a structure that protects you from jumping too fast. Break the problem into price potential, demand risk, competitive response, and execution constraints. Under price potential, ask which products and customer segments drive margin. Under demand risk, test urgency, substitutes, loyalty, and price visibility.

The proxy diagnosis might be mixed. Urban commuters may value speed, habit, and convenience, which could create selective pricing room. Occasional customers may be more price aware.

The data request should follow the logic: recent price-change history, product margin by item, loyalty churn, complaint themes, competitor menu prices, peak-time capacity, and basket mix. If the interviewer gives an exhibit, use it to validate the proxy, not to decorate your answer. Practice that handoff with Case interview math practice, because the moment data appears you need to translate price, volume risk, and margin impact into a clean calculation.

The recommendation should not be a blanket price increase. A stronger answer would be: My hypothesis is that the client has selective pricing power, especially where convenience, habit, and product differentiation are strongest.

That answer is not pretending to know elasticity. It is making a business recommendation with uncertainty made visible.

Common mistakes in pricing power answers

Pricing cases go wrong when candidates use the right vocabulary but skip the commercial logic. Interviewers hear that quickly.

A short practical guardrail: competitor analysis is valid, competitor coordination is not. The FTC's price-fixing guidance is a useful reminder that pricing recommendations should analyze independent market behavior and avoid any suggestion of coordination with competitors in real business conduct. In an interview, that means you can say competitors may respond, but you should not suggest aligning prices with them.

Recommendation checklist for a pricing-power case

Before you speak, run a compact checklist. It keeps the answer grounded and helps you choose between raise price, segment price, test, hold price, or move away from pricing. If that branching logic is hard, the decision tree framework is the better mental model than a formula.

• Segment: Which customers or products have the strongest willingness-to-pay logic?
• Value reason: Why would those customers accept the price move?
• Alternatives: What substitutes or competitors cap the move?
• Economics: What price, margin, and volume-risk data would change the recommendation?
• Execution: Is the move list price, packaging, tiering, renewal pricing, or a targeted test?
• Downside trigger: What signal would stop the rollout?
• Evidence status: What is confirmed, and what remains a hypothesis?

BCG's interview-process page frames case interviews for client-facing roles as a way to assess problem-solving and analytical skills in context. Your synthesis should show both: a clear business answer and the discipline to separate evidence from assumption.

A sample final synthesis could be: I would not recommend a broad price increase yet. I would recommend a targeted test where urgency, differentiation, and switching costs are strongest, while protecting price-sensitive entry products.

Practice drill path for pricing power, math, and synthesis

Use Road to Offer as a sequence, not a random case bank. Start with the Free drill picker so the first weakness gets isolated instead of hidden inside a full case.

If your opening structure is weak, use the Case interview structure drill to turn a vague pricing prompt into a clean issue tree. If you freeze when the interviewer finally gives price or volume data, use Case interview math practice. If the data arrives as a customer, competitor, or price-history exhibit, use the Chart and exhibit drill. If your recommendation sounds generic, use the Synthesis drill until every answer includes segment, reason, risk, and next step.

After that, do free case practice and force yourself to use the same logic under pressure. For more prompts beyond pricing, work through case interview questions and classify each one by the branch it tests: pricing, volume, mix, cost, market structure, or execution.

Once your drill path feels stable, test the full flow in a live-style case so the recommendation has to survive structure, data, math, and final synthesis.

Sources and Further Reading (checked 2026-06-02)

• Boston Consulting Group - Consulting Case Study Interview Preparation
• Boston Consulting Group - Consulting Interview Process
• Bain & Company - Our Hiring Process
• OpenStax - Price Elasticity of Demand and Price Elasticity of Supply
• Harvard Business School Online - Willingness to Pay: What It Is and How to Calculate
• Harvard Business School Online - A Beginner's Guide to Value-Based Strategy
• Federal Trade Commission - Price Fixing