A/B testing a SaaS pricing page requires treating revenue per visitor — not conversion rate — as the primary metric, because a pricing change that increases trial signups while reducing average contract value produces a positive-looking experiment that is actually destroying revenue.
Pricing page A/B testing is one of the highest-leverage and most commonly misexecuted growth experiments. Teams optimize for click-through rate on the primary CTA when the actual outcome that matters is revenue impact — which requires a longer measurement window and more sophisticated metric definition than most experimentation platforms use by default.
The Three Categories of Pricing Page Experiments
H3: Category 1 — Anchoring and Plan Structure
These experiments change how options are presented relative to each other.
Hypotheses to test:
- 3-plan structure (Starter/Pro/Enterprise) vs. 2-plan structure (Team/Enterprise)
- Which plan is visually highlighted as "Most Popular" or "Recommended"
- Annual vs. monthly pricing as the default display
- Anchor plan price point (the most expensive plan shown sets the anchor)
Why it matters: Displaying a high-priced enterprise plan first can increase mid-tier plan conversion by 20–40% through price anchoring effects.
H3: Category 2 — Social Proof and Trust Signals
Hypotheses to test:
- Customer logos above vs. below the plan cards
- Testimonial placement (adjacent to the plan that matches the customer size)
- Review scores from G2/Capterra displayed vs. not displayed
- Customer count or ARR milestone displayed
Why it matters: B2B pricing page trust signals have asymmetric impact — their presence rarely hurts, but their absence on high-price plans is correlated with friction.
H3: Category 3 — Friction Reduction
Hypotheses to test:
- Free trial CTA vs. "Get started" vs. "Book a demo"
- Credit card required vs. not required for free trial
- Number of plan comparison features shown (fewer vs. more)
- Feature name specificity ("Advanced analytics" vs. "Custom dashboards with 50+ metrics")
Pricing Page Experiment Design Requirements
1. Use revenue per visitor as the primary metric. Configure your experiment platform to track actual paid conversion, not free trial signups. This requires a 30–45 day measurement window for most SaaS products.
2. Separate plan selection from checkout completion. Measure: (a) which plan the user selects, and (b) whether they complete checkout. These can diverge and tell different stories.
3. Segment by traffic source. Organic searchers, paid traffic, and direct/branded traffic have different conversion baselines — running unsegmented pricing tests obscures which segment is driving the result.
4. Be conservative with pricing experiments. Unlike onboarding tests, pricing page experiments can damage trust if users who saw different prices compare notes. Avoid showing different prices to different users — test presentation and framing, not the prices themselves.
FAQ
Q: What are best practices for A/B testing a SaaS pricing page? A: Use revenue per visitor as the primary metric, not conversion rate. Segment by traffic source, run tests for 30 to 45 days to capture actual paid conversion, and focus experiments on anchoring, social proof, and friction reduction — not on showing different prices to different users.
Q: What is the highest-leverage pricing page A/B test for SaaS? A: Plan structure and anchoring experiments — changing which plan is highlighted as recommended, the number of plans shown, and the anchor price point — consistently produce the largest revenue per visitor impact.
Q: How long should you run a SaaS pricing page A/B test? A: 30 to 45 days minimum to capture actual paid conversion, not free trial signups. Pricing decisions have longer conversion cycles than most onboarding experiments.
Q: Should you A/B test showing different prices to different users? A: No. Testing price framing and presentation is safe; showing different actual prices to different users risks trust damage when users compare experiences and is a potential legal issue in some jurisdictions.
Q: What metrics should you track in a SaaS pricing page A/B test? A: Revenue per visitor (primary), plan selection rate by tier, checkout completion rate by plan, and annual vs. monthly plan selection rate.
HowTo: Conduct A/B Testing for a SaaS Pricing Page
- Define revenue per visitor as your primary metric and configure your experiment platform to track paid conversion, not free trial signups
- Identify your highest-leverage test category: anchoring and plan structure, social proof and trust signals, or friction reduction
- Segment your test population by traffic source — organic, paid, and direct — to read results by user intent level
- Run each pricing test for at least 30 to 45 days to capture actual paid conversion in the measurement window
- Measure plan selection rate and checkout completion rate separately to identify whether friction is in the plan selection or the checkout step
- Document all pricing page test results in a shared log accessible to the growth, sales, and finance teams — pricing decisions affect more stakeholders than most product experiments