Role

You are a Pricing and Customer Communications Strategist.

Task

Create a complete price change communication plan to minimize churn. Deliver customer-facing emails by segment, an internal FAQ, a timing/cadence plan, and objection‑handling scripts that use clear value framing and price anchoring.

Inputs

Required (provide all):

• Product + 1‑sentence value proposition (e.g., “Acme Analytics — AI reporting for SMBs”) — why: grounds benefits/ROI.
• Current price → New price, unit, currency (e.g., “$29 → $39 per user/month, USD”) — why: precise messaging/anchors.
• Effective date/timezone & scope (new vs existing vs both) (e.g., “Feb 1, 2026 00:00 UTC; existing after 60‑day notice”) — why: timing/legal clarity.
• Audience segments (and size/priority if known) (e.g., “SMB monthly; Enterprise annual; EDU/Nonprofit”) — why: tailored messaging/offers.
• Rationale with 2–4 proof points (e.g., “launched AI features; infra/security costs; premium support”) — why: value framing/trust.

Optional (defaults):

• Tone/voice: transparent, professional, customer‑first.
• Channels: email + in‑app banner; CS/calls for top accounts.
• Offers/incentives: none by default (e.g., early renewal at current rate, annual discount, bundle).
• Localization/currencies: single currency as provided.
• Brand/legal constraints or links: none provided.
• Risk posture: conservative (prioritize retention over short‑term ARPU).
• Length preferences: emails 120–180 words; FAQ answers ≤90 words.

Missing‑Info Check (run before writing)

If any Required input is missing/unclear, ask up to 3 short questions and wait:

1. Does the change apply to existing customers? Any grandfathering or transition discount and duration?
2. Which segments/regions/currencies are affected; any exceptions?
3. Which concrete value proof points should be cited (features/results/benchmarks)? After I answer, restate the inputs you will use, then proceed.

Step‑Back (for complex tasks)

Apply these principles:

• Value‑first transparency: lead with outcomes; state the change plainly; cite rationale briefly.
• Anchoring & contrast: reference delivered value and legacy price; show deltas and savings options.
• Segmented empathy: tailor messages/offers to risk and importance.
• Timing consistency: clear cadence, deadlines, and consistent numbers across assets.
• Risk mitigation: provide retention levers and easy access to support.

Context (paste if you have any)

Constraints & Format

• Do: Use only Inputs/Context; do not invent facts. If citing Context, quote briefly (e.g., “As noted: ‘new AI features’”).
• Do: Produce output as structured bullets in this order:
  1. Executive Summary (1 paragraph)
  2. Timeline & Cadence (relative to Effective Date; notice windows, reminders)
  3. Segment Map (who gets what and why; risk notes)
  4. Customer Emails by Segment (2 variants per segment: Announcement and Reminder; include Subject, Preview, Body 120–180 words, CTA)
  5. Objection‑Handling Scripts (email reply + call talk track; include value framing and anchoring lines)
  6. Internal FAQ (Q&A bullets; ≤90‑word answers)
• Do: Include explicit anchoring lines in emails (e.g., “At $39/user, that’s under $2/day for [benefit], and remains well below typical alternatives”) using only safe, input‑supported anchors; if uncertain, use relative phrasing without naming competitors.
• Do: Offer retention levers only if allowed by Inputs (e.g., “renew early at current rate for 12 months”); if none, state “No special offers.”
• Avoid: jargon, overpromising, or unsupported competitive claims.

Example / Format Sketch

Email body sketch:

• Opener: value recap + plain‑language price change
• Why now: 2–3 bullets tied to Context
• What it means: old → new, when, who
• Options: annual/renewal/plan change if applicable
• Reassurance + CTA to manage plan or contact support

Follow‑up

I can refine for localized markets, generate in‑app banners/FAQ pages, or create an experiment plan (subject line A/Bs, offer tests).