How to Interpret Conjoint Analysis Results

What Does Conjoint Analysis Output Look Like?

Conjoint analysis produces four main outputs: part-worth utilities for each attribute level, relative importance scores for each attribute, willingness-to-pay estimates when price is included, and a market simulator for testing hypothetical product scenarios. Understanding how to read each one turns raw numbers into product decisions.

The numbers themselves aren't intuitive at first glance. A utility score of 85 for "$29/month" means nothing in isolation. But when you compare it to -112 for "$129/month," you're measuring exactly how much that price difference matters to respondents relative to other features. This guide walks through each output with worked examples so you can extract the right insights from your data.

Part-Worth Utilities: The Core Output

Part-worth utilities (sometimes called "partworths" or "utility scores") are the building blocks of everything else in conjoint. Each level of each attribute gets a score. Higher scores mean stronger preference.

How to Read Them

Here's an example from a SaaS pricing study with 400 respondents:

Three Rules for Reading Utilities

Rule 1: Compare within attributes, never across them. The 85 for "$29/mo" and the 39 for "Unlimited users" aren't on the same scale. You can't say $29/mo is "preferred more" than unlimited users. The scales are relative within each attribute because of how the math works (zero-centered within each attribute).

Rule 2: Differences between levels are what matter. The gap between $29 (85) and $49 (42) is 43 utility points. The gap between $49 (42) and $79 (-15) is 57 points. That second price jump hurts more, even though both are $30 increases. This tells you there's a psychological price threshold between $49 and $79.

Rule 3: Negative utilities aren't "bad." A utility of -45 for "10 GB" doesn't mean respondents dislike 10 GB storage. It means they prefer every other storage option more. If you offered a product with 10 GB storage and every other feature at its best level, plenty of respondents would still choose it. Utilities are relative, not absolute.

Spotting Surprises

Look for non-linear patterns. In the storage example above, Unlimited (5) scores lower than 200 GB (28). That's counterintuitive but common. Respondents may distrust "unlimited" marketing claims, or they may not value the jump from 200 GB to unlimited enough to offset the skepticism. These surprises are some of the most valuable findings in a conjoint study.

Relative Importance Scores

Importance scores answer: "Which attributes drive the most decisions overall?"

The Calculation

For each attribute, take the range of utilities (highest minus lowest). Then calculate each attribute's share of the total range:

Importance = attribute range / sum of all attribute ranges

From our example:

• Price range: 85 - (-112) = 197
• Storage range: 28 - (-45) = 73
• Users range: 39 - (-62) = 101
• Support range: 15 - (-22) = 37

Total: 197 + 73 + 101 + 37 = 408

Price drives nearly half the decision. Support barely registers. If your product team is debating whether to invest in better support tiers or more competitive pricing, the data says pricing wins by a wide margin.

Importance Score Limitations

They're relative to your study. An attribute's importance depends on what else is in the study. If you'd included "brand" as an attribute, Price might have dropped to 35%. Importance scores are valid within a study but shouldn't be compared across studies with different attribute sets.

They're averages. A 48% importance for Price is the average across all respondents. Some segments may care far more about Users (B2B teams) while others are primarily price-sensitive (freelancers). Always check segment-level importance before making blanket decisions.

They're driven by level range. If your Price levels span $29-$129 (4.4x range) but your Storage levels span 10 GB-Unlimited, the ranges aren't equivalent in consumer perception. Wider level ranges can inflate an attribute's apparent importance. Keep this in mind when comparing attributes with very different level spreads.

Willingness to Pay (WTP)

When price is one of your attributes, you can calculate dollar values for every other feature. This is one of conjoint's most powerful outputs.

The Calculation

First, calculate the utility-per-dollar rate from your Price attribute:

Price range in dollars: $129 - $29 = $100 Price range in utility: 85 - (-112) = 197 Utility per dollar: 197 / 100 = 1.97 utils per dollar

Now divide any feature's utility gain by this rate:

• Upgrading from 10 GB to 200 GB storage: 28 - (-45) = 73 utils. WTP = 73 / 1.97 = $37/month
• Upgrading from 1 user to Unlimited users: 39 - (-62) = 101 utils. WTP = 101 / 1.97 = $51/month
• Upgrading from Email to Phone support: 15 - (-22) = 37 utils. WTP = 37 / 1.97 = $19/month

These numbers tell your product team exactly what each feature is worth in pricing terms. Unlimited users is worth $51/month to the average respondent. If you can add it for less than that, it's a clear value-add.

WTP Caveats

Stated WTP from conjoint tends to run 15-30% higher than what people actually pay. Use the numbers for relative comparisons between features (unlimited users is worth roughly 2.7x what phone support is worth) rather than as exact price points.

Market Simulation

The market simulator takes utility scores and predicts share of preference for specific product configurations.

How It Works

Define 2-5 product profiles (yours plus competitors) by specifying a level for each attribute. The simulator calculates total utility for each profile (summing the part-worths across attributes), then converts those into predicted market shares using a logit or randomized first choice model.

Example Scenario

Scenario: You're choosing between two pricing strategies.

The simulator might predict: Product A captures 42% preference share, Product B captures 35%, Competitor captures 23%. That tells you the lower price point with 200 GB wins more share than the premium configuration, even though Product B has objectively "better" features.

Run 10-20 scenarios to map the decision space. The point isn't to find one optimal product; it's to understand which trade-offs gain or lose share and by how much.

Presenting Results to Stakeholders

Skip the utility tables. Non-technical audiences need three things:

1. Importance bar chart. A horizontal bar chart showing relative importance of each attribute. This answers "what matters most to our customers?" in one visual.

2. WTP comparison. A table or chart showing dollar values for key features. This answers "what are customers willing to pay for each upgrade?"

3. 2-3 simulation scenarios. Show the share-of-preference results for the specific product configurations your team is debating. This answers "what happens if we do X?"

Frame everything as business decisions, not statistical outputs. "Unlimited users is worth $51/month to customers" is actionable. "Unlimited users has a part-worth utility of 39 in a zero-centered model" is not.

Frequently Asked Questions

Can I compare utilities across different conjoint studies?

No. Utility scales are specific to each study's attributes and levels. An attribute that scores 40 in one study and 60 in another isn't necessarily more important in the second study. If you need cross-study comparisons, use the same attribute set and level definitions in both studies.

What does it mean when the "none" option has high utility?

A high "none" share in simulations means your product configurations aren't compelling enough to pull respondents away from not buying. It's a signal that your attribute levels need adjustment or that the market isn't ready for what you're testing.

How do I know if utility differences are statistically significant?

Check the standard errors or confidence intervals around each utility estimate. If the confidence intervals for two levels overlap substantially, you can't reliably distinguish between them. Most conjoint software reports these alongside the utility estimates.

Related Guides

• Conjoint Analysis: Complete Guide -- Full methodology overview
• Conjoint Analysis Examples by Industry -- See interpretation in context
• How to Design a Conjoint Study -- Design decisions that affect what you can interpret
• Conjoint Analysis Sample Size Requirements -- Why sample size affects estimate precision
• Van Westendorp Pricing Model -- Simpler alternative for pricing-only questions
• Conjoint Sample Size Calculator -- Plan your study for reliable estimates

Analyze conjoint results in real time -- try Quali-Fi free for 14 days.