Pricing is the most uncomfortable decision you will make as a founder. You can spend months building features, writing copy, perfecting your onboarding flow. But the moment someone asks "how much does it cost?" your stomach drops. You mumble a number. You watch their face. You immediately wonder if you said too much or too little.

Here is the thing most founders do not realize until it is too late: pricing is not a math problem. It is a positioning decision. The number you put on your product tells the market who you are, who you are for, and how seriously you take your own work. Get it wrong and you attract the wrong customers, leave money on the table, or both.

This guide covers what I have learned from watching hundreds of early-stage founders price their products for the first time. Some of them nailed it. Most of them did not, at first. The patterns are clear enough that you can skip the worst mistakes.

Why most founders underprice (and why that kills you)

The default instinct for a first-time founder is to charge too little. The logic feels sound: "If I price low, more people will sign up, and I can raise prices later once I have traction." This reasoning is wrong in almost every case.

Low prices attract low-quality customers. A person who signs up for your $9/month plan because it is the cheapest option in the market will churn the moment someone else undercuts you by a dollar. They are buying on price, not value. They will also demand the most support, leave the harshest reviews when something breaks, and never refer anyone.

Low prices also signal low value. When Superhuman launched their email client at $30/month with zero free tier and a waitlist, people assumed the product had to be exceptional to charge that much. And it was. But the price itself created the perception of quality before anyone even opened the app. If they had launched at $5/month, nobody would have written articles about it. Nobody would have bragged on Twitter about getting off the waitlist.

The deeper issue is fear. You are afraid someone will say "that's too expensive." You are afraid of rejection. So you preemptively lower your price to avoid that conversation. But you need that conversation. The person who tells you "that's too expensive" is giving you information. They are telling you that your value proposition is not clear enough, or that they are not the right customer. Both are useful signals. Cheap prices hide those signals from you.

"I charged $9/month for the first year. I had 200 users and made $1,800/month. Then I raised the price to $49/month. I lost 60% of my users and my revenue went up to $3,900/month. The customers who stayed were better in every way." - Founder on Indie Hackers

The 10x value rule and how to apply it

The most reliable pricing heuristic for B2B SaaS is the 10x rule: your product should cost roughly one-tenth of the value it creates for the customer. If your tool saves a team 10 hours per week, and their average hourly cost is $50, that is $500/week in value, or about $2,000/month. Your price should be somewhere around $200/month.

This is not a formula. It is a sanity check. If you are charging $19/month for a product that saves businesses $2,000/month, you are leaving 99% of the value on the table. That is not generosity. That is a business model that cannot sustain customer support, product development, or your own rent.

The tricky part is quantifying value. For some products, the math is straightforward. If you replace a tool that costs $500/month, your value is at least $500/month plus any additional benefits you provide. For others, the value is harder to pin down. A design tool that makes someone's work 20% faster. A project management app that reduces missed deadlines. You need to put dollar amounts on those outcomes, even if the estimates are rough.

Here is how to do it in practice:

  1. Talk to 10 potential customers and ask: "What do you currently spend (in money, time, or headcount) on solving the problem my product addresses?"
  2. Convert time to dollars using their approximate hourly cost (salary plus overhead, roughly 1.5x their hourly wage).
  3. Take the average across your 10 conversations. Divide by 10. That is your starting price.
  4. If the number feels uncomfortably high, good. Launch there anyway.

Patrick Campbell, who built ProfitWell (acquired by Paddle for $200M), ran pricing studies across thousands of SaaS companies. His data showed that companies who priced based on value grew 2x faster than companies who priced based on competitors, and 4x faster than companies who priced based on cost. The 10x rule is how you operationalize value-based pricing without needing a pricing consultant.

Cost-plus vs. value-based pricing: pick the right model

There are really only two pricing philosophies. Everything else is a variation.

