How to Price Your SaaS in 2026: The Indie Hacker's No-Nonsense Guide

You have spent weeks building the thing. The code works. The deploy pipeline is green. And now you are staring at a Stripe dashboard trying to decide whether to charge $9/month or $29/month. This decision will determine whether your SaaS becomes a business or stays a side project.

Most indie hackers get pricing wrong. Not slightly wrong -- catastrophically wrong. They underprice out of fear, give away too much for free, and end up with a product that has users but no revenue. Then they burn out and quit. The product was fine. The pricing killed it.

This guide is everything I have learned about SaaS pricing from building products, talking to founders who have exited, and watching hundreds of indie hackers make the same mistakes. No theory. No MBA frameworks. Just what works.

The three pricing models that actually work for indie SaaS

Forget the 47 pricing models you read about on some VC's blog. As an indie hacker, you have three real options:

Flat pricing. One price, one plan, everything included. Basecamp made this famous. It is the simplest to implement, the easiest for customers to understand, and the fastest to get to revenue. If you are launching your first SaaS, start here. $29/month or $49/month, all features, done. You can always add tiers later. Flat pricing eliminates decision paralysis for your customers and lets you focus on building instead of optimizing plan matrices.

Tiered pricing. Two or three plans, differentiated by usage limits, features, or seat count. This is the workhorse model for most SaaS between $10K and $1M ARR. The key is keeping it simple: a starter plan for individuals, a growth plan for small teams, and maybe a pro plan for larger customers. Three plans, max. If you need a fourth plan, you have a positioning problem, not a pricing problem.

Usage-based pricing. Customers pay for what they use. API calls, emails sent, storage consumed, records processed. This works when your costs scale linearly with usage (like infrastructure or API products) and when customers intuitively understand the unit of value. Plausible Analytics charges per pageview. Resend charges per email. The unit maps directly to value delivered. Usage-based pricing is harder to implement -- you need metering, invoicing, and overage handling -- but it aligns incentives perfectly. Customers only pay when they get value.

If you are not sure, start with flat pricing. You can migrate to tiered or usage-based later. Going the other direction -- simplifying from complex to simple -- is much harder because you have to take features away from existing customers.

Why most founders underprice (and why that kills you)

Here is the uncomfortable truth: you are probably charging too little. Almost every indie hacker I talk to is underpricing by 2x to 5x.

The psychology is predictable. You think "nobody will pay $49/month for this, I will charge $9 to get traction." So you get 200 users at $9/month. That is $1,800/month. After Stripe fees, server costs, and support time, you are making less than minimum wage. You cannot afford to hire help. You cannot afford to take a week off. You are trapped.

Meanwhile, the founder charging $49/month with 50 customers is making $2,450/month with a quarter of the support load. They have breathing room. They can invest in the product. They can afford to lose a few customers without panicking.

Low prices attract the worst customers. I mean that literally. Customers paying $9/month send more support tickets, request more features, churn faster, and leave nastier reviews than customers paying $49/month. The $9 customer is price-sensitive by nature -- they chose you because you were cheap, and they will leave the moment something cheaper shows up. The $49 customer chose you because you solve a real problem, and they will stick around as long as you keep solving it.

The math is brutal: to hit $10K MRR at $9/month you need 1,112 paying customers. At $49/month you need 205. At $99/month you need 102. Which of those numbers sounds achievable for a solo founder?

The 10x value rule: charge 10% of the value you create

The most reliable pricing heuristic is simple: figure out how much value your product creates for the customer, then charge about 10% of that.

If your tool saves a freelancer 5 hours per week, and their time is worth $100/hour, you are creating $2,000/month in value. Charging $49/month is a 40:1 return for them. That is a no-brainer purchase. Even $199/month is a 10:1 return -- still easy to justify.

If your tool helps an e-commerce store increase conversions by 2%, and they do $50K/month in revenue, you are creating $1,000/month in value. Charging $99/month gives them a 10:1 return. Charging $29/month is leaving $70 on the table every single month.

The hard part is quantifying value. For time savings, multiply hours saved by an hourly rate. For revenue generation, estimate the uplift. For cost reduction, calculate what they would spend without you. If you cannot articulate the value in dollars, you have a positioning problem -- fix that before you set a price.

Free tier vs freemium vs free trial -- when each works

"Should I have a free plan?" is the most common pricing question I hear. The answer depends on your distribution strategy:

