What we got wrong about SaaS pricing (and how we fixed it)
We launched our first product with usage-based pricing. It made sense to us at the time — pay for what you use, align cost with value. Clean. Simple. Fair.
We were wrong. Not in theory. In practice.
The Problem With Our Usage-Based Model
The issue wasn't the concept. It was the anxiety it created. Customers couldn't predict their monthly bill. Procurement teams couldn't budget for us. Enterprise buyers, who already distrust new vendors, couldn't justify an unpredictable cost to their CFO.
Our churn in months two and three was brutal. People loved the product. They just couldn't live with the uncertainty.
One customer told us directly: "We'd renew in a heartbeat if we knew what we were paying next month." That line stuck.
Round Two: Seat-Based Pricing
We switched to seat-based pricing. Predictable monthly cost per user. Everyone in SaaS does it — we figured it must work.
It worked better. Churn dropped. But a new problem emerged: customers gamed the seat count. Teams of fifteen would buy three seats and share credentials. We weren't growing revenue with them even as they scaled.
Worse, small teams who needed the product most couldn't justify paying for ten seats upfront just to try it.
Finding the Right Mix
The model that actually worked was a hybrid: a flat base fee that gives customers a predictable number, plus a usage component that scales only after a generous threshold.
Here's what changed when we made that switch:
- Trial-to-paid conversion went up 34%. Small teams could start cheap and grow into higher tiers naturally, without a big upfront commitment.
- Average contract value grew 41%. Customers who would previously cap their seat count now had a usage model that grew with them — and they were fine with paying for it because the base fee gave them psychological safety.
- Churn dropped to under 4% monthly. Predictability is a retention strategy. When customers can budget for you, they keep you.
The Honest Lesson
We spent almost nine months optimizing the wrong variable. We thought pricing was about fairness. It's actually about reducing friction — friction to buy, friction to budget, friction to expand.
If I could go back, I'd talk to ten customers about their budgeting process before writing a single pricing page. Not about willingness to pay. About how they get software approved internally.
That conversation changes everything.
The right pricing model isn't the one that makes sense to you as a founder. It's the one that makes your customer's internal buying process as easy as possible.