Pricing cases

Intuition

Pricing is the most powerful profit lever a company has, a 1% price increase often beats a 1% cost cut by a wide margin, because it drops almost straight to the bottom line. Yet most companies price lazily, slapping a margin on cost. A pricing case asks you to think harder: what is this thing actually worth to the buyer, and how much of that value can we capture without losing them?

Picture a bottle of water. It costs pennies to produce, but in a desert it's priceless and at home it's nearly free. Same product, wildly different value, and value, not cost, is what smart pricing chases.

Framework

• Three lenses on price: Cost-based (cost + target margin, the floor), Competitor-based (relative to substitutes, the reference point), Value-based (the economic benefit to the customer, usually the ceiling and the goal).
• Willingness to pay & segmentation. Different customers value the product differently, segment and price accordingly (versions, tiers, discounts).
• Elasticity. Estimate how volume responds to price; the profit-maximizing price balances margin per unit against units sold.
• Competitor reaction & strategy. Will rivals follow or undercut? Is the goal profit, share, or signaling?

Worked Example

A software firm prices a new analytics tool. Cost-based says $20/user, but it saves each customer roughly $500/month in analyst time, so value-based supports far more. Competitors charge $80–120. Recommendation: anchor on value with a $99/user tier, plus a cheaper limited tier to capture price-sensitive small firms (segmentation) and an enterprise tier for heavy users. Check elasticity with a pilot before rolling out. Cost barely entered the decision, the customer's saved $500 did.

A second flavor: a 60-room boutique hotel. Cost-plus says $90 a night covers operations with margin. Comparable hotels nearby run $180–220, the reference point. But on festival and conference weekends, demand data shows rooms clearing at $400. The strong answer prices dynamically: a $200 base anchored to the competitive set, premium pricing on the 30 high-demand nights a year, and discounted midweek corporate rates to fill empty rooms. Three lenses, three different prices, because willingness to pay moves with the calendar, not with the cost.

In the room

Open with the three lenses, in order: "I'd look at this price through three lenses. Cost sets the floor, below it every unit loses money. Competitors set the customer's reference point. And value to the customer sets the ceiling, what the product is actually worth to them. I'd anchor on value, then test how much volume we'd lose at each price point." The question that comes next, almost without fail: "How would you actually estimate willingness to pay?" Be concrete, not hand-wavy. Quantify the customer's economics first, "the tool saves an analyst-day a week; that's worth roughly $2, 000 a month", then name a validation method: a conjoint survey, an A/B pilot in one region, or the sales team's win/loss data. An answer with a measurement plan attached signals you've priced things in real life, not just in frameworks.

Pitfalls

• Defaulting to cost-plus and leaving value (and profit) on the table.
• Ignoring elasticity, celebrating a price rise while volume quietly collapses.
• Forgetting competitor response and the strategic goal (sometimes you price low to win share, not profit).