How to Price Your Startup Idea Before You Build

The most common objection to pricing early is that you do not have a product yet, so any number is a guess. That is true. But the purpose of early pricing is not to set a final price — it is to test whether the idea can support a price high enough to make the business work.

This is a unit economics question that you can answer before writing a single line of code. If you need $50/month to reach your revenue target with a reasonable customer count, and the problem your product solves is worth $8/month to the customer, the mismatch is not a launch problem. It is a concept problem. Finding that out after six months of development is the expensive version of the lesson.

This connects directly to market sizing. Price and market size are linked: a $10/month product in a small market is a different business than the same product in a large one. Know both numbers before you start.

Cost-plus pricing works for physical goods where raw material costs set a floor. For software, the marginal cost of an additional customer is near zero. Cost-plus produces prices that are either too low to capture the value you deliver or too high to make sense when competitors offer similar functionality for less.

Value-based pricing starts with a different question: what is the problem worth to the customer? Not what does your solution cost to build — what does the problem cost them when it goes unsolved?

• Time cost. How many hours per week does the problem consume? At the customer's effective hourly rate, what does that add up to per month?
• Revenue cost. Does the problem directly suppress revenue — missed leads, slow processes, conversion failures? Quantify it.
• Existing spend. What are they paying right now to partially solve this problem? Workarounds, manual processes, and cheaper tools all have a price. Your product needs to beat that on value, not just on cost.

Founders who are afraid of rejection price low. The logic is: if the price is low enough, the objection disappears. What actually happens is different.

A low price signals low value. Customers who buy a $5/month tool treat it differently than customers who buy a $50/month tool that solves the same problem. The $5 customer churns faster, demands less, and is more easily replaced by a competitor who charges $4. The $50 customer is more invested, uses the product more, and tells other people about it because the decision to pay feels significant.

Low prices also make the unit economics nearly impossible. At $5/month, you need 2,000 paying customers to reach $10k MRR. At $50/month, you need 200. Those are different acquisition problems, different support loads, and different businesses. The harder one is not always the higher price — it is often the lower one.

The fear driving low pricing is usually about conversion, not economics. But conversion problems are marketing and positioning problems. The right fix is a clearer value proposition and better targeting, not a lower number on the pricing page.

You do not need a product to test price sensitivity. You need a landing page and an honest call to action.

Put up a page that describes the problem, the outcome your product delivers, and a price. The call to action should be something real: a pre-order, a waitlist that requires payment information, or a direct “buy now” with a clear note that the product is in development. Count the people who try to complete the action. The ones who do are signal. The ones who do not are also signal.

This is how you find out whether the question “will people pay for my idea” has a real answer. A landing page with a real price tests two things simultaneously: whether the problem description resonates and whether the price creates enough friction to stop people. Both data points are useful. Neither is available from a survey.

Run at least two price points if you can. The difference in conversion rate between $29/month and $49/month tells you more about your market than any amount of customer research.

The discipline of setting a price before you build forces a set of questions that founders who skip this step never answer until it is too late.

Who is the buyer? In B2B, the person who experiences the problem and the person who approves the budget are often different. The price has to clear both. A $500/month tool that saves an individual contributor two hours a week might be valued by the IC and invisible to the manager signing off on it.

What is the comparison? Customers evaluate your price against alternatives — not just direct competitors, but the cost of doing nothing, or doing it manually, or using the general tool they already pay for. If you do not know what your price will be compared to, you cannot set it intelligently.

Does the model match the value? A tool that saves one hour of work per month is not a monthly subscription product — the value event is too infrequent to justify recurring billing. A tool that runs continuously in the background has a different value structure. Price model and value delivery have to align, or customers will correctly feel that the pricing is wrong even if they cannot articulate why.