The Pricing Mistake Nobody Talks About
A founder came to us last year with a promising product. Good user acquisition. Solid retention. Clear problem-solution fit.
They were dying.
Their pricing model was per-seat. A team of 10 paid $99/month. A team of 1,000 paid the same $99/month.
The product delivered more value at scale. They got nothing for it.
The Three Models
1. Per-Seat Pricing
Charge per user per month. Works when your product's value scales with headcount.
When it fails: When value doesn't increase with team size, or users share accounts.
2. Usage-Based Pricing
Charge based on consumption. Works for APIs, infrastructure, monitoring.
When it fails: Users fear unpredictable bills. Enterprise buyers need budget approval.
3. Hybrid Pricing
Base fee + usage add-ons. Works when you have both base value and scalable value.
The Pricing Model That Kills SaaS Products
Common mistakes:
- Per-seat when value is flat (one user manages everything)
- Usage-based when users fear commitment
- Flat pricing for everyone (power users subsidize casual ones)
The Math Nobody Does
Model your unit economics:
- Gross margin per customer: What does it actually cost to serve them?
- LTV: Average revenue x average customer lifespan
- CAC: What can you spend to acquire customers profitably?
- LTV:CAC ratio: Should be at least 3:1 for a healthy SaaS
Pricing Psychology
Anchoring: Show a premium tier first. Your mid-tier looks reasonable.
Decoy Pricing: Three tiers. Middle is the target.
Freemium Math: Free tier users who never pay cost you money. Every feature you give away is work you did for free.
What Actually Works
For Most SaaS: Tiered Per-Seat
Starter: $29/month (3 users) Professional: $79/month (10 users) Team: $199/month (25 users)
For Developer Tools: Usage-Based with Caps
$0 free tier, then $49-199/month with limits.
For Enterprise: Hybrid
Base + users + usage + add-ons.
The Biggest Mistake
Underpricing.
Founders price low to "get customers." But low prices attract price-sensitive customers who leave at the first sign of trouble.
A $99/month product signals different quality than a $9/month product.
When to Change Your Pricing
Change when: costs changed significantly, you're consistently outpricing competitors, or customer feedback mentions pricing.
Don't change when: you're impatient for growth, one customer complained, or you're about to launch a new feature.
The Framework
- Know your costs
- Define your customer
- Match model to value
- Model unit economics
- Test pricing
- Raise prices yearly
The Question to Ask
"What's the most expensive customer you ever had, and why did they pay that much?"
The answer reveals your pricing ceiling. If you want to charge more, you need to deliver more value.
Want help with SaaS pricing? We work with founders on pricing strategy as part of our MVP engagement.
