The Pricing Strategy Case Interview: Full Framework

A pricing case is not an accounting exercise. It is a test of whether you understand the relationship between value, competition, and customer behavior.

Imagine a locksmith who charges $20 per hour to open a lock. A competitor offers to do the same job for $15. A purely cost-based buyer would pick the cheaper locksmith. But if you're locked out of your house at midnight in winter, with a flight to catch at 6 AM, you will pay $150 without hesitation. The value of the service at that moment dramatically exceeds both prices. The locksmith who only thinks about cost, and not about the circumstances of the customer's need, leaves enormous money on the table. Pricing cases ask you to think like the locksmith who charges $150.

Any pricing recommendation requires you to run three lenses in parallel: cost-based, value-based, and competitive.

Cost-based pricing establishes the floor. Calculate variable cost per unit, add allocated fixed costs, add a margin target, and you have the minimum price the company can charge without destroying economics. This is not a recommendation; it is a constraint. Understanding unit economics is essential here — the cost floor is only meaningful when you know exactly what it costs to deliver each incremental unit.

Value-based pricing establishes the ceiling. What is the economic value delivered to the customer by this product or service? If your software saves a finance team 10 hours per week at a fully-loaded cost of $100 per hour, it creates $52,000 of annual value per user. A price of $10,000 per user per year captures roughly 20% of the value created, leaving 80% with the customer. Whether you price at $10,000, $20,000, or $5,000 depends on competitive intensity, willingness to pay, and strategic goals. But the ceiling is $52,000, and any price below that is leaving value on the table.

Competitive benchmarking sets the context. What do comparable products charge? What does that imply about customer price expectations? If your price is dramatically above market, you need differentiation that is visible and credible. If your price is dramatically below, you risk signaling low quality.

When an interviewer presents a pricing case, your first job is to clarify what kind of pricing decision this is: setting a price for a new product, adjusting price for an existing product, responding to a competitor's price move, or segmenting pricing across customer types.

Say: "Before I structure the framework, I want to understand: are we setting a price for a new product launch, or reconsidering pricing for something already in market?" This distinction matters because a new product requires all three lenses in full, while a repricing decision often starts with understanding why current pricing is underperforming.

Then structure clearly: "I'll look at this from three angles: the cost floor, the value ceiling, and competitive positioning. Then I'll think about price segmentation and execution."

Practice this framework on a real case: the Luckin Coffee 2020 case on BoardroomIQ puts you inside one of the most aggressive pricing strategies in modern retail, where subsidized pricing was used as a growth weapon until the economics collapsed.

A single price leaves value on the table at both ends. Some customers would pay far more; others won't buy at all at your standard price.

Think of an airline's pricing model. The same seat, on the same flight, at different prices for the business traveler who books last-minute and the vacationer who books six months ahead. The airline isn't just responding to demand fluctuations. It is segmenting by willingness to pay and extracting more value from customers with higher urgency or fewer alternatives.

In your pricing case, ask whether segmentation is possible: by customer type, by use case, by volume, by geography, or by product tier. Good-better-best pricing (a basic tier, a standard tier, and a premium tier) is one of the most reliable segmentation mechanisms in consumer and SaaS markets. It serves the price-sensitive segment without requiring you to lower the standard price.

Exercise 1: Reverse-engineer a price. Pick three products you use daily. For each, estimate the cost floor, estimate the value ceiling (what problem does it solve and what would it cost to solve it another way?), and then explain whether the actual price is closer to the floor or the ceiling and why. This builds intuition for where real-world pricing sits.

Exercise 2: Elasticity stress-test. For any pricing recommendation you make in practice cases, ask: "What happens to volume if price increases 10%? 20%? What happens to total revenue in each scenario?" Forcing yourself to estimate price elasticity, even roughly, adds rigor to any recommendation. In subscription and SaaS contexts this connects directly to customer lifetime value — a higher price point that reduces volume may still improve LTV if it attracts customers who churn less.

Exercise 3: Competitive response simulation. Pick a pricing decision and then simulate the competitor's response. If you raise price by 15%, does the nearest competitor match, undercut, or ignore? What does each scenario imply for your market share and revenue? Competitive reaction is the variable most candidates forget in pricing cases. Also test whether your chosen price is compatible with profitable growth by checking that the customer acquisition cost required to win customers at that price stays well below the resulting lifetime value.

The best way to practice pricing cases is under realistic pressure, with a case that fights back.