← Writing

Charge Before You're Ready

Pricing for technical founders: why engineers undercharge, why free users tell you nothing, and how a price is a question that tests if the problem is real.

Free users are the most expensive customers you’ll ever have.

They cost you support, infrastructure, and your time, and they pay you in the one currency that’s worthless: a usage you can’t trust. Someone who didn’t pay will tell you they love it and can’t wait for the next version. None of it predicts whether they’d open their wallet, and the wallet is the only vote that counts.

You’ll want to wait to charge, until it’s more polished, until it’s worth it, until you’re ready. That instinct is going to cost you months of clean, false signal.

Why engineers undercharge

You undercharge because you can see the cost and they can’t. You know exactly how long it took, how simple the core really is, which corners are held together with tape. From inside, it feels like charging much would be taking the mickey.

But customers don’t buy your effort. They’ve never been able to see it and they don’t want to. They buy the size of the problem you remove. A bookkeeper doesn’t pay for your reconciliation algorithm; they pay to stop losing two hours every week and to stop dreading end of month. Priced against their pain, the number you were embarrassed to say is usually too low.

There’s a second reason, quieter: a price is a judgement, and judgement can be rejected. A free product can’t really be turned down, and so it can’t really be wanted, either. Charging means standing behind a number and letting someone say no to your face. That’s uncomfortable for exactly the reason it’s valuable. The discomfort is the signal arriving.

A price is a question

A price isn’t a number you settle once the product deserves it. It’s a question you ask to find out whether the problem is real: is this worth more to you than the money? Until someone answers yes with money, you don’t have a business: you have a hobby other people are enjoying for free.

So charge early, and treat the first prices as experiments, not commitments. The goal isn’t to maximise revenue from ten people. It’s to learn three things only a price can teach you: whether the problem is painful enough that money moves, who it’s painful enough for, and how much. None of that survives contact with a free tier, because free changes who shows up. The people who’ll tolerate a rough free thing are not the people who’ll pay for a good one, and building for the first group quietly steers you away from the second.

Watch the flinch. When you say the price, the honest reactions live in the half-second before politeness takes over. A flinch and a sale means you’re priced about right and they feel it. A flinch and a no means the problem isn’t big enough for them. Useful, keep going. No flinch at all, easy yes, “oh, is that all?” You’re too cheap, and you just learned you can charge more before you’ve built a thing more.

What this looks like

Picture an engineer who built a genuinely good internal-tooling product and gave it away to twelve teams to “get traction first.” All twelve loved it. The dashboards said engagement was strong. Eighteen months in, asked to convert to a modest paid plan, eleven of the twelve quietly left, not because the price was wrong, but because they’d only ever valued it at free, and free was the entire reason they’d shown up. The one that stayed had been trying to pay for a year. That one customer, found on day one with a price, would have been worth more than the eighteen months of applause.

The lesson lands harder in a smaller market. You can’t run the volume game an enormous market forgives: pile up a million free users and monetise a sliver later. With a smaller home market and thinner capital, your unit economics have to work earlier, which means you need to know what people will pay sooner, not once you’ve scaled. Charging early isn’t greedy here. It’s how you find out if the maths can ever close.

What to do Monday

Pick a price that feels slightly too high, high enough that saying it out loud makes you a little uncomfortable. Then take it to five people who have the problem, and ask them to actually pay, now, not “would you pay.” Watch the flinch. Count the yeses. You are not trying to get rich off five people; you’re buying the truth about whether you have a business, and a price is the only place to buy it.

The product doesn’t have to be ready. You have to be ready to hear the answer.

Next: even a thing people will pay for dies in silence: if no one can find it, it doesn’t exist.