How to Price Your First Product

Price your first product on the value you create for the customer, not on what it cost you to make. Look at what your customer already pays to solve this problem today, then price relative to that number. Then charge sooner than feels comfortable, because someone paying you is the clearest proof your idea works.

Most first-time founders get this backwards. They add up their costs, tack on a small margin, and call it a price. That feels safe and fair, but it caps your price at your own effort instead of tying it to what the customer actually gets. A product that saves someone ten hours a week is worth a lot more than the twenty dollars of tools you used to build it.

What is value-based pricing?

Value-based pricing means you set your price based on how much the customer gains from your product, not how much it costs you to build.

The question you’re answering isn’t “what did this take me to make?” It’s “what is this worth to the person buying it?” If your app helps a small business owner get back three hours every week, the price should reflect the value of those three hours, not your hosting bill.

This is the opposite of cost-plus pricing, which is the default most people reach for without thinking. Both have a place, but for a new product where you’re still figuring out demand, value-based pricing gives you room to actually earn something.

Value-based vs cost-plus pricing

Here’s the difference laid out side by side.

	Cost-plus pricing	Value-based pricing
Starting point	Your costs	The customer’s outcome
Question asked	”What did this cost me?"	"What is this worth to them?”
Price ceiling	Your effort and expenses	The value delivered
Best for	Commodities, physical goods with thin margins	New products, software, anything with a clear payoff
Risk	Leaves money on the table	Requires you to understand the customer well

Cost-plus isn’t wrong. If you’re selling handmade candles, your materials set a real floor and competitors set a real ceiling. But if you’re building software or a service where the marginal cost of one more customer is close to zero, cost-plus will almost always tell you to charge too little.

Value-based pricing asks more of you. You have to actually know what your customer is trying to accomplish and what solving that is worth to them. That’s why pricing starts with understanding the customer, not with a spreadsheet. If you haven’t done this yet, customer interviews are where you find those numbers.

How do I figure out what to charge?

Start by anchoring to what the problem already costs your customer. Almost nobody has “no solution” — they have a slow, annoying, or expensive current solution, and your price lives in relation to that.

Here’s a process you can run this week.

1. Find the alternative. What does your customer do right now instead of using your product? A spreadsheet, a freelancer, a competitor, or just living with the problem. That’s your anchor.
2. Put a number on the pain. How much does the current solution cost in dollars, hours, or stress? A tool that replaces a $50/month subscription has an obvious reference point. So does one that saves five hours of manual work.
3. Estimate the value you deliver. How much better, faster, or cheaper is your version? You don’t need to capture all of that value — you just need to price below it so the customer clearly comes out ahead.
4. Pick a starting price. Land somewhere that’s a clear win for the customer but still real money for you. If your product saves them $50 a month, charging $15 is an easy yes and still meaningful revenue.
5. Say the price out loud to a real person. Not “would you pay?” but “it’s $15 a month” and then watch their face. Flinching, hesitating, or shrugging tells you more than any survey.

Notice that none of these steps start with your costs. Your costs matter for whether the business survives, and you’ll check that with unit economics. But they don’t decide the price a customer is willing to pay.

Why should I charge sooner than feels comfortable?

Because charging is the sharpest form of validation there is. People say a lot of nice things about your idea when it’s free. The moment you ask for a card number, the polite lies fall away and you find out who actually has the problem.

A free signup tells you someone was curious. A paid signup tells you someone had a problem worth money. Those are completely different signals, and only one of them means you have a business.

Charging early also protects you from building the wrong thing for months. If you can’t get a single person to pay a small amount, that’s information you want in week two, not week twenty. This is the same reason your MVP should be small — you’re testing whether the core idea holds, and price is part of that test.

You don’t need the product to be finished. You can pre-sell, take a deposit, or charge for a manual version you deliver by hand. The point is to introduce the friction of payment early, while it’s still cheap to learn from it.

The most common pricing mistake: charging too little

Underpricing is the default trap, and it’s easy to fall into because it feels generous and safe. It usually is neither.

When you price too low, three things happen. You leave money on the table that you’ll never get back from those early customers. You attract price-sensitive users who churn the fastest and complain the most. And you signal that your product is cheap, because in a lot of markets, a low price reads as low quality.

Low prices also hide problems. A product priced at a dollar can look like it has demand when really people just aren’t paying enough attention to say no. Raise the price and you learn who actually values what you built.

Raising a price later is harder than lowering it. You can always run a discount or a launch sale to bring a high price down. Clawing a price back up after you’ve trained customers to expect cheap is a much uglier conversation. Start higher than feels natural, and treat any discount as a deliberate, temporary tool.

How do I test a price without guessing?

You test a price the same way you test any assumption — put it in front of real buyers and watch what they do, not what they say.

• Name one real price and watch the reaction. Tell three potential customers the exact number. Easy yes means you’re probably too low. Hard no from everyone means you’re too high or talking to the wrong people. Some yes, some no is a healthy sign.
• Try different prices with different people. Offer $19 to one group and $29 to another. If both convert at similar rates, the higher price is free money.
• Watch the “take my money” moment. The strongest signal isn’t a survey answer, it’s someone reaching for their wallet before you’ve even finished the pitch. That means you’re priced under the value you deliver.
• Sell before you build. A pre-order or deposit on a product that doesn’t fully exist yet is the cleanest price test there is. This connects directly to testing your idea before you build it.

Your first price is a hypothesis, not a commitment. You’ll set it, watch how people respond, and adjust. That loop is the whole job.

What pricing is not

A few things worth clearing up, because they trip up almost every first-time founder.

• Pricing is not permanent. Your first number is a starting bet. You will change it, probably more than once.
• Pricing is not about being fair to yourself. The price isn’t a reward for your effort. It’s a reflection of the customer’s outcome.
• Pricing is not “match the cheapest competitor.” Racing to the bottom just means you both make less. Compete on the value you deliver, not the smallest number.
• Pricing is not one line in a spreadsheet you set and forget. It’s a lever you keep pulling as you learn who your best customers are.

Where pricing fits in the bigger picture is on your business model — the price you choose shapes your whole plan. If you haven’t mapped that yet, the Lean Canvas is a fast way to see how price, costs, and customers connect on one page.

How long does this take, and what should you do next?

Setting your first price should take an afternoon, not a month. You’re not trying to be perfect — you’re trying to pick a defensible starting number and get it in front of real people.

Do this: find the alternative your customer already pays for, price clearly below the value you add but above what feels comfortable, and then charge one real person this week. What you learn from that single transaction beats weeks of guessing.

At batch0, students set and test a real price during the Build and Market sprints, because a price nobody will pay isn’t really a price. Once you have a number that holds up, the next question is how you reach the people who’ll pay it — start with how to get your first 10 customers.