Design to Cost · Target
Price-Value Alignment
Check that the price customers accept matches the value they perceive — a gap means margin risk or value left unpriced.
- Time45 min
- FormatSmall group
- StageTarget
Price-Value Alignment: what it is and why it works
Price-value alignment checks whether the price you charge matches the value customers actually perceive, feature by feature. You map the product's features against evidence of what buyers pay for, taken from interviews, win/loss reviews and lost-bid debriefs. Two kinds of mismatch appear: features that add cost but no perceived value, and value customers want that the product does not deliver. For each feature the team then decides to invest, keep, simplify or drop, and those decisions flow back into the target cost allocation.
The method matters most when prices are built as cost plus markup, because that approach assumes customers value every dollar of cost equally, which they rarely do. Aligning price to value first and cost to price second protects margin in two directions: it stops spending on features nobody rewards, and it reveals value that could be priced but is currently given away. It draws on the same logic as value analysis, which judges every cost by the function it delivers. Kano classification helps explain why some features are ignored, value perception maps show where you overspend relative to competitors, and functional analysis translates feature decisions into design changes.
What you need
- A list of the product's main features, options and service elements
- Evidence on customer value: interviews, win/loss analysis, lost-bid debriefs, service feedback
- Current pricing structure, including discounts and how options are priced
- An approximate cost per feature from the cost breakdown
- Competitor offers and price points for the same segment
What you get
- A feature map marking cost-without-value and value-without-delivery
- A decision per feature: invest, keep, simplify or drop
- Candidate price or packaging changes for features that deliver unpriced value
- Updated inputs to the target cost allocation
When to use it
When pricing is cost-plus and the market quietly disagrees.
How to do it, step by step
- Map the main product features against what customers actually pay for, from interviews or win/loss data.
- Mark features that add cost but no perceived value.
- Mark value that customers want but the product does not deliver.
- Decide per feature: invest, keep, simplify, or drop.
- Feed the decisions back into the target cost allocation.
Worked example: Electric valve actuators for water utilities
Illustrative scenario — figures are realistic but not from a real company.
A manufacturer of electric valve actuators for water and wastewater plants priced its range at cost plus a fixed markup. Win rates had fallen on mid-size municipal bids, while margins on the range were slipping. The team reviewed 60 recent bids and interviewed 12 plant engineers and system integrators.
- The team listed eight features, including a stainless steel housing, local display, Bluetooth commissioning, fieldbus interfaces, a fail-safe option and a five-year warranty.
- The stainless housing, standard on every unit and worth about $140 over coated aluminum, was rarely mentioned by buyers for indoor installations; it was flagged as cost without value for that segment.
- Integrators consistently cited fast fieldbus integration and short delivery as reasons for choosing a supplier, yet fieldbus was priced as a low-margin add-on and delivery was not promised in quotes.
- The team decided to make coated aluminum standard with stainless as a priced option, keep the display, simplify Bluetooth commissioning to one app, and invest in pre-configured fieldbus profiles.
- The revised feature list and cost shifts were passed into the actuator target cost allocation for the next revision.
Result. In the following two quarters, the standard actuator cost fell by roughly $120 while the fieldbus package, now priced at its value, carried a healthier margin. Win rates on integrator-led bids improved. The team learned that the loudest internal opinions about which features mattered were the least reliable source.
Common pitfalls and how to avoid them
- Relying on the sales team's opinions instead of customer evidence.Use win/loss data, bid debriefs and direct interviews, and record who said what.
- Treating all customers as one segment, so a feature valued by one group is dropped for all.Analyze by segment and consider making segment-specific features into priced options.
- Cutting features without checking regulatory, safety or specification requirements.Screen every drop or simplify decision against standards and typical tender specifications before acting.
- Stopping at the analysis without changing the target cost or price list.Close the loop: update the cost allocation, the option structure and the pricing in the same cycle.
Frequently asked questions
What is the difference between cost-plus and value-based pricing?
Cost-plus pricing adds a markup to the product's cost, so price follows cost. Value-based pricing sets the price from what customers perceive the product is worth compared with alternatives. Cost-plus is simple but can underprice valuable features and overprice ones customers ignore. Value-based pricing requires evidence about customer value but lets price and cost be managed separately.
How do you measure perceived value in B2B markets?
Combine several sources: structured interviews with buyers and users, win/loss reviews, lost-bid debriefs, and the economics of the customer's operation, such as downtime, energy or labor saved. In industrial markets, value is often visible in total cost of ownership and in what integrators or contractors say saves them time. Look for consistent patterns across sources rather than single anecdotes.
How does price-value alignment relate to target costing?
Target costing starts from an acceptable market price. Price-value alignment checks that this price reflects what customers actually value and that the cost is spent on the right features. Its decisions to invest in, simplify or drop features feed directly into how the target cost is allocated across modules and options.
Origin
Value-based pricing logic — industrial economics; linked to value analysis (L. D. Miles, GE, 1947).
Related methods
- Kano ClassificationSort features by customer reaction: basics, performers, delighters — and question the ones nobody would miss.
- Value Perception MapPlot what customers value against what it costs to deliver; the expensive-ignored quadrant is your saving…
- Functional AnalysisExpress the product as functions — verb plus object — free of solutions: what must it do, not how.
More in “Target”
Set the cost the market allows — before designing a single part.