Use case
Pricing testing
Get a price range and the reasoning behind it before you touch the paywall.
The problem
Why this is hard today.
Pricing is the decision with the most revenue attached and the least evidence behind it. Proper willingness to pay research is slow and expensive enough that most teams skip straight to copying a competitor.
How userken does it
Four steps.
- Pick an audience, usually a category plus your own app so you can see the gap.
- Describe the thing being priced and the unit, for example a monthly subscription.
- Run a Van Westendorp sequence: too cheap, cheap, expensive, too expensive, asked of every persona and weighted by segment size.
- Read the acceptable range and the indifference point, then read the verbatims, which is where the actual objection lives.
run_pricing_test
Van Westendorp sequence with a weighted acceptable range.
ask_audience
Follow up on a specific price point or bundle.
Van Westendorp template
In-app template, four questions, one chart.
Tool names are the MCP tools and in-app templates. The same engines power both.
Illustration
What a run looks like.
Illustrative example, not a result we are reporting
Illustration: a news app tests an ad free tier
- Audience: the news category, reviews from the last 18 months, ratings 1 to 5.
- Sequence: the four Van Westendorp questions about a monthly ad free subscription.
- What you would read: the range, plus whether the ad fatigued segment and the loyal subscriber segment want different things for the same money.
Stated willingness to pay is not revenue. Treat the range as a shortlist to test for real, not as a forecast.
Related
Next door to this.
Run a pricing testing on your category.
Accounts are provisioned by hand during early access. Tell us the question and the category and we will set you up.