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.