Been thinking about this as I evaluate tools for my own workflow: a lot of products look reasonably priced on the surface, but the actual cost/value only becomes clear after you're locked in auto-renewing annual plans marketed as "discounts," usage-based pricing that spikes unexpectedly, or feature-gating that pushes you into a much pricier tier than you expected.
Curious to hear from other makers and users here:
What's a pricing structure that seemed reasonable at signup but turned out to be a bad deal in practice?
In hindsight, what pricing-page signal should you have caught before paying?
As a maker, how do you think about pricing transparency for your own product to avoid this exact reaction from users?
We were celebrating a steady drop in our monthly churn rate, assuming it meant users were genuinely loving the product. But during recent feedback calls, a few long-term customers admitted they stay mostly because transferring their data and workflow to an alternative feels like too much work.
It made me realize that passive retention can easily hide a lack of real product delight.
How do you distinguish between customers who stay because they genuinely love your product versus those who are just locked in?
When we structured our tiers, we gated advanced features like reporting and integrations behind higher plans. However, some of our power users get massive ROI using just our core features, while smaller users pay for advanced tools they barely touch.
It made me realize that feature gating doesn't always reflect where the real value is generated for the customer.
How did you decide on your pricing model did you align it with feature access usage volume or direct revenue impact?
Our 14 day free trial has a solid signup rate but most users go quiet around day 8 without reaching key milestones. We tried tweaking our onboarding emails and in-app nudges, but the drop-off barely moved.
It made me realize that forcing users into a fixed timeframe might be asking for commitment before they ve experienced real value.
How did you optimize your trial conversion did you shorten the trial, switch to freemium, or change when you ask for payment?
Everyone says an MVP doesn t need to look polished. Just build the core feature, get it in front of users, and see what happens.
I agree with most of that.
But there s something that bothers me about the design can wait approach.
Say you launch a simple tool with a genuinely useful feature. The UI is a little confusing, the layout feels unfinished, and users aren t quite sure what to do next.
This is pre-launch, but I am afraid that I will struggle finding even my first user for my SaaS. Do you have similar experiences? I have been reaching out to my ICP for days now.
I asked Cursor to add input validation to a form handler. It reported editing three files. I checked git diff: two files changed. The third was a no-op.
The agent had described what it planned to do, not what it did. I only caught it because I diff every change now.
It's so easy to fall into the trap of automating everything just because you can write a script for it.
I automated our weekly invoice sorting process but it turned out that going through those files manually was the only time I caught subtle client trends and bugs.
Once it became fully automated, I stopped looking at those details altogether. Are there certain tasks you purposely refuse to automate now because you need eyes on them?
The quiet churn is honestly way more brutal than angry cancellation emails. When people just fade away without saying a word it usually means your tool is nice to play with when life is calm but the second things get busy it gets completely forgotten.
We thought our clean dashboard and smooth UX were enough but we hadn't anchored ourselves to a painful daily bottleneck.
If you noticed your users drifting off silently, how did you figure out what was missing to make the product truly essential?
