# How to Raise Prices Without Losing Customers > How to raise SaaS prices without losing customers: test on new sign-ups first, frame the value, give notice, apply at renewal, and choose a grandfather policy. - Canonical: https://zeroraised.com/blog/how-to-raise-prices-without-losing-customers - Published: 2026-11-07T07:29:28Z - Author: ZeroRaised Team (https://zeroraised.com/blog/authors/zeroraised) - Publisher: ZeroRaised (https://zeroraised.com/) - Section: Revenue - Tags: saas, pricing, revenue, churn To raise prices without losing customers, change the price for new customers first, then roll it out to your existing base with clear notice, a value-based explanation and an effective date at each customer's next renewal. Decide in advance whether current customers keep the old price for a while, and watch conversion, cancellations and support replies for a few weeks after each step. This guide is about rolling out an increase to people who already pay you. If you are still choosing your first price, start with our guide on [how to price a SaaS product](https://zeroraised.com/blog/how-to-price-a-saas-product) instead. ## TL;DR - **Test on new customers first.** New sign-ups see only the new price, so you learn whether it converts without touching anyone's existing bill. - **Frame the increase with shipped value.** Name the features, reliability work and support you have added since customers signed up. - **Give notice.** Our default is at least one full billing cycle, with the old price, new price and effective date in the first paragraph of the email. - **Apply at next renewal.** Stripe says that with proration disabled, "customers are billed the full amount at the new price when the next invoice is generated" ([Stripe](https://docs.stripe.com/billing/subscriptions/prorations)). - **Pick a grandfather policy on purpose.** Permanent, timed (6 to 12 months) or an annual lock-in offer each have trade-offs. - **Measure against your own baseline.** No industry churn figure tells you what is normal for your product. **Disclosure:** ZeroRaised publishes this guide and is a launch site for bootstrapped products. Billing behaviour quoted here comes from Stripe and Paddle documentation checked on 7 Nov 2026. ZeroRaised has no commercial relationship with either company. The rest is our editorial advice, not data. ## Why raising prices is a different job from setting them Setting a first price is a design problem: you pick a value metric, plan structure and number with no existing customers to upset. Raising prices on an existing base is a communication and operations problem. The number matters, but most of the risk sits in how and when customers find out. Customers rarely cancel because a price went up by a sensible amount. They cancel when the increase feels arbitrary, arrives without warning, lands mid-cycle, or comes from a product that has not visibly improved. Every step below exists to remove one of those triggers. Our read: for a bootstrapped SaaS, a well-run increase is one of the cheapest ways to grow revenue. You do not need new customers, new features or a new channel. You need a plan and a calm email. ## Step 1: Test the new price on new customers first Before you touch an existing subscription, change the price on your pricing page and checkout for new sign-ups only. This is the lowest-risk move available, because no current customer's bill changes and you get a clean read on willingness to pay. How to run it: 1. **Create new prices in your billing tool rather than editing old ones.** In Stripe and Paddle, prices are separate objects, so existing subscribers stay on their current price while new checkouts use the new one. 2. **Update the pricing page.** If the page also needs a rewrite, our guide on [how to write a SaaS pricing page](https://zeroraised.com/blog/how-to-write-a-saas-pricing-page) covers plan names, anchors and FAQs. 3. **Run it long enough to see a few cycles of trials or sign-ups.** A small product may need several weeks to see enough checkouts to mean anything. 4. **Compare with your recent baseline.** Look at visitor-to-trial, trial-to-paid and refund requests at the new price against the same numbers from before. If new customers convert at roughly the same rate, you have evidence that the new price is defensible. If conversion drops sharply, you have learned that cheaply, and you can adjust before a single existing customer is affected. If you run a free plan or trial, check that the upgrade path still makes sense at the new price. Our comparison of [freemium vs free trial for solo founders](https://zeroraised.com/blog/freemium-vs-free-trial-for-solo-founders) explains how each model changes who reaches the paywall. ## Step 2: Frame the increase with value you have already shipped The most persuasive reason for a price increase is that the product is worth more than it was when the customer signed up. Make a list before you write anything: - **Features shipped** since the customer's sign-up date, especially ones they use. - **Reliability work**: uptime improvements, faster pages, better backups. - **Support**: faster response times, onboarding help, documentation. - **Cost changes you absorbed**, if they are real and you can say them plainly. Then write the reason in one or two sentences a customer would repeat to their boss. "Since you joined, we have added scheduled exports, team accounts and a status page, and we want to keep investing in the product" is concrete. "Due to rising costs and our commitment to excellence" is not. Our read: if you cannot list meaningful improvements, the increase may still be right (early prices are often too low), but say that honestly. "Our launch price was too low to sustain the product" is more credible than inventing a feature story. ## Step 3: Give clear advance notice Surprise is the fastest way to turn a price increase into churn. Tell customers before the change, and make the key facts impossible to miss. Our defaults: - **Monthly plans:** at least one full billing cycle of notice, so every customer sees one more invoice at the old price. - **Annual plans:** notice well before the renewal date, so the customer has time to budget or ask questions. A reminder close to renewal helps too. - **Check your terms of service and local consumer rules.** Your own terms may promise a notice period, and some jurisdictions set requirements for subscription price changes. If in doubt, ask a lawyer before you send. Every notice should state four facts near the top: the old price, the new price, the effective date, and what the customer needs to do (usually nothing). Do not bury the number three paragraphs down. Customers who have to hunt for it assume you were hiding it. ## Step 4: Apply the new price at the next renewal A customer who has paid for this month should get this month at the price they paid. Apply the increase at their next renewal, not as a mid-cycle charge or a prorated adjustment. Both major billing tools support this: - **Stripe.** To disable prorations, Stripe says to "set the `proration_behavior` parameter to `none`", and that "customers are billed the full amount at the new price when the next invoice is generated" ([Stripe prorations](https://docs.stripe.com/billing/subscriptions/prorations)). For changes that should land on a specific future date, subscription schedules move a subscription between phases: "When a phase starts, Stripe updates the subscription based on the attributes of the next phase" ([Stripe subscription schedules](https://docs.stripe.com/billing/subscriptions/subscription-schedules)). - **Paddle.** You set `proration_billing_mode` when changing a subscription. With `full_next_billing_period`, Paddle says the "prorated amount isn't calculated" and the customer "is billed for the full amount on their next renewal" ([Paddle proration](https://developer.paddle.com/concepts/subscriptions/proration)). Paddle also notes that "you can't make changes to a subscription if the next billing period is within 30 minutes" ([Paddle](https://developer.paddle.com/build/subscriptions/replace-products-prices-upgrade-downgrade)), so do not leave changes to the last minute. Test the change on one internal or test-mode subscription first and check the preview invoice before running it across your base. **Never cancel and re-subscribe customers to move them to a new price.** It can reset billing dates, trigger new trials or welcome emails, lose payment history, and in some setups require the customer to re-enter card details. Update the existing subscription instead. ## Step 5: Choose a grandfather policy before you announce Grandfathering means letting existing customers keep their old price for some period. Decide this before you write the announcement, because it shapes the whole message. | Option | How it works | Good for | Watch out for | |---|---|---|---| | No grandfathering | Everyone moves at their next renewal after notice | Small increases, products with clear new value | Highest short-term cancellation risk | | Timed grandfather | Existing customers keep the old price for a set period, often 6 to 12 months | Most bootstrapped products | Track the end dates and send a second notice | | Annual lock-in offer | Customers can switch to an annual plan at the old price before the change | Improving cash flow while softening the increase | Only offer terms you are happy to honour for a year | | Permanent grandfather | Early customers keep their price for as long as they stay | Rewarding founding customers and small early cohorts | Leaves revenue behind indefinitely, and old prices pile up | Our read: a timed grandfather period or an annual lock-in is the best default for most solo founders. It rewards loyalty, gives customers time to adjust, and still ends with everyone on a sustainable price. If you promised founding customers a locked price when they signed up, keep that promise. ### Segment your messaging Not every customer needs the same email. Consider: - **Highest-value accounts:** a personal note or a short call from the founder, ideally before the bulk email goes out. - **Price-sensitive tiers:** lead with the lock-in or downgrade option so customers see a way to stay. - **Customers on plans you are retiring:** explain which new plan they map to and what changes. ## A sample announcement structure You can adapt this outline for most SaaS price increases. Keep the email short and in plain text if that is how you normally write to customers. 1. **Subject line:** say what it is. "Changes to [Product] pricing from [date]" beats a clever teaser. 2. **First paragraph, the facts:** "From [effective date], the [plan] plan will change from [old price] to [new price] per [month or year]. This applies from your next renewal on or after that date." 3. **Why:** one or two sentences naming the value you have shipped, from Step 2. 4. **What it means for you:** grandfather period, lock-in offer or downgrade option, with dates. 5. **What you need to do:** usually "nothing, your subscription will update automatically", plus a link to manage or cancel billing. 6. **Thanks and a real reply-to:** sign it with your name and invite questions. Reply to every answer yourself. Send it from the same address customers already recognise, and post the same information on your pricing page or changelog so anyone who missed the email can find it. ## Metrics to watch after the change Set up your tracking before the announcement so you have a baseline to compare against. Watch these: 1. **New-customer conversion at the new price.** Visitor-to-trial and trial-to-paid, compared with your pre-change numbers. 2. **Cancellations and downgrades around each effective date.** Look at the weeks after the notice email and after each cohort's renewal, not just the overall monthly rate. 3. **Cancellation reasons.** If "too expensive" suddenly dominates, the amount or the framing missed. Our guide to [reducing SaaS churn](https://zeroraised.com/blog/how-to-reduce-saas-churn) explains how to collect reasons at cancellation. 4. **Support themes.** Count replies that ask about the change, and note which questions repeat. Repeated confusion means the email was unclear. 5. **Revenue per customer and total MRR.** The point of the change is more revenue, so confirm it arrived. How to read the results: a small, temporary bump in cancellations around the change can be normal, because some customers were already marginal. A sustained spike that does not settle after a cycle or two means the story or the amount was wrong. Compare with your own history, not an industry benchmark, because what is normal varies widely between products. ## Common mistakes when raising prices 1. **Raising existing prices before testing on new customers.** You take the biggest risk first, with no evidence the new price converts. 2. **Hiding the number.** If customers have to scroll to find the new price, they assume bad faith. 3. **Charging mid-cycle, or cancelling and re-subscribing to switch prices.** Update the existing subscription so the change lands at renewal. 4. **Vague reasons.** "Rising costs" with no specifics invites scepticism. Name what has improved. 5. **Forgetting grandfather end dates.** If you promise 12 months at the old price, put a reminder in your calendar and send a second notice before it ends. 6. **Raising several things at once.** Changing price, plan structure and limits in one go makes it hard to tell what customers reacted to. Change one variable at a time where you can. 7. **Not replying to replies.** The customers who write back are often the ones you can keep. 8. **Panicking at the first cancellation.** Read the trend over a cycle or two before reversing course. ## Frequently asked questions ### How do you raise prices without losing customers? Test the new price on new customers first, then tell existing customers in advance, explain the increase with value you have already shipped, and apply it at their next renewal. Offering a timed grandfather period or an annual lock-in gives price-sensitive customers a way to stay. ### How much notice should I give before a SaaS price increase? Our read: at least one full billing cycle, so every monthly customer sees one more invoice at the old price before the change. Give annual customers notice well before their renewal date, and check your own terms of service and local consumer rules, which may set a minimum. ### Should I grandfather existing customers on the old price? It depends on your margins and how many early customers you have. Permanent grandfathering is generous but leaves revenue behind for good. A timed grandfather period, often 6 to 12 months, or an offer to lock in the old price on an annual plan, is a common middle path. ### Should a price increase apply immediately or at renewal? At renewal. Customers have already paid for the current period, so a mid-cycle charge feels like a broken promise. Stripe and Paddle both let you change a subscription's price without charging a prorated amount, so the new price arrives on the next invoice. ### What metrics should I watch after raising prices? Track new-customer conversion at the new price, cancellations and downgrades in the weeks around each cohort's effective date, and the themes in support replies. Compare against your normal baseline rather than an industry benchmark. ## Where ZeroRaised fits ZeroRaised is a launch directory for products built without institutional VC or accelerator equity. If you have just repackaged your plans or shipped the features behind your price increase, you can [submit your product](https://zeroraised.com/submit) for free. For more guides on pricing, revenue and growing without investors, [join the ZeroRaised newsletter](https://zeroraised.com/newsletter). ## Sources - [Stripe: Prorations](https://docs.stripe.com/billing/subscriptions/prorations), checked 7 Nov 2026 - [Stripe: Subscription schedules](https://docs.stripe.com/billing/subscriptions/subscription-schedules), checked 7 Nov 2026 - [Paddle: Proration](https://developer.paddle.com/concepts/subscriptions/proration), checked 7 Nov 2026 - [Paddle: Replace products and prices (upgrade or downgrade)](https://developer.paddle.com/build/subscriptions/replace-products-prices-upgrade-downgrade), checked 7 Nov 2026 ## Frequently asked questions ### How do you raise prices without losing customers? Test the new price on new customers first, then tell existing customers in advance, explain the increase with value you have already shipped, and apply it at their next renewal. Offering a timed grandfather period or an annual lock-in gives price-sensitive customers a way to stay. ### How much notice should I give before a SaaS price increase? Our read: at least one full billing cycle, so every monthly customer sees one more invoice at the old price before the change. Give annual customers notice well before their renewal date, and check your own terms of service and local consumer rules, which may set a minimum. ### Should I grandfather existing customers on the old price? It depends on your margins and how many early customers you have. Permanent grandfathering is generous but leaves revenue behind for good. A timed grandfather period, often 6 to 12 months, or an offer to lock in the old price on an annual plan, is a common middle path. ### Should a price increase apply immediately or at renewal? At renewal. Customers have already paid for the current period, so a mid-cycle charge feels like a broken promise. Stripe and Paddle both let you change a subscription's price without charging a prorated amount, so the new price arrives on the next invoice. ### What metrics should I watch after raising prices? Track new-customer conversion at the new price, cancellations and downgrades in the weeks around each cohort's effective date, and the themes in support replies. Compare against your normal baseline rather than an industry benchmark.