How to raise SaaS prices without losing customers

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

Raise prices for new customers first, on a set date, then decide separately whether and how to bring existing customers along. Almost every solo founder waits too long because the first price was a guess made before anyone had paid anything, and guesses made under launch-day fear are almost always low. The mechanics that keep customers: never silently re-bill someone, either grandfather existing customers or give them long, clear notice, and treat the raise as a value question, not just a revenue one.

Why your first price was almost certainly too low

You set your launch price before a single customer had paid, which means it was based on fear of getting zero customers, not evidence about what the product was worth. That's a reasonable place to start and a bad place to stay. Once you have real conversion data, the original number stops being a pricing decision and becomes an anchor you're stuck to for no reason. How to price a micro-SaaS covers the initial-pricing problem in depth; this guide picks up once you already have paying customers and are wondering whether that number still holds.

The signals it's time to raise

Watch for these together, not as single data points:

• Near-zero pushback on price in trials, sales conversations, or support threads.
• High conversion at the current price — trial-to-paid running comfortably above what you'd expect for the category, meaning price isn't the bottleneck.
• Customers say it's cheap, unprompted. "This should cost more" is one of the most reliable signals in SaaS, and founders often dismiss it as flattery rather than data.
• You've shipped real value since launch — integrations, support, features that didn't exist when you set the price.
• Competitors have moved and you haven't, which is a reason to check your assumptions, not to copy their number.

None of these alone means raise now. A few of them holding for a few months means the price is stale.

The safe mechanics: new customers first

The lowest-risk move, and the one most often skipped, is changing the price for new signups only while leaving every existing subscriber exactly where they are. This isolates the read: you find out whether the new price still converts without any churn risk contaminating the result, and you never put an existing customer in the position of explaining an unexpected charge.

Concretely: update the pricing page and checkout, keep existing subscriptions on their current plan or price ID, and let both cohorts run for at least one full billing cycle — ideally two or three — before deciding anything about existing customers.

Grandfathering early customers indefinitely, as thanks for taking a risk on you, is a completely legitimate permanent policy and the option that generates the least backlash. Moving everyone to the new price eventually is a separate decision, made later with a plan, not the same day you flip the marketing page.

If you do change price for existing customers, do it honestly

Sometimes grandfathering forever isn't sustainable — support costs rise, or the gap between old and new pricing gets wide enough that new customers are effectively subsidizing legacy ones. If you go this route:

• Give real notice, measured in weeks, not days, before the new price takes effect on their account.
• Say why, plainly — "we've added X, Y, Z" or "our costs have changed" is honest; vague language like "to continue providing quality service" reads as evasive because it is.
• Give them an out — a clear path to cancel, downgrade, or lock in the old price for a period before the change lands.
• Keep the email short: what's changing, why, when, and how to reach you.

A silent re-bill is the fastest way to turn a loyal customer into a chargeback and a public complaint. Treat any legacy cohort you do raise on as something to actively watch afterward, covered below.

Value-based increases beat blanket ones

A price increase lands better when it's visibly tied to something, not just a number that moved. "We added the integration you asked for, and the price reflects that" is a different conversation than "prices are going up." If you've shipped real improvements since launch, line the increase up with a release or a new capability, and say so. This also gives you a cleaner test: does the new price hold up in trial-to-paid conversion once the added value is visible on the pricing page, versus only working at the old number?

Packaging instead of raising

Sometimes the real signal isn't "the price is too low," it's "some customers would pay more for more, while others would leave if the base moved." The lower-risk answer is to leave the entry tier alone and add a higher one — more usage, more seats, priority support, whatever your heaviest users already ask for. This captures upside from your best customers without touching anyone who's price-sensitive at the bottom. As covered in how to grow from 100 to 500 MRR, a lot of the next revenue chunk in an indie SaaS comes from giving engaged customers a ceiling worth paying for, not from raising the floor.

Testing per product across a portfolio

If you run more than one product, don't apply the same move everywhere at once. Products differ in audience, maturity, and price sensitivity — a raise a mature, high-retention product absorbs easily might sink conversion on one still finding its audience. Change one product's new-customer price, hold the others as a rough baseline, and give it a real read — several weeks of signups, minimum — before rolling the same move elsewhere. Running several products means you can learn faster than a single-product founder, as long as you don't mistake "it worked once" for "it works everywhere."

What to measure

Watch two numbers specifically, for both cohorts, rather than guessing at the outcome:

• Conversion at the new price — trial-to-paid, and visitor-to-trial if you track it, compared to the rate before the change. A meaningful drop is your answer, regardless of what you expected.
• Churn in the affected cohort — if you applied a change to existing customers, track their cancellation rate for the following billing cycles, separately from baseline churn. A spike specific to that cohort points at the communication or the size of the increase, not the whole business — the same discipline covered in how to reduce SaaS churn, since a price change is one of the most common deliberate churn events you'll ever run.

If you're already tracking revenue, conversion, and churn across several products, spotting this kind of before/after cohort shift is faster from one view than digging through each product's own dashboard — that's the comparison the metrics view in SoleOS is built for. This guide is published by SoleOS, portfolio intelligence for solo founders running multiple products. To be direct about when you don't need it: if you run one product and already check Stripe's dashboard weekly, a spreadsheet comparing two cohorts for a few weeks does the job just fine.

Frequently asked questions

How much should I raise prices by?

There's no universal number, and anyone giving you one is guessing on your behalf. Measure instead: if trial-to-paid conversion at a new price holds steady across several weeks of signups, you have room; if it drops noticeably, you've found the ceiling for now. Small, testable increases beat one large speculative jump because they're easier to read and easier to reverse.

Should I ever silently raise prices on existing customers?

No. Even where your terms technically allow it, billing someone more than they agreed to without clear advance notice generates chargebacks, cancellations, and public complaints that cost more in trust than the increase gains in revenue. Grandfather existing customers, or tell them clearly and early — there's no safe silent version of this.

How long should I wait before judging a price change?

Long enough to see a full cohort of new signups convert or not — usually several weeks at minimum, a full billing cycle or two if you're also watching churn on an affected existing cohort. Judging a change after a handful of signups is judging noise, not signal.

What if existing customers push back hard on an increase?

Pushback from customers you gave real notice to is normal and worth handling case by case — offering a legacy rate to a few vocal long-time customers costs little and preserves goodwill. Pushback from new visitors at the new price is a different signal: it's telling you the number itself, not the notice period, is the problem, and it belongs in your conversion metric, not just your inbox.

Is a price increase a substitute for fixing high churn?

No, and it can make an existing churn problem worse if the product hasn't actually improved. A price increase without added value is a bet that customers won't notice or won't bother to leave; that bet sometimes pays off short term and sometimes accelerates churn you already had. Fix retention first, or at least in parallel, rather than using price as a patch for a product problem.