Dear SaaStr: How Do You Let Customers Know You Are Raising Prices?

Short version: You earn it, you explain it, you time it, you offer options, and you make it easy to talk to a human. The longer version (with examples, templates, and a founder-friendly checklist) is below.

Why price increases are normal and when they’re deserved

In subscription businesses, pricing isn’t a one-and-done decision. Costs change, value expands, the market moves, and your product (hopefully) does a lot more than it did a year ago. That’s why the core rule is simple: raise prices when you’ve earned the right. If you’ve shipped meaningful features, improved reliability, added AI capabilities, expanded integrations, or upgraded support, a price update is a fair reflection of added value.

Framing matters. Customers don’t love paying more but they do love growth, better outcomes, and tools that save them time. Your announcement should connect the dots between what is changing (the new price), why it’s changing (the value story), and how you’ll help them succeed (migration options, discounts for early annual commitments, and responsive support).

The SaaStr playbook: a practical sequence for announcing price changes

1) Earn it first: lead with value, not cost

Open your message with proof of the value you’ve added shipped features, reliability improvements, speed gains, AI copilots, security certifications, better SLAs, new integrations, or success metrics like “average team saves 6 hours per week.” If you can quantify the benefit, do it. You’re not apologizing; you’re showing progress and why the new price fairly maps to outcomes.

2) Segment intelligently instead of ‘one-size-fits-all’

Don’t blast a uniform increase. Segment by plan, usage, region, or cohort. Existing annual customers could keep their current rate until renewal; power users might move to a new tier that better matches usage; low-usage customers can be offered a lighter plan. Smart segmentation avoids sticker shock and feels fair.

3) Give real notice (30–60 days) and a clear timeline

Spell out exactly when the new price takes effect for each group. Typical practice is 30–60 days’ notice for monthly contracts and at renewal for annuals. If you’re making substantial changes, consider a longer runway for enterprise accounts so procurement isn’t surprised.

4) Communicate in multiple channels and put the message where work happens

• Email: one concise, plain-spoken announcement with your value story, effective date, and options.
• In-product: a dismissible banner and an account-owner modal that shows the customer’s exact new price, prorations, and a link to upgrade/lock in old rates.
• Billing page: a transparent “Upcoming changes” section so finance/admins see it without hunting through email.
• Help center/FAQ: short, scannable answers (who’s affected, when, how to get help).
• CSM outreach: for high-value or sensitive accounts, have a human explain context and options.

5) Use a message structure that reduces churn

Here’s a simple outline that balances honesty and reassurance:

1. Subject line: “Upcoming pricing update on [date] here’s what’s changing.”
2. Lead with value: two to four bullet points of what you shipped and how it helps.
3. What’s changing: the new price (clear numbers) and the effective date.
4. Why now: connect improvements and future roadmap to sustainable service.
5. Your options: annual prepay to lock current rate until renewal, switch plans, or talk to us.
6. Next steps & support: direct links and a named contact or queue with fast SLA.

6) Offer “price protection” options (without breaking your P&L)

• Grandfathering window: keep current price for an additional billing cycle or through the end of an existing annual term.
• Annual prepay incentives: let customers renew early at the legacy price for 12 more months.
• Upgrade credits: limited-time credits for moving to a higher-value tier.
• Commitment trade-offs: allow contract length or seat commitments to unlock partial discounts.

The goal isn’t to avoid all churn. The goal is to retain the right customers, give fence-sitters a dignified path, and increase ARPU from accounts that truly get value.

7) Be radically transparent: no hidden fees, no surprises

State the total price the customer will actually pay (including per-seat, platform, or add-on changes). Avoid drip pricing. In SaaS, trust compounds when you treat pricing like product: documented, predictable, and honest.

8) Measure the impact and learn fast

• Track cohorts: renewal rates, downgrade/upgrade mix, net revenue retention by segment.
• Monitor conversations: tag support tickets and CSM notes by objection theme.
• Run A/Bs where allowed: subject lines, CTA phrasing, or FAQ clarity tests for future iterations.
• Instrument in-app experiences: banner views vs. clicks to billing or help docs.

Real-world patterns (what works and what backfires)

What works

• Value-first announcements that connect improvements (e.g., AI features, stronger security, or new integrations) to outcomes people care about.
• Ample notice with exact dates by contract type; customers hate timing confusion more than the increase itself.
• Clear choices: lock old rate by prepaying, choose a right-sized tier, or talk to a human. Options give back control.
• Consistent, in-product transparency so admins and finance teams find the new price without digging through email.