Cost-plus pricing starts with what it costs you to deliver the product and adds a margin. Your servers cost $200/month, your time is worth $100/hour, and you spend 20 hours a month on maintenance, so your cost is $2,200/month. You add a 50% margin and charge $3,300/month. This approach is common in manufacturing and services, and it is almost always wrong for software. Your costs have nothing to do with the value you create, and software costs scale differently than physical goods. Your marginal cost of adding one more customer might be $0.50 in hosting.

Value-based pricing starts with the customer. What outcome does your product create for them? What would they pay for that outcome? What are they currently paying (in dollars, time, or frustration) for the alternative? Your price anchors to that value, not to your AWS bill.

Basecamp is the textbook example of value-based pricing done with conviction. They charge $349/month. Flat rate. Unlimited users. When they made that decision, they were not thinking about their server costs or how much Jira charges per seat. They were thinking about the fact that a single disorganized project at a 50-person company can waste thousands of dollars in duplicated work and missed deadlines. $349/month to prevent that is a rounding error.

The exception: if you are building a product where customers will directly compare your price to a commodity alternative (like cloud storage or basic email), cost-plus thinking matters more because the market has anchored to a specific price range. You will have a hard time charging 10x the going rate for commodity infrastructure. But most SaaS products are not commodities. If yours is, you have a differentiation problem, not a pricing problem.

How to actually pick your first price point

Here is the practical process. You can do this in a weekend.

Step 1: Map your competitive pricing

Go to the websites of the 5 closest alternatives to your product. Write down their pricing tiers. Note which tier is most prominently featured (that is the one most customers choose). Write down the price of that tier. Calculate the average.

This is your baseline. You do not have to match it, but you need to know it exists because your customers will compare you to it whether you like it or not.

Step 2: Run the Van Westendorp survey

Talk to 15-20 potential customers (not friends, not family, actual people who have the problem you solve). Ask them four questions:

  1. At what price would this product be so cheap you would question its quality?
  2. At what price would this product be a great deal?
  3. At what price would this product start to feel expensive but you would still consider it?
  4. At what price would this product be too expensive to consider?

Plot the answers. The "great deal" and "getting expensive" ranges will cluster. Your price should sit in the overlap between those two clusters. This takes about 2 hours of phone calls and tells you more than any amount of desk research.

Step 3: Launch with one plan

Do not build three tiers. Do not create an enterprise plan. Do not add a "contact us" option. Launch with one plan at one price. You can always add complexity later. Right now, you need to learn whether people will pay your price at all. Multiple tiers just dilute that signal.

Linear did this beautifully. When they launched, they had a free plan and a paid plan. That was it. No "Pro" vs. "Business" vs. "Enterprise." One product, two options. The simplicity made the buying decision trivially easy: do you want Linear, or do you not?

PostBuild maps your competitors' pricing and positioning automatically. Paste your URL to see where you fit in the market. Takes 90 seconds. Free.

The "$29/month sweet spot" myth

There is a persistent belief in the indie hacker community that $29/month is the magic price point for SaaS. Low enough that people do not need approval to buy. High enough that you can build a real business. The number gets repeated so often that founders treat it as a default rather than a decision.

The problem: $29/month is only a good price if it maps to the value your product creates. For a solo freelancer buying a time-tracking tool, $29/month might be exactly right. For a company buying software that replaces a $4,000/month contractor, $29/month is absurdly low and actually hurts your credibility.

The math also works against you. At $29/month, you need 345 paying customers to hit $10K MRR. At $99/month, you need 101. At $249/month, you need 40. The number of customers you need to support, onboard, and retain changes the type of company you are building. Supporting 345 customers as a solo founder is a full-time job. Supporting 40 is manageable.

Here is the real framework for choosing a price tier:

Pick the range that matches your value, not the one that feels safest.

Free vs. freemium vs. free trial: when to use each

This decision confuses founders more than the price itself. Let me simplify it.

Free (open source or ad-supported): Only works if you have a separate monetization path. WordPress is free because they monetize through hosting (WordPress.com) and enterprise features. Unless you have a clear second revenue stream, "free" is not a pricing strategy. It is a charity.

