Charging for the first small thing you build: what changes and what it costs

Built something small and put a price on it from the first day rather than growing an audience first. What actually changed.

What charging changes immediately

• The feedback becomes real. Free users are polite. Someone who paid tells you what is wrong within a week, in specifics.
• You find out if the problem is real in days, not months. Ten people saying they would use it and nobody paying is a complete answer and you get it early.
• Scope shrinks by itself. It is much easier to cut a feature when the question is whether it justifies a price rather than whether it is nice.

What it costs

• Far fewer users. Expect a fraction of what free would give, and it feels bad for the first month.
• You now have obligations: refunds, invoices, tax handling, and answering support. Small, and not zero.
• Some things genuinely need scale before they are worth anything, and charging early kills those.

Practical bits

• Charge a small one-off rather than a subscription for a first thing. A subscription is a promise to keep maintaining it and you do not know yet whether you will.
• Price it higher than feels comfortable. The number of people willing to pay a small amount and a slightly larger amount is nearly the same, and the second group complains less.
• Ship the payment before the polish. It is the part most likely to be broken and the only part that must work.