How to monetise a side project
Pick the simplest model your project supports, price it against what the customer saves rather than what it cost you to make, and start charging before it feels ready. For most side projects that means a subscription if people get value repeatedly, a one-off price if they get it once, and a service if you have fewer than ten customers and want revenue this month. The usual mistake is waiting until the product deserves money, which is a judgement only customers can make and one they make by paying.
Choose the model your project already fits
The model is mostly decided by the shape of the value, not by what you would prefer. Work out how often the customer gets the result, and the answer falls out.
- Repeatedly, and it gets more valuable over time: subscription. Software, tools, anything with saved state.
- Once, and then they are done: one-off price. A template, a course, a report, a piece of work.
- It depends heavily on the customer: a service, priced per engagement. Slow to scale, fastest to revenue, and it teaches you what to build.
- Value comes from other people being there: paid access to a group, or a marketplace fee.
- Value comes from attention rather than from the user: sponsorship or affiliate. Needs an audience first, so this is rarely the first model.
Price against the saving, not the effort
What a thing cost you to make has no bearing on what it is worth to a customer. The number that matters is what they save or gain: hours back, a cost avoided, revenue that would not otherwise arrive. Price is a fraction of that number, and the fraction can be larger than most first-time founders dare.
Two practical rules. First, whatever price you first think of, it is too low; almost everyone underprices at the start and the cost of that is not just the revenue, it is that a cheap price attracts customers who churn and complain. Second, a price that nobody pushes back on is too low, so expect and welcome a bit of friction.
If you genuinely cannot tell, offer three tiers and watch which one people pick. That is cheaper than research and more honest than asking.
Start charging before it feels ready
There is a version of this where you finish the product, polish it, and then introduce a price. It is emotionally comfortable and it is the slowest possible route, because the entire time you are working from guesses about what people will pay for.
The faster version: put a price on it now, at whatever stage it is at, and describe honestly what it currently does. Early customers are considerably more tolerant of missing features than of being surprised later. They are also the most useful people you will ever talk to, because they have proved they care about the problem with money.
If it truly is too early, sell the outcome instead of the software. Do the thing manually for a customer, charge for it, and use what you learn to decide what to automate.
What to do when the free users leave
Introduce a price to a free product and a large share of users will go. This feels like a failure and is usually the opposite: the people who leave were never going to pay, and the cost of serving them was hiding how small the real business was.
What to watch is not the number who left but what the ones who stayed have in common. That is your actual customer, and it is often narrower and more specific than the audience you thought you had. Rewrite the landing page for them.
What "monetised" should mean at first
The first meaningful target is not replacing your salary. It is the first payment from someone you are not related to, then ten of them, then enough that the thing pays for itself. Each of those is a different problem and only the first one is about the product.
Set the number that would make it real to you and write it down. Most people never do, and so the project has no finish line and every month is ambiguous.
Frequently asked questions
When should I start charging for a side project?
Earlier than feels right, and before the product feels finished. Whether it deserves money is a judgement only a customer can make, and the way they make it is by paying. Waiting means every decision until then is based on a guess.
How much should I charge?
A fraction of what the customer saves or gains, not a multiple of what it cost you to make. Whatever number you first think of is probably low. If nobody ever pushes back on the price, it is definitely low.
Subscription or one-off payment?
Subscription if the customer gets value repeatedly and the thing accumulates state. One-off if they get the result once and are done. Charging monthly for something used once produces cancellations and refund requests rather than revenue.
Can I monetise a side project without an audience?
Yes, and most do. An audience helps with one model, sponsorship, and it is the slowest to reach. Selling a product or a service to a hundred specific people you contact individually needs no audience at all.
How much money is a realistic first target?
The first payment from a stranger, then ten customers, then covering its own costs. Replacing a salary is several problems further along and treating it as the first target makes everything before it feel like failure.