Pause vs discount vs downgrade: choosing the right retention offer

Most SaaS cancel flows reach for a discount first. It’s the easiest offer to build, and it feels generous. But a discount only solves one problem, price, and it can create others: lower margin, customers who learn that cancelling gets them a better deal, and saves that quietly fall apart when the discount ends.

There are four common retention offers: a pause, a discount, a downgrade and a call. Each fits a different reason for leaving. This guide covers when to use each, what can go wrong, and how to test whether an offer works.

The four offers at a glance

Offer	Solves	Best for	Main risk	Cost to you
Pause	Temporary lack of need	Seasonal use, project gaps, budget freezes	Pause turns into silent churn	Lost revenue during the pause
Discount	Price	Customers who value the product but feel it costs too much	Discount addiction, margin erosion	The discount amount
Downgrade	Price, over-buying	Customers using a fraction of their plan	Permanent lower revenue	Difference between plans
Call	Confusion, missing features, setup trouble	Higher-value accounts, complex products	Staff time; friction if forced	Team hours

The rule underneath the table: match the offer to the reason. A discount doesn’t help someone who isn’t using the product. A pause doesn’t help someone who found it too expensive. Your cancel flow should ask the reason first and then show the one offer that fits.

Pause

When it fits

A pause is the right offer when the need is real but temporary:

• “I’m not using it enough right now.”
• “Our project ended; the next one starts in a few months.”
• “We’re freezing spend this quarter.”
• Seasonal businesses (tax, events, education).

The appeal for the customer is that nothing is lost: settings, data and history stay, and billing stops. For you, a paused customer is far easier to bring back than a cancelled one, because restarting needs no new decision.

Risks

• Pause as delayed churn. Some customers will pause and never return. Track what share of paused customers resume and stay.
• Endless pauses. Cap the duration (for example one to three months) and the number of pauses per year.
• Surprise charges at resume. Remind customers by email before billing restarts. An unexpected charge after a pause is a classic source of refunds and disputes.

How it works in Stripe

Stripe lets you stop collecting payment on a subscription with pause_collection, choosing what happens to invoices during the pause (keep them as drafts, mark them uncollectible, or void them) and optionally a date to resume (Stripe docs: pause subscriptions). Note that Stripe’s customer portal does not offer a pause option to customers (Stripe support), so a pause offer needs your own flow or a dedicated tool. You also need to decide what “paused” means in your product: read-only access, no access, or full access.

Discount

When it fits

A discount fits when the customer says the price is the problem and they are getting value. Signs that a discount may work:

• They use the product regularly.
• They chose “too expensive” rather than “not using it.”
• They’re on a plan that matches their usage (otherwise, downgrade first).

Risks

• Discount addiction. If every cancellation attempt produces a discount, some customers will learn to cancel every few months to get a lower price. Limit retention discounts to once per customer, or once per year. Stripe’s own retention rules, for instance, restrict retention discount coupons to a single use per customer (Stripe docs).
• Margin. A 30% discount on a customer who would have stayed anyway is pure lost revenue. You only know how many would have stayed with a holdout test (see below).
• The cliff. When a three-month discount ends, the customer faces the original price again, often with the same objection. Measure retention after the discount period, not just at acceptance.
• Fairness. Long-term customers paying full price may notice that leavers pay less. Keep retention discounts modest and time-limited.

Designing a discount offer

• Time-limit it. “40% off your next 3 months” is easier to justify than a permanent discount. In Stripe, coupons can last once, for a set number of months, or forever (Stripe docs: coupons).
• State the full terms. “Then $49/month from March” in the same sentence.
• Pick a number you can afford. Calculate the cost before launching: discount percent times monthly price times months.

Downgrade

When it fits

A downgrade fits when the customer is paying for more than they use:

• Seats they no longer fill.
• Usage limits well above their actual usage.
• Features on a higher tier they never touched.

For these customers, a downgrade is often a better answer than a discount: the price drop is permanent and honest, and the customer stays on a plan that matches their needs, which makes them less likely to leave later.

Risks

• Lower revenue for good. Unlike a discount, a downgrade doesn’t expire. That’s the point, but count it as reduced MRR, not saved MRR.
• Missing features. Make sure the cheaper plan really covers what they use. Show them what they’d lose before they confirm.
• Plan design debt. If many customers downgrade, your pricing may be wrong. Treat a high downgrade rate as a pricing signal.

Showing the right plan

Don’t show a list of all plans. Recommend one plan based on actual usage (“You used 3 of your 10 seats last month; the 5-seat plan is $29/month”) and make it one click.

Call

When it fits

A call fits when the problem is information or effort, and the account is worth the time:

• “It’s missing a feature” (maybe it isn’t, or there’s a workaround).
• “Too hard to set up or use.”
• “Switched to a competitor” (you may learn something, even if you don’t save them).
• High-value or annual accounts.

Risks

• Forced calls are obstruction. Offering a call is fine. Requiring one to cancel is not, and laws such as California’s automatic renewal law restrict this for customers who signed up online. See our click-to-cancel rules overview.
• Team time. Limit call offers to accounts above an MRR threshold, or to reasons where a call can actually help.
• No-shows. Let the cancellation go through or wait, at the customer’s choice; never hold it hostage to a meeting.

Choosing by reason

Cancel reason	First choice	Alternative	Usually avoid
Too expensive	Downgrade if over-buying, else discount	Annual billing if cheaper	Pause
Not using it enough	Pause	Downgrade	Discount
Missing a feature	Call or roadmap info	None	Discount
Too hard to use	Call	Pause while they get help	Discount
Switched to competitor	Call (to learn)	None	Large discount
No longer needed	None	Pause, if it might come back	Any pushy offer
Other	None	Read the free text	Guessing

How to test offers

Retention offers are easy to fool yourself with. An offer that is “accepted” 30% of the time can still lose money if most of those customers would have stayed, or leave a month later. A few rules keep the test honest.

Use a holdout group

Randomly assign a share of customers who start the cancel flow to a group that sees no offer (just the reason question and confirmation). Compare the groups. The difference in retention is what the offer caused. Without a holdout, you are measuring acceptance, not impact.

Measure at 30, 60 and 90 days

Count a customer as saved only if they are still paying at each checkpoint. For discounts, include a checkpoint after the discount ends.

Measure revenue, not just customers

For each group, compare the revenue retained over 90 days (or longer), net of discounts and downgrades. An offer that saves more customers but less revenue may still be right, but you should know.

Test one thing at a time, per reason

Change one offer for one reason at a time. “Pause vs no offer for ‘not using it’” is a clean test. Changing three offers at once tells you nothing about which one mattered.

Wait for enough data

Small cancel flows produce small numbers. If only a few dozen customers per month pick a given reason, a test can take months to tell you anything. Decide on the sample size before you start, and don’t stop the test the first time the numbers look good; early results swing widely. Our guide to predicting churn with your own data covers sample size and confidence in more detail.

Testing checklist

• One reason, one offer change per test.
• Random holdout with no offer.
• Sample size decided in advance.
• Saves measured at 30, 60 and 90 days.
• Revenue measured net of discount.
• Repeat offers limited per customer.
• Results recorded, including tests that failed.

How NoChurn helps

In NoChurn’s cancel flows, each cancel reason maps to one offer: a discount through a Stripe coupon, a pause, a downgrade or a call. A one-click “Cancel now” button stays visible on every step. You can run the flow as a hosted modal or build your own interface on the headless API. Customers who leave anyway get win-back emails at 30, 60 and 90 days, written from their reason. Every feature is on every plan, priced by MRR only (pricing).