Every founder hits this wall. You have a product that works. You have users who seem to like it. And then someone asks: "So what does it cost?"
And you freeze.
Pricing is the question most founders are least prepared for. Not because it is complicated, but because it feels like a test you cannot study for. You pick a number and hope it is right. Usually, it is not.
Here is what I have learned from working through this: the problem is not that you do not know the answer. The problem is that you are asking the wrong question first.
The three ways founders get pricing wrong
The most common approach I see is the competitor copy. You find two or three similar products, average their pricing tiers, and land somewhere in that range. The logic feels safe. If someone else is charging $49 a month, that must mean the market will accept $49 a month.
The problem is you are not them. Your costs are different, your customer base is different, and your product delivers different value. You end up anchoring your revenue ceiling to someone else's business model instead of your own.
The second mistake is cost-plus pricing. You add up your infrastructure costs, your time, your overhead, and you tack on a margin. This works fine in manufacturing. In SaaS, where your marginal cost per additional customer is nearly zero, it produces prices so low they signal poor quality instead of good value.
The third mistake is the round number guess. You pick $19 or $99 or $299 because it feels like what software costs. There is no logic behind it. It is just a number that sounds like a price.
All three of these approaches share the same flaw: they start with your costs or your competition instead of starting with your customer.
Start with willingness to pay
The right question is not "what should I charge?" The right question is: what would a customer pay to get the outcome my product delivers?
That question shifts you from guessing to researching. And the research is simpler than most founders expect.
Pick five to ten customers or prospects you can talk to. Do not send a survey. Get them on the phone. Ask them one direct question: "If you had to pay to keep using this, what would feel like a fair monthly price?"
Then listen. Do not anchor them first. Do not give ranges. Just wait for a number.
You will hear things like: "I don't know, maybe thirty dollars?" or "Honestly, if it saved me two hours a week, I'd pay a hundred." Those answers tell you far more than any competitor analysis. The closer you are to the moment of value, the more honest the number becomes.
If you do not have existing users yet, ask prospects. Walk them through the product, show them the outcome it produces, and ask what they would pay for that outcome. Do this before you build a pricing page. Do this before you set anything public.
The 10x ROI rule
Here is a framework that cuts through the noise. If your product saves someone time or generates revenue for them, calculate the value of that outcome and price at roughly one-tenth of it.
If your product saves a sales manager three hours a week and their fully loaded hourly cost is $80, you are saving them roughly $960 a month in labor. A price of $100 a month delivers a 10x return on their investment. That is easy to justify in any budget conversation. You do not have to sell them on value — the math does it for you.
This does not mean you can always capture that full tenth. Market dynamics, competition, and buyer psychology all play a role. But the 10x rule gives you a logical floor. If you are pricing below what a customer can clearly justify in ROI terms, you are almost certainly leaving money on the table — and sending a signal that your product is not confident in its own value.
Run a simple pricing experiment before you set anything in stone
Most founders treat their first price as permanent. It is not. Treat it as a hypothesis.
Set a price based on your willingness-to-pay research. Put it in front of twenty real prospects over the next four weeks. Watch what happens.
If nobody pushes back on price, you are too cheap. Raise it by 30 to 50 percent and run another batch.
If price is the first thing people raise as an objection, you either have a value communication problem or a genuine pricing problem. Before you lower the number, check whether you are explaining the outcome clearly enough. Most early-stage pricing objections are actually positioning objections in disguise.
If about one in five prospects raises price as a concern but most of them still convert, you are probably close to the right zone. Some resistance is a good sign. Zero resistance is a bad one.
What to do once you have a number
Lock in a starting price and commit to it for at least 60 days. Enough time to see a pattern, not so long that a bad number does serious damage. Change it with evidence, not anxiety.
Raise your price before you feel ready. Most founders wait until they have more customers, more features, more confidence. But your best moment to raise prices is when you have growing demand and a product that genuinely delivers results. That is now, or close to it. Waiting for permission from the market is how founders undercharge for years.
And do not overthink the tiers. Start with one or two options. A single paid tier is fine. Complexity in pricing comes later, when you understand which customer segments value different things and are willing to pay differently for them. At the start, your only job is to find a price that the market accepts and that covers your growth. Everything else is iteration.
Pricing is a dial, not a destination. The founders who get it right are not the ones who guessed perfectly on day one. They are the ones who treated pricing as a conversation with their market — and kept adjusting the signal until the market answered clearly.