Most pricing advice for startups applies to products that already exist and have real customers. Pre-product pricing is a different problem: you need to name a number before you know exactly what the product will do, without data from paying customers to anchor to, and without the ability to watch where people drop off in a checkout flow.
You still need a number. Here's why, and here's how to get to a defensible one before you've written the first line of code.
Why You Need a Price Before You Have a Product
Two reasons, both practically significant.
To run a valid smoke test. A smoke test -- asking potential customers to actually pay for access before the product exists -- requires a specific price. "Would you pay for this?" is a question. "$49/month -- would you buy it?" is a test. The difference in signal quality is substantial. A landing page that collects emails with no price on it tells you people are interested. A landing page with a price that collects pre-orders tells you people are willing to pay specifically that amount for this specific thing.
To validate the business economics. The price you charge determines how many customers you need to cover your costs and reach your income target. A product priced at $10/month needs 1,000 customers to generate $10,000 MRR. A product priced at $100/month needs 100. These require completely different acquisition strategies. If the product you're building requires a marketing and development investment that only makes sense at $100/month but you're planning to charge $15/month, the business math is broken -- and you should know this before you build.
The pre-product pricing exercise forces you to confront these economics while you can still change the product's scope, target market, or positioning rather than after you've built something that doesn't support the business you need.
The Two Pricing Decisions
There are actually two pricing decisions at this stage, and they're different:
The smoke test price: What you charge for pre-orders, beta access, or founding member status. This could be lower than your eventual price (as a founding discount) or the same. It's primarily a willingness-to-pay signal.
The ongoing launch price: What the product will cost at public launch. This needs to be set before you build to ensure you're building for a price point that makes sense. A product that costs $15/month needs to be built cheaply and operationally light. A product at $200/month can have a more intensive customer experience.
Work out the ongoing price first. The smoke test price follows from it (often with a founding member discount applied).
The Four Pricing Benchmarks
Benchmark 1: What Do People Pay for the Closest Alternative?
Your starting point is what people are already paying for the problem. If your customer currently uses a combination of a $30/month tool and 3 hours of manual work per week, you have an anchoring point: the relevant willingness to pay includes both the $30/month direct cost and the value of 3 hours of their time.
Find the pricing pages of your 2-3 closest alternatives. Look for:
- The most common price point where users enter (usually the middle tier)
- The price point where their largest customer segment pays
If your closest competitor charges $99/month as its primary tier, pricing at $99/month is a credible benchmark. Pricing at $15/month against a $99/month competitor signals either a significantly inferior product or an uneducated pricing decision -- neither reads well to the buyers who are aware of the competitive context.
Benchmark 2: What Is the Problem Worth to the Customer?
This is value-based pricing, and it's the strongest justification for any price.
Ask in customer interviews: "What would it be worth to you if this problem was completely solved?" The answers are often surprising. A customer who pays $200/month for a tool that saves them 5 hours per week is getting an excellent deal at their hourly rate. The value calculation is: hours saved per week × hourly rate × 4 weeks. At $75/hour, five hours per week = $1,500/month in value. Charging $99/month against $1,500/month in delivered value is easy to justify.
You don't need to capture all the value. Capturing 10-20% of the delivered value in price is the standard range for most B2B tools. But knowing the value helps you set the price floor: you should almost never price below 5% of delivered value, because at that level you're leaving so much on the table that either your value estimate is wrong or your pricing is.
Benchmark 3: What Budget Category Does This Fall Into for the Buyer?
Different price points land in different budget authority contexts.
For B2B products:
- Under $50/month: typically purchased without approval, expensed or on a personal card
- $50-$200/month: often requires manager approval but still fast
- $200-$500/month: frequently requires a department head's approval
- Over $500/month: usually requires a procurement or finance sign-off
This doesn't determine your price, but it determines how your sales process works. If you're building a tool that requires individual contributors to make a purchasing decision, pricing at $300/month means they need approval you didn't plan the sales process around.
Benchmark 4: What Do Your Unit Economics Require?
Work backward from your income target.
If your goal is $10,000 MRR within 12 months: how many customers do you need at your proposed price? Is that number achievable given the size of the market you're entering and your acquisition strategy?
| Price Point | Customers for $10k MRR | Customers for $50k MRR |
|---|---|---|
| $15/month | 667 | 3,333 |
| $49/month | 204 | 1,020 |
| $99/month | 101 | 505 |
| $299/month | 34 | 167 |
| $499/month | 20 | 100 |
Lower prices require more customers. More customers require more acquisition effort and usually a more scalable (and expensive) acquisition channel. If your Go-to-Market is personal relationship-driven outreach, hitting 667 customers at $15/month is far harder than hitting 101 customers at $99/month from the same effort.
The Van Westendorp Price Sensitivity Method
The most useful pre-product pricing research tool. Add four questions to your customer interviews:
- Too cheap: "At what price would [product] be so cheap that you'd question its quality?"
- Acceptable cheap: "At what price would [product] feel like a bargain -- expensive, but fair?"
- Acceptable expensive: "At what price would [product] start to feel expensive?"
- Too expensive: "At what price would [product] be so expensive you'd never consider buying it?"
Collect these answers from 10-15 people who match your customer profile. Plot the four price points on a simple chart for each respondent. The range between "acceptable cheap" and "acceptable expensive" across your respondents reveals the acceptable price range -- the zone where your price is defensible to the market.
The most important finding from Van Westendorp is usually the floor rather than the ceiling. Founders consistently price below what the market considers credible. If respondents say the product would start to feel "too cheap" at $20/month, pricing at $12/month is actively working against you -- it signals low quality to the exact people you want to buy.
The Willingness-to-Pay Signal Hierarchy
Not all pricing signals are equal. From weakest to strongest:
| Signal | What It Tells You | Reliability |
|---|---|---|
| "Would you pay for this?" in interview | Stated intention, not behavior | Low |
| Van Westendorp price range exercise | Acceptable range in customer's mind | Medium |
| Landing page with specific price + email capture | Behavioral intent (they stayed after seeing the price) | Medium-high |
| Pre-order at specific price | Actual willingness to transact | High |
| Completed payment | Confirmed willingness to pay | Highest |
For pre-product validation, move as far down this hierarchy as your stage allows. A landing page with a visible price point is the minimum; a pre-order or payment link is the gold standard.
The Most Common Pre-Product Pricing Mistake
Starting too low. Almost universally.
The reasoning founders use: "I'll charge less now because I don't have all the features yet. I'll raise prices once the product is more valuable."
Why this fails:
Low price attracts price-sensitive customers -- the cohort with the highest churn, lowest satisfaction threshold, and lowest referral rate. You then optimize your first product development cycle around the wrong customers.
Raising prices is harder than you expect. Early customers expect they'll keep the founding member rate forever. Raising prices on an installed base is a churn trigger, a support burden, and a PR risk with the specific people whose goodwill you most want.
Low price signals low value to the sophisticated buyers who would pay more. A product at $9/month in a market where alternatives cost $79/month sends a signal that something is missing -- and the sophisticated buyer will look for what it is rather than assume they've found a bargain.
The correction: whatever price your gut suggests, test whether the conversations change meaningfully at 2-3× that price before committing to the lower number.
The Freemium Decision at Pre-Product Stage
Almost always the wrong choice before you have 1,000 paying customers.
The reasons: freemium requires sufficient volume of free users for the conversion math to work. At the pre-launch stage, you do not have that volume, and the free tier will attract users who don't convert rather than helping you identify who does.
More importantly: free users provide different feedback than paying users. The threshold for reporting a bug, requesting a feature, or engaging with customer research is different for someone who has paid $99 you for something versus someone who opened an account because it cost them nothing.
During the validation and early-launch phase, charge for everything or offer a time-limited free trial rather than a permanently free tier. The customer who converts from a 14-day trial to a paid account has given you actionable data. The customer who stays on a free tier indefinitely has given you cost without signal.
Freemium is a scale strategy. Use it after you have the conversion data to know that free users convert at a rate that justifies the cost of serving them.
The Pre-Product Pricing Process in Order
-
Collect competitor pricing: 30 minutes. Document the primary price point and tiers for your 2-3 closest alternatives.
-
Estimate value delivered: From customer interviews, calculate (or estimate) the financial value of solving the problem completely. This is your ceiling.
-
Run Van Westendorp on 10-15 interview subjects: Adds 5 minutes to each interview. Analyze the acceptable price range.
-
Check unit economics: Work backward from income target at your proposed price. Does the required customer count match your expected acquisition capacity?
-
Set the price: Should fall within the Van Westendorp acceptable range, at or above 5-10% of delivered value, and at a level that produces unit economics you can reach.
-
Put it on the landing page: A visible price point on the landing page is a validation test in itself. The conversion rate at that price is data.
-
Run a smoke test if possible: A Stripe Payment Link or Gumroad product at the target price, linked from the CTA. Real payment completions are real signal.
The price you set now is not permanent. It will change as you learn more, serve more customers, and understand your market better. But starting with a defensible price based on real research, rather than a guess you're uncomfortable defending, is the starting point that makes every subsequent pricing decision easier.
Ready to validate your idea?
Start using WarmLaunch today to grow your waitlist.