Pricing A/B Test Design Planner
Design statistically valid pricing experiments with sample size calculations. Enter values for instant results with step-by-step formulas.
Formula
Sample Size per Variant = 2 × p(1-p) × (Zα + Zβ)² / MDE²; Revenue/Visitor = Conversion Rate × Price; Expected Conversion = Current × (1 + Price Change × Elasticity)
The sample size formula calculates visitors needed for statistical power, where p is the pooled conversion rate, Z values represent confidence and power levels, and MDE is the minimum detectable effect. Revenue per visitor combines conversion rate and price—the key metric for pricing tests. Expected conversion uses price elasticity to predict how conversion changes with price. This works because pricing effects on conversion are typically predictable through elasticity, and revenue optimization requires considering both price and volume. The sample size formula ensures enough data to detect real effects vs. random noise.
Worked Examples
Example 1: SaaS Monthly Plan
Problem:Current: $99/month, 3.5% conversion. Testing $119/month. 50,000 monthly visitors. Want 95% confidence.
Solution:Price increase: about 20.2% Expected conversion using the calculator's elasticity model: 3.5% × (1 - 0.303) ≈ 2.44% Required sample size: About 4,017 visitors per variant At 50,000 monthly visitors, the calculator estimates enough traffic in about 1 week. Revenue per visitor: Control = 3.5% × $99 = $3.47 Test = 2.44% × $119 ≈ $2.90 This scenario reduces revenue per visitor.
Result:$99→$119 | 3.5%→2.44% expected | Revenue/visitor falls | About 1 week needed
Example 2: E-commerce Product
Problem:Product at $49, 5% conversion. Testing $59 (about a 20.4% increase). 100,000 monthly visitors.
Solution:Expected conversion using the calculator's elasticity model: 5.0% × (1 - 0.306) ≈ 3.47% Revenue per visitor: Control = 5.0% × $49 = $2.45 Test = 3.47% × $59 ≈ $2.05 Required sample size is modest at this traffic level, so the calculator reaches power in about 1 week. This test points toward weaker revenue at $59.
Result:$49→$59 | Revenue likely decreases | About 1 week to power | Consider a smaller increase
Example 3: Subscription Annual Plan
Problem:Annual plan $499, 1.2% conversion. Testing $599. Only 10,000 monthly visitors.
Solution:Price increase: about 20.0% Expected conversion using the calculator's elasticity model: 1.2% × (1 - 0.301) ≈ 0.84% Because traffic and conversion are both low, required sample size is much larger. The calculator estimates roughly 11 weeks to statistical power at this traffic level. A smaller price step or longer test window is safer.
Result:Low power situation | About 11 weeks needed | Consider a smaller price change
Frequently Asked Questions
Why A/B test pricing instead of just raising prices?
A/B testing provides data-driven confidence. You learn the actual elasticity of your customers, minimize risk of revenue loss, and can optimize incrementally. Blind price changes may lose significant revenue or leave money on the table.
How long should a pricing A/B test run?
Long enough for statistical significance—typically 2-8 weeks depending on traffic. Must cover full business cycles (weekday/weekend, pay periods). Stopping early for positive results inflates false positives. Plan duration before starting.
What's a good minimum detectable effect for pricing tests?
Typically 10-20% relative change in conversion or revenue. Smaller effects require huge sample sizes. If a 5% revenue change doesn't matter to your business, don't design tests to detect it—you'll wait forever.
Should I test multiple prices simultaneously?
A/B/C or A/B/n tests can be valuable for finding optimal price points. However, they require more traffic and complexity. Start with A/B for simplicity, then iterate. Each additional variant increases sample size requirements.
What about price elasticity in my analysis?
Price elasticity measures demand sensitivity to price changes. Elasticity of -1.5 means 1% price increase causes 1.5% demand decrease. Estimate from historical data or industry benchmarks. It's the key variable in predicting test outcomes.
Can I test pricing on existing customers?
Testing on existing customers is risky—they may notice price changes and feel unfairly treated. Better to test on new customers or be transparent about testing. Grandfather existing customers if raising prices significantly.
What metrics should I track in pricing tests?
Primary: revenue per visitor (combines conversion and price). Secondary: conversion rate, average order value, churn (for subscriptions), customer lifetime value. Don't optimize conversion at expense of revenue.
How do I calculate sample size for pricing tests?
Use standard A/B test sample size calculators with your expected conversion rates and minimum detectable effect. For revenue metrics, variance is higher, requiring larger samples. 10,000+ per variant is common for pricing tests.
What if my test shows no significant difference?
No significant difference means you can't distinguish the prices with your sample. This could mean: prices truly perform similarly (raise price!), sample too small, or test ran too short. Analyze directional trends even if not significant.
What are common pricing strategies and how are they calculated?
Cost-plus pricing adds a fixed margin to costs. Value-based pricing sets prices based on perceived customer value. Competitive pricing matches or undercuts competitors. Penetration pricing starts low to gain market share. Price elasticity (% change in demand / % change in price) helps predict how price changes affect sales volume.