Pricing

How to test pricing before launch

Gut-feel pricing is the most expensive decision most solo founders make. Here are three pre-launch tests that beat intuition — and the one mistake almost everyone makes.

7 min readUpdated April 2026

Why gut-feel pricing fails

Founders price their first product against themselves. You anchor on what you would pay, what your peers would pay, and what your calendar app charges. That’s three wrong reference points. The right reference point is the person in your core segment on the day the problem is worst.

Three pricing tests that actually work before launch

1. Persona willingness-to-pay (WTP) probes

Generate a persona inside your core segment, present the product, and ask the direct WTP question: “What would you expect to pay per month for this, and at what price would it start feeling expensive?” Repeat across 3–5 personas in core and 2 in adjacent. The cluster at the top of core gives you the ceiling.

2. Van Westendorp inside synthetic segments

The Van Westendorp Price Sensitivity Meter asks four anchored questions: “too cheap,” “a bargain,” “getting expensive,” “too expensive.” Run this inside a synthetic segment of the right size and you get a price corridor instead of a single number — and you avoid pricing under the “too cheap” cliff that destroys perceived value.

3. Anchored package comparison

Show three named packages with the same core value but different commitments (e.g. Solo, Team, Studio) and ask which one the persona would choose. The pattern of choices reveals anchoring and signals whether a higher-tier exists — which almost always lifts your average revenue per user.

Monthly, annual, or usage

  • Monthly. Keep as your primary plan until retention is proven. It is the only honest measurement of fit.
  • Annual. Introduce after month-three retention stabilizes. It smooths revenue but hides churn.
  • Usage. Best when the value to the customer is variable (volume, seats, compute). Worst when it makes budgets unpredictable for buyers.

When to start charging

On day one, for anything you expect to be commercial. Free-from-the- start products attract users who never intended to pay and train you to build for them. Launch with a real price, keep it above the floor suggested by your WTP probe, and run one more synthetic test before every price change.

See how launchsims prices itself
Sanity-check the structure we recommend by looking at the one we run.
Start
Run a pricing probe inside your core segment
Generate a segment, ask the WTP question, iterate in minutes.
Start

FAQ

What should my first price be?

Start above the price you think feels safe. First prices are almost always too low — they are set against a generic audience instead of the core segment. Use persona WTP probes to find the top of the range your core is willing to pay and price just under that ceiling.

How do I price for different regions?

Do not translate your USD price by exchange rate. Run the WTP probe separately per locale on a representative segment. Regional PPP (purchasing-power parity) and category norms usually matter more than the rate of the day.

Should I offer a free tier?

Only if free users visibly help paid users convert (content, network effects, or referrals). Otherwise a free tier becomes a support cost with no retention benefit. A limited trial is usually safer before launch.

What about annual vs. monthly?

Before launch, sell monthly. Annual contracts hide churn and let you fool yourself about fit. Introduce annual pricing only after you can see real monthly retention stabilize.

Can I change pricing after launch?

Yes, but it’s expensive. Grandfather early users, communicate early, and tie the increase to something visibly new. The best pre-launch test prevents you from needing a price raise in month 2.