I’ve launched four products in the last two years. Three of them had the same problem, and it had nothing to do with the code, the marketing, or the feature set. The problem was the price.

With the first product, I charged $9/month because it “felt right.” With the second, I offered a generous free tier because I wanted traction. With the third, I matched a competitor’s pricing without thinking about whether their cost structure had anything to do with mine.

Every single time, the pricing was wrong. And every single time, the fix was the same: charge more.

This is not another generic article about pricing models. This is what I actually learned, what I got wrong, and the framework I use now before putting a number on anything.

Why Indie Hackers Are Terrible at Pricing

Let me be direct. Most developers undercharge, and they do it for reasons that feel logical but are not.

Fear of rejection. You spent weeks building something. The thought of someone seeing the price and bouncing feels personal. So you set it low to reduce friction. The problem is that low prices attract the worst customers. Price-sensitive users churn faster, request more support, and are the first to complain.

Anchoring to your own budget. You are a developer. You probably would not pay $49/month for a tool unless it was incredible. So you price your product at $12 because that is what you would pay. But you are not your customer. A marketing agency that saves three hours per week using your tool will happily pay $49. A freelancer who closes one extra client per month because of your product will pay $99.

Confusing price with value. Price is not about what the product costs you to run. It is about what it is worth to the person using it. If your tool saves someone ten hours per month and they bill at $100/hour, the value is $1,000/month. Charging $29 for that is not generous. It is leaving money on the table.

The competitor trap. You look at what competitors charge and match it. But competitor pricing is often wrong too, especially in indie hacker space where everyone is undercharging for the same psychological reasons. Matching a bad price does not make it a good price.

The Real Cost of Undercharging

Undercharging is not just leaving revenue on the table. It actively damages your business in ways that are not obvious until you are deep in the hole.

You cannot afford to grow. Customer acquisition costs money. Even organic channels like SEO and content marketing take time, which is money when you are a solo founder. If your margin per customer is $8/month, you cannot afford to experiment with paid channels, hire help, or invest in the product.

Support economics break. Every customer needs some level of support. At $9/month, if a customer sends you two emails that take 15 minutes each to handle, the math does not work. At $49/month, those same support interactions are a reasonable cost of doing business.

You attract the wrong users. This is worth repeating because it is the most counterintuitive part. Customers paying $9/month are statistically more likely to churn, more likely to request refunds, and more likely to leave negative reviews than customers paying $49. The reason is not that expensive customers are nicer. It is that paying a meaningful amount forces people to actually use the product and get value from it.

Your motivation suffers. When you are working 40 hours a week on a product making $400/month from 50 customers, the math hits you. You are making $10/hour before expenses. That is not sustainable, and it kills the energy you need to keep shipping.

The Framework I Use Now

After getting pricing wrong multiple times, I developed a simple framework that I run through before setting any price.

Step 1: Identify the Value Metric

A value metric is the unit of measurement that correlates with how much value a customer gets from your product. Good value metrics increase as the customer gets more value.

Examples:

  • For an email tool: subscribers or emails sent
  • For an analytics product: page views or tracked events
  • For a project management tool: team members or projects

The best value metric passes two tests. First, customers intuitively understand why the price goes up as the metric increases. Second, the metric naturally segments customers by how much value they get.

Step 2: Research Willingness to Pay

This is the step most founders skip because it feels awkward. You need to talk to potential customers about money.

The Van Westendorp method is simple and works. Ask four questions:

  • At what price would you consider this product too expensive?
  • At what price would you consider this product a bargain?
  • At what price would you start to think it is too cheap to be good?
  • At what price would it start to get expensive but you would still consider it?

Ask ten people. The overlap between questions two and four is your acceptable price range. The overlap between questions one and three is your optimal price point.

Step 3: Price Higher Than Your Gut Says

Whatever number you arrive at, add 20 to 30 percent. I am serious.

A 1% price increase can yield a 10 to 20 percent improvement in profit without touching conversion rates or churn. Most indie hackers are not 1% off. They are 50 to 200 percent off.

Step 4: Start with One Plan

Do not launch with three tiers. Do not build a complex pricing page with feature matrices and comparison tables. Start with one plan at one price.

One plan also gives you cleaner data. Every customer is on the same plan, so you can see exactly how usage patterns vary and where the natural breakpoints are for future tiers. You are building your pricing strategy on real data instead of guessing.

Step 5: Make the Free Tier Earn Its Keep

If you decide to offer a free plan, it needs to serve a specific strategic purpose. “Getting traction” is not a strategy. It is a hope.

One founder I follow closely killed their free plan entirely and saw revenue increase 60 percent within three months. The free users who converted were already going to convert. The free users who did not were just consuming resources.

If your free tier has 150 free users for every 1 paying user, you are not running a business. You are subsidizing people who will never pay.

Pricing Psychology That Actually Matters

Anchoring works because brains are lazy. The first price a customer sees becomes their reference point. If your highest plan is $299/month, your $79 plan feels reasonable. Without that anchor, $79 feels like a big commitment.

The decoy effect is not manipulative. When you do add tiers, the middle tier should be the one you want most people to buy. The top tier exists partly as an anchor and partly for power users. The bottom tier exists to make the middle tier look like the obvious choice.

Price signals quality. In the SaaS world, a very low price does not signal “great deal.” It signals “this probably is not very good.” Pricing at $29/month signals confidence. The product is worth something. The founder is serious. It will be around next month.

When and How to Raise Prices

If you have been running your product for a while and suspect you are undercharging:

Grandfather existing customers. Give current paying customers their current price for 6 to 12 months, or forever if your margin allows it. This eliminates the biggest source of backlash.

Announce it transparently. Send an email explaining why prices are going up. Be honest. Customers respect honesty.

Test before committing. Raise the price for a percentage of new signups and compare conversion rates. Most founders who do this discover that conversion barely changes, or in some cases actually improves because of the quality signal.

Do it sooner than you think. Every month you spend at the wrong price is revenue you cannot get back.

The Lifetime Deal Trap

I need to talk about lifetime deals because they are everywhere in the indie hacker world, and they are almost always a mistake.

The appeal is obvious. You get a chunk of cash upfront, you get a bunch of users fast. It feels like a shortcut to traction.

The reality is that lifetime deal customers are the hardest customers to serve. They paid once and expect support forever. Your server costs scale with usage but your revenue from these users does not.

If you have a product with meaningful ongoing infrastructure costs, lifetime deals are almost never the right move. If you do one, cap the number of licenses strictly and price it at a minimum of 3x your annual plan.

Real Numbers: What Actually Works

Micro SaaS: $15 to $49/month. Tools that solve one specific problem for one specific audience. These work when the user count is high and support needs are low.

Vertical SaaS: $49 to $149/month. Products targeting a specific industry or profession. Higher prices work because the product is tailored and the customer has fewer alternatives.

B2B tools: $99 to $499/month. Products used by teams or that impact business revenue directly. If your tool helps a company make or save more than $500/month, charging $99 to $499 is reasonable and expected.

The indie hackers who consistently grow revenue have a few things in common. They validate the pain before building. They invest in distribution from day one. And they price based on the value they deliver, not on what feels comfortable.

Stop undercharging. Your business depends on it.

This article was first published at Iron Triangle Digital Base.