Learn Why Users Struggle to Choose a Plan
Pricing-page research asks whether users can connect your plans, limits, and charges to their own situation. UserTold lets a consenting participant compare the plans, then conducts a focused voice debrief about the information they used or could not find.
Use this study when analytics shows visits without a plan selection, sales conversations repeatedly clarify the same limit, or users choose a plan that does not fit. It investigates comprehension and decision context; it does not estimate willingness to pay or identify an optimal 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 users you can already reach who actually make or influence that decision. Include their real constraints rather than supplying an answer in the task.
Avoid combining pricing comprehension, checkout usability, and cancellation into one study. If the plan choice is clear but payment fails, that is a separate workflow to investigate.
A study you can adapt
This is an illustrative study script, not a customer result.
| Stage | Task or goal |
|---|---|
| Introduction | Explain that the study records the experience, that participation is voluntary, and that no purchase is required. |
| Context | Ask the participant to describe the team or project they would choose a plan for. |
| Observation | “Using this situation, find the plan you would consider and the information you need to decide. Stop before purchasing.” |
| Debrief | Understand how they interpreted limits, charges, and the fit to their situation. |
| Close | Ask what remains unanswered and thank them. |
In UserTold, use a planned Talk for context, silent Observe for comparison, and another Talk for the debrief. Enable realtime analysis for that debrief to use a running summary of the preceding speech and product activity. Set Visibility to the relevant pricing pathname and review the Invitation before activation.
Follow the Quickstart to install the Project snippet. Use Study Design and the pricing template to configure the flow.
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?
The final question is appropriate only when the return was actually observed. Do not ask “Was our pricing confusing?” or assume that a pause means the price was too high.
Review a concrete example
Illustrative example: a buyer returns to a usage FAQ, then says they cannot tell whether usage is counted per person or across the team.
The useful evidence is the observed path plus that explanation. A defensible Finding might be “The usage unit is unclear to this buyer when estimating team cost.” It does not establish that the product is overpriced.
Before choosing a fix, inspect the current page and other relevant interviews. The answer may be a clearer unit label or worked cost example. A price reduction addresses a different hypothesis.
Use interview analysis to keep the source and interpretation separate, then prioritize the supported problem.
What should we measure after a change?
Repeat the same comprehension task with appropriate participants. Check whether they can explain the unit, limits, and expected charge in their own words. Review relevant product analytics separately for plan selection and checkout behavior. A before/after change in conversion alone does not establish that the copy caused it.
See the interviewer and start a study
Explore the AI user interviewer to see how observation informs the debrief. If your uncertainty is broader than plan comprehension, start with identifying user needs or learning why users switch.