Pricing Framework for Case Interviews

Pricing cases ask how a product or service should be priced. The common mistake is picking one angle — usually cost — and stopping there. A complete framework weighs three distinct approaches.

The three approaches

  • Cost-based pricing — price relative to what it costs to produce, plus a target margin. Simple, but ignores what customers are actually willing to pay.
  • Value-based pricing — price relative to the value the customer gets, compared to alternatives (including doing nothing). Requires understanding the customer, not just the product.
  • Competition-based pricing — price relative to what alternatives in the market charge. Straightforward in a crowded market, less useful for something genuinely new.

These three are MECE in the sense that they're three distinct anchors for a price — cost, customer value, and competitive alternatives — and a defensible price usually considers where all three land, even if one ends up dominating the final recommendation.

Why picking just one is a common trap

Leading with cost-based pricing alone often produces a price that leaves real value on the table if customers would pay more. Leading with value-based pricing alone can produce a price with healthy margins on paper but no grounding in what competitors charge, making it hard to defend. The strongest answers triangulate between all three rather than committing to one immediately.

A worked example

Case: A startup has built a project management tool with a few genuinely unique features. How should it price a monthly subscription?

  • Cost-based: Hosting and support costs are low per user — a cost-based price alone would land far below what's actually defensible.
  • Value-based: Competing tools save teams meaningful time; customers likely would pay a premium for the unique features, if positioned well.
  • Competition-based: Established competitors charge $10-15/user/month for comparable core functionality.

Conclusion: Price near or slightly above the competitive range ($12-18/user/month), justified by the unique features under value-based reasoning — cost-based pricing alone would have underpriced the product significantly.

Practice weighing trade-offs, not just naming them

The skill in a pricing case is connecting all three angles into one recommendation, not listing them as three disconnected bullet points. Practice case structuring on Meceify →

FAQ

What are the three main pricing approaches in a pricing framework?

Cost-based pricing (price relative to what it costs to produce), value-based pricing (price relative to what it's worth to the customer), and competition-based pricing (price relative to what alternatives cost). A full pricing recommendation weighs all three.

Which pricing approach should I lead with in a case?

There's no universal answer. It depends on the industry and what the case emphasizes. Commodity products lean cost-based, differentiated products lean value-based, and crowded markets lean competition-based, but a strong answer considers all three rather than picking one by default.