Freemium (free plan with paid upgrades): Works when your product has natural viral loops or network effects. Slack gave away their free tier because every free team that adopted Slack became a sales lead for the paid version. Figma offered a free tier because designers who used Figma in one company would bring it to their next company. If your product does not spread from user to user, freemium just gives you a large base of non-paying users who consume support resources and never convert.

Dropbox's freemium model worked because storage is inherently viral (you share files with people who then need Dropbox to access them). Calendly's free tier works because every meeting link is an advertisement for the product. Look at your product honestly. Does using it naturally expose new potential customers to it? If yes, freemium can work. If no, it probably will not.

Free trial (14 days, no credit card required): The right choice for most early-stage SaaS products. It gives people enough time to experience the value without committing. The "no credit card required" part is important at the early stage because you do not have enough brand trust for people to hand over payment details before they have tried the product.

After your first 100 customers, you can test requiring a credit card upfront. This will cut your trial signups by 50-70%, but it will dramatically increase trial-to-paid conversion because only serious buyers enter their card. At the early stage though, you want volume. You want people in the product. You want feedback. Remove every barrier.

Pricing psychology that actually works

There are two psychological principles worth applying to your pricing page. Everything else in the "pricing psychology" genre is either too subtle to matter or too manipulative to use with a straight face.

Anchoring

People evaluate prices relative to the first number they see. If your pricing page shows your most expensive plan first ($299/month), your $99/month plan feels like a deal. If it shows the cheapest plan first ($29/month), your $99/month plan feels expensive.

This is why most SaaS pricing pages show plans from left to right in ascending order but visually highlight the middle or upper-middle plan. The expensive plan on the right anchors the perception of value. The highlighted plan in the middle feels reasonable by comparison.

When you eventually move from a single plan to multiple tiers (after your first 50-100 customers), put the plan you want most people to buy in the center, and put a more expensive plan to its right. The expensive plan does not need to sell well. Its job is to make the center plan look smart.

The decoy effect

The Economist ran a famous pricing experiment. They offered three subscription options: digital only ($59), print only ($125), and print + digital ($125). The print-only option at the same price as print + digital was obviously a bad deal. Nobody chose it. But its presence made print + digital look like an incredible value, and 84% of subscribers chose that option. Without the decoy, only 32% chose print + digital.

You can use this when you add a second or third tier. Create one option that is intentionally less attractive to make the option you want customers to choose look more compelling. This is not deceptive. You are just making the comparison easier for the buyer.

Real pricing examples worth studying

Theory is useful, but let me walk through three companies that made specific, contrarian pricing decisions and how those decisions shaped their businesses.

Basecamp: $349/month, flat rate, unlimited users

Basecamp rejected per-seat pricing entirely. In a world where every project management tool charges per user per month, they charge one flat rate regardless of team size. Jason Fried has written extensively about why: per-seat pricing punishes companies for growing. It creates a tax on collaboration. It means the customer has to think about whether adding one more person to the project is worth the incremental cost.

Flat-rate pricing made Basecamp the obvious choice for growing teams who were tired of watching their project management bill climb every time they hired someone. It also simplified their sales process to a single question: "Do you want Basecamp?" No calculator needed.

The lesson: if per-seat pricing is the default in your category, charging a flat rate is a legitimate differentiation strategy. You will lose on unit economics at very large companies, but you will win on simplicity and attract the mid-market teams who feel nickel-and-dimed by the incumbents.

Superhuman: $30/month with a mandatory onboarding call

Superhuman launched at $30/month for an email client. That is roughly 10x what most people pay for email (which is zero, since Gmail is free). They also required every new user to do a 30-minute onboarding call before they could use the product.

