Pricing Page Usability Test Questions and Script

Pricing-page research answers one question: can a buyer connect your plans, limits, and charges to their own situation? A consenting participant compares the plans, then a focused voice debrief covers what they used to decide and what they could not find.

Run it when analytics shows visits without a plan selection, when sales keeps clarifying the same limit, or when users pick a plan that does not fit. It studies comprehension and decision context — not willingness to pay, and not the right price.

Choose one pricing question

Focus the Study on one decision, such as “Can a small team work out which plan covers its usage?” Invite people you can already reach who actually make or influence that call, and let them bring their real constraints instead of handing them an answer in the task.

Do not fold pricing comprehension, checkout usability, and cancellation into one study. If the plan choice is clear but payment fails, that is a separate workflow.

Adapt this study script

In UserTold that is a Talk segment for context, a silent Observe segment while they compare, and a second Talk for the debrief. Turn on Pre-debrief analysis for that second Talk so its questions draw on the speech and product activity before it. Show the study only on your pricing page, and read the invitation once more before you publish.

Follow the Quickstart to install the Project snippet. Use Study Design for the field and advancement rules.

Ask about the decision without suggesting an answer

• Which information did you use to decide whether this plan fits?
• How would you explain the charge to a teammate?
• What did you expect that limit to include?
• What information would you need before deciding?
• You returned to the comparison table. What were you looking for then?

Ask the last one only if you actually saw them go back. Do not ask “Was our pricing confusing?”, and do not read a pause as “too expensive”.

Copy the complete pricing page test script

Replace the team and plan language with the real situation your buyers bring to the page. The task stops before purchase.

{
  "version": 2,
  "goals": [
    {
      "id": "plan-choice",
      "description": "Learn whether a small team can identify the plan, limits, and expected charge that fit its current usage."
    }
  ],
  "segments": [
    {
      "id": "buyer-context",
      "mode": "talk",
      "title": "The buyer's situation",
      "talk": {
        "research_mode": "discovery",
        "goals": ["plan-choice"],
        "system_prompt": "Ask the participant to describe the team, expected usage, and constraints they would use to choose a plan. Ask one question at a time. Do not recommend a plan or explain the pricing page."
      }
    },
    {
      "id": "instructions",
      "mode": "speak",
      "title": "Instructions",
      "speak_text": "Using the situation you described, find the plan you would consider and the information you need to decide. Stop before purchasing. I will stay quiet while you compare the options; choose Done when you are ready to talk."
    },
    {
      "id": "compare-plans",
      "mode": "observe",
      "title": "Compare the plans",
      "instruction": "Find the plan you would consider for your current situation and the information you need to decide. Stop before purchasing.",
      "conductor_context": "Preserve which plans, limits, pricing examples, and supporting pages the participant checks. Do not assume a pause means that the price is too high or that a return visit means confusion.",
      "max_duration_s": 300
    },
    {
      "id": "decision-debrief",
      "mode": "talk",
      "title": "Explain the decision",
      "talk": {
        "research_mode": "usability_debrief",
        "goals": ["plan-choice"],
        "system_prompt": "Use the captured comparison context to ask which information the participant used, how they interpreted limits and charges, and what remained unanswered. Ask about a return or hesitation only when the context supports it. Ask one question at a time; do not recommend a plan or suggest that pricing was confusing."
      },
      "experimental_capabilities": {
        "realtime_analysis": true
      }
    },
    {
      "id": "thanks",
      "mode": "speak",
      "title": "Thanks",
      "speak_text": "Thanks for comparing the plans and explaining how you made the decision."
    }
  ]
}

Ask your agent to adapt it

Adapt the pricing page usability test at https://usertold.ai/use-cases/pricing-page-research to my product.

Ask me for the pricing URL, the buyer segment, the real usage constraints they bring, and any action the test must stop before. Keep pricing comprehension separate from willingness to pay and checkout usability. Show the complete Study JSON and wait for approval before saving or activating anything.

Review a concrete example

A buyer returns to a usage FAQ, then says they cannot tell whether usage is counted per person or across the team.

The evidence is the path plus the explanation. A Finding you could defend: “The usage unit is unclear to this buyer when estimating team cost.” Not: the product is overpriced.

Before choosing a fix, read the current page again and check your other interviews. The answer may be a clearer unit label or a worked cost example. A price cut answers a different question.

Use interview analysis to keep the source and interpretation separate, then prioritize the supported problem.

Measure the change with the same task

Repeat the same comprehension task with comparable participants and check whether they can explain the unit, the limits, and the charge they expect in their own words. Read plan-selection and checkout analytics separately. A conversion change on its own does not tell you the copy caused it.

See the interviewer and start a study

See how observation feeds the debrief on the AI user interviewer page. If your uncertainty is broader than plan comprehension, start with Feature Request Interview Questions, Churn Interview Questions, or another User Interview Script Template.