# How Many Pricing Plans Should You Show? Test Idea

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/how-many-pricing-plans-should-you-show-test-idea

## Hypothesis

In a set without the plan whose features overlap with another, visitors may compare the remaining options with less effort and hesitate less. The simplified set could then beat the full set on revenue per visitor, though that depends on which plan those buyers would turn to instead.

## When to run this test

Support questions about which plan to buy, session recordings of visitors moving back and forth between plans, or a rarely chosen plan whose features largely overlap with another are good reasons to try a slimmer plan set. When simplification helps, visitors who see the smaller set settle on a plan more easily, and revenue per visitor reflects it. If the hesitation comes from prices or unclear plan contents, fix those first, and pick the plan to remove for its overlap, not to leave the plan you most want to sell as the only path.

## Primary metric

**Revenue per visitor (RPV)**: Once both plan sets are defined, compare revenue per eligible assigned visitor over the same period.

## Other metrics

- **Average plan value**: Use plan value to explain revenue; a lower average does not necessarily mean lower revenue per visitor.
- **Plan selection rate**: Compare the share of visitors who select any plan.
- **Cancellation or downgrade rate**: Compare cancellations and downgrades after the same follow-up period.
- **Plan-selection support requests**: Track questions about choosing a plan using the same visitor denominator.

## What to check before and during the test

- **Plan sets**: Compare the current set with a version that removes one redundant tier, selected before launch based on overlapping features and the prior 90 days of plan selections.
- **Keep constant**: Keep prices, plan features and card design unchanged.
- **Revenue**: Decide using revenue per visitor, not plan selection alone.
- **Selection mix**: Review how plan choices shift to explain the result.
- **Audience**: Review customer groups separately without changing assignment rules.

## What to watch when reading the result

- A higher plan selection rate is not enough to ship the simplified set; revenue per visitor makes the call. A lower average plan value can still come with steady revenue, and more selections can still come with less of it, so read them together and compare cancellation or downgrade rates once both arms reach the end of the follow-up period.
- The result describes these two plan sets, not plan count in general. Keep existing subscribers of the removed plan out of the test, review customer groups separately, and treat removing a different plan as a new test.
- Revenue per visitor swings more than a selection rate, so a small gap may be noise at your traffic level. Before a rerun, get the sample per variant for the current plan selection rate and your target lift from the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator), then count the days of traffic per arm it takes; revenue, being noisier, needs even more. Also note how plan-selection support requests moved.

## Frequently Asked Questions

### How should the plan to remove be selected?

Choose one whose features substantially overlap with other plans using a predefined historical period. Exclude existing subscribers to the removed plan. The result concerns these two specific plan sets.

### Is more plan selection enough?

No. Use revenue per visitor as the primary outcome. Average plan value and conversion explain the result but cannot replace it.

### How can unsuitable purchases be detected after simplifying plans?

Monitor cancellations, downgrades and plan-selection support over equal follow-up windows. Do not remove alternatives simply to force buyers into one commercial choice.