Test your pricing page
How to test plan layout, anchoring and copy on a pricing page without changing what anyone pays.

Start with presentation, not price
Changing a price creates fairness and legal questions. Changing how plans are laid out does not. Most of the available gain is in presentation, so test that first.
What to test
- Which plan is marked recommended.
- The order of plans, low to high or high to low.
- Monthly versus annual shown by default.
- Feature list length on each plan.
- The wording on the main button.
Bucket by account, not by visit
A visitor who sees two different pages on two different days will lose trust. Bucket by a stable identifier, and keep the assignment for the length of the trial.
Pick a metric that reaches the bank
Clicks on a plan button are a weak signal. Use trial starts at least, and paid conversions where the volume allows. If your sales cycle is long, use a leading indicator that you have shown predicts payment.
Watch the guardrails
Cheaper looking pages can lift conversion and raise refunds. Track refund requests, support contacts and plan downgrades for the buckets over the full trial window.
Segment, then be careful
Check whether the effect differs for small and large teams. Treat segment results as hypotheses and confirm them with a follow up test.
When you are ready to test price
Limit the test to new visitors, use a narrow range around the current price, and get finance and legal to sign off first. Never show a different price to an existing customer.
More playbooks

Run your first checkout test
A step by step plan for testing a checkout change without risking revenue.

Improve onboarding activation
A playbook for finding your activation event and running a steady series of onboarding tests.

Run a painted door test
Measure demand for a feature before you build it, using a fake entry point and an honest follow up.