Both decisions were deliberate constraints. The price filtered out casual users who would not fully engage with the product. The onboarding call ensured every user knew how to use the keyboard shortcuts and workflows that made Superhuman feel fast. The result: extremely high retention, passionate word-of-mouth, and a cult following that treated paying $30/month for email as a status signal.

The lesson: a high price plus a high-touch onboarding experience can create a premium perception that drives both retention and referrals. This only works if your product genuinely delivers a premium experience. If it does not, you are just charging people more for a bad time.

Linear: free, then paid, then enterprise

Linear launched their issue tracker as free for small teams. They did not monetize immediately. Instead, they focused entirely on building the fastest, most polished project management tool on the market. Teams adopted it because it was genuinely better than Jira, not because it was cheaper. Once they had strong adoption and clear product-market fit, they introduced paid plans for larger teams and added enterprise features.

The lesson: if you are entering a market with deeply entrenched competitors (like Jira), a free entry point can remove the biggest barrier to adoption. But this strategy requires either venture capital or personal runway, because you are trading revenue today for market share tomorrow. If you are bootstrapping and need revenue to survive, this approach is risky.

How to raise prices without losing customers

You will need to raise your prices. Probably sooner than you think, and probably by more than feels comfortable. Here is the process that minimizes drama.

Grandfather existing customers. When you raise prices, keep your current customers on their existing rate for at least 90 days. This is non-negotiable. These people took a chance on you when you were unproven. Rewarding their trust with an immediate price hike is a fast way to generate churn and bad reviews.

Give notice. Send existing customers an email 60 days before moving them to the new pricing. Explain what you have added since they signed up (new features, better performance, improved support). Frame the increase in terms of value delivered, not costs incurred. "We've added X, Y, and Z since you joined, and we're adjusting our pricing to reflect that" is better than "our costs went up."

Offer an annual plan at the old rate. This is the smoothest move in pricing. When you announce a price increase, offer existing customers the option to lock in their current rate by switching to annual billing. You get cash upfront. They get a discount. Everyone wins.

Expect some churn. That is fine. When you raise prices, you will lose some customers. The customers you lose are almost always the ones who were paying the least and demanding the most. The math usually works in your favor. If you raise prices by 40% and lose 15% of your customers, your revenue still goes up.

The "double your price" experiment

If you have been selling for a few months and you are not sure whether you are underpriced, try this: double your price for the next 30 new signups. Do not change anything else. Same landing page, same product, same onboarding. Just change the number.

Three outcomes are possible:

Jason Lemkin at SaaStr has talked about this extensively. His observation is that most SaaS founders could raise their prices 20-40% with zero impact on conversion rates and they simply never try. The fear of losing customers keeps them at a price they set when they had no confidence in their own product.

"If no one has ever said 'that's too expensive,' you are not charging enough." - A pricing truism that is overused because it is true.

Putting a number on it: what to do this week

Pricing is not something you figure out once and forget about. It is something you revisit every quarter as your product improves, your market shifts, and your understanding of your customer deepens. But you have to start somewhere, and waiting for the "right" price is just another form of procrastination.

Here is your action plan for this week:

  1. Talk to 5 potential customers and ask what they currently spend (in time or money) on the problem you solve. Convert those answers to a monthly dollar figure.
  2. Look up the pricing pages of your 5 closest competitors. Write down the most popular tier for each. Calculate the average.
  3. Set your price at the higher of: one-tenth the average value you create (from step 1) or 20% above the competitor average (from step 2).
  4. Launch with one plan. No tiers, no enterprise option, no "contact us." One price. One product.
  5. After 20 customers, run the double-your-price experiment for the next 30 signups.
  6. After 60 days, look at your data. Adjust. Repeat.

The worst thing you can do is agonize over the perfect price and delay your launch by another month. A slightly wrong price that you fix in 60 days is infinitely better than no price at all. Ship the number. Watch what happens. Adjust.

And if you want to see exactly how your competitors price and position themselves before you set your own number, PostBuild maps the competitive landscape for you in 90 seconds. Paste your URL and see where the gaps are.