Tool Mango

Posted on May 7

I dropped my SaaS Pro tier from $19 to $9 in 24 hours. Here's why.

#saas #startup #indiehackers #webdev

TL;DR

I shipped Pro at $19/mo, looked at it 24 hours later, dropped it to $9/mo, and felt instantly more honest about my product. Here's what changed about my pricing thinking — and the framework I use now.

What I shipped first

I built ToolMango — an AI tool directory with a Stack Builder that recommends a custom tool stack based on your project description. Pro tier was supposed to add: save stacks, label them, history dashboard, PDF export, email-the-stack, priority API queue, agency white-label, team workspace.

I priced it at $19/mo because that's the SaaS-indie default. It's where every other "AI thing" starts. ChatGPT is $20. Cursor is $20. Notion AI is $10. So $19 felt right.

But here's what I actually shipped on day 1:

Pro features that worked:

Save stacks (dashboard list)
Stack history (list all your stacks)

Pro features I "promised" on the pricing page:

PDF export (not built)
Email-the-stack (not built)
Priority API queue (just marketing copy)
Agency white-label (months away)
Team workspace (months away)

The honest competitive comparison:

Product	$/mo	What you get
ChatGPT Plus	$20	Frontier AI you'd use daily
Cursor	$20	Replaces a junior engineer
Notion AI	$10	AI inside an entire workspace
Buffer	$6	Multi-account social scheduler
Carrd Pro	$19/yr	Entire website builder
My ToolMango Pro at launch	$19/mo	Save 5 stacks + history

I was charging like Cursor and ChatGPT but delivering "saved bookmarks." Anyone who paid $19 and saw what they got would feel cheated within a week, then leave a bad review. That's the fastest way to kill a new product.

Why I dropped to $9

Three reasons, in order of importance:

1. Honest pricing reflects what you've actually built

I was anchoring Pro to the promise of features (PDF, email, white-label, priority) rather than the delivery of features (save + history). That's bait-and-switch by another name.

Pricing should reflect what a customer can use the day they pay. Roadmap features are the reason someone might pay later when they ship — not the reason to charge more now.

2. $19 was a credibility leak

In SaaS pricing, you anchor against what the user has bought before. They've bought ChatGPT at $20. They've bought Notion AI at $10. They know what those products feel like.

If I show up at $19 with "save your stacks," they don't compare me to "save your stacks at $25." They compare me to "ChatGPT at $20." And lose.

At $9, the comparison flips. They compare me to "Buffer at $6" and "Carrd at $19/yr." Now I look reasonable. The exact same product is positioned completely differently.

3. Lower price compounds via word-of-mouth

The single biggest source of indie SaaS growth at our scale is "my friend mentioned this tool." For that to happen, the price has to be at "I just signed up, you should too" levels — sub-$10/mo.

At $19, the conversation is "is this worth $19?" At $9, the conversation is "this is cool, you should try it." The first is a sales conversation. The second is word-of-mouth. The second compounds.

The pricing ladder I committed to publicly

Today:        $9   saves + history + labels
+PDF export:  $12  real deliverable utility
+email send:  $14  workflow automation
+team/agency: $29  Agency tier; existing Pro stays $14

Anyone who signed up at $9 today is grandfathered at $9 forever, even when prices rise. That solves two problems:

Loyalty signal — early adopters get rewarded
No price-cap on revenue — new signups pay current price

Existing customers don't churn on price increases (because they're not affected), and new customers pay what the product is now worth.

Pricing framework I use now

The four questions I ask before setting a price:

Q1: What can the customer use the day they pay?

Not what's on the roadmap. What works. List those features only. Stop counting roadmap features.

Q2: What does this anchor against in the user's mental model?

If they're thinking "this is like Notion AI, $10," start within 50% of that. If they're thinking "this is like a $200 enterprise tool," start higher. The user's frame matters more than your competitive analysis spreadsheet.

Q3: At this price, would I recommend it to a friend?

If I'm hesitating, it's too expensive. The friend recommendation is the marketing channel. Price has to enable it.

Q4: How does the price scale with what I ship next?

If price stays the same forever, I never get to capture the value of what I'll ship later. If price rises with features, early adopters churn.

The answer is rising tiers + grandfathering. Each new feature ships with a small price bump for new signups. Existing signups stay at their original price. Both groups feel like they're getting a deal.

The math of grandfathering

Counter-intuitively, grandfathering early customers at lower prices is more profitable than not.

Without grandfathering:

Sign up early adopter at $9
Raise to $14 in 3 months
Early adopter churns at month 3 because "the value isn't worth $14"
You lose them forever

With grandfathering:

Sign up early adopter at $9
Raise to $14 for new customers in 3 months
Early adopter stays at $9 forever, becomes a happy reference customer
New customer pays $14, anchored against what current $9 customers experience

LTV is much higher in the grandfathered version. And early adopters become your evangelists — they share screenshots of "I'm only paying $9, the new price is $14" which is basically free marketing.

What I changed in code

Three small updates:

Stripe Price: Created a new $9/mo Price in the same Product. Old $19 Price archived (still works for any test customers who already subscribed at $19).
/pricing page: Updated copy. Listed only delivered features. Moved roadmap items to a clearly separated "On the roadmap" block with the disclosure that they're not yet built.
Dashboard upgrade CTA: Updated to mention the $9 founder rate and grandfathering.

Total change: ~50 lines of code, including the dashboard.

The deeper lesson

Indie SaaS pricing is over-influenced by the "what should I charge?" question and under-influenced by the "what can I deliver?" question. The two need to match.

If they're out of sync, the customers either feel ripped off (too high relative to delivery) or you leave money on the table (too low relative to delivery). The fix is honest scoping: what works today, what's the closest competitive anchor, and where can the price grow as the product grows.

I now think of pricing as a curve, not a number. The number changes as the curve moves. Customers grandfather on the curve they signed up at. Both sides win.

The site

If you want to see what $9/mo Pro looks like in the wild: ToolMango is the planner. /pricing shows the new positioning. /about explains the editorial ROI methodology.

Roast the pricing in the comments — that's what dev.to is for.

DEV Community