Almost every price in the world is set one of two ways. Either you start from what the product costs you and add a markup, or you start from what it's worth to the buyer and work back. The first is cost-plus pricing. The second is value-based pricing. Most companies default to the first because it's safe and easy, and most of them leave real money on the table doing it.
But value-based pricing isn't automatically the answer either. It's harder, it can misfire, and for some products it's overkill. This is a clear-eyed comparison: how each one works, what it actually earns you, where each fails, and why the smartest move is usually to stop treating it as a binary.
- Cost-plus pricing builds the price up from your cost. Value-based pricing sets it from the buyer's perceived value. They answer the same question from opposite ends.
- Cost-plus is predictable and easy but blind to demand and competition, so it overprices when costs spike and underprices when buyers would happily pay more.
- Value-based captures more margin but demands real evidence of what buyers value. Guess wrong and you price yourself out.
- You rarely pick one for the whole catalog. Use cost-plus as a floor, value as the ceiling, and let data decide where each product lands between them.
Cost-plus pricing: build up from cost
Cost-plus pricing is the most intuitive method there is. Take the cost to make or buy a product, add a markup, and that's your price. The math is a one-liner:
price = cost / (1 − target margin)
A product that costs you $40 and needs a 33% gross margin lands at roughly $60. A SaaS seat that costs $50 to serve, marked up 20%, prices at $60. No demand modeling, no market research, just arithmetic.
That simplicity is the appeal. Cost-plus is transparent and defensible, which is why it dominates places where prices have to be justified: public tenders, defense contracts, construction, standardized commodities. Caterpillar and Lockheed Martin price huge programs this way. When a customer or auditor can ask "how did you get this number," cost-plus has a clean answer.
The weakness is that cost-plus is blind to everything outside your own ledger. It doesn't know what a buyer would pay, and it doesn't know what competitors charge. So it fails in two predictable directions: it overprices when your costs spike, pushing you above what the market will bear, and it underprices when customers would gladly pay more, quietly handing them margin you could have kept.
Cost-plus pricing isn't wrong, it's incomplete. It tells you the price you can't go below without losing money. It says nothing about how high you could reasonably go.
Value-based pricing: work back from worth
Value-based pricing flips the starting point. Instead of beginning with cost, you begin with the buyer's perception of value and set the price as a share of that.
The classic illustration is the iPhone. It costs Apple roughly $225 to build a unit that retails around $649, a markup approaching 190%. No cost-plus formula produces that number. The price reflects what the phone is worth to the person buying it, not what it cost to assemble.
The reason this matters is the gap cost-plus leaves behind. Picture a product that costs $40 to make, where the buyer would happily pay $100. Cost-plus at a normal markup prices it near $60, and you've just gifted the customer $40 of value you could have charged for. Value-based pricing sets it at $75 or $80, capturing the surplus that was always there.
- Key term — Consumer surplus
The gap between what a buyer would have paid and what you actually charged. Cost-plus pricing tends to leave a lot of it on the table. Value-based pricing is, at its core, the discipline of capturing more of it without pushing the buyer away.
The catch is that value-based pricing is only as good as your read on value, and value is hard to measure. It demands evidence: willingness-to-pay research, segmentation, an understanding of the alternatives a buyer is weighing. Get that read wrong and the method that promised more margin prices you straight out of the deal. It also varies by buyer, which is why value-based pricing leans naturally into customer-segment pricing, charging a wholesale account, a new region, and a premium tier differently from the same cost base.
Side by side
| Cost-plus pricing | Value-based pricing | |
|---|---|---|
| Starting point | Your cost | The buyer's perceived value |
| Inputs needed | Accurate cost data | Willingness-to-pay, segments, alternatives |
| Strength | Simple, transparent, defensible | Captures more margin, higher win rates |
| Weakness | Ignores demand and competition | Hard to measure, easy to misjudge |
| Best for | Commodities, tenders, steady costs | Differentiated brands, niches, premium |
| Failure mode | Leaves margin on the table | Prices you out of the deal |
The false choice
Here's what gets lost in most "cost-plus vs value-based" debates: you almost never have to pick one for your whole catalog. The strongest pricing setups use both, on different products, at the same time.
The pattern that works is cost-plus as the floor and value as the ceiling. Cost-plus tells you the price you can't drop below without losing money. Value tells you how much higher the market will let you go. Every product lives somewhere in that band, and where it lands depends on the product, not on a company-wide doctrine.
A commodity with thin differentiation and a transparent market sits near the cost-plus floor. A flagship product with a strong brand and few real substitutes sits much closer to the value ceiling. Treating that as a per-product decision instead of a one-size policy is the difference between a pricing strategy and a pricing habit. Elastly's engine is built around exactly this idea, letting you assign a pricing strategy per product or category rather than forcing one across the board.
The third option most teams miss
There's a method that sits between the two and gets less attention than it deserves: elasticity-based pricing. Instead of guessing at perceived value through surveys, it infers it from behavior, learning how sensitive each product's demand is to price from your own sales history.
Elasticity is value-based pricing's empirical cousin. A product with low elasticity, where buyers barely flinch at a higher price, has room to move toward the value ceiling. A highly elastic one punishes every cent and belongs nearer the floor. You're still capturing surplus, but you're doing it from data the business already generates rather than from a focus group's best guess. That's the approach we walk through in how AI price optimization works, and it's how a price optimization engine can weigh cost, value, and competition together instead of forcing you to choose one lens.
Letting guardrails enforce the floor
One practical reason teams cling to cost-plus is fear. Move away from cost-based math and you worry a price will drift below cost. The answer isn't to keep pricing off a markup, it's to make the floor a rule the system enforces no matter which strategy is running.
That's precisely what a margin-floor guardrail does. Whatever sets the target, whether a value-based strategy or an elasticity model reaching for the ceiling, a margin floor clamps the result so it can never cross your cost-plus minimum. The cost-plus discipline becomes a safety net rather than the whole strategy. The full set of constraints and how they're ordered is in the guardrails reference.
How to choose, product by product
- Set the cost-plus floor everywhereKnow your true landed cost and the minimum margin you'll accept on every SKU. This is your floor, full stop, regardless of method.
- Find the differentiated productsThe ones with a real brand, few substitutes, or a clear edge are your value-based candidates. They have headroom above the floor.
- Let elasticity place the restFor everything in between, let demand sensitivity decide how far above the floor each product can sit, instead of guessing.
- Enforce it with guardrails, not willpowerMake the margin floor a rule the engine applies automatically, so reaching for the value ceiling can never accidentally sell below cost.
The takeaway isn't that value-based beats cost-plus, or the reverse. It's that the question itself is too coarse. Cost-plus defines where you can't go. Value defines where you could. A good pricing system knows both numbers for every product and lands each one in between on purpose. The connectors that feed the real cost and sales data behind all of it are covered in Elastly's integrations.
Elastly assigns the right strategy per product and enforces your margin floor automatically, with every price showing its math.
Common questions
Is value-based pricing always better than cost-plus?+–
Can you use cost-plus and value-based pricing together?+–
How is elasticity-based pricing related to these two?+–
Doesn't moving off cost-plus risk selling below cost?+–
Ready to stop pricing off a single blunt rule? See how Elastly handles price optimization, read how AI price optimization works, or explore Elastly's pricing.
The Elastly team writes about pricing strategy, elasticity, and building pricing systems you can actually explain.