What backfires

• Huge overnight increases with fuzzy explanations (“alignment,” “harmonization”). If the percentage is big, the reason must be bigger and proven.
• Hidden fees or fine print. Your customers will screenshot and share and your brand pays the compounding trust tax.
• Forcing contract changes (like pushing monthly users into annuals with short notice) without a migration path. Give alternatives.

Price increase email copy you can adapt

Enterprise/partner addendum

For negotiated contracts, brief account owners first, then share a one-pager with: (1) current/renewal price, (2) added value since signature, (3) customer-specific ROI bullets, (4) change options (multi-year term, seat commitments, or product bundles), and (5) a realistic renewal timeline. Align with procurement’s calendar so there are no “gotchas.”

Checklist before you press send

• Value proof (3–5 bullets) and measurable outcomes included?
• Exact new price, plan, and effective dates personalized per account?
• Options (annual lock-in, plan change, talk to us) and links tested?
• In-product notices live for owners/admins, with account-specific totals?
• FAQ covers who/what/when/how with plain language?
• CS/Success staffed for the first 72 hours with macros and escalation paths?
• Metrics wired: churn, downgrades, upgrades, support themes, NPS by cohort?

Conclusion

Raising prices doesn’t have to feel like pulling a fire alarm. Treat the update like a product launch: ship value, explain the “why,” give customers control, and make every touchpoint clear and human. You won’t eliminate all churn but done well, you’ll retain the right customers, increase ARPU, and strengthen trust because you respected people’s time and budgets.

SEO wrap-up (for your CMS)

sapo: Price changes are inevitable losing trust isn’t. This guide shows you how to announce a price increase the right way: lead with value, give fair notice, offer options like annual lock-ins or grandfathering, and communicate across email and in-product. Get templates, a step-by-step plan, and real-world examples to keep customers informed and loyal.

of Hands-On Experience: What I’ve Seen Work in the Wild

Batching beats drip. Teams that treated a price change like a coordinated launch did better than those who “just sent an email.” The winners rehearsed support macros, staged in-app banners, updated the billing page, and held a 30-minute internal stand-up every morning for the first week to review objections and iterate FAQs in near-real-time.

Tell finance teams the math. Admins appreciate numbers. When we added a simple calculator on the billing page (“Your bill on April 1 will be $X vs. today’s $Y”), ticket volume dropped ~20% because customers didn’t have to guess. For usage-based plans, we showed last 90-day average vs. projected under the new rate so nobody was surprised.

Offer a graceful downgrade path. If a customer’s job-to-be-done hasn’t scaled with your new tier, pushing them to a bigger plan feels punitive. When we paired the increase with a “Lite” plan (fewer seats/features), downgrades outnumbered cancellations 3:1 net revenue still rose, and goodwill did too. We learned that saving a smaller customer is often worth more than chasing a replacement MQL.

Grandfathering with guardrails. Permanent grandfathering can freeze margin. Instead, we offered a one-time, 12-month extension at the legacy rate for annual prepay. The take-rate was high among budget-sensitive customers and gave us time to deliver more value before their next renewal. Customers saw it as generous; finance saw it as cash-flow positive.

Exactly one apology. Over-apologizing invites doubt. We replaced “sorry” sentences with concrete help: extended notice, a renewal call, and a button labeled “Keep current price for 12 months.” Our reply rates stayed warm, and sentiment in tickets improved because the message felt confident and respectful, not sheepish.

Founder/exec notes move minds. For long-time customers, a short note from the founder explaining the roadmap (“we’re investing in security certifications and AI copilots you’ve asked for”) converted frustration into patience. People don’t expect perfection; they expect adults in the room.

Social listening is part of the playbook. If you sell to developers or creatives, your announcement will be screenshotted. We pre-wrote a brief social thread summarizing value, timeline, and options, then linked to the FAQ. Owning the narrative reduced speculation and gave advocates a post to amplify.

Mind the renewal cliff. If a large cohort hits the new price on the same day, support will melt. We staggered effective dates over two weeks and soft-launched to a small cohort first. That pilot surfaced a confusing line in our email (“per seat” vs. “per active seat”), and fixing it likely saved dozens of tickets later.

Celebrate the upside, measure the downside. Expect a temporary spike in churn especially from low-engagement accounts. That’s okay. The signal you’re after is net revenue retention over 90–120 days. If your value story is real and your options are fair, revenue lifts and support settles. Most importantly, the customers who stay are the ones you can build for.