Indie Dev Workflow

A Support Workflow for Raising Prices on Existing Customers

A practical support workflow for raising prices on existing customers: decide the scope, check billing and legal rules, prepare replies, send clear notice, sort responses and follow up.

SupportMe••12 min read

If you're raising prices on existing customers, plan the support work before you send the announcement. Decide exactly who is affected and when. Check the notice rules that apply to your billing platform and your customers' locations. Write your answers and your exception rules ahead of time. Send one clear notice with a real effective date. Then sort the replies into a few categories so you can answer them consistently.

The rest of this guide goes through each step for solo developers and small SaaS teams who answer their own support inbox. It covers what Stripe, the App Store and Google Play actually do when you change a price. It also points to the consumer-protection rules you may need to check. This is not legal advice, so for contracts and consumer law, read the source rules or ask a lawyer.

Step 1: Decide the scope before you write anything

Most support confusion during a price change comes from decisions nobody made in advance. Write down answers to these questions before you draft the announcement:

  • Who is affected? All existing customers, only some plans, or only monthly subscribers?
  • Are any customers grandfathered? Will some keep the old price for good, for a set time, or not at all?
  • When does it take effect? Pick a calendar date or "your next renewal after X date". For annual customers, say which renewal.
  • What do customers get for the higher price? If nothing changes, say so plainly. Don't make up a reason.
  • What are the alternatives? A cheaper plan, switching to annual billing, or cancelling.
  • What exceptions will you allow? Write rules like "nonprofits keep the old price for 12 months" or "no individual discounts" now, so you don't have to decide case by case later.

That last list matters most for support. Without written exception rules, you'll end up negotiating ticket by ticket. Customers who push hardest get better deals, and customers who compare notes later will notice.

Step 2: Check what your billing platform does

Your billing platform decides how much control you have. That affects what you can promise in the announcement.

Stripe and other direct billing

Stripe lets you change the price on existing subscriptions by updating the subscription item to a new price, without cancelling and recreating it. By default, changing a price can create prorations. That means a mid-cycle charge or credit for the rest of the billing period. Stripe's docs explain how to preview prorations or turn them off.

The support takeaway: if your announcement says "starting at your next renewal", make sure the billing change really happens at renewal. A surprise prorated charge mid-cycle will create tickets that a well-written email can't prevent.

Apple App Store

If you sell subscriptions through the App Store, Apple's subscription pricing documentation gives you two choices when you schedule an increase:

  • Keep the current price for existing subscribers. This is grandfathering. People who subscribed before the change keep their price.
  • Apply the increase to existing subscribers. Apple then either asks subscribers for consent or just notifies them.

According to that page, subscribers must consent if any of these is true:

  • They live in a region that requires consent for any price change.
  • The increase is more than 50% of the current price and more than about US$5 per period (or US$50 per year for annual plans).
  • They already had a price increase on that subscription in the past 12 months.

If a subscriber who needs to consent doesn't agree, the subscription expires at the end of the current billing cycle. Apple also says that once an increase takes effect, you can't reverse it. For increases that only need notice, Apple emails subscribers 27 days before renewal and also shows in-app and push messages.

Google Play

Google's price change documentation says price increases for existing subscribers are opt-in by default. Subscribers have to accept the new price or their subscription won't renew. The higher price is charged after a 37-day notice period. You get seven days after starting the increase to notify subscribers yourself before Google Play starts notifying them. Opt-out increases are only available in some locations, with limits on how much and how often you can raise prices. You can also keep existing subscribers on the old price and raise it only for new subscribers.

The support takeaway for both app stores: an opt-in or consent flow means some loyal customers will lose their subscription simply because they ignored a notification. Expect "why did my subscription stop?" tickets weeks after the announcement, and prepare an answer for them.

Step 3: Check the notice rules that apply to you

Notice rules depend on where your customers are, whether they are consumers or businesses, and what your terms say. Here are two documented examples:

  • California (consumer auto-renewal plans): Under AB 2863, a business that changes the fee on an existing automatic renewal plan must send a clear notice of the change and cancellation information. The notice must go out no less than 7 days and no more than 30 days before the change takes effect (Wilson Sonsini summary; bill text). Law-firm summaries say the amendments apply to contracts entered into, amended or extended on or after July 1, 2025.
  • United Kingdom (consumer subscriptions): The DMCC Act subscription contracts regime will require key pre-contract information, including whether later payments may be higher, plus renewal reminders. As of October 2026, the draft regulations have been laid before Parliament with a planned start date of 1 January 2027, subject to approval (Wiggin DMCC tracker; Latham & Watkins).

For B2B SaaS, your own terms of service or signed contracts usually set the notice period and whether you can change prices during a contract term. Read them before you pick a date. If a customer has a signed annual contract at a fixed price, the price increase may only apply at renewal.

A practical default (my recommendation, not a legal rule): give at least one full billing cycle of notice. For annual customers, give notice well before renewal. Make sure the date you pick fits every legal window that applies to you.

Step 4: Prepare support before the announcement

Do this work in the days before you send the email, not after the replies arrive.

