Answers

What is value-based pricing?

The pricing conversation moves from a feature list to a quantified outcome. The buyer sees what they get, the vendor captures a share of what they created, and the number on the pricing page stops being a guess.

Start free trial See pricing

Short answer

Value-based pricing sets price from the quantified outcome the customer gets, like revenue delivered, cost avoided, or hours saved, instead of marking up internal cost or matching a competitor. The vendor estimates the dollar value created for a defined customer segment and charges a fraction of that number, typically ten to twenty percent. The approach aligns the invoice with results and lifts willingness to pay well above what cost-plus or competitor benchmarks would ever justify.

Key points

What matters most.

What value-based pricing actually is, how it differs from cost-plus and competitor pricing, and the metric that holds the whole model together.

Definition

Price from outcome, not cost.

Value-based pricing anchors the price to the measurable outcome the customer gets from the product. Revenue delivered, cost avoided, hours returned, risk reduced, and conversion lifted are the usual outcomes. The vendor quantifies that number for a defined segment and charges a disciplined fraction of it, instead of marking up a cost structure or matching a competitor list price.

The ten to twenty rule

Charge a fraction of value created.

A healthy value-based price captures roughly ten to twenty percent of the quantified value the customer receives. The customer keeps the larger share, which is what makes the deal defensible, and the vendor gets a price well above cost-plus. Patrick Campbell and the ProfitWell team popularized this ratio as the practical range where both sides win over multi-year relationships.

Not cost-plus

Cost is a floor, not a target.

Cost-plus pricing adds a margin to internal cost and ignores what the customer is willing to pay. It leaves money on the table whenever value exceeds cost, which is nearly always in software. Value-based pricing treats cost as a hard floor the price must clear, then sets the actual number from the outcome, not the input.

Not competitor matching

The list across the street is noise.

Competitor pricing anchors the number to whatever a rival charges, which bakes their mistakes into your business. Their cost base, segment, positioning, and roadmap are not yours. Value-based pricing starts from the customer and the outcome, uses competitor data as context, and refuses to let a competitor set the ceiling on what the product is worth.

Requires a value metric

The unit the value is measured in.

Value-based pricing only works when the outcome can be stated in a specific unit, like dollars of pipeline accepted, hours of manual work removed per month, or percentage points of conversion added. Without a crisp value metric the pricing conversation collapses back into feature comparisons and the vendor loses the frame that justifies the number.

Segment-specific

The same product is worth different numbers.

A twelve-person startup and a three-thousand-person enterprise do not get the same dollar outcome from the same product. Value-based pricing is segmented by firmographic and use case, with a defined value model and willingness-to-pay band for each segment. One list price for the whole market is almost always leaving money on both ends.

How it works

The anatomy of a value-based price.

Every disciplined value-based price is built from the same four components: a segment, a value model, a willingness-to-pay band, and a value metric that holds everything together. Teams that skip a step end up back on cost-plus by accident.

Segment definition

Pick who the price is for.

Value-based pricing starts with a specific customer segment, usually defined by company size, industry, and the job they hire the product to do. The same software is worth very different amounts across segments, so the pricing exercise runs once per segment, not once across the whole market.

Value model

Quantify what they get.

The value model is a short arithmetic proof that converts product capability into dollars of outcome for the segment. It might read: fifty reps, two extra meetings a week, twenty percent close rate, average deal size forty thousand dollars, equals two million dollars of annual pipeline accepted. The output is a single defensible number.

Willingness to pay

Research the band, not a point.

Willingness to pay is researched through buyer interviews, Van Westendorp price-sensitivity surveys, and conjoint analysis. The output is a band with a lower bound where buyers see the price as cheap, an upper bound where they walk away, and a sweet spot in between. That band and the ten-to-twenty rule triangulate the list price.

Value metric

Pick the scaling unit.

The value metric is the unit the invoice scales with as the customer gets more value: seats using the product, pipeline accepted, documents processed, leads qualified. A strong metric rises with outcome from the customer's perspective, is easy to measure, and makes the invoice feel like a share of success rather than a tax on activity.

Capture ratio

Ten to twenty percent of value.

A healthy value-based price captures roughly a tenth to a fifth of the quantified value the customer receives. Below ten percent and the vendor is giving the product away. Above twenty percent and the deal starts to feel exploitative and churn risk rises. The ratio is a sanity check, not an iron law, but it holds across most SaaS categories.

Narrative anchor

The sentence that sells the number.

