Value-based pricing formulas

The ceiling formula treats price and customer implementation cost as the first-year investment. If the ceiling is below the supplier floor, the modeled deal has no feasible range under the entered assumptions.

Worked enterprise solution example

The customer currently spends $1 million annually in the affected process. A 20 percent reduction creates $200,000 of cost savings. The solution may also enable $500,000 of incremental revenue; at the customer’s 40 percent contribution margin, that revenue is worth $200,000 rather than the full top line. Avoided annual loss adds $100,000.

The $500,000 gross benefit is multiplied by an 80 percent realization probability, producing $400,000 of risk-adjusted gross value. A 25 percent vendor share gives a $100,000 annual target price. After that price and $50,000 of customer implementation cost, the customer retains $250,000 of first-year net value.

Customer ROI is 166.67 percent on $150,000 of combined price and implementation investment, with a 4.50-month simple payback if value accrues evenly. Vendor delivery cost of $45,000 produces a $64,285.71 floor at a 30 percent minimum margin. A 100 percent minimum customer ROI produces a $150,000 ceiling, so the $100,000 target sits inside the feasible range.

Start with a defensible customer baseline

A vague claim such as “save time” is not a price foundation. Convert minutes to a real economic effect only when capacity can be redeployed, headcount avoided, revenue accelerated, quality improved, or risk reduced. Do not value every minute at a fully loaded wage if no cost or capacity changes.

Value incremental revenue at contribution, not gross sales

New revenue requires delivery. Subtract product, hosting, payment, fulfillment, commission, support, returns, and other costs that vary with the additional sale. The customer’s contribution margin can differ by product, region, channel, and capacity.

A solution rarely causes all forecast growth. Separate product demand, sales effort, price, seasonality, and market effects. Use an experimental or matched baseline where feasible. Apply probability to volume, conversion, timing, and adoption rather than using one optimism factor without support.

Revenue may arrive after implementation. Discount or phase value when a multi-year model is material. Avoid charging one year’s price against several years of benefit without showing the period on both sides.

Avoided risk needs probability and consequence

Risk value should reflect the change in expected loss: probability times consequence before the solution minus probability times consequence after it. Do not enter a catastrophic maximum as though it occurs every year. Consider insurance, controls, response, detection, recovery, and residual risk.

Regulatory, safety, cybersecurity, downtime, fraud, quality, and reputation consequences require domain experts. A vendor should not guarantee legal compliance or risk elimination unless the contract and evidence support that commitment.

Keep risk value separate in negotiation because procurement may accept operating savings but reject speculative avoided loss. The target can be recalculated with risk set to zero as a conservative scenario.

Choose a value share through evidence and bargaining

The vendor share is not dictated by a universal percentage. Alternatives, switching cost, differentiation, intellectual property, implementation capacity, buyer power, risk allocation, competitive bids, budget, procurement policy, and price metric all matter.

Price architecture can be fixed, per user, per transaction, usage-based, performance-based, subscription, or hybrid. Align the metric with value without making the invoice unpredictable. Add floors, caps, tiers, measurement definitions, audit rights, and renewal treatment where needed.

A performance fee can share risk but creates attribution, data, timing, and dispute complexity. Confirm revenue recognition, collectability, contract law, and customer procurement rules before using contingent consideration.

The supplier floor still matters

Value-based pricing does not excuse a loss-making delivery model. Include implementation, support, hosting, third-party licenses, success management, payment fees, warranty, expected credits, compliance, data, insurance, and variable sales compensation. Allocate shared costs separately from incremental cost.

The floor formula uses gross margin on price, not markup on cost. At a 30 percent margin, $45,000 of cost requires $64,285.71 of price. Adding 30 percent to cost would produce only $58,500 and a lower margin.

If the customer’s ROI ceiling falls below the supplier floor, redesign scope, reduce cost, improve evidence, change risk sharing, find a better-fit segment, or decline the deal. Discounting cannot solve negative joint economics.

Turn the value case into a durable price architecture

A strong annual target price can still fail if the billing metric does not follow how the customer experiences value. Per-seat pricing is simple but can discourage adoption. Usage pricing follows activity but can create budget uncertainty. Transaction pricing aligns with volume but may reward the vendor when customer profitability falls. A platform fee plus a capped variable component can balance predictability and participation.

Define included volume, overage, minimum commitment, ramp, true-up, unused entitlement, renewal index, currency, tax, payment timing, service credit, termination, and data source. Model how price changes at the customer’s low, expected, and high usage. The target result is annual economics; it does not decide whether the invoice should be prepaid, monthly, milestone-based, or contingent.

Discounts should exchange value rather than merely reduce price. A longer term, prepayment, reference rights, narrower scope, standardized implementation, reduced support, higher minimum, or better forecast can lower vendor cost or risk. Record list price, concession, consideration received, and approval. Otherwise, a value-based launch can drift into inconsistent deal-by-deal bargaining that is hard to renew and difficult to explain.

U.S. claims, procurement, and disclosure boundaries

Substantiate savings and performance claims. Define dependencies, customer responsibilities, exclusions, service levels, remedies, and data rights. Sales decks and ROI tools can create expectations even when labeled estimates. Legal review should address advertising, contract, privacy, sector, and state requirements.

Federal Acquisition Regulation Part 15.4 illustrates structured cost and price analysis for fair and reasonable negotiated prices in federal procurement; it does not turn this private commercial worksheet into a government-approved method. Public companies using adjusted value or margin metrics should consider SEC non-GAAP and KPI guidance.

Price and implementation expense can have tax and accounting consequences that differ across parties.

Value-pricing evidence checklist

1. Define the affected process.
2. Document the current baseline.
3. Build the no-purchase counterfactual.
4. Value revenue at contribution.
5. Probability-adjust uncertain benefits.
6. Include customer implementation cost.
7. Calculate vendor delivery cost.
8. Set a customer ROI threshold.
9. Test floor against ceiling.
10. Choose an auditable price metric.
11. Assign measurement owners.
12. Substantiate every sales claim.

Frequently asked questions

References

• Federal Acquisition Regulation Subpart 15.4, contract pricing
• Federal Acquisition Regulation 15.405, price negotiation
• U.S. Small Business Administration, financial management and cost-benefit analysis
• SEC Commission Guidance on KPIs and metrics
• SEC non-GAAP financial measure interpretations