How to A/B Test Your SaaS Pricing (Without Upsetting Customers)

May 20, 2025

The Pricing Paradox: Why Most SaaS Companies Get It Wrong

Pricing is perhaps the most powerful lever for improving your SaaS company's revenue and profitability—yet it remains one of the most underutilized strategies. According to research by Price Intelligently, while SaaS companies regularly A/B test their marketing copy, website layouts, and feature sets, only 5% consistently test their pricing strategy.

Why this disconnect? For many executives, pricing feels risky. There's a legitimate fear that testing different price points could alienate existing customers or create perception problems in the market. However, with the right approach, you can systematically optimize your pricing without compromising customer trust or brand perception.

Why A/B Testing Pricing Matters

Before diving into methodologies, let's understand what's at stake:

  • A mere 1% improvement in price optimization can translate to an 11% profit increase, according to McKinsey research
  • The majority of SaaS companies are leaving 25-40% of potential revenue on the table due to suboptimal pricing, as reported by OpenView Partners
  • Companies that regularly test and optimize pricing grow 2x faster than those that don't, according to ProfitWell

Patrick Campbell, CEO of ProfitWell, puts it bluntly: "Pricing is the most important lever that SaaS companies have, but almost none of them systematically optimize it."

The Key Challenge: Testing Without Transparency Issues

The central difficulty with pricing tests is balancing the need for data with customer expectations of fairness. Here's how to strike that balance:

1. Segment-Based Testing Instead of Random Assignments

The Wrong Approach: Randomly showing different prices to visitors on your website.

The Right Approach: Test pricing with carefully selected audience segments.

Instead of showing different prices to random visitors—which can create issues when customers compare notes—segment your tests by:

  • Geographic regions
  • Customer acquisition channels
  • Company size brackets
  • Industry verticals

By testing different pricing in discrete segments, you reduce the likelihood of direct comparisons while still gathering valuable data.

2. New Feature/Tier Testing

Rather than adjusting existing prices, create new pricing tiers or feature bundles. This approach allows you to:

  • Test premium pricing with additional value
  • Experiment with entry-level offerings
  • Try different feature groupings at various price points

Slack demonstrates this approach masterfully, regularly introducing new enterprise tiers with expanded features at different price points, allowing them to test price elasticity without disrupting existing customers.

3. New Customer Cohort Testing

One of the safest approaches is testing price changes only with new customers. According to research by Simon-Kucher & Partners, 75% of successful SaaS pricing tests follow this methodology.

The process:

  1. Set a calendar cut-off date
  2. Keep all existing customers on current pricing
  3. Apply new test pricing only to customers who sign up after that date
  4. Run tests for a statistically significant period (typically 2-3 months)
  5. Measure conversion rates, average revenue per user (ARPU), and long-term retention

4. Time-Limited Promotional Testing

Frame your pricing test as a promotional offer to gauge elasticity at lower price points:

  • "Get 25% off for the first year when you sign up by [date]"
  • "Summer special: Premium features at Standard pricing"

This approach provides valuable data on price sensitivity while positioning the test as a benefit rather than a variable experiment.

Metrics That Matter in Pricing Tests

When running your tests, focus on these key metrics:

  • Conversion rate: How does the pricing change affect your trial-to-paid or visit-to-signup ratios?
  • Average revenue per user (ARPU): Are you making more money per customer?
  • Customer acquisition cost (CAC) payback period: How quickly do you recover the cost of acquiring customers?
  • Net revenue retention: Are customers expanding their usage over time?
  • Churn rate: Are customers more likely to cancel at the new price point?

According to data from OpenView's SaaS Benchmarks Survey, the most successful pricing tests optimize for long-term net revenue retention rather than short-term conversion improvements.

Communicating Changes: The Art of Pricing Transparency

If your tests indicate a need for broader pricing changes, here's how to implement them without alienating customers:

Grandfather Existing Customers

The gold standard in SaaS pricing changes is to grandfather existing customers into their current rates, at least for a considerable period. Intercom famously maintained legacy pricing for existing customers even as they significantly revised their pricing structure for new users.

Provide Value-Based Justification

When communicating pricing changes, focus on value delivered rather than business necessity:

✅ "We've added 15 new features over the past year and expanded infrastructure to improve reliability."

❌ "Our costs have increased so we need to raise prices."

Give Advance Notice

According to customer sentiment research by ProfitWell, providing at least 60 days' notice before implementing pricing changes significantly reduces negative reactions and churn risk.

Real-World Success Stories

Case Study: Zapier's Pricing Evolution

Zapier, the workflow automation platform, has effectively tested pricing through tier evolution. Rather than directly changing prices, they've:

  1. Added new higher-tier plans with expanded capabilities
  2. Adjusted limits on existing tiers
  3. Introduced team and company plans at premium price points

This approach has allowed them to effectively increase their average contract value by 35% while maintaining strong customer satisfaction, according to their CEO Wade Foster.

Case Study: Buffer's Transparent Testing

Buffer took a unique approach to pricing tests by being completely transparent. They:

  1. Announced they were testing new pricing structures
  2. Invited customers to opt-in to beta pricing
  3. Gathered extensive feedback alongside quantitative data
  4. Made final decisions based on both metrics and customer sentiment

While this approach limited their ability to gather unbiased quantitative data, it created enormous customer goodwill and provided rich qualitative insights.

Implementing Your First Pricing Test

Ready to start? Here's a simple framework for your first pricing test:

  1. Define your hypothesis: What pricing change do you believe will improve your metrics?
  2. Select your testing methodology: Choose from segment-based, new feature, cohort, or promotional approaches
  3. Determine your success metrics: Set clear KPIs before beginning the test
  4. Establish your minimum viable sample size: Use statistical significance calculators to determine how long to run the test
  5. Prepare for all outcomes: Have a plan for implementing changes if the test succeeds—and for further testing if it doesn't

Conclusion: The Continuous Pricing Journey

Pricing isn't a set-it-and-forget-it decision—it's an ongoing optimization process. The most successful SaaS companies test pricing at least quarterly, according to data from ProfitWell, treating pricing as a product that requires continuous refinement.

By taking a systematic, customer-respectful approach to price testing, you can unlock significant revenue and growth potential without undermining trust or transparency. Remember that the goal isn't just to extract more revenue, but to align your pricing with the genuine value you deliver to customers—a win-win that drives both growth and satisfaction.

The companies that will thrive in the increasingly competitive SaaS landscape will be those that overcome their pricing hesitation and embrace strategic, careful testing as a core business practice.

Get Started with Pricing-as-a-Service

Join companies like Zoom, DocuSign, and Twilio using our systematic pricing approach to increase revenue by 12-40% year-over-year.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.