How do you decide what features should be free and what should be paid?
Let me start from the creator’s perspective:
I personally don’t have a product (apart from hiring people for creative work or offering personal consultations).
But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).
So some things I share for free to eventually move toward a paid collaboration.
Personally, it’s sometimes hard to judge when I might be giving away too much for free.
And I assume it’s similarly tricky for builders.
You want users to try the product, but then comes the question of paid features, or a trial limited by time or usage.
How do you decide which parts of your product or service remain free, and which become paid?
When I share content publicly, I usually provide generalised advice. But when it comes to a specific case or a tailored strategy that requires a personal approach, that’s where it becomes paid.
Replies
My take (I'm launching soon too):
I'm doing exactly what you're considering, all features free during the free trial. No gating.
Because I want a real test. If I hide features behind a paywall, users never see the full value. They churn thinking "it's missing something" when that something was the killer feature all along.
So my plan: 30 days, everything unlocked. Then pay or lose access. Some people will use it, finish their project, and never pay. Honest feedback. If they don't pay after experiencing everything, either my product isn't valuable enough, or my price is wrong. That's real data I need.
Has anyone tried full-featured time-limited trials? Did it convert better or worse than feature-gated freemium? Am I doing right or not?
I'd rather have 10 paying customers who love the product than 100 free users who never saw what it can really do.
For me the answer came down to one simple rule: if the feature creates immediate value, it should be in the paid tier. If it builds trust and lets people understand the product, keep it free.
I built a Mac menu bar app called TokenBar that tracks AI spending across 20+ providers. The free/paid split was tough but I landed on: Basic tier ($5 one-time) gives you real-time spending tracking for up to 5 providers. Pro tier ($10 one-time) unlocks all 20+ providers, budget alerts, and detailed breakdowns.
The key insight was making the free-to-paid boundary feel like a natural upgrade rather than a paywall. People who only use ChatGPT and Claude don't need 20 provider integrations. But once they see the value of tracking even 2 providers, upgrading to Pro when they add more tools is a no-brainer.
Also - one-time pricing instead of subscriptions. In a world where every tool wants $20/month, charging $5 once creates instant goodwill and removes the "is this worth it every month" anxiety. My conversion rate is way higher than I expected because of this.
I see free as onboarding, not limitation.
If people get real results for free, conversion becomes natural—not forced.
Great question — this was one of the hardest decisions I faced building DealNotify, a price drop and restock alert tool for Amazon, Walmart, Best Buy and more.
My rule was simple: the free tier has to deliver real value, not just a taste of it. If someone can't genuinely use the product for free, they'll never trust it enough to pay.
So here's where I drew the line:
Free gets:
Real price drop and restock alerts (the core value)
Up to 3 products tracked
Checks every 6 hours
30-day trial
Pro ($4.99/mo) gets:
Unlimited products
Checks every 2 hours
The key insight: I didn't gate the feature, I gated the frequency and scale. A free user still gets the "wow" moment when they receive their first alert email. That experience is what converts them — not a paywall.
The things I kept firmly free: no ads, no selling data, no watermarks on emails. Those would have killed trust immediately.
My rule of thumb for dev tools: make the core workflow free, gate the scale.
For example — if you're building an AI coding tool, let users run it locally for free with no limits. But charge for team features (shared context, usage dashboards, multi-repo orchestration).
The free tier should be good enough that a solo developer genuinely loves it. That's your distribution engine. The paid tier should solve problems that only matter when you have a team or hit scale — collaboration, governance, cost tracking.
The mistake I see most often: gating the "aha moment" behind a paywall. If users can't experience why your product is valuable without paying, your conversion rate will always be low.
Great question — and one I wrestled with when building Katie (AI sales co-pilot).
My rule ended up being simple: free should create the "aha moment," paid should sustain it.
For Katie, the free tier lets you run the full pipeline once — see your ICP, get cold emails, get a closing
strategy. That's the aha moment. You experience the value before spending a cent.
But running it repeatedly across different products, saving goals, tracking deals, getting daily AI coaching —
that's where the habit forms. That's paid.
The mistake I almost made: gating the aha moment itself. If someone can't feel the product's value for free, they'll
never convert. You're not giving too much away — you're just doing good marketing.
Your analogy is spot on: free content = generalised value = trust. Paid = personal, repeated, sustained value. Same
principle applies to SaaS.
SellerClaw
most of the time it’s not really about features for us
it’s more about when the product starts doing real work for someone
we’ve seen people use “paid” features casually and still churn, and others stick around just because one small thing saves them time every day
so the line ends up being closer to “does this replace effort or responsibility” rather than how complex the feature is gets messy though, because the things that look small on the surface often carry most of the value
CrabTalk
I'm struggling at this point these days exactly, gonna launch my new product next week (I don't provide any cloud services, the product runs on users' machine totally.)
Free should make people love you, paid should make people need you.
The threshold I found is "Does removing this feature make the free version feel broken or limited?", both free and pro share the biggest core features of my product and the worst mistake would be putting too much in Pro on day one.
Today's Pro feature becomes tomorrow's free feature, because you built something even better for Pro!
I've gone fully "free" with 800+ utility tools on my site because the SEO and trust they build are worth more to me than a small paywall right now.
My general rule is: If it’s a quick utility that runs in the browser, keep it free to grow the brand. If it requires my manual time, specialized expertise, or heavy server resources, that’s where it becomes a paid service. Free is the marketing; paid is the specialized solution.
Kim Personal Health Assistant
Love this thread Nika! Swati and Janefrances really nailed it, free should deliver that quick wow moment and actually create the hunger for the paid version. As a self-funded builder, I keep it simple: free gives instant real value with basically zero cost to me, while scale, depth, and anything expensive goes behind the paywall. The real test is whether users walk away satisfied… or still wanting more. What are you working on?