Live billing as a forcing function

I turned billing on at hey anna later than I should have, and I knew the principle the entire time. The moment money changes hands you find out three things you can’t learn any other way: whether the value is real, whether the price is right, and who the customer actually is. I could have written that sentence months before I acted on it. The gap between knowing it and doing it is what this is about.

The reasoning I gave myself sounded responsible. Get the product right first. Don’t charge for something half-finished. Build trust, then ask for money. Each one is defensible on its own, which is what made them dangerous together. “I’ll charge later” felt like discipline and was avoidance.

Free usage hides the one number you need

Free usage tells you that people will use a thing that costs them nothing, which is very close to no information. Usage at a price of zero measures curiosity, politeness, and the absence of friction. It doesn’t measure value, because value is what someone gives something up for, and at zero they give up nothing.

A charge is the cheapest instrument you own for measuring value and the signal comes back clean. When the card goes in, you’ve learned the value cleared the price. When it doesn’t, you’ve learned something more useful: either the value isn’t there yet, or the price is wrong, or the person you built for isn’t the person who turned up. Free usage smears all three together into one flattering number, whether that’s sign-ups or sessions or time-in-app, and that number goes up and to the right while telling you nothing about whether you have a business.

What I was protecting myself from was the answer, rather than a half-finished product. While billing was off, “will anyone pay for this” stayed an open question, and an open question is more comfortable to sit with than a result. Recognising that in myself was less flattering than I’d have liked.

The charge tells you who the customer is

I underestimated the third thing. A price doesn’t only test value, it sorts people. The accounts that converted the day billing went live skewed towards a particular kind of operator with a particular problem, and they weren’t always the group I’d been designing for in my head. Free usage had been quietly averaging together the people who would pay and the people who never would, then presenting the blend to me as “users”.

You can’t see that blend until a price splits it. The moment one did, the roadmap got an opinion it had been missing, because I could finally tell which feedback came from someone with money on the table and which came from someone with nothing at stake. Both are worth hearing. They aren’t worth the same weight, and free usage gives you no way to tell them apart.

The lesson

Without the self-flagellation or the founder bravado that turns every mistake into a humblebrag: I delayed a cheap, reversible experiment because the result felt high-stakes, and the delay cost me months of clarity I could have bought with a Stripe integration and a slightly uncomfortable email.

Turning billing on is a two-way door. If the price is wrong you change it. If the timing was early you refund and apologise. Almost nothing about charging is irreversible, which is why “I’ll charge later” is so rarely right. You’re deferring a cheap, recoverable test in order to protect yourself from information, and information is the thing you’re short of.

The discipline I thought I was practising by waiting was the opposite of discipline. Discipline would have been turning it on early, watching who flinched and who reached for a card, and letting the answer reorganise the product around the people who were actually there.

If you’re sitting on a product with billing switched off and a good reason ready, have a look at whether the reason is about the product or about you. Then turn it on.