Launch Before You Have Revenue: Signals to Chase Until the First Payment
Before revenue, a launch is judged by a ladder of signals: curiosity, understanding, a first use, a return visit, a reply that describes the problem and finally a request to pay. Chase the highest rung you can reach this month, show a price earlier than feels comfortable and set a date by which a free product must either earn or change.
What counts as progress when revenue is zero?
Not every number is equal, and a product with no revenue needs a way to tell strong evidence from weak. Rank what you can observe, from the cheapest for a visitor to give to the costliest. The higher the rung, the more it should change what you do next.
| Rung | Signal | What it tells you | Reading rule |
|---|---|---|---|
| 1 | A visit or a vote | The tagline got a click | Treat as noise until paired with a higher rung |
| 2 | Time on the page, a scroll to the main section | The sentence made sense | Compare across tagged links, not in isolation |
| 3 | A finished main task | The product works for a stranger | Ratio of visitors to finishers is your first real number |
| 4 | A return visit without a reminder | It solved something | The best free signal; note who and why |
| 5 | A reply describing their own problem in their own words | You found the right person | Copy their words onto the page |
| 6 | A question about price, or a request to pay | Value exists | Say a price now; do not wait to be asked twice |
Keep this table somewhere you can see it during launch week. When a day produces fifty rung-one signals and no rung-four ones, the day was a failure of fit, not a success of reach. The launch metrics to track page shows how to record each rung per link.
When should the first price appear?
As early as someone has reached rung three. A price is the cheapest way to find out whether the finished task was worth anything. Hiding it keeps visitors, but it also keeps you from the one answer you most need.
- A stated price with a free trial works when the value shows up quickly: a visitor can feel it in a session.
- A founding price for early users works when the product is rough and you want committed testers, not just a free crowd.
- A paid pilot for a few teams suits products sold to businesses, where the trial is a conversation, not a button.
- A waitlist with a price shown tells people what they are waiting for. A waitlist with no price teaches you less.
The first paying customer playbook goes through the first sale, and the guides to pricing a micro SaaS and making money from an app compare models.
How long can the product stay free?
Set a date before you launch, and decide what happens on it. A rule that works: pick a day about six to eight weeks out, write on a card what evidence would make you start charging and what evidence would make you change the product, then read the card on that day.
- Evidence to charge: at least a handful of people reached rung four, and one of them asked about price or said they would pay.
- Evidence to change: people reached rung three and left. The product works, but not for them. Change the user or the promise before the features.
- Evidence to stop: nobody got past rung two after you reached the right people with a clear sentence. That is a result, and a cheap one to learn at this stage.
What should the page say when there is nothing to buy yet?
Say what it does today, what is not built and what you will charge later, if you know. “Free while in early access; I plan to charge for teams later” is honest and lets a visitor decide whether to invest effort. Avoid fake scarcity and fake logos, and do not describe customers you do not have.
Publishing a free listing is a low-cost start. On the launch board the form asks for a pricing model, so state it truthfully before you press Publish; the listing is final afterwards, so a plan that changes later is explained on your own page. If you are still working out what to build, the ideas board and the finance ideas show how people phrase problems that might be worth paying for.
What can you skip while revenue is zero?
- Revenue-style reporting. A table with the six rungs per channel replaces any dashboard.
- Growth spend. Without a price you cannot judge what a user is worth.
- Feature requests that only free users make. Weigh the requests of the people who reached rung five or six first.
When a price has been tested and someone has paid, move to the thirty-day plan or the ninety-day roadmap to turn it into a routine.
Frequently asked questions
Can I launch a product before it earns anything?
Yes, and most products do. Treat the launch as a test: judge it by a ladder of signals, from a finished task and a return visit to a reply describing the problem and a question about price. Set a date to decide whether to charge, change or stop.
When should I add pricing to a new product?
Once a stranger has finished the main task. A price is the cheapest honest question, and praise cannot answer it. A trial, a founding price or a paid pilot are all reasonable ways to ask, so choose the one that fits how the product is sold.
Is a waitlist a good signal without revenue?
A waitlist with a price shown is a better signal than one without, because it tells you whether people will wait for something at that cost. A bare email list tells you someone was curious. Count return visits and replies as stronger evidence than sign-ups.
How long should I keep a product free?
Set a date before launch, about six to eight weeks away, and write down what evidence would make you charge, change or stop. Read it on the day. Without a date a free product drifts, which wastes the one advantage of being early: you can learn quickly and cheaply.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.