Use case
Message testing
Find the sentence that does the work, and the one that quietly costs you users.
The problem
Why this is hard today.
Positioning arguments are unresolvable without evidence, because every version sounds fine to the person who wrote it. Meanwhile the wrong emphasis does real damage: it attracts the wrong segment or reactivates an old complaint.
How userken does it
Four steps.
- Choose the audience, including the segments you are trying not to upset.
- Enter the message variants, up to six.
- Run a message test. You get clarity, believability and appeal read per variant, plus the weighted preference.
- Drill into any segment whose reaction diverges from the average.
run_message_test
Variant level read with clarity, believability and appeal.
run_name_test
The same mechanism for names rather than sentences.
Message test template
In-app template with per variant verbatims.
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 rewrites its subscription prompt
- Audience: reviewers of the category who mention paywalls or subscriptions.
- Variants: one leading on journalism funding, one on ad free reading, one on saved articles.
- What you would read: which variant the paywall sceptic segment finds believable, and which one makes them repeat the complaint they already left in a review.
Related
Next door to this.
Run a message 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.