You made a thing, people use it, and it is free. A template, a checklist, a newsletter, a small guide. Every so often someone says you should charge for this, and you deflect, partly out of modesty and partly because you honestly cannot tell whether they mean it.
This article is for that moment. Free users are real evidence, but of something narrower than most builders hope, and the gap between "people use this" and "people would pay for this" is exactly where the decision lives. What follows are the signals that separate the two, and a way to flip the switch that does not torch the goodwill the free thing has earned.
- People ask for more of it, unprompted
- Someone offered money, or spent real effort
- The problem is already paid for elsewhere
None of these are opinions. All three are things people do, not things people say.
Free users are evidence, but of what exactly
Give free usage its due first. It proves the problem exists, that your thing genuinely touches it, and that your distribution reached at least some of the right people. That is not nothing. Plenty of paid products died without ever getting that far.
Here is what it does not prove: that anyone would trade money for it. At a price of zero, taking the thing costs nothing, keeping it costs nothing, and saying something nice about it costs nothing. A download is not a decision. A subscriber who never opens is not a customer. Free usage measures reach and mild interest. Price measures value, and you have not measured it yet.
So the question is not "do people like it." People are lovely. The question is whether anyone has behaved as if the thing has a price. The three signals below are all versions of that behavior, in ascending order of how often you will see them.
Signal one: people ask for more of it unprompted
The most common readiness signal is requests arriving without being invited. "Do you have one of these for freelancers?" "When is the next one coming?" "Does it cover the part where the client disappears?" Each of those is a person who consumed the free version and hit its edge wanting more, and each request has a specification hiding inside it.
That is the difference between a request and praise. Praise is a full stop: "this is great, thanks." A request points somewhere: more coverage, another format, the next level of depth. Praise tells you the free thing landed. Requests tell you what the paid thing is.
Keep a file of these asks, verbatim, with dates. It serves two jobs at once: it is your evidence that pull exists, and it is the draft table of contents for whatever you eventually charge for. If the file stays empty for months while usage stays flat, that is an answer too, and a free one.
Signal two: someone offered money, or something that costs them effort
The cleanest signal is rare and unmistakable: someone tried to pay you. Asked if they could buy you a coffee, asked whether there is a paid version, asked if their company could get an invoice. When it happens, the free-versus-paid question is already answered. Somebody priced your work above zero without being asked to.
Most builders never get the direct money offer, so widen the lens to effort, which is money's honest cousin. A long email describing exactly how someone uses the thing. A user who shared it with their whole team. A request for permission to use it inside a company. A stranger asking for a customized version. Every one of those cost the sender time or social capital, and cost is what separates evidence from noise.
The rule from the previous section applies with full force here: weigh actions, not adjectives. One person who tried to pay, or who spent twenty minutes writing to you about their workflow, outweighs any number of kind comments. Count the costly things.
Signal three: it solves a problem people already pay to solve elsewhere
The third signal lives outside your inbox: is there already money moving around this problem? Look for paid products, tools, templates, or services that people currently use for the job your free thing does. Paid neighbors are good news. They prove the problem carries a budget, that people in this category have already practiced paying.
To make it concrete with an invented example: suppose the free thing is a spreadsheet that tracks freelance invoices. Freelancers already pay for invoicing software and bookkeeping help, so a sharper, cheaper, more specific tool is entering a category where wallets are open. If instead nobody anywhere pays anything to solve the problem, your free users may simply be the whole market, and the kindest thing the shelf can do is tell you before you build a paywall.
If this check comes back positive, your free project is not a hobby sitting outside the economy. It is an unpriced member of a paying category, and the only unusual thing about it is the price tag.
The switch: charge for the next version, not the past one
The thing that makes builders hesitate is loyalty: charging feels like a betrayal of the people who showed up when it was free. The clean way through is to point the price forward. Everything you published free stays free. The price goes on what comes next: the expanded edition, the version with worksheets, the full guide that the free checklist summarizes, the next season of the work.
Nobody loses anything they had. Free users keep every promise you ever made them, and the most invested ones get what they were already asking for, which is more. The announcement can be exactly that plain: here is what the next version includes, here is when it lands, here is the price. Tell the free list first, before any public listing. Their replies are your final validation round, and a few of them will pre-order on the spot, which is the strongest yes that exists. If you want to formalize that step, the pre-sell playbook is the full method.
Picking the number is its own decision with its own method, competitor scan, fee math, a price you can defend on the page, and it is covered in how to price your first digital product without guessing. The short version: the busy shelf you found in signal three is also your pricing anchor.
What changes the day it costs money (support, refunds, expectations)
Be clear-eyed about what you are signing up for, because a buyer is not a user. A buyer expects the file to arrive, the format to be stated up front, questions to get answered, and a refund path that does not require an argument. None of this is heavy, but all of it is real: write the refund policy in plain words, say exactly what is inside and how it is delivered, and name the files like a product instead of a draft. Packaging a free artifact into something worth paying for is a skill of its own, and the free-tools version of it is laid out in how to launch a digital product with no money.
The expectations also start working for you. Buyers reply more seriously than users. Complaints arrive with specifics instead of shrugs. And your dashboard simplifies to three honest numbers, visits, sales, refunds, which are the only three that can tell you whether the paid version is actually working.
Charging, in the end, is not a betrayal of the free thing. It is the answer to a request your most serious users were already making. The three signals just tell you when the request is real.
From free artifact to listed product
Deciding to charge turns a side project into a short, concrete project: package the thing properly, price it with the fee math in front of you, write a page that sells it, and launch it to the people with context. The Zero-Cost Launch guide is that project as a 14-day path, using only free tools the whole way, so the paid version earns its first dollar before it ever costs you one.
Get Zero-Cost Launch, 19 dollars