If you can't take payments yet, should the price be on the page?

You can't test a price nobody is able to pay. That's the bit I keep running into — the number is up, the button doesn't charge anyone, and I have no way to tell what it's doing.

I put pricing live before payments were open, with an email-capture button where checkout will eventually go. Three options were on the table and I've been second-guessing the one I picked.

Hiding the price entirely. Cheapest thing to build, but it moves the whole conversation to "is this going to be expensive," and I lose the people who'd have been fine with the number.

Showing a range. Felt honest until I tried to write it down. Any range wide enough to be safe is too wide to be useful, and narrowing it is committing to a price with extra steps.

Showing the real price with a notify-me button. That's what's live. It costs me the people who see the number, decide it's not for them, and leave without ever trying the free tier — which is the entire product right now.

What I can't measure is that last group. There's no purchase event to compare anything against, so a bounce off the pricing page and a bounce off any other page look identical to me. I know how many people land there. I don't know which of them left because of the number.

If you've launched with prices up before you could charge — did you find any signal at all in that gap? Or is it just something you accept until the first real transaction?