TL;DR: We changed SEOJuice pricing 3 times in the first year. Each time taught us something different. The first change (raising from $9 to $29) lost us 40% of signups but reduced churn by 60%. The second change (adding tiers) increased average revenue per user by 35%. The third change (annual pricing) stabilized cash flow. Here's the framework we landed on.
I want to start with the specific numbers, because abstract pricing advice is everywhere and specifics are rare.
When we launched SEOJuice, our lowest tier was $9/month. I chose that price for the worst possible reason: I was afraid to charge more. I thought a low price would reduce friction and bring in users who would later upgrade. The theory sounded reasonable. The reality was brutal.
At $9/month, we attracted users who expected free-tier quality and complained about everything. Support tickets per user were 3x higher than they'd be at our later price points. Churn was 12% monthly — meaning we replaced our entire user base roughly every 8 months. And the users who stayed the longest were the ones who used the product the least, which made retention metrics look fine on the surface while the actually engaged users were leaving.
That experience shaped everything I now believe about SaaS pricing. Price isn't just a revenue lever. It's a filter for the kind of customers you attract, the kind of business you build, and the kind of product development decisions you make.
Six months after launch, I raised the lowest tier from $9/month to $29/month. I was terrified. I spent a week writing and rewriting the announcement email. I expected angry cancellations.
Here's what actually happened:
The lesson was painful but clear: price is a signal. At $9, we were signaling "budget tool, not mission-critical." At $29, we were signaling "professional tool worth investing in." The product hadn't changed. The perception had.
I should be honest about the downside: we did lose some early users who genuinely loved the product but couldn't afford $29/month. That felt bad. A few of them emailed me personally. I grandfathered the most engaged ones at the old price because they'd given us valuable feedback. (Aside: I still think that was the right call. These users were effectively unpaid advisors. A $20/month discount for product feedback is cheap.)
At $29/month flat, we had one problem: no room for users to grow with us. A freelancer managing 2 sites and an agency managing 30 sites were paying the same price. The agency was getting wildly more value but had no way to express that through their spending.
We introduced three tiers:
The results after 3 months:
What I got wrong: the initial tier boundaries. I set the Professional tier at "up to 10 websites" based on intuition. After watching usage data for two months, I realized most Professional users had 4-6 websites. The jump from 3 to 10 was too large, and users at 4-5 websites felt they were overpaying. I adjusted the boundaries, which is fine — tiers aren't permanent. But I should have looked at usage data before setting them instead of guessing.
Our third pricing change was adding annual billing at a ~20% discount. This was less about revenue optimization and more about business survival. Monthly SaaS has a cash flow problem: you spend to acquire a customer today but only collect revenue month by month. If a customer churns at month 4, you may not have recouped the acquisition cost.
Annual pricing shifted the economics:
The lesson: annual pricing isn't about the discount. It's about getting customers to make a commitment decision. Once someone pays for a year, they're psychologically invested. They're more likely to actually use the product, which means they're more likely to get value from it, which means they're more likely to renew.
After three pricing iterations, here's the mental model I use for pricing decisions. It's not original — it's synthesized from our experience and from observing how other SaaS companies we admire approach pricing:
Your customers don't care about how many features your SaaS has. They care about outcomes. Instead of emphasizing "advanced dashboards" or "customizable templates," highlight results: "save 10 hours per week on SEO reporting" or "find 50+ internal linking opportunities automatically."
We rewrote our pricing page three times before getting this right. The version that performs best doesn't list features at all — it lists outcomes per tier. "Starter: Keep your site healthy. Professional: Grow your traffic. Agency: Scale your business."
Not every customer is your ideal customer. At $9/month, we attracted hobbyists. At $29/month, we attracted professionals. At $99/month, we attracted agencies. The product was the same; the audience shifted dramatically with each price point.
Ask yourself: who benefits most from your product? What's solving their problem worth to them? Price according to value delivered, not cost to build.
Higher prices push you to build better. When we charged $9/month, we felt guilty about the support quality we could afford. At $49/month, we could afford a proper onboarding flow, faster support response times, and better documentation. The product improved because the pricing supported the investment.
Every price increase we've done has ultimately been positive for the business. The initial signup dip is real and scary, but the improvement in customer quality, retention, and LTV consistently outweighs it. If your product is delivering real value and your churn improves when you raise prices, you were underpriced.
| Mistake | Why It Happens | What I'd Do Instead |
|---|---|---|
| Starting too low out of fear | You're afraid no one will pay. So you price at "can't say no" levels. | Price at what the value is worth, not what feels safe. If your product saves someone 10 hours/month, $29 is a bargain. |
| Promising to raise prices "later" | You tell yourself $9 is temporary. But "later" never comes because you're afraid of losing the users you have. | Set a date when you launch. "We'll evaluate pricing at 100 users" or "after 6 months." And actually do it. |
| Pricing based on features | You list 47 features and let customers figure out the value. | Price based on outcomes. "Save time" and "grow traffic" resonate more than "API access" and "custom reports." |
| Ignoring competitor context | You price in a vacuum without checking what alternatives cost. | Know your market. If Ahrefs is $129/month and you're solving a similar problem, $9/month looks suspicious, not attractive. |
| Not talking to customers about price | You assume you know what customers will pay. | Ask them. We surveyed 50 users before our first price change. Their willingness-to-pay was higher than we expected. |
Pricing is emotional. I know this because every price change I've made came with anxiety, second-guessing, and at least one sleepless night. The $9-to-$29 change was the hardest because I was directly confronting my fear of rejection. What if nobody signs up? What if existing users all leave?
Neither happened. Some users left. More came. The ones who came were better fits. The business got healthier. And I learned that underpricing wasn't protecting me — it was attracting the wrong customers and starving the business of the resources it needed to improve.
If you're currently agonizing over whether to raise your prices, here's what I'd tell past-me: do it. Survey your users first (their willingness-to-pay will surprise you). Grandfather your most loyal early adopters. Communicate the change clearly with a 30-day notice. And then watch what happens to your customer quality, not just your signup count.
The signup count might dip. The business will get better.
Related reading:
Price frames perception.
Excellent framing — pricing does signal quality as you note. In my 8 years running GTM for B2B SaaS we paired a ‘start with price’ design with Van Westendorp and short paid pilots, which raised ASP 35% and cut low-value churn; recommend that validation step before full feature builds. Happy to connect and share the survey template.
This is gold! 🔥 The “work backwards from the price point” idea and the $49/month example made me rethink packaging — we bumped a plan and saw better engagement because users expected more. Please do a tutorial on pricing page copy + anchoring experiments, would love a walk-through 🙏
Love that tweak worked. Quick playbook: set a clear anchor (create an obvious $99 premium), label your $49 as “Most value” + show annual savings, add a decoy mid-tier, then A/B test price endings/CTA. Track conversion rate, ARPU, churn and 7/30‑day upgrade velocity. Did this once (moved $35→$49 + $99 anchor) — +18% conversions. Want a short thread with copy templates? #SaaS
no credit card required
