Sunk Cost Fallacy in Your Pricing Model: A Reframe

Most pricing decisions are made by looking backward instead of forward.

A brand spends eighteen months developing a product line. The R&D costs are substantial—six figures, maybe more. The team has invested time, reputation, and internal resources into this thing. When it comes time to price, there's an invisible pressure: the price must justify what's already been spent. The logic feels sound. It isn't. This is sunk cost fallacy operating at the strategic level, and it's quietly destroying margin across e-commerce and SaaS alike.

Sunk costs are expenses that have already been incurred and cannot be recovered. They should have zero influence on future pricing decisions. Yet they dominate. A founder thinks, "We spent $200,000 on development, so the product must be priced at $X to recoup that." A retailer thinks, "We've already committed to this inventory, so we need to move it at a certain price point." The past investment becomes the anchor for future revenue, which is economically irrational but psychologically irresistible.

Here's what makes this particularly damaging: it locks pricing to internal reality rather than market reality. Your customer doesn't care what you spent. They care what the product does for them and what alternatives cost. When you price based on sunk costs, you're either overpricing (because you're trying to recover expenses that should have been written off) or underpricing (because you're desperate to justify the investment). Neither serves the business.

The real cost of this fallacy runs deeper than a single mispriced product. It creates a culture where decisions are justified by past commitments rather than future potential. Teams become defensive about initiatives that aren't working because abandoning them feels like admitting the sunk cost was wasted. Pricing stays rigid even when market conditions shift. Customers who should be paying more for genuine value are charged less because the business is still trying to recover yesterday's expenses.

Consider a concrete example: a software company builds a feature that took three months and significant engineering resources. The feature is genuinely useful but not differentiated—competitors offer similar functionality. The team wants to price it as a premium add-on because of the development cost. The market won't bear that price. The company either overprices and loses customers, or underprices and trains the market to expect low value. Both outcomes are driven by the same mistake: letting sunk costs dictate pricing strategy.

The reframe is straightforward but requires discipline. Price based on three things only: what the customer perceives as value, what competitors charge, and what margin you need to sustain the business going forward. The $200,000 you spent on development? That's already gone. It's a sunk cost. It should inform your decision to continue or discontinue the product line, but it should never touch your pricing model.

This distinction matters because it separates strategic thinking from emotional attachment. If a product isn't worth the price the market will pay, you have two options: improve it until it is, or stop making it. What you cannot do is price it based on what you've already invested. That's not strategy—it's hope dressed up as mathematics.

The brands that win in pricing are the ones that can separate past investment from future value. They ask: "What is this worth to the customer right now?" not "How do we recover what we spent?" They're willing to kill products that don't meet market-based pricing thresholds, which frees resources for initiatives that do. They adjust pricing when conditions change, not when they've finally recouped their costs.

Sunk cost fallacy in pricing is particularly insidious because it feels rational. You're trying to be responsible with capital. You're trying to justify decisions. But you're actually doing the opposite—you're letting dead money dictate living strategy. The only way forward is to stop looking back.