Free trial (7-14 days). Best for most indie SaaS. The customer gets the full product, experiences the value, and then decides whether to pay. No crippled feature set, no usage caps that make the product frustrating. Just a clean time boundary. If your product delivers value within 14 days, a free trial is your best bet. Basecamp does 30 days. Most B2B SaaS does 14. Do not go shorter than 7 -- customers need time to integrate your tool into their workflow.

Freemium (permanently free with limits). Works when you have a product-led growth loop -- free users invite paid users, or free users generate content that drives organic traffic. Notion, Slack, and Figma pull this off because free users create workspaces that colleagues then join (and need paid features for). If your product does not have a natural viral loop, freemium just gives people a reason to never pay. You end up supporting thousands of free users who cost you money and never convert.

No free anything. Underrated. If your target customer is a business with budget, skip the free tier entirely. Charge from day one. A 30-minute demo or a short video walkthrough replaces the free trial for higher-ticket products. This works especially well above $99/month, where the sales cycle already involves some evaluation.

The cardinal rule: whatever you give away for free must create demand for the paid version. If free users can accomplish their core job without upgrading, you have set the free tier too generously. Tighten the limits until free becomes a taste, not a meal.

Pricing psychology that actually moves the needle

Skip the "charm pricing" nonsense about $29 vs $30. That is not what moves conversion rates. These three things do:

Anchoring. Put your most expensive plan first (or at least second). When someone sees the $199/month plan first, the $49/month plan feels like a deal. When they see the $19/month plan first, the $49/month plan feels expensive. Same product, same price, completely different perception. On your pricing page, lead with the premium option.

Decoy pricing. Three plans where the middle one is the obvious choice. Your starter plan at $19/month has basic features. Your growth plan at $49/month has everything most people need. Your pro plan at $99/month adds white-labeling and priority support that most customers do not need yet. The pro plan exists not to sell itself -- it exists to make the growth plan look like the smart choice. 60-70% of customers should land on your middle tier. If they do not, adjust your feature allocation until they do.

Annual discounts. Offer 2 months free on annual plans (effectively 17% off). This is not about the discount -- it is about cash flow and retention. Annual customers churn at 3-5x lower rates than monthly customers because they have committed. And that upfront annual payment gives you runway to invest in the product. Display the annual price as a monthly equivalent ("$41/month, billed annually") so it still feels comparable to the monthly option. Most pricing pages should default to showing annual pricing with a toggle to monthly.

How to find willingness-to-pay: the Mom Test for pricing

You cannot figure out pricing in a spreadsheet. You have to talk to customers. But most founders ask the wrong questions.

Do not ask "would you pay $X for this?" People say yes to be polite. They say yes because hypothetical money is not real money. Instead, use the Van Westendorp framework -- four questions that bracket willingness-to-pay:

• "At what price would this be so cheap you would question its quality?" This gives you a price floor. Below this, customers assume you are not serious or not sustainable.
• "At what price is this a great deal?" This is where most of your conversions will happen. The sweet spot.
• "At what price does this start to feel expensive but you would still consider it?" This is your price ceiling for most customers -- and your target for your mid-tier plan.
• "At what price is this too expensive, no matter how good it is?" This caps your premium tier. Above this, you lose the deal entirely.

Ask 15-20 people in your target market. Plot the answers. The overlap between "great deal" and "getting expensive" is your optimal price range. This works. It is not perfect -- nothing is -- but it is infinitely better than guessing.

An even simpler approach: launch at a price that feels slightly uncomfortable. If nobody complains, raise it. If 20% of prospects balk at the price, you are in the right range. If nobody balks, you are too cheap. You want some people to say "that is more than I expected" -- that means you are capturing real value.

When to raise prices (and how to grandfather existing customers)

Raise prices when you have evidence that you should. That evidence looks like:

• Your close rate is above 40% -- you are leaving money on the table.
• Customers tell you the product is "a steal" or "ridiculously underpriced." Take the compliment, then raise your prices.
• You have added significant features since launch and have not adjusted pricing.
• Your churn rate is below 3% monthly -- customers are sticking, which means the value justifies a higher price.
• You are drowning in support and cannot afford to hire help at your current revenue per customer.

How to do it without torching customer goodwill: grandfather existing customers on their current plan for 6-12 months. Email them: "We are raising prices on [date]. Your plan stays the same until [date]. After that, the new pricing applies." Give them enough notice and frame it around the value you have added since they signed up. Most will accept it. The ones who leave were never going to be long-term customers anyway.

