Users don't upgrade because the jump from free to paid is too big
Let users start free and pay more as they use more. Removes the "is it worth $X/month?" question.
When to use
Your product has a clear usage metric that correlates with value. Users currently hesitate at the free-to-paid boundary.
Hypothesis template
If we switch to usage-based pricing tied to fill in: usage metric, conversion will increase by fill in: target% because users pay proportional to the value they receive.
Method
The problem: Your free plan is limited and your paid plan costs $15+/month. The gap is too wide — users either stay free or don't sign up at all.
What Vercel did: Free tier for hobby projects, then pricing based on bandwidth, builds, and team members. Users scale into paying naturally without making a binary upgrade decision.
The result: Usage-based pricing aligns cost with value. Users never feel overcharged because they pay for what they use. And heavy users pay significantly more than a flat fee would charge.
How to do it:
- Identify your value metric: what do users do more of as they get more value? (API calls, seats, storage, experiments, etc.)
- Set a generous free tier that lets users get real value
- Price the next tier to kick in naturally as usage grows
- Show current usage clearly in the dashboard so there are no surprises
- Send alerts before users hit tier limits
- Compare revenue per user vs flat pricing to validate
Key insight: Usage-based pricing eliminates the biggest conversion friction: "Am I sure I need this?" Users don't decide to upgrade — they grow into it.
Success metrics
- •Free-to-paid conversion rate
- •Revenue per user
- •Expansion revenue
- •Churn rate (should decrease)
Prerequisites
- A measurable usage metric
- Billing system that supports usage-based charges
- Clear communication about pricing tiers
Common pitfalls
- •Setting the free tier too low (users churn before they see value)
- •Not showing usage transparently
- •Surprising users with bills
- •Making the pricing too complex to understand
Source: Vercel, Twilio, AWS. Usage-based pricing is the dominant model for developer tools.
Suggested ICE scores
Ready to run this experiment?
Sign up free to use this playbook with step-by-step guidance and track your results.