Skip to main content
winner+100.0% lift

Pricing Page: Usage-Based Pricing Model vs Feature-Tiered Pricing

Hypothesis

Switching from feature-tiered pricing (limited features on cheaper plans) to usage-based pricing (all features on all plans, differentiated only by video upload limits) would remove conversion barriers by helping users understand full product value

PricingPricing PageSaaSsaasvideopricing_modelWistia

Test Results

Key Learning

Problem: How prices are displayed on the pricing page directly influences perceived value and willingness to buy.

What worked: For SaaS video tools competing with free alternatives, removing feature gates and competing on usage limits rather than features is a powerful pricing restructure. Customers who can try the full product are more likely to upgrade. Pricing model architecture itself is a major CRO lever. (+100.0% lift)

Takeaway: This is a significant win worth prioritizing for implementation. Pricing perception changes are high-leverage — consider testing anchor pricing, tier order, and billing defaults as follow-ups.

How to Apply This to Your Site

This experiment demonstrated that pricing page: usage-based pricing model vs feature-tiered pricing can produce a +100.0% improvement in conversions. The test was run on a pricing page page in the saas industry.

Before you test: Consider that pricing tests typically require adequate traffic to reach statistical significance. Run your test for at least 2 full business cycles to account for weekly traffic patterns.

What Was Tested

helped Wistia fundamentally restructure their pricing model. Original model locked features behind higher tiers. New model gave all plans identical feature access, differentiated only by monthly video upload limits. This made feature comparison against free tools like YouTube/Vimeo clearer and removed the 'what am I actually getting?' objection.

Methodology

Confidence Level
85%
Lift Range
90.0% to 110.0%

Build On These Learnings

Save your own experiments, spot winning patterns across your test history, and stop repeating what's already been tried.

Related Experiments

Explore More Experiments