A more aggressive approach that also works: grandfather existing customers permanently on their current price, but only for their current plan. If they want to upgrade, they pay the new rates. This rewards loyalty while still capturing the value of new features.

B2B vs B2C: different games, different prices

This is the single biggest factor in your pricing strategy, and most founders do not think about it enough.

B2C (selling to individuals): Price sensitivity is high. Customers pay from their own pocket. $5-$29/month is the sweet spot for most consumer SaaS. Churn is high (5-10% monthly is normal). You need volume. Marketing is everything. If you are going B2C as a solo founder, you need a product that practically sells itself through word-of-mouth or content marketing, because you cannot afford paid acquisition at these price points.

B2B (selling to businesses): Price sensitivity is lower because the buyer is spending company money, not their own. $29-$299/month for SMB, $500-$5000/month for mid-market. Churn is lower (2-5% monthly). You need fewer customers but more trust -- case studies, security pages, compliance docs. The sales cycle is longer but the lifetime value justifies it.

The hybrid trap: Do not try to be both. Pricing that works for individuals does not work for teams, and vice versa. If you price at $9/month to attract individuals, businesses will not take you seriously. If you price at $99/month for businesses, individuals bounce immediately. Pick one audience and price for them. You can add the other audience later with a separate plan structure, but do not try to serve both from day one.

The most reliable path for indie hackers: B2B SMB (small and medium businesses). High enough prices to build a real business, short enough sales cycles that you do not need a sales team, and large enough market that you can find customers through content marketing and communities.

The pricing page that converts

Your pricing page is the highest-leverage page on your site. More important than your homepage. Here is what works:

• Show prices. Hiding prices behind "contact sales" kills conversion for anything under $500/month. If you are afraid to show your prices, you do not trust your value prop. Fix the value prop, not the pricing page.
• Default to annual billing. Show the annual price (as a monthly equivalent) by default, with a toggle to monthly. Anchoring on the lower annual number increases conversions and annual plan adoption.
• Highlight one plan. Your recommended plan should have a visual distinction -- a border, a "Most Popular" badge, a slightly different background. Guide the decision. Do not leave customers to figure it out themselves.
• Keep the feature comparison short. Five to eight differentiating features, max. Long feature matrices create decision fatigue. If a feature is in all plans, do not list it -- it is not helping anyone decide.
• Include social proof near the CTA. Logos, testimonial quotes, or a simple "Trusted by 500+ teams" line next to the pricing cards. Social proof at the point of purchase decision reduces friction.
• Answer objections below the fold. A short FAQ covering refund policy, plan changes, data portability, and security. These are the questions that stop people from clicking "Subscribe."

What to hide: do not list every single feature in a comparison matrix that spans three screens. Do not show more than three plans (four absolute max if you need an enterprise tier). Do not put asterisks and footnotes everywhere -- it signals that the real price is not the one shown.

Real numbers from indie SaaS founders

Theory is nice. Here is what actually happened when founders changed their pricing:

The 3x price increase. A developer tools SaaS raised from $19/month to $59/month. They expected to lose 40% of customers. They lost 12%. Revenue nearly tripled overnight. The customers who left were the ones filing the most support tickets. Support load dropped. Profit margin increased. The founder went from working 60-hour weeks to 35.

The freemium removal. A project management tool killed their free tier entirely. Signups dropped 80%. Revenue increased 35%. The free users had been consuming 60% of server resources while generating zero revenue. After removing the free tier, the product got faster for paying customers, support response times improved, and word-of-mouth actually increased because the paying customers were happier.

The annual-only pivot. An analytics SaaS switched from monthly billing to annual-only (with a monthly option hidden behind a support request). Churn dropped from 8% to 2% monthly. Cash collection upfront let the founder hire a part-time developer. MRR doubled in six months because they could actually invest in the product instead of constantly firefighting churn.

The per-seat pivot. A team collaboration tool switched from flat $49/month to $12/user/month. Average revenue per account went from $49 to $84 as teams grew. The pricing scaled with the value delivered -- bigger teams got more value, so they paid more. Expansion revenue became the primary growth driver, with zero additional acquisition cost.

How your tech stack affects pricing flexibility

Your ability to experiment with pricing is constrained by your billing infrastructure. If changing from flat to tiered pricing requires two weeks of development, you will not experiment. And if you do not experiment, you will never find the optimal price.

