Find the benefit your audience finds most compelling and actually believes. Refine it before you ship the page, the ad or the deck.
Value proposition testing answers one question: which benefit should we lead with? It is one of the four kinds of concept test. Use it when the product is settled and the promise isn’t.
Show people the product first, then ask about the promise. Synthetic participants meet the concept, then hear each benefit statement and say whether it’s compelling and whether they believe it. The report separates a benefit that doesn’t appeal from one people understood and didn’t buy, because each has a different fix.
Run a value proposition test right before a homepage rewrite, a launch campaign, a sales deck refresh or a positioning shift, when shipping the wrong promise is expensive and testing first is cheap.
It catches the benefit that sounds sharp in the boardroom and lands as generic, or unbelievable, with the audience it was written for.
The concept comes first. Participants who haven’t met it see it and are checked for understanding; participants who have are asked to recall it, without it being pitched again.
Each benefit statement, shown word for word and in a different order for each participant: is it compelling, and do they believe it?
A choice at the end: the most compelling statement, and the least believable one.
A concept test report titled by what you ran (“Value proposition test v1”), with the statements compared rather than whole concepts. Each section appears when the interviews give it something to show.
Find the concept worth sharpening with concept testing, then test how to state its benefit.
A name is judged against a settled promise, so run name testing and messaging testing once the benefit is chosen.
How you state the value shapes what people will pay, so test the price against the benefit you chose.
A standard concept test asks whether an idea lands at all. A value proposition test starts from one concept you've settled on and asks which way of stating its benefit people find most compelling and believe. Participants meet the concept first, then hear each benefit statement in that context. Most teams run the standard test once, then a value proposition test when it's time to decide what the homepage, the ad or the sales deck leads with.
No. The test is about whether your words carry the benefit you intend, to the audience you mean, not whether the product works. You can test benefit statements for something still in development, a repositioning of a live product, or a campaign that hasn't launched. What you do need is a concept clear enough that participants understand what the product is before they judge what it promises.
As you'd ship them, one benefit per statement. Candor checks each option before you move on to the next step. A bare product name or a whole product description isn't a benefit statement, so that blocks the test until you replace it, because it would waste the run. Softer issues, like a vague benefit or a feature stated instead of a benefit, get a note that doesn't block, often with a suggested rewrite of your own wording.
2 to 5 in one test. Two gives you a clean head-to-head. Three or four let you span a range, such as outcome-led against feature-led, or practical against emotional. If you have more candidates, cut to the strongest few first. Every participant hears every statement, so a long list blurs the comparison rather than sharpening it.
It means participants understood the claim and didn't buy it. That's a different problem from a benefit that doesn't appeal, and it has a different fix: back the claim with proof, or make it smaller and credible. The report counts that apart from participants who misread the claim, which needs a clearer rewrite instead. Both are flagged at the top, so you can deal with them before you compare which benefit won.
Start with a free project, or walk through Candor with us first.