Two Methods That Answer Different Questions
Pricing a product requires more than covering expenses or matching a competitor. Your price must support the business while giving customers a compelling reason to buy. Cost-plus and value-based pricing approach that challenge from opposite directions: one begins with what you spend, while the other begins with what customers gain.
Cost-plus pricing asks, “What must we charge above our costs?” Value-based pricing asks, “What is this outcome worth to a particular customer?” Neither method removes uncertainty. Costs change with volume, and perceived value depends on the buyer’s needs, available alternatives, and confidence that your product will deliver.
The choice is therefore not simply operational discipline versus ambitious margins. It is about which information provides the strongest basis for a pricing decision. Many products benefit from using costs to establish an economic baseline and customer value to shape positioning, packaging, and the price ultimately tested.
How Cost-Plus Pricing Works
Under cost-plus pricing, you calculate a relevant unit cost and add a markup. In a hypothetical example, a product with a fully allocated unit cost of $20 and a 50% markup sells for $30. That produces a gross margin of about 33%, not 50%, assuming the $20 represents cost of goods sold. Markup is measured against cost; margin is measured against selling price.
The difficult part is defining cost consistently. Depending on the product, consider materials, manufacturing, hosting, delivery, support, and transaction fees. For a fuller profitability assessment, account for overhead and customer acquisition separately or allocate them using explicit assumptions. Avoid counting an expense twice, and remember that fixed cost per unit changes when sales volume changes.
Cost-plus is useful when costs are reasonably predictable, products are standardized, or buyers expect transparent cost-based quotations. Its weakness is that internal expenses do not establish customer demand. A calculated price may exceed what buyers will pay, or sit far below what a differentiated product is worth. It also risks passing inefficiency to customers rather than prompting improvements.
How Value-Based Pricing Works
Value-based pricing sets prices around the benefits customers expect relative to their next-best alternative. Those benefits might include time saved, fewer errors, faster implementation, or greater convenience. Value can also be subjective: design, ease of use, and confidence in a supplier can influence willingness to pay even when they resist a precise monetary estimate.
Consider a hypothetical workflow tool that reduces repetitive administration. Estimate the tasks it could eliminate, how frequently they occur, and whether saved time can actually be redeployed. Do not assume every hour saved becomes cash savings. Setup effort, training, switching costs, and uncertain adoption all reduce the benefit a buyer may reasonably expect.
This method works best when customer segments have distinct needs and the product delivers meaningful differentiation. Interviews, buying conversations, and paid pilots can reveal which outcomes matter. However, a customer’s estimated benefit is not a pricing formula. Alternatives, purchasing authority, budget constraints, and delivery risk influence how much of that value the supplier can capture.
Choose Based on Your Product and Customer
Lean toward cost-plus as a starting point when you sell a relatively standardized offering, can estimate delivery costs reliably, and have limited evidence of differentiated value. Even then, compare the resulting price with realistic alternatives. If the market will not support it, revisiting costs, scope, or the target customer is more useful than defending the formula.
Lean toward value-based pricing when outcomes differ substantially between customer groups or when your product solves an expensive, urgent problem. Business software and specialized services may fit this pattern, but the label alone proves nothing. A software product with many interchangeable substitutes may have little pricing power.
Often the strongest approach combines both methods. Model contribution and overall profitability at plausible sales volumes, then investigate willingness to pay within a specific segment. Use packages to connect price with meaningful differences in scope, usage, or service. Avoid arbitrary tiers whose only purpose is to make the middle option look attractive.
Test the Price and Revisit the Assumptions
Start with a clearly defined customer, offer, and pricing hypothesis. Test a small number of understandable packages through transparent sales conversations or limited pilots. Ask what buyers would use instead, what might prevent adoption, and which benefits justify the expense. Treat stated willingness to pay as a clue rather than proof of purchasing behavior.
Evaluate more than conversion. Watch contribution per sale, acquisition costs, support demands, retention, and reasons for winning or losing deals. A lower price can increase sales while worsening economics; a higher price can improve revenue per customer while attracting expectations your team cannot meet.
Revisit pricing when costs, capabilities, or customer needs materially change. Preserve clear terms for existing customers and communicate adjustments plainly. The goal is not to identify a permanently perfect number, but to build a repeatable process that balances sustainable delivery with value customers recognize.
