The Cost-Plus vs. Value Fallacy
Type: warning
Stage: Stage 3: Pricing Proof
Difficulty: intermediate
Pricing based on your hosting and API costs instead of the value you deliver is a structural underpricing error — software value is rarely related to what it costs to run.
Overview
Cost-plus pricing is the default mode for founders who haven't yet built a model for quantifying customer value. It feels responsible: calculate your costs, add a margin, set a price. But software is not a physical product. The marginal cost of serving one more customer in SaaS is near zero (except for AI-native products with significant compute costs). Pricing that anchors to your costs rather than your customer's value delivered will systematically underprice the product relative to what the market would pay.
Why it happens
Cost-plus pricing is intuitive because it's how physical goods are priced. A manufacturer calculates material + labor + overhead + margin and arrives at a price. The price is bounded from below by costs and bounded from above by competition.
Founders apply the same logic to software: hosting is $50/month, API costs are $200/month, tools and subscriptions add $100/month — total costs are $350/month, so charge $500/month to cover costs and leave a margin.
The problem: this calculation has nothing to do with what the product is worth to the customer. A product that saves a customer $50,000/year in manual labor costs the founder $350/month to run. Cost-plus pricing would put the price at $500/month. Value-based pricing would put it at $5,000–$10,000/month — 10–20x higher — and the customer would still be getting 5–10x ROI.
The gap between cost-plus and value-based pricing is the measure of how much money a founder is leaving on the table.
The risk
Companies that use value-based pricing strategies achieve measurably higher growth rates than those anchoring to costs — the gap is frequently cited at 25–30% in comparative studies of SaaS pricing approaches.
The structural reason: cost-plus pricing creates a ceiling. Once a founder sets a price based on costs + margin, the psychological anchor is established. Raising prices feels like 'gouging' because the internal justification for the price is 'this is what it costs us to provide.' When costs don't go up, raising prices feels unjustified.
Value-based pricing has no ceiling. As the product improves and delivers more value, the price can increase to reflect the additional value delivered. The justification for price increases is product improvement — a justification customers can accept.
Quantifying the cost of doing nothing
The alternative to cost-plus pricing is value-based pricing, and the starting point for value-based pricing is the 'cost of doing nothing' calculation.
The cost of doing nothing is what your potential customer is currently spending — in time, money, tools, and errors — to solve the problem your product addresses. It's the baseline against which your product's value is measured.
Examples:
• A sales team using spreadsheets for pipeline management: 3 hours/week per rep × $60/hr effective cost × 10 reps = $1,800/week in labor cost → $93,600/year
• A content team running manual social media scheduling: 2 hours/day × $40/hr × 250 working days = $20,000/year
• An operations team doing manual inventory reconciliation: 8 hours/month × $75/hr = $7,200/year in direct labor, plus error costs
Once you've quantified the cost of doing nothing, pricing at 20–30% of the annual value delivered is a commercially reasonable starting point. At that price, the customer's ROI is 3–5x, which makes the purchase decision straightforward.
How to avoid it
Replace the cost model with a value model before setting any price.
The value model:
1. Identify the specific workflow your product replaces or improves
2. Quantify what that workflow currently costs the customer (time × rate, error frequency × error cost, or direct tool cost)
3. Estimate how much of that cost your product eliminates
4. Price at 20–30% of the annual value eliminated
Always pressure-test the value model in customer conversations before finalizing the price. Ask: 'If this tool saved you X hours per week, what would that be worth to your business?' The answers will calibrate your model against reality.
For AI-native products with meaningful compute costs, the cost floor matters — but the ceiling is still determined by value, not costs. The pricing objective is to find a price that keeps you well above cost floor while capturing a fair fraction of the value you deliver.