✦ Task type · Research and checks
Pricing pages fail by being understood differently
Almost nobody says a pricing page is confusing. They pick the wrong tier, guess a number that is not on the page, and leave, and none of that appears as confusion in any tool you own.
Pricing pages rarely fail by being unclear in the way a survey would detect. They fail by being clear about something other than what you meant, and the reader leaves confident and wrong.
What to put in the public brief
- That it is written feedback on a pricing page
- The rough category
- How long a response you expect
- That there is no product to install or buy
Keep the URL and the brand private, or you get answers from people who already know what you charge.
What to put in the private instructions
Give a scenario before the link
Concrete: team size, usage, budget sensitivity. A person reading pricing with no situation in mind reads it as a critic rather than a buyer.
Ask what it would cost them, in a number
Before asking anything else. The gap between their number and the real one is the finding, and everything afterwards is explanation.
Ask which tier and why they rejected the one below
The rejection reason is more useful than the choice. It is the line that is doing the work on your page, or failing to.
Ask what they still do not know
Limits, overages, what happens at renewal, whether support is included. Every item on that list is a support ticket you have not received yet.
Proof worth requiring
Ask for
Their estimated cost as a number, the tier they chose, why they rejected the adjacent one, and the list of things still unclear.
Do not ask for
Whether the price seems fair. Strangers with no stake reliably say things are expensive, and you will learn nothing you can price against.
When this task type is the wrong tool
If people never reach pricing, the problem is earlier — a first-impression test will find it faster.
If they understand the page and still do not buy, that is an offer problem rather than a comprehension one, and concept feedback asks the right question about it.
Common questions
What is the single most useful question?
"What would this cost you, per month, in your situation." Not whether it is clear, not whether it seems good value. A number they arrive at themselves either matches your intent or reveals exactly where the page misled them.
How do I test tier choice without leading?
Give them a scenario rather than asking which tier they prefer. "You are two people and you send about fifty of these a month, which would you choose and why" produces a decision; "which plan looks best" produces a preference for the middle one, which is what the layout already suggested.
What reward is fair?
Six to fourteen dollars. It is reading and reasoning rather than clicking, and the paragraph you want at the end is only worth reading if the reward justified writing it.
Should I test against competitor pricing?
Usually not in the same task. Comparison shifts attention to relative value and away from comprehension, which is what you need first. Get people to understand your page before finding out how it stacks up.
Thinking of taking this task?
The same job, from the other side. Rewards are set by the poster, so treat these as the range this task type usually sits in rather than a promise.
- Usually pays
- $6 to $14
- You need
- Nothing beyond written attention
- Proof expected
- Your estimated cost as a number, plus written answers
Give your own number before reading closely. The gap between your guess and the real price is exactly what the poster is buying.
Create a worker accountTest your pricing
Set the reward and how many responses you need. Workers reserve a spot; the page stays private until it is theirs.
Post this task