Most founders set a price, put it on a landing page, and treat any conversion problems as messaging problems. Often they're right. But sometimes the price itself is the problem -- and without deliberately testing it before launch, there's no way to know which is true.
Pricing is a hypothesis. Like any hypothesis in the validation phase, it should be tested with increasingly strong evidence before committing to it. This post covers every pricing test available before launch, from the weakest signal to the strongest, in the sequence that produces the most useful data with the least wasted effort.
The Signal Hierarchy
Not all pricing signals are equally reliable. Running the tests in order of signal strength -- starting with easy-to-collect qualitative data, ending with actual payment behavior -- produces a picture that is far more reliable than any single data point.
| Test Method | Signal Type | Reliability | Effort |
|---|---|---|---|
| Interview: Van Westendorp | Stated preference | Low-medium | Low |
| Interview: budget anchoring | Stated preference | Low-medium | Low |
| Community mention with price | Observed reaction | Medium | Low |
| Landing page tier click data | Behavioral intent | Medium-high | Medium |
| Cold outreach price conversation | Behavioral intent | Medium-high | Medium |
| Smoke test: pre-order without payment | Behavioral intent | Medium-high | Medium |
| Smoke test: completed payment | Actual behavior | High | Medium-high |
Work through this stack. Don't rely on one method. Conflicting signals between methods are themselves informative -- they tell you that different segments have different price perceptions.
Method 1: Interview-Based Pricing Research
Van Westendorp Price Sensitivity Method
Add four questions to every customer interview. For each potential customer interviewed:
- "At what price would this feel too cheap -- so cheap you'd question its quality?"
- "At what price would this feel like a bargain -- expensive but fair?"
- "At what price would this start to feel expensive?"
- "At what price would this be so expensive you'd never consider it?"
After 10-15 interviews, the overlap between "feels like a bargain" and "starts to feel expensive" across respondents defines your acceptable price range. The lower bound of "too cheap" is your price floor -- pricing below it actively signals low quality.
Most founders discover two things from Van Westendorp: their planned price is within the acceptable range, and their "too cheap" floor is higher than they assumed. People are more willing to signal quality concern at low prices than founders expect.
The Budget Anchoring Conversation
A technique for discovery calls with B2B prospects. Rather than asking about price directly, have a conversation where budget naturally comes up:
"If this solved [specific problem you've been discussing], how would you normally budget for something like this? Is it a software expense, an operations expense, something that would need sign-off?"
The conversation reveals: (a) which budget category this falls into, (b) the rough magnitude of spend they're accustomed to in that category, (c) whether this is an individual decision or requires approval.
This is not a question about your specific price. It's a conversation about how they think about spending on the category of problem you're solving. Their answer provides the context for your price -- you learn whether $99/month is a rounding error to them or requires a purchasing committee.
What to Do with Interview Data
Plot the Van Westendorp ranges from each respondent. Identify:
- The price below which quality concern begins (your floor)
- The range where "fair" and "starting expensive" overlap (your target zone)
- The price above which you lose more than half your respondents (your ceiling)
Budget conversation data tells you the approval path at different price points. Under the approval threshold: fast individual decision. Above it: slower, requires a different sales process.
Method 2: Community Pricing Reactions
Post in the communities where your target customers are (following community guidelines for what's allowed). Include the price explicitly in the post.
Two formats that work:
The "I'm planning to charge X" post: "I'm building [thing] and planning to charge $[X]/month. Here's what it does: [specific description]. Does that pricing make sense for what it solves?"
Direct responses in the comments signal: "seems reasonable" (you're in the zone), "that seems high for a new product" (you may be above ceiling for early adopters), or "that's way less than I expected" (you've left money on the table).
The feedback request post: Describe the product, include the price in the description, and ask for feedback on the product itself. Price reactions that come unprompted ("the price seems off" or "I'd pay more than that") are stronger signal than prompted price opinions because the respondent chose to address the price rather than being asked about it.
The limitation: community respondents may not be your exact target customer. Calibrate the weight you give this data by checking whether the people responding match the profile of your intended buyer.
Method 3: Landing Page Tier Click Data
A pricing page with real tiers, where each CTA ("Join waitlist for X tier") fires a tagged analytics event and routes to a segmented waitlist form. Track which tier receives the most engagement after 200+ pricing section views.
Key signals:
- Middle tier getting 50-70% of clicks: price is in range
- High tier getting >30% of clicks: you're underpriced
- Low tier getting >60% of clicks: targeting issue or middle tier undifferentiated
- All tiers low engagement: problem is copy above the pricing section, not the price itself
Combine with heatmap data (hover time per tier, scroll behavior on pricing section) for additional signal about which tier captures consideration even from visitors who don't click.
This method requires traffic to the landing page. 200+ pricing section views is the minimum for actionable data. Without this volume, data is directional, not conclusive.
Method 4: Cold Outreach Pricing Conversation
Reach out directly to 15-25 potential customers who match your ICP. After establishing context about what you're building, include the price explicitly in the message.
The format: "I'm building [product] to solve [specific problem]. It's going to be $[X]/month. If you're dealing with [problem], I'd love to show you what I'm building and get your reaction to whether the price makes sense for the value."
The response pattern is the signal:
- No response at all: may be the wrong ICP or the message didn't resonate (not definitive about price)
- Positive interest without price comment: price is not a barrier, at minimum
- Interest with "that seems like a lot": the price is above their expectation
- Interest with "that seems reasonable" or no price qualifier: you're in range
- "I'd pay more for X": you've underpriced or under-featured
Cold outreach pricing conversations have better signal than survey responses because the person is responding in the context of actually hearing about your product and deciding whether to engage -- a more realistic purchase evaluation context than an abstract interview.
Method 5: The Smoke Test
The strongest pre-launch pricing signal comes from observing whether people actually initiate or complete a payment at your price point.
Pre-Order Without Payment Collection
A landing page CTA: "Pre-order at $[X] -- be first when we launch." The button routes to a form that captures email and stated intent to purchase at the listed price. Not a checkout -- just a commitment to buy when available.
Signal value: moderate. The person has completed an action that implies purchase intent at a specific price. This is stronger than clicking a "join waitlist" button, weaker than actually paying.
Volume for conclusive signal: 20-30 pre-order form completions from cold traffic (not personal network, not from a community where they know you).
Completed Payment
The strongest possible pre-launch pricing signal: a real payment at your planned price.
Implementation options:
- Stripe Payment Link: Create a product in Stripe at your planned price. Link the "buy" button to the payment link. When a customer completes payment, email them personally explaining that access will be provided at launch date and they're locked in at the founding rate.
- Gumroad pre-order: Gumroad supports pre-order products natively. Payment is collected at order time; you can set a delivery / launch date.
The ethical requirement: if you collect payment pre-launch, you must either deliver exactly what was promised or offer a full refund. Don't collect pre-launch payments unless you are committed to launching.
Signal value: highest available before launch. A stranger who completes a payment at your planned price has demonstrated behavioral willingness to pay that no survey, interview, or click data can match.
Volume for conclusive signal: 5-10 completed payments from cold traffic. This is a high bar precisely because it's the strongest signal. 5 completed payments at $99/month from cold traffic is extremely strong validation. 50 "interested" survey responses is not.
Combining Methods: What to Do When Signals Conflict
Conflicts between methods are common and informative.
Interview says $99 is in range, but landing page shows 70% engaging with the $49 tier: Your interview population may skew higher-WTP than your actual web traffic. Check traffic source. Are you driving community traffic (lower WTP, more price-sensitive) or targeted outreach traffic (higher WTP, more qualified)?
Community reactions say "too expensive," but cold outreach produces no price objections: Community members may not be your target customer. Your target customer (in cold outreach) isn't raising price as an issue. Weight the outreach data higher.
Pre-orders are few, but landing page tier clicks look strong: Intent to click at a price is not intent to pay. The gap between click data and payment completion is normal; it's the cost of moving from stated preference to revealed preference. Neither signal is wrong -- they're measuring different things.
Rule: Always weight behavioral signals (payment, click, form completion) over stated signals (interview responses, community reactions). When they conflict, the behavioral signal is usually closer to true purchase behavior.
The "Price Too High" vs. "Price Too Early" Distinction
When conversion is poor at your price, there are two possible causes that produce identical symptoms:
Price too high: The price exceeds what the market is willing to pay for what you've described. Reducing the price would improve conversion.
Price too early: The visitor doesn't have enough trust, context, or understanding of the value to evaluate the price correctly. They may be willing to pay the price after more information -- but they're evaluating it with the information currently on the page, which isn't enough.
The diagnostic: do your best-informed potential customers (those who have seen a demo, read everything, spoken with you personally) raise price objections? If not, the issue is information (earlier in the funnel) rather than price.
Fix the information problem before reducing the price. A price reduction applied to a presentation problem doesn't solve the presentation problem -- it just makes the product cheaper without improving conversion.
The Pre-Launch Pricing Test Stack in Order
Run these in sequence, not simultaneously. Each informs the next.
- Van Westendorp + budget anchoring in interviews (weeks 1-3 of validation): establish the acceptable range and approval context
- Community post with price included (week 3): get unprompted reactions from the broadest relevant audience
- Landing page with pricing tiers + event tracking (weeks 3-8): collect behavioral click data as traffic arrives
- Cold outreach price conversations (weeks 4-8): test the price in a realistic consideration context
- Smoke test: pre-order or payment link (weeks 6-8+): if the other signals are green, test with actual payment mechanics
By the time you complete this stack, your price is not a guess. It's a hypothesis that has been tested with five distinct methods, each with its own limitation and each contributing to a more complete picture of true market willingness to pay.
That picture is more reliable than any single perfect test.
Ready to validate your idea?
Start using WarmLaunch today to grow your waitlist.