Here is what you need from your stack:

• Stripe or Paddle/LemonSqueezy as your billing provider. Stripe gives you maximum flexibility: flat, tiered, per-seat, usage-based, and hybrid billing are all supported through the API. Paddle and LemonSqueezy handle tax compliance for you (merchant of record) but are more opinionated about billing models. If you are selling globally and do not want to deal with VAT/GST yourself, merchant of record is worth the higher fees.
• Webhook-driven subscription lifecycle. Your app should react to billing events (subscription created, updated, canceled, payment failed) via webhooks, not polling. This decouples your billing logic from your user-facing code and makes plan changes atomic and reliable.
• Feature flags tied to plans. Do not hardcode plan checks with if user.plan == "pro" scattered across your codebase. Use a feature matrix that maps plans to capabilities. When you change what is in each plan -- and you will -- you update one configuration instead of grepping through controllers.
• Usage metering (if needed). For usage-based pricing, you need reliable event tracking and aggregation. Stripe has built-in metering, or you can roll your own with a counter table and a periodic sync job. The key is accuracy -- billing disputes over miscounted API calls will destroy trust.

Rails makes this straightforward. A Subscription model with plan, status, and billing period. A Plan model (or YAML config) defining features per tier. A webhook endpoint that updates subscription state. And Stripe Checkout for the actual payment flow -- do not build your own credit card form.

# A simple plan-feature matrix
# config/plans.yml
starter:
  price_monthly: 2900  # cents
  price_annual: 29000
  features:
    - projects: 5
    - team_members: 1
    - api_access: false
    - priority_support: false

growth:
  price_monthly: 7900
  price_annual: 79000
  features:
    - projects: 25
    - team_members: 10
    - api_access: true
    - priority_support: false

pro:
  price_monthly: 14900
  price_annual: 149000
  features:
    - projects: unlimited
    - team_members: unlimited
    - api_access: true
    - priority_support: true

The point is not the specific implementation -- it is that your billing infrastructure should let you change pricing in a day, not a sprint. If it takes you two weeks to test a new price point, you will never iterate fast enough. The founders who win at pricing are the ones who can run experiments quickly: test a higher price for new signups, offer a limited-time annual discount, add a usage-based add-on, or create a seasonal promotion -- all without rewriting billing logic.

The pricing mistakes that kill indie SaaS

Avoid these, and you are already ahead of 80% of founders:

• Pricing based on costs instead of value. "My server costs $20/month so I will charge $29/month." Your costs are irrelevant to the customer. They care about the value you deliver. A $20/month server that saves someone 10 hours a week is worth $200/month. Price on value, not costs.
• Too many plans. Five tiers with 30 features in a comparison matrix. The customer is paralyzed. They leave. Three plans. Clear differentiation. Done.
• Lifetime deals. Selling a $49/month SaaS for a one-time $199 payment. You get a cash bump and then spend the next five years supporting customers who will never pay again. LTDs attract the most price-sensitive, highest-maintenance customers. If you must do a lifetime deal, price it at 3-5x annual (not 4 months of monthly pricing) and cap the number sold.
• Discounting to close. A prospect asks for a discount. You give 20% off. Now you have set a precedent. Every future prospect who talks to that customer will expect the same discount. Instead of discounting, offer more value: extend the trial, add a setup call, throw in an extra month. Keep the price intact.
• Not raising prices for years. Your product is 10x better than when you launched. Your costs have gone up. Your competitors charge more. But your price is the same as 2024. Raise it. Your existing customers already know the value. New customers have never seen the old price. There is literally no downside except the fear in your head.

The bottom line

Pricing is not a math problem. It is a confidence problem. You are not afraid of the spreadsheet -- you are afraid that people will say no. So you set the price low enough that nobody could possibly object, and then you wonder why you are broke.

Here is the playbook: start with flat pricing at a number that makes you slightly uncomfortable. Talk to 15 potential customers using the Van Westendorp questions. Adjust based on data, not fear. Default to annual billing. Do not offer a free tier unless you have a viral loop. Raise prices every time you add significant value. Grandfather existing customers. And for the love of your sanity, stop comparing your price to competitors -- compare it to the value you create.

The difference between a $2K MRR side project and a $20K MRR business is rarely the product. It is almost always the pricing. Get this right and everything else gets easier -- hiring, marketing, product investment, and eventually, your exit.