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.
8.6K views

Add a comment

Replies

Best

are you able to display a demo so people can see what you are building, instead of giving away part of the app for free?

I built ComplaintForge, and the paid side is not a subscription, so this thread reads differently from where I sit. The analysis is free, so a user finds out whether they actually have a case before paying anything. The letter and the Ombudsman pack are flat one time fees. That works because each case is a one time need, not something people come back to monthly, so a subscription would be solving a problem the user does not have. My free and paid line ended up being about repeat use rather than feature depth. Anything used once stays a flat fee. Anything used again and again would need a different model, and I have not had to build one of those yet.

 How many products did you build? :D Because it seems you have many :D

 Three shipped and live so far, ComplaintForge, DBADocs and PagePulse, with a couple more in build. It is a portfolio bet rather than one big swing, alongside a full time job, so progress on any single one is slower than I would like but the total surface area compounds.

 I would swear you have more, because you mentioned in our discussions way more products :D

Our line is cost and commitment, not features. Describing your business and watching it get built is free, with no account and no card. That is the moment someone decides if it is for them, and it is a cost we can carry.

Paying starts when the business goes live and the team begins producing things every week: posts, videos, pages. Each of those costs us real money, so a free tier there would mean limits that feel stingy, or a bill we could not pay. For the same reason we chose $1 for the first week, one time only, over a classic free trial. My rule of thumb: free for the part that helps someone decide, paid from the moment we do recurring work for them.

For us the rule is simple. The core thing people come for should be free, and the stuff that costs us money to run is where the limit goes. In Biteme the AI scans cost us per use, so they run on Spice. Everyone gets 10 free Spice a day, and that's where paid starts. By the time someone runs out, they're already using the app every day, so paying doesn't feel like a trap.

 I decided to keep 2 features for free, the rest will be paid and I will be adding to paid section anyway :D

 Makes sense. Adding stuff to paid over time is way easier than taking things away from free later. People get mad about that fast

In the dating space, the free tier needs to be useful enough that people experience real value - seeing profiles, basic searching. But the paid features should solve a specific pain point: video chat, AI coaching, verified profiles. If your free users can't tell you what they're missing, your paywall isn't positioned right.

the real answer nobody here is saying: if your product has variable costs per user (like AI inference), your free tier IS your marketing budget. treat it that way.

i run AI-heavy pipelines and every prompt costs real money. so i structured it as: free tier = enough to hit the wow moment, maybe 5-10 uses. paid = unlimited or high volume. the key insight was tracking exactly where users go from "oh cool" to "i actually need this in my workflow" and putting the gate right after that moment.

what changed everything for me was caching aggressively. i cache outputs with vector similarity search so if someone requests something close to what already exists, i serve the cached version instead of burning another API call. cut my costs by 60-70% overnight. suddenly the free tier became way more generous without actually costing more.

the trial vs freemium debate is a false choice imo. trials work when your product needs time to click (like writing tools or habit apps). freemium works when value is immediate but scales with usage. combining both usually just confuses people about what theyre actually getting.

Honestly, as a solo creator, charging from day 1 is the only sustainable path.

You need to give enough free value to build trust, but the product still has to be worth paying for.

I am figuring out that balance too.

I think about free vs. paid as an optimization function.


Your free tier exists to attract the volume of users you need to hit your paid conversion targets. The parameters are simple: the higher the value your paid tier delivers, the fewer free users you need in the funnel.

So the real question isn't "what do I give away?" It's "how valuable is my paid tier, and how many free users do I need to reach the paying ones?"


I'm building Olkano, a daily check-in app for people who live alone. Free gives you the core experience — one contact gets alerted if you miss a check-in. Paid unlocks unlimited contacts. The free tier is fully functional, not a teaser. But it creates natural demand for more.


The way I see it: your free tier is just the cost of advertising. The difference is that instead of paying Meta or Google, you're "paying" by running infrastructure for free users. And unlike ads, those free users already know and trust your product when they convert.

The way we think about it at PrometAI: free should solve a real problem on its own, not just hint at one. If the free tier feels like a demo, users churn before they ever see the value.

The line we drew was between breadth and depth. Broad access is free. The deeper the output, the more it becomes a paid feature. That way someone can get genuine value without paying, but scaling that value requires upgrading.

The "giving too much away" anxiety is real, but in practice most people don't convert because of what they got for free. They convert because they trust the product enough to pay. Free builds that trust.

I'm Narek, co-founder of PrometAI. We built an AI business planning platform trusted by 100,000+ founders worldwide. From idea validation to financial projections, we guide the whole journey. Relaunching on PH soon! Follow along if that sounds interesting. Let's connect!

Simple framework we use at :

Give away the thing that creates the "oh crap" moment for free. Charge for the solution.

Our free flood zone checker tells homeowners if their property is in a flood zone. Takes 20 seconds. Free, no signup.

The "oh crap I'm in a flood zone" moment? That's when they want the full property report — zoning, buildability, environmental risk. That's paid.

Free tool = trust + traffic. Paid report = revenue.

The mistake most people make: they gate the awareness. Don't. Gate the action.

First
Previous
•••
141516
•••
Next