Every value-based price needs a one-sentence anchor that connects the number to the outcome. It is the sentence a champion repeats to their CFO when they justify the purchase. Without that sentence, the price becomes a negotiation starting point. With it, the price becomes a share of a result both sides already agreed on.

The three models

Value-based vs cost-plus vs competitor pricing.

Three pricing philosophies compete for every SaaS team's attention. They produce very different numbers for the same product, and the model a team picks quietly shapes gross margin, growth rate, and valuation for years.

Cost-plus

Price from the input side.

Cost-plus pricing adds a target margin on top of production and delivery cost. The method is defensible to procurement and easy to compute, but it ignores customer willingness to pay. In software, where marginal cost is near zero, cost-plus almost always underprices the product and caps the business well below what the market would support.

Competitor pricing

Price from the market across the street.

Competitor pricing matches, undercuts, or marks up relative to a rival list price. It is comfortable because the number already exists in the world, but it imports the competitor's segment, cost base, and strategic mistakes. Any team that leads with competitor benchmarks is letting a competitor set the ceiling on what their own product is allowed to earn.

Value-based

Price from the customer outcome.

Value-based pricing starts from the dollar value the customer receives, applies a capture ratio, and lands on a defensible list price. It is the hardest model to run because it requires buyer research, segmentation, and a crisp value metric, but it produces the strongest unit economics and the longest runway for pricing power as the product matures.

When cost-plus fits

Commodities and regulated inputs.

Cost-plus still fits in categories where the product is a commodity, where regulated pricing requires auditable margin, or where the vendor has no visibility into customer outcome. For most B2B SaaS, none of those conditions hold, which is why the category has moved so decisively away from cost-plus thinking over the last decade.

When competitor pricing fits

Perfect substitutes in mature categories.

Competitor pricing is defensible in mature categories where the product is a near-perfect substitute for a well-known rival and the buyer actively compares list prices line by line. In most B2B SaaS the product is differentiated, the buyer evaluates on fit rather than list, and competitor pricing undersells the actual value gap.

The hybrid in practice

Value sets the price, the others sanity-check it.

Mature pricing teams use value-based pricing to set the number, cost-plus to sanity-check the floor, and competitor data as context in sales conversations. The three models are not alternatives in the end. They are inputs with different weights, and value-based has the heaviest weight by far in software.

The hard parts

Why value-based pricing is harder than it reads.

Value-based pricing is the model with the strongest math and the longest implementation path. Teams that move to it underestimate the research, the segmentation, and the organizational muscle required to defend the number inside live sales conversations.

Research cost

The value model is real work.

Quantifying customer outcome demands buyer interviews, use-case studies, benchmark data, and a value model the sales team can run on a whiteboard. The research is weeks of effort per segment, and the output has to be refreshed as the product and market move. Most teams underestimate the ongoing cost of keeping the value model current.

Segment discipline

One price does not fit all.

A disciplined value-based motion runs the pricing exercise per segment, with different list prices or packaging per segment. Teams that collapse everything into a single list leak revenue at the top and lose deals at the bottom. The segmentation is where the model earns its margin, and skipping it defeats the whole approach.

Sales enablement

Reps must sell the outcome.

Value-based pricing fails if the sales team sells features and leaves the value conversation on the pricing page. Reps need the value model as a native tool, the ability to run it live with a prospect, and the muscle to defend a price that is anchored to outcome rather than seat count. That is a hiring and training shift, not a pricing-page update.

Narrative risk

The outcome has to land.

If the value model promises a hundred thousand dollars of outcome and the customer sees ten thousand, the entire relationship is poisoned. Value-based pricing demands conservative value models, honest benchmarks, and a customer success motion that drives the outcome the pricing already promised. The narrative at close becomes a commitment, not a brochure.

Procurement friction

Buyers want cost-plus logic back.

Procurement teams are trained to compare price to cost. A value-based number without a cost reference feels arbitrary and triggers price audits. Mature value-based motions arm the champion with the narrative and the math to answer procurement in their own language, which is a sales artifact, not a change to the pricing itself.

Continuous update

The number is a living artifact.

The value a product creates changes as the product matures, the segment matures, and the market reprices. Value-based pricing is not a one-time project. The best teams revisit the value model, the capture ratio, and the willingness-to-pay band annually, and expect to raise or restructure prices on a predictable cadence.

Set prices from outcome, not guesswork.

Strkr lands quantified value on every account, feeds the forecast from realized outcome, and keeps renewal and expansion workflows anchored to the same number the sales team sold on. One record, one value story, one pricing conversation that holds.

Start free See the platform

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.