Pricing is the highest-leverage decision in your SaaS business. A 10% price increase can mean the difference between profitability and burn. Yet most bootstrapped founders set their price once — usually by guessing — and never touch it again because they're terrified of losing customers.
I've helped 25+ bootstrapped SaaS companies run pricing experiments. The result: 80% of them were undercharging, and a well-executed price test increased revenue by 15–40% with negligible churn impact.
This article gives you a complete framework for testing prices scientifically — without angering customers or tanking your conversion rate.
Why Most Founders Never Test Pricing
The fears are predictable:
"If I raise prices, everyone will leave."
(Reality: In my experience, price-related churn from a 15–20% increase is typically 2–5% of customers.)"If I lower prices, I'll devalue my product."
(Reality: Lower prices only devalue your product if your positioning is weak. Price is a signal, not the product.)"I don't know how to test without making it obvious."
(Reality: There are 5 legitimate methods for testing prices discreetly. We'll cover all of them.)"What if existing customers find out new customers are paying less?"
(Reality: New customer discounts are standard practice. SaaS companies offer them all the time.)
The real reason founders don't test pricing isn't fear — it's that they don't have a framework. So let's build one.
The Pricing Experiment Framework
Step 1: Establish Your Baseline (1 Week)
Before changing anything, you need to know your current numbers cold.
Pricing Baseline Template
═══════════════════════════════════════════
Current Pricing:
Free tier: $0 (limits: __________)
Starter: $___/month (___ annual customers)
Pro: $___/month (___ annual customers)
Business: $___/month (___ annual customers)
Current Metrics:
Monthly signups: ___
Trial-to-paid conversion: ___%
Average revenue per user: $___
MRR: $___
Churn rate: ___%
CAC: $___
LTV: $___
Customer Distribution:
Free → Paid conversion: ___%
Starter plan %: ___%
Pro plan %: ___%
Business plan %: ___%
Plan upgrade rate: ___%/month
This baseline is your control group. Every experiment will be measured against these numbers.
Step 2: Form a Hypothesis
Pricing experiments should be hypothesis-driven, not random. Use this template:
Hypothesis Template:
──────────────────────────────────────────────
I believe that [changing X pricing variable]
will result in [expected outcome]
because [underlying reasoning].
I'll measure success by [specific metric]
and consider the experiment successful if
[threshold for success].
I'll run the experiment for [duration]
and rollback if [rollback condition].
Example hypotheses:
Hypothesis 1 (Price Increase):
"I believe that increasing the Pro plan from $29 to $39
will result in less than 5% churn and increase MRR by 15%
because my customer survey showed 73% of Pro users would
pay $40+. I'll measure success by net MRR change and
consider it successful if net MRR increases. I'll run for
30 days and rollback if churn exceeds 8%."
Hypothesis 2 (New Tier):
"I believe that adding a $59 Business tier between Pro ($29)
and Enterprise ($199) will capture 10% of Pro users who need
more features, because 15 customers have requested features
that should be in a mid-tier. I'll measure by tier adoption
rate and consider it successful if 8+ customers upgrade
within 60 days."
Hypothesis 3 (Annual Discount):
"I believe that offering 2 months free on annual plans
will increase annual subscription rate from 20% to 35%
because it improves cash flow and commits customers longer.
I'll measure by annual conversion rate and consider it
successful if it reaches 30%."
The 5 Pricing Experiment Methods
Method 1: A/B Test on New Visitors (Recommended)
Show different prices to different visitors on your pricing page. Only new visitors see the test — existing customers keep their current price.
// Pricing page A/B test
const PRICING_TEST = {
name: 'pro_plan_price_test',
variants: {
control: { pro_price: 29, label: '$29/mo' },
variant_a: { pro_price: 39, label: '$39/mo' },
variant_b: { pro_price: 49, label: '$49/mo' }
},
traffic_split: { control: 0.34, variant_a: 0.33, variant_b: 0.33 }
};
function getVariant(userId) {
// Use deterministic assignment so the same user always sees the same price
const hash = simpleHash(userId + PRICING_TEST.name);
const bucket = hash % 100;
if (bucket < 34) return 'control';
if (bucket < 67) return 'variant_a';
return 'variant_b';
}
function renderPricingPage(req, res) {
const variant = getVariant(req.user?.id || req.sessionID);
const pricing = PRICING_TEST.variants[variant];
// Log the variant assignment
analytics.track('pricing_test_assigned', {
test_name: PRICING_TEST.name,
variant: variant,
user_id: req.user?.id,
session_id: req.sessionID
});
res.render('pricing', { pricing });
}
Tracking what matters:
// Track conversion by variant
analytics.track('pricing_test_conversion', {
test_name: PRICING_TEST.name,
variant: user.assignedVariant,
plan: 'pro',
price: user.assignedPrice,
converted: true,
time_to_convert: hoursSinceVisit
});
Statistical significance: You need at least 100 visitors per variant and at least 10 conversions per variant before drawing conclusions. Use a significance calculator — don't eyeball it.
Example Results After 30 Days (1,200 visitors per variant):
═══════════════════════════════════════════════════════
Variant | Visitors | Conversions | Rate | Revenue
─────────────|──────────|─────────────|───────|────────
$29 (control)| 1,200 | 48 | 4.0% | $1,392
$39 (var A) | 1,180 | 35 | 3.0% | $1,365
$49 (var B) | 1,210 | 22 | 1.8% | $1,078
Analysis:
$39 generates 98% of the revenue of $29 with fewer customers
→ Less support load, similar revenue
$49 generates 77% of revenue — price too high
Decision: Test $39 further or try $35 as a middle ground
Method 2: New Customer Only Pricing
Change the price for new customers only. Existing customers keep their current pricing (grandfathered).
Email to existing customers:
─────────────────────────────────
Subject: Your price is locked in 🎉
Hi [Name],
We're updating our pricing on [date] to reflect
the significant improvements we've made to [Product]
over the past year.
But here's the good news: as a thank you for being
an early customer, your current price of $[current]
is locked in forever. You won't see any change.
New customers will pay $[new_price] starting [date].
Thank you for your support,
[Your Name]
Pros: Zero risk to existing revenue. Clean test of new price acceptance.
Cons: Creates a pricing disparity that needs managing long-term.
Best practice: Set an expectation that grandfathered pricing is a limited-time benefit. Consider a 12–18 month horizon, after which grandfathered customers move to the new price (with advance notice).
Method 3: The Annual vs. Monthly Test
Instead of changing the headline price, test different annual discounts:
Test A: "Save 20% with annual billing" (current)
Test B: "Save 33% with annual billing" (2 months free)
Test C: "Save 16% with annual billing" (aggressive monthly pricing)
Measure: What annual discount maximizes annual subscription rate
without sacrificing total revenue?
This is one of the safest tests because you're not changing prices — you're changing the incentive structure.
Method 4: Feature-Based Tier Testing
Instead of changing prices, change what's included in each tier:
Test: Move a popular feature from Pro to Business tier
Current: Test:
Starter ($19) Starter ($19)
- 5 projects - 5 projects
- Basic analytics - Basic analytics
Pro ($39) Pro ($39)
- Unlimited projects - Unlimited projects
- Advanced analytics - Advanced analytics
- API access ← - (moved to Business)
Business ($99) Business ($99)
- Priority support - Priority support
- SSO - SSO
- API access ← NEW
Measure: Does moving API access to Business increase Business tier adoption without increasing Pro tier churn?
Method 5: The "Free Trial → Paid" Price Test
Test different price points during the trial-to-paid conversion:
// When trial expires, show different pricing
function trialExpiredScreen(user) {
const variant = user.pricingTestVariant;
const offers = {
'control': { price: 29, message: 'Continue your subscription' },
'discount': { price: 19, message: 'Special offer: 35% off your first 3 months' },
'annual_push': { price: 290, message: 'Pay annually and save 2 months' }
};
const offer = offers[variant];
return `
<div class="trial-expired">
<h2>Your free trial has ended</h2>
<p>${offer.message}</p>
<div class="price">${formatPrice(offer.price)}</div>
<button>Subscribe Now</button>
</div>
`;
}
Running the Experiment: The Process
Pre-Experiment Checklist
- [ ] Baseline metrics documented (conversion rate, MRR, churn)
- [ ] Hypothesis written using the template
- [ ] Success metric and threshold defined
- [ ] Rollback condition defined
- [ ] Experiment duration set (minimum 2–4 weeks)
- [ ] Tracking implemented and verified
- [ ] Existing customers protected (grandfathered or excluded)
- [ ] Sample size calculated (100+ visitors per variant)
During the Experiment
Monitor at Day 7 (early signals: favorable/unfavorable/inconclusive), Day 14 (check statistical significance), and Day 28 (final: significance, revenue impact, churn impact, decision to adopt/reject/iterate).
Post-Experiment Analysis
Calculate Revenue per Visitor (RPV) for each variant:
control_rpv = (control_conversions * control_price) / control_visitors
test_rpv = (test_conversions * test_price) / test_visitors
rpv_lift = (test_rpv - control_rpv) / control_rpv * 100
# Statistical significance (z-test, 95% confidence)
pooled_rate = (control_conversions + test_conversions) / (control_visitors + test_visitors)
se = (pooled_rate * (1 - pooled_rate) * (1/control_visitors + 1/test_visitors)) ** 0.5
z_score = (test_rate - control_rate) / se if se > 0 else 0
significant = abs(z_score) > 1.96
# Adopt if test RPV > control RPV AND significant
# Reject if significant but test RPV < control RPV
# Extend test if not yet significant
Pricing Experiment Mistakes to Avoid
Mistake 1: Testing too many variables. Change ONE variable per experiment — price, features, or layout, never all three.
Mistake 2: Running too short. Minimum 2 weeks, ideally 4. A 3-day test captures weekday bias.
Mistake 3: Ignoring Revenue per Visitor. Conversion rate is vanity for pricing tests. Always calculate RPV = (Conversions × Price) / Total Visitors. The highest RPV variant wins.
Mistake 4: Not protecting existing customers. Grandfather existing customers for 12–18 months on price increases. Offer lower prices automatically on decreases. Only A/B test with new/anonymous visitors.
Mistake 5: Concluding too early. Wait for statistical significance AND minimum test duration. Never decide based on 3 days of data.
The Pricing Experiment Roadmap
Q1 (Foundation): Establish baseline, run first A/B test (10–20% increase on new visitors), analyze and iterate.
Q2 (Structure): Test annual vs. monthly discount structures, test adding/removing a tier, analyze revenue mix.
Q3 (Value Extraction): Test feature redistribution between tiers, test usage-based pricing, analyze which structure maximizes RPV.
Q4 (Optimization): Scale winning structure, grandfather old customers onto new pricing, annual review.
The Pricing Experiment Checklist
Before: Document baseline metrics, write hypothesis, define success metric & threshold, define rollback condition, calculate sample size, set 2–4 week minimum duration, implement tracking, protect existing customers, set up monitoring log.
During: Verify data collection (Day 1), review early signals (Day 7), check significance (Day 14), monitor for churn/complaints, resist concluding early.
After: Calculate final RPV per variant, verify significance, assess churn impact, document decision, implement winner or rollback, update baseline, plan next experiment.
Final Thoughts
Pricing is the only lever in your SaaS that directly affects revenue without requiring more customers, more features, or more support. A 20% price increase applied to 500 customers adds $10,000/month in revenue with zero additional cost.
But pricing isn't a one-time decision — it's an ongoing experiment. The price that worked at $5K MRR may be wrong at $20K MRR. The price that worked for early adopters may be wrong for the mainstream market.
The founders who win at pricing treat it like science: hypothesize, test, measure, decide. Not like a guessing game that you set once and hope for the best.
Your pricing page is the most important page on your website. It deserves the same rigor you apply to your product. Run your first experiment this month. Even a small test — a 10% increase on new visitors for 2 weeks — will teach you more about your customers' willingness to pay than months of speculation.
The data is waiting. Go get it.
Top comments (0)