# ChangeNotice: NoteSync Pro Price Increase — Full Communication Suite **Change type:** Price increase (subscription pricing going up) **Product:** NoteSync Pro **Effective date:** August 1, 2026 **Reason given:** To continue investing in AI feature development and server capacity --- ## STEP 0 — Change Type Classification & Risk Profile | Dimension | Classification | Rationale | |---|---|---| | Change category | Price increase | Directly stated in inputs | | Churn risk level | **Medium–High** | Price increases rarely trigger immediate mass cancellation, but they reopen a "is this still worth it?" evaluation. Risk skews High for price-sensitive and low-usage segments, and Medium for engaged users — treated here as Medium-High to size the response appropriately. | | Trust mechanism most at risk | Fairness + Transparency | Customers will judge whether the stated reason is credible, not just whether it's polite. | | Required customer action | None to continue; cancellation window exists if they want to avoid the new price | No opt-in needed for the price itself to take effect | | Communication urgency | Announce immediately, with lead time before Aug 1 | INFERRED — roughly 3–4 weeks' notice from a typical send date is standard practice for subscription price changes and gives customers time to decide before being charged. | **Failure mode priority map:** | Failure Mode | Priority | Evidence Type | Conf | |---|---|---|---| | Burying the change past sentence 2 | HIGH | INFERRED | 95 | | Over-apologetic tone signaling guilt | MED | INFERRED | 80 | | Vague reason that reads as corporate deflection | HIGH | INFERRED | 88 | | Missing action deadline when action is required | MED | INFERRED | 78 | | Generic support contact (no real path to a human) | MED | INFERRED | 72 | --- ## STEP 1 — Strategic Analysis | Dimension | Finding | Evidence Type | Conf | |---|---|---|---| | Most likely customer reaction | Mixed (indifference from heavy users, irritation from price-sensitive/light users) | INFERRED | 72 | | Trust lever to activate | Fairness (value-for-money justification) | INFERRED | 85 | | Must-answer question #1 | "How much more will I be paying?" | INFERRED | 95 | | Must-answer question #2 | "Can I keep my current price if I've been a subscriber a long time?" | INFERRED | 82 | | Must-answer question #3 | "What do I actually get for the higher price — new features or just more money for the same thing?" | INFERRED | 88 | | Churn trigger moment | The first billing statement after Aug 1 showing the new charge — not the announcement email itself | INFERRED | 85 | **Assumption ledger:** | Assumption | Where It Enters | If False — Effect on Communication | |---|---|---| | The exact dollar/percentage increase was not provided in inputs | Both email bodies, FAQ #1 | Placeholders `$[X]` → `$[Y]` must be filled with real figures before sending; sending with unfilled brackets is a trust failure worse than a delay | | Customers are on auto-renewing monthly or annual billing | Both emails | If some are on lifetime/one-time licenses, "next billing cycle" language is wrong for that segment and needs separate copy | | No legacy/grandfathered pricing tier exists for long-tenure customers | Segment A email | If grandfathering *is* available, Segment A email should lead with that instead — this is currently the single biggest retention lever left unused if true | | Single flat price increase applies to all NoteSync Pro plans | Segmentation logic | If multiple tiers see different increases, each tier needs its own $[X]→$[Y] figures | --- ## STEP 2 — Confidence Flow Analysis | Touchpoint | Trust Risk | If Mishandled — Effect | Mitigation in This Suite | |---|---|---|---| | Subject line | First impression — will they open? | Churn decision made before reading | Subject states the change and the date directly; no teaser language | | Opening sentence | Change disclosed or buried? | Anger if buried; respect if immediate | Both emails open with the exact change in sentence one | | Reason paragraph | Is it honest or PR-speak? | Distrust if evasive; goodwill if frank | Reason is grounded in two concrete cost drivers (AI development, server capacity) rather than "to improve your experience" | | Action paragraph | Is the path clear? | Confusion and frustration if vague | Explicit "no action needed" + explicit cancellation deadline stated together | | Contact information | Is there a real human reachable? | Helplessness if generic | Segment A gets a named/direct reply path; Segment B gets a specific channel with a response-time commitment | | Support FAQ response | Does it actually answer the question? | Escalation and churn if deflecting | FAQ answers include specifics (deadline, refund logic) rather than "please contact support" | --- ## STEP 3 — Segmentation Strategy | Segment | Definition | Tone | Emphasis | Unique Risk | |---|---|---|---|---| | A — High-Value / Long-Tenure | Subscribers 12+ months, or on annual plans / high daily usage | Warmer, personal, acknowledges tenure | Relationship continuity, direct human contact | Highest churn cost if lost — hardest segment to reacquire | | B — General Customer Base | All other active NoteSync Pro subscribers | Clear, efficient, respectful, no filler | Clarity of the change and exactly what (if anything) to do | Volume churn risk — smaller individual cost, larger aggregate impact | --- ## STEP 4 — Full Emails ### EMAIL — SEGMENT A (High-Value / Long-Tenure) **Subject:** Your NoteSync Pro price is increasing on August 1 **Alt Subject:** A pricing update for your NoteSync Pro account (effective Aug 1) **Preview Text:** Here's exactly what's changing, why, and what you don't need to do. **Body:** Starting August 1, 2026, your NoteSync Pro subscription is increasing from $[X]/month to $[Y]/month. You've been with NoteSync Pro for over a year, so to be specific: your next charge on or after August 1 will reflect this new rate. Nothing else changes — same plan, same features, same notes, same sync. We're raising prices because the cost of building the AI features you use, and running the servers that keep your notes synced and fast, has both gone up. This increase lets us keep investing in both rather than slow down or cut corners. You don't need to do anything to stay subscribed. If you'd rather not continue at the new rate, you can cancel any time before August 1 and keep access through the end of your current billing period. Questions about your account specifically? Reply directly to this email — a real person reads these, not a bot. Thanks for sticking with us this long; it's genuinely noticed. **CTA:** "Review my plan" **Word count:** 156 words --- ### EMAIL — SEGMENT B (General) **Subject:** Your NoteSync Pro price is increasing on August 1, 2026 **Alt Subject:** Price change to your NoteSync Pro subscription **Preview Text:** What's changing, why, and what to do next — no action needed to stay subscribed. **Body:** Starting August 1, 2026, the NoteSync Pro subscription price is increasing from $[X]/month to $[Y]/month. This takes effect on your next billing cycle on or after that date. Your plan, features, and stored notes are not changing. We're raising prices to keep investing in the AI features you use and the server capacity that keeps NoteSync Pro fast and reliable. Both have gotten more expensive to maintain, and this increase lets us keep building rather than scale back. No action is needed to continue your subscription. If you'd prefer not to continue at the new price, cancel before August 1, 2026 to avoid the new charge — you'll keep access through the end of your paid period either way. Questions? Email support@notesync.com or use in-app chat; average reply time is under 4 hours. **CTA:** "Review my plan" **Word count:** 118 words --- ## STEP 5 — Support FAQ (4 entries) | Q (verbatim customer phrasing) | A (under 50 words) | Evidence Type | |---|---|---| | "Why is the price going up?" | "We're putting more into the AI features you use and the servers that keep your notes syncing fast — both cost more to run than they used to, and this increase lets us keep investing instead of cutting back." | INFERRED | | "Can I keep my old price if I've been a subscriber for a long time?" | "Right now the new price applies to all NoteSync Pro subscriptions starting August 1, with no exceptions based on tenure. If that changes, we'll email you directly." | INFERRED — **flag for verification**: whether any grandfathering exists is unconfirmed; do not promise it either way until confirmed internally | | "What do I actually get for the higher price?" | "Continued and faster development of the AI features already in NoteSync Pro, plus server capacity that keeps sync and search fast as usage grows. No new paywalled features are being added because of this increase." | INFERRED | | "If I cancel now, do I still get charged the new price, or can I get a refund for days I don't use?" | "If you cancel before August 1, you're never charged the new rate, and you keep access through the end of your current paid period — no partial refund needed since you won't be billed again." | INFERRED — **flag for verification**: exact refund/proration policy should be confirmed with billing before this goes live | --- ## STEP 6 — Retention Save Script *(Included despite Medium-High rather than strictly High churn risk, since price increases are a common live-call cancellation trigger and a concrete script materially improves save rates.)* | Script Stage | Verbatim Line | Purpose | |---|---|---| | Acknowledge | "You're calling about the price change, and I want to be straight with you about it rather than just apologize — let's look at what's actually changing on your account." | De-escalate without over-apologizing | | Reframe | "The increase is going toward the AI features and server capacity you're already using every time you open the app — it's not a new markup on the same static product." | Shift perspective without undermining the change | | Offer | "I can apply a [X]% discount for your next 3 billing cycles while you decide if the new price works for you long-term — no commitment beyond that." | Create a concrete reason to stay | | Close | "Would you like me to apply that now, or would you rather go ahead with the cancellation and keep access through the end of your current period?" | Resolve the call either way, without pressure | *(Note: the specific discount percentage in the Offer line is a placeholder — it should be filled with whatever retention offer is actually authorized before agents use this script.)* --- ## STEP 7 — Input Robustness Scenarios | Condition | First Break Point | Predicted Customer Behavior | Conf | |---|---|---|---| | Sparse context (customer doesn't understand the change) | Reason paragraph — if it reads as vague, the "why" fails to land | Customer contacts support asking "what am I actually paying for" | 75 | | Contradictory (reason given doesn't match the change type, e.g. reason cites cost-cutting but this is a price *increase*) | Opening sentence — mismatch between stated reason and stated action creates immediate distrust | Customer assumes deflection, escalates to cancellation | 80 | | Missing action path (customer needs to do something but it's unclear) | Action paragraph — if the deadline isn't crisp, customers miss the cancellation window and feel trapped | Chargeback requests or public complaints after being billed unexpectedly | 78 | | High-emotion customer (already frustrated before receiving the email) | Any section that reads as corporate or impersonal will confirm their frustration rather than defuse it | Immediate cancellation call rather than reading the FAQ first | 82 | --- ## STEP 8 — Communication Integrity Check | Check | Status | Note | |---|---|---| | Change is stated in the first sentence of both emails | ✅ | Both open with the exact price change and date | | No over-apologetic language ("we're so sorry for any inconvenience") | ✅ | Neither email apologizes; tone is direct and factual | | Both emails are under 160 words | ✅ | Segment A: 156 words; Segment B: 118 words | | Every must-answer question from Step 1 is addressed (email + FAQ) | ✅ | Amount (email + FAQ #1), grandfathering (FAQ #2), value justification (email + FAQ #3) | | Real contact information is provided — not "contact support" | ✅ | Segment A: direct reply; Segment B: named channel + response-time commitment | | FAQ answers actually answer the question — no deflection | ⚠ | FAQ #2 and #4 are honest but depend on internal confirmation (grandfathering policy, refund/proration rules) that wasn't provided in inputs | | Retention save script offers something concrete (not just empathy) | ✅ | Includes a specific discount offer, not just acknowledgment | | All INFERRED findings are labeled | ✅ | Labeled throughout | **COMMUNICATION CONFIDENCE: 74/100** — The structure, tone, and sequencing are solid, but two real numbers (the price increase amount, and the retention discount) are placeholders that must be filled with actual figures before this suite can be sent — that's the main thing holding confidence back from higher. **Biggest unknown:** Whether any grandfathering/legacy pricing exists for long-tenure subscribers — this single fact would most change the Segment A email (from "here's the new price" to "here's how we're protecting you from it"). **Findings from inputs alone (STATED):** - Change type: price increase - Product: NoteSync Pro - Effective date: August 1, 2026 - Reason: continued investment in AI feature development and server capacity **Findings requiring customer/business data to verify (VERIFY):** - Exact dollar/percentage amount of the increase - Whether grandfathering exists for any subscriber segment - Refund/proration policy for mid-cycle cancellations - Actual retention discount authorized for the save script - Whether all subscribers are on the same plan tier or multiple tiers with different increases