Est. 2001 · Relaunched 2026 Independent & reader-supported

Modern Business Daily

Tools, tactics and straight answers for solopreneurs, AI builders and small teams.

Build & Launch

How to Price a One-Person SaaS (Without Underselling It)

Solo founders price like they're apologising. Here's a saner way to pick a number, structure your tiers, and raise prices without losing sleep — or customers.

By Daniel Mercer · July 2026 · 8 min read

Here's the arithmetic nobody runs before launching at $9 a month: to pay yourself a modest $60k salary at $9/month, you need roughly 700 customers after churn and fees. At $29, you need about 200. At $79 — a normal price for B2B software that solves a real problem — you need about 70. Same product, wildly different businesses. Pricing isn't a detail; for a company of one, it's the business model.

Why solo founders underprice

Three reasons, all psychological, none good: you know the product's flaws intimately, so it feels unfinished; you compare against consumer app prices instead of the value delivered; and a low price feels like armour against rejection. But your customer isn't buying your code — they're buying the spreadsheet they no longer maintain, the hours they get back, the client they don't lose. Price against that.

Picking your first number

  1. Find the value anchor. What does the problem cost your customer per month — in hours, mistakes or missed revenue? Charging 10–20% of the value you create is a defensible starting zone.
  2. Check the category ceiling. What do the incumbents charge? Pricing at 40–70% of the established player is credible; pricing at 10% signals "hobby project" and actually hurts trust with business buyers.
  3. Apply the wince test. Take the number that feels comfortable and raise it until it feels slightly uncomfortable. That discomfort is almost always you, not the market — every founder who's raised prices reports the same anticlimax: nobody noticed.

Structure: keep it boring

Two or three tiers, named for who they're for (Solo / Team / Business), differentiated by an axis that naturally grows with the customer — seats, projects, volume. One decision per tier. Skip the five-column comparison grid with 40 feature rows; complexity at the pricing page is where conversions go to die.

  • Annual plans from day one at roughly two months free. Solo businesses live and die on cash flow, and annual prepays are oxygen.
  • Free trial over free tier, as the default. A free tier is a support burden that mostly attracts people who will never pay; a 14-day trial attracts people with the problem. (Free tiers make sense later, as marketing — not at launch, as validation avoidance.)
  • Merchant of record (Paddle, Lemon Squeezy) unless you enjoy global sales tax paperwork. The extra percentage is the best admin-avoidance money you'll spend.

The launch-phase moves

Early-adopter pricing beats launch discounts. "Founding customer: $19/month, locked forever, price goes to $29 at v1.0" rewards the risk-takers, creates honest urgency, and lets you raise prices on a schedule you announced rather than one you have to justify later.

Grandfather generously. When you raise prices — and you should, roughly annually — let existing customers keep their rate for a long time or forever. It costs you little (they're already paying), and it converts your earliest users into your loudest advocates.

When to raise prices

The signals are unambiguous: nobody has complained about price in months; trial conversion is high; customers say some version of "this is a steal"; support load per customer is falling. Any two of those, raise 20–40% for new customers and watch what happens. The most common outcome, reported with almost suspicious consistency across the indie SaaS world: revenue up, support load down, customer quality up.

Cheap isn't kind, and it isn't humble. It's just a slower way to run out of runway.

Pricing is step five of our prototype-to-paying-customers checklist — the rest of the list is worth a read before launch day.

Frequently asked questions

How much should I charge for a one-person SaaS?

Anchor to the value of the problem solved (10–20% of what it saves the customer monthly is defensible), sanity-check against category incumbents (40–70% of their price is credible; 10% signals hobby project), then raise the number until it feels slightly uncomfortable. For B2B tools, that lands most solo products in the $19–79/month range — far above the apologetic $9 default.

Should my SaaS have a free tier or a free trial?

At launch, a 14-day trial: it attracts people who actually have the problem and forces a real purchase decision. A free tier is a support burden that mostly collects users who will never pay — it makes sense later as a deliberate marketing channel, not at launch as validation avoidance.

How do I raise SaaS prices without losing customers?

Raise for new customers only and grandfather existing ones generously — it costs little and converts early users into advocates. Announce increases ahead of time as founding-customer urgency ("$19 locked forever until v1.0"), and expect the standard indie result: revenue up, complaints near zero.