Pricing cases

Hi,

I think the reason pricing cases feel awkward is that candidates often confuse "factors that influence price" with "a framework to determine price."

Costs, competitors, and customer value are useful inputs, but they don't tell you how to make the pricing decision. If you simply list those three buckets, you often end up with information but no recommendation.

Instead, I would start pricing cases with this clarifying question:

What is the client's objective?

Pricing is ultimately an optimization problem. The "right" price depends on what the client is trying to maximize.

For example:

• Maximize profit?
• Maximize revenue?
• Position the brand as premium?
• Accelerate adoption of a new product?

Once the objective is clear, I would structure the case as follows:

1. Understand the product and customer

2. Determine willingness to pay

3. Assess market constraints

4. Assess economic constraints

5. Recommend the price that best achieves the client's objective

Notice that the three pricing methods (customer value, competitors, and costs) are covered in steps 2, 3, and 4, but the framework goes beyond that. You still need to connect these inputs back to the client's objective and make a clear, quantified recommendation.

If you want to practice realistic price cases feel free to contact me in DM

Best,

Franco

Hi,

For most pricing cases, it helps to think in terms of narrowing down a feasible range and then choosing a point within it rather than simply “cost / competition / value.”

A structure that often works well is:

• Segment and profile customers. Pin down who is buying the product and what drives their willingness to pay. In many markets there isn’t a single “value” but several, tied to different use cases or buyer types (e.g. a cost‑sensitive segment vs. a premium‑seeking one). Knowing the segments helps you consider whether a uniform price, tiered offerings or bundling make sense.
• Define the price floor and ceiling. The floor is set by economics: it must at least cover variable costs and contribute to fixed costs. The ceiling is set by customer perception and substitutes: the price at which they would switch to alternatives or forego purchase. Competitor pricing is useful here as a proxy for where the market ceiling currently sits; cost structure tells you where the floor is. The gap between these is your playing field.
• Choose a pricing strategy appropriate to the situation. For a commodity product facing strong competition you might need to price close to competitor levels and compete on differentiation or channel efficiency. For a differentiated product (e.g. innovative software) you might adopt a skimming strategy (high price initially, then lowering) or penetration pricing (low price to build share quickly) depending on whether volume or margin is more critical. Think about whether tiered pricing, bundles, subscription, usage‑based pricing or regional pricing would better capture the different willingness‑to‑pay you identified.
• Model scenarios and trade‑offs. Build simple volume‑price curves based on expected elasticity: higher prices may reduce volume but increase margin, lower prices may attract more customers but depress profit per unit. Run a few scenarios to see which price points meet the client’s objectives (e.g. hitting a target EBIT, achieving market share goals, discouraging new entrants). This also prepares you to discuss how competitors might respond.
• Check practical and qualitative constraints. Psychological price thresholds (e.g. €9.99 vs €10.50), regulatory limits, channel mark‑ups, and the brand’s desired positioning all influence the final decision. A medical device, for instance, may face reimbursement caps; a luxury brand may need to stay above certain price points to maintain exclusivity.

For a product with no direct competitors, your focus shifts to the customer segments and value. You still need a floor and ceiling, but the ceiling is set by what the target customers might pay relative to indirect substitutes or the cost savings/benefits the product delivers. In practice you might start high (skimming) if early adopters have a high willingness‑to‑pay, and then broaden your market via lower‑priced versions.

As an illustration, imagine pricing a new electric bicycle. You would 

1. Segment users (commuters vs. recreational riders),
2. Estimate a cost floor (manufacturing and distribution costs),
3. Research what comparable transport alternatives (e.g. other e‑bikes, scooters, public transport) cost to set the ceiling,
4. Decide whether to price premium to signal quality or penetration to build volume quickly, and
5. Model profit at different price points while considering retailer margins and regulatory incentives (subsidies, tax credits).

This way of thinking goes beyond simply listing “cost, competitors, value” and forces you to convert those inputs into a recommendation aligned with the context and the client’s goals.

Hi there

I know that it's probably annoying to receive the 'don't use typical frameworks' answer, but it seems like, effectively, you are looking for the 'key that opens all doors'. And there isn't one. 

What you can find, however, are a set of principles and elements that often show up in pricing cases. Some of these are the ones that you've identified as well. 

If you're keen on developing this area, reach out since I offer a targeted frameworks session, and we can tailor it further to only look at pricing cases if helpful for you. 

Best,
Cristian