Write an internal FAQ. Keep it short and factual:

  • Old price, new price, and the effective date for each plan
  • Who is grandfathered, and for how long
  • What changed in the product, if anything
  • How to downgrade, switch billing period or cancel, with exact steps
  • Your exception rules from Step 1
  • What happens on the App Store and Google Play if someone ignores the consent prompt

Draft replies for the predictable questions. You'll see the same handful of messages again and again (see Step 6). Write a starting reply for each one so every customer gets the same answer.

Update your public pages. Update the pricing page, help docs and any in-app billing screens on the same day as the announcement. A support reply that contradicts your pricing page causes more confusion.

Pick a quiet week. Don't announce a price change right before you go away. If you have to, follow a vacation support workflow and move the announcement until you're back.

Set up tags or labels. Create a label like pricing-2026 in your inbox so you can count and review the replies later.

Step 5: Send one clear announcement

The announcement is your most important support document, because it answers questions before anyone has to write in. Include:

  1. The change in the first two sentences: old price, new price, which plan.
  2. The effective date, as a specific date or "your first renewal on or after [date]".
  3. The reason, stated plainly and honestly.
  4. What stays the same, if a customer's grandfathered or still in a fixed-price contract.
  5. Their options: downgrade, switch to annual, or cancel, with direct links.
  6. How to reach you, and a note that a real person reads the replies.

Avoid fake urgency, vague phrases like "price adjustment", and burying the number at the bottom. If customers have to hunt for the price, they'll write in to ask.

Send it from an address that accepts replies. For app store subscribers, remember that Apple and Google send their own notices too. Your email should match their dates and amounts exactly.

The same principle of closing the loop with customers applies in a workflow for deprecating a feature. Both are changes customers didn't ask for, and both go better with clear dates and clear options.

Step 6: Sort the replies into categories

Most responses fit into a few groups. Handling each group the same way keeps you fair and fast.

CategoryWhat they're askingHow to handle it
Clarification"Does this affect me?" "When exactly?"Answer from the internal FAQ. Check their account for their actual plan and renewal date.
Billing mechanics"Will I be charged mid-cycle?" "Why did my subscription stop?"Explain the effective date or the app store consent flow. Link to the steps for re-subscribing.
Pushback"This is too expensive."Acknowledge it, restate the options and apply your exception rules. Don't improvise discounts.
Exception request"Can I keep my price?"Check it against your written rules. Approve or decline in the same way for everyone.
Cancellation"Please cancel."Cancel promptly or send the exact steps. Don't make cancelling harder than it already is.
Feedback"I'd pay more if you added X."Thank them, tag the message, and add it to your product notes.

Hypothetical example replies

These are illustrative examples, not real customer exchanges.

Hypothetical — clarification:

Hi Dana, thanks for checking. You're on the annual Pro plan, which renews on 14 March 2027. The new price applies from that renewal, so nothing changes before then. If you'd rather switch to monthly or move to the Starter plan first, you can do that under Settings → Billing.

Hypothetical — pushback, no exception:

Hi Sam, that's fair feedback, and I understand the increase isn't welcome. I'm not offering individual discounts, so everyone gets the same price. If Pro doesn't make sense at the new price, Starter keeps the core features you use most, and you can switch anytime before your renewal on 2 December. If you'd rather cancel, reply here and I'll take care of it.

Hypothetical — app store consent lapse:

Hi Alex, sorry about the interruption. Apple asked for your approval of the new price before your renewal, and when that wasn't confirmed, the subscription ended at the end of the billing period. You can re-subscribe from the app's Settings screen, and your data is still there.

Step 7: Follow up after the effective date

The effective date brings a second round of tickets: surprise charges, failed renewals, and people who missed the email. Plan for it:

  • Send a short reminder before the effective date if your notice period was long. Check that this fits any legal timing windows (California's 7–30 day window, for example).
  • Watch for billing errors in the first renewal cycle. Check a few accounts by hand to confirm the right price was charged on the right date.
  • Review your pricing-2026 label. Count the replies by category. If one question keeps coming up, fix the FAQ, the email or the billing page. A process for turning support patterns into tasks works well here.
  • Close the loop on feedback. If customers named features that would make the new price worth it and you later ship them, tell those customers. The approach in notifying customers when fixes ship applies to this too.

Where AI drafting fits

Price-change replies are repetitive, but they're also sensitive. Each one has to state the right date, the right plan and the right exception rule, in a calm tone. That's why a human should review every reply before it goes out.

An AI support assistant can help by drafting from your internal FAQ and earlier replies so you don't type the same explanation fifty times. SupportMe, for example, drafts email replies in your writing style and never sends anything without your approval. Whatever tool you use, check every draft against the customer's actual plan and renewal date before you send it.

Conclusion

A price increase creates support work you can predict. Most of it can be handled before the announcement goes out. Decide the scope and exception rules first. Check what Stripe, Apple or Google will actually do to existing subscriptions. Confirm the notice rules for your customers' locations and contracts. Then send one clear email with real numbers and dates. Sort the replies into categories, answer each category the same way, and use what you learn to fix the gaps before the next pricing change.

References

Tags

raising prices existing customersprice increase emailSaaS price increasegrandfathering pricingsubscription price changecustomer support workflowprice increase notice

Related posts