Can you charge for this yet?
You’re wondering whether to put a price on it, or whether it’s too early and asking for money would kill the momentum you have. Four questions and you will know which.
Everything runs in your browser. Nothing is sent anywhere, and the answer gets its own link you can send to your team.
About this check.
How do I know if I can charge for my product yet?
The strongest signal is people asking what it costs before you bring price up. After that: whether they already pay for something to solve this problem, whether anyone would complain if you switched it off tomorrow, and whether you can say in one sentence what somebody gets for the money without having to explain it.
Should I launch free and charge later?
Free is a reasonable place to be while you’re still learning what the product is, but it teaches you almost nothing about what somebody will pay for. Free users tolerate things paying users will not, and the switch later is harder than introducing a price early. If people are already asking the price, waiting is costing you information as well as money.
How should I price a new product?
Start with one price, one sentence and one thing it does. Tiers are almost always a symptom of not being sure what you’re selling, and users read that uncertainty accurately. The first number will be wrong, which is fine — a price is much easier to change than to introduce.
Is it free, and where do my answers go?
Free, with no account and no email. Everything runs in your browser, nothing is sent to a server, nothing is stored, and I never see what you clicked.
Other checks.
-
Why is nobody using your product?
Which of the five you’re in, why the other four are not it, and the cheap test that confirms it.
-
Was that feedback real, or just polite?
A verdict on that one conversation, and the cheapest next move for it.
-
Is this feature worth building?
Build it, build a smaller version, wait, or say no — with the reason behind it.
-
Should you decide this now, or think longer?
How much of your time this decision deserves, and the one check to run before you commit.
-
Why does your team keep redoing the same work?
Which of four things is causing it, and the smallest change that stops it.