Problems with conjoint for pricing
Conjoint captures trade-offs but misses context, thresholds and lock-in effects. It gives an illusion of precision that can lead to costly mispricing.
Conjoint analysis is a powerful tool for understanding how consumers weigh different product attributes against each other, including price. But as a pricing tool it has fundamental limitations. Conjoint presents price as one of several attributes in an experimental design — not as the central decision criterion it often is in reality.
The first problem is context. In a conjoint, the respondent sees a series of hypothetical choice situations that do not mirror the actual purchase situation. The second problem is thresholds. Conjoint assumes that price functions linearly within the design, and cannot identify the sharp acceptance thresholds that exist in reality. The third problem is lock-in — conjoint assumes the consumer is free to choose, but in many categories switching costs are high.
Reflect uses conjoint when it is the right tool — to understand relative preferences between product attributes. But for pricing decisions we always complement with monadic price measurement and context analysis. Relying solely on conjoint for pricing is building strategy on a simplification.
Key takeaways
- Conjoint treats price as one attribute among others, but price is special
- Experimental choice situations lack realistic purchase context
- Conjoint cannot identify sharp price thresholds
- Lock-in effects and switching costs are not captured
- Conjoint should be complemented with dedicated price measurement
Example
A tech company used conjoint to price its new subscription model. The results indicated customers would accept 149 SEK/month. In reality, the threshold at 99 SEK proved decisive — most customers mentally categorized anything above 100 SEK as "expensive" regardless of functionality.
Related articles
Why price is not linearWhy pricing must be top-downPrice perception and contextPrice barriers and thresholdsWhy willingness to pay is the wrong questionProblems with AI pricing without contextMonadic pricing modelCaptive demand and lock-in effectsReflect pricing frameworkSee related service →Discuss your pricing with us
Contact us