In this article
The most common question we hear from early founders is whether the first version of their product should be free while it's still rough. The honest answer is almost always no. Charge from day one, even while it's genuinely unfinished.
That advice sounds harsh until you look at what a free product actually gives you. Mostly it gives you a number that looks like progress. Signups climb, a few people say nice things, and none of it tells you whether the thing is worth building further.
The exact moment someone types in their card number is the moment you have real proof the pitch worked.
A free user tells you almost nothing
People will try almost anything if it costs nothing. They click around for two minutes, then leave, and you'll never know why. Maybe the idea was wrong. Maybe the onboarding was confusing. Maybe they were just curious and had no problem to solve. A free user gives you no way to tell these apart.
A paying user behaves completely differently. They email you the moment something breaks. They tell you specifically what's missing, because they're now invested in the thing working, not just curious about it. They reply to your questions because they want the problem fixed.
That difference is the whole reason to charge early. You are not chasing revenue at this stage. You are buying honest information, and a price is the cheapest way to get it.
What a paying customer shows you that a free one never will
Once money is involved, several things you were guessing about become visible.
- Whether the problem is painful enough that someone will spend real money to solve it
- Which people it is painful for, and which people only said it was interesting
- What they expected to get for the price, which is often different from what you planned to build
- Which missing feature they would actually leave over, as opposed to the ones they mention politely
- How they talk about the problem, which is the wording your website should use

The real test of whether it's needed
If the product solves a genuinely painful business problem, people will pay for a half-finished version of it that saves them real time. Hesitating to charge because it isn't ready is often a quieter admission that the product solves a nice-to-have rather than a must-have.
That is a more useful thing to learn in week one than in month six. By month six you have spent half a year of engineering on something that people like but do not need, and the work cannot be taken back.
The objections you will hear, and what they mean
The first few times you ask for money, you will get answers that are not quite a yes or a no. They are worth reading carefully.
"I'll pay once it's ready" usually means the problem is not urgent. If it were, they would take the rough version today. Ask what would have to be true for them to start now. If the answer is a specific feature, you have a roadmap item. If the answer is vague, you have a lukewarm lead.
"Can I have it free while it's early?" is a request to keep the risk on your side. A fair reply is a real discount, not a free plan. Something like half price for the first months, in exchange for honest feedback, keeps the price signal and rewards the early trust.
"Send me a proposal" for a small monthly tool usually means you are talking to someone who cannot decide. Find the person who can, or move on.
How to actually run it
A fourteen-day free trial is fine, but require a card upfront. The exact moment someone types in their card number is the moment you have real proof the pitch worked. It is not a survey answer and not a nice comment. It is an actual purchase decision.
Everything you learn after that point is worth more than everything you learned before it. Trials without a card measure curiosity. Trials with a card measure intent.
If a card feels like too much friction for your market, ask for a small paid pilot instead. A paid month at a low price beats an unpaid quarter every time.
Not sure how to price your first version?
How much to charge at the start
Most first prices are too low, because the founder is pricing against their own nervousness instead of against the customer's problem. A better starting question is what the problem costs the customer today, in hours, in lost orders or in mistakes.
Pick a price that is small next to that cost and large enough that nobody signs up by accident. You can change it later. Early customers understand that a new product's price moves, and it is far easier to raise a price for new customers than to introduce one for people who have always paid nothing.
Keep the first pricing simple. One plan, one price, monthly. Usage tiers, seat counts and add-ons can wait until you know what people actually use.

When free is the right call
There are honest exceptions. A marketplace needs both sides present before either is useful, so one side is often free at first. A consumer product that earns from advertising or from a large network has to grow before it can charge. Open tools that win by being widely adopted may give the core away and charge for support or hosting.
But these are specific models with a reason for being free. A business tool that solves a problem for a company is almost never in that group. If you are building one and telling yourself it should be free to get traction, check whether that is strategy or whether it is fear.
A simple plan for the first thirty days
If you are about to launch and want a concrete starting point, this is one that works for most small business tools.
- Write down the one problem the product solves and who has it
- Pick a price that is small next to the cost of that problem
- Talk to ten people who have the problem and ask for the sale, not for feedback
- Charge the ones who say yes, and ask each of them what nearly stopped them
- Fix the top two things they name before you build anything new
Charging is a way of listening
Founders often treat pricing as something to work out after the product is good. It works better the other way round. A price, even a modest one, turns vague interest into a clear answer, and clear answers are what an early product runs on.
If nobody will pay for the rough version, that is not a failure of pricing. It is the market telling you something while it is still cheap to hear.
Written by the 101Turn studio
A small studio in Ahmedabad, India building apps, websites and SaaS products. If this touched something you are working on, we reply within one working day.
Ready to build the first version people will pay for?







