How to Test Your Pricing Before You Launch
Most founders pick a price by staring at a competitor's site and adding or subtracting a few dollars. That is not pricing. That is copying someone who probably guessed too. The good news is you can test a price before you build the full product, before you spend on ads, and before you commit to a number you regret.
Here is how to do it with the people and tools you already have.
Start with the value, not the cost
Price tracks the value a customer gets, not what it costs you to deliver. A spreadsheet that saves a contractor ten hours a week is worth far more than the two dollars of compute behind it.
Before you set a number, write down one sentence: what does the customer get, and what is that worth to them in money or time? If you cannot answer that, you are not ready to price. You are ready to interview customers.
Ask the questions that reveal willingness to pay
Do not ask "would you pay for this." People say yes to be nice, and that yes means nothing. Ask questions that force a real reaction:
- "What do you use today, and what does it cost you?"
- "If this disappeared tomorrow, what would you do instead?"
- "What would feel too expensive, and what would feel so cheap you'd doubt it?"
That last one is the van Westendorp idea in plain language. Ask ten to fifteen people in your target group and a usable price band appears. The point where "too cheap" and "too expensive" overlap is your safe zone.
Run a fake door test
You do not need a finished product to test a price. You need a page and some traffic.
- Build a simple landing page that describes the offer and shows real prices.
- Add a clear button: Start, Buy, or Get access.
- Send a small amount of traffic to it, from a forum post, a small ad, or your own audience.
- When someone clicks the button, show a short message: "We are opening access soon, leave your email."
The click is the signal. People who click after seeing the price have told you the number did not scare them off. If almost nobody clicks, your price or your offer is off. Test two pages with two prices and you learn even more.
Charge before you finish building
The strongest test is taking money. A pre-order, a deposit, or a founding-member rate proves intent in a way no survey can. If five people pay forty dollars for something that does not fully exist yet, you have learned more than a hundred survey responses would teach you.
Be honest about timing. Tell buyers it is early, offer a refund, and deliver. The people who pay early are also your best source of feedback later.
Test three prices, not one
Never test a single number. You learn nothing from one data point. Pick a low, middle, and high price and watch how behavior changes.
A common pattern: the middle price converts almost as well as the low price but brings in far more revenue per customer. You only see that by testing the range. Raising a price often filters out the customers who would have complained the most anyway.
Read the objections, not just the clicks
When someone hesitates, ask why. The reason behind a no is worth more than the no itself.
"Too expensive" usually means the value was not clear, not that the number was wrong. "I need to think about it" often means you are talking to the wrong person. Sort these reasons and you will know whether to change the price, the message, or the audience.
Watch what competitors and reviews tell you
Your competitors have already run pricing experiments, and the results are sitting in their pricing pages and their reviews. Look for where customers say a competitor is overpriced, or where they happily pay a premium. That tells you where the market has room.
This is where doing the research before you launch pays off. Reading real demand and the gaps in competitor offers gives you a price band grounded in evidence instead of a guess. A DemandSonar scan pulls that signal together, mining real discussions, tearing down competitor offers and reviews, so the price you test on launch day is one the market has already shown it will pay.