Price Increase Announcement
A price increase is a trust event, and most are botched by burying the number, over-justifying, or blindsiding support the day the emails land. This writes the version that respects the customer: the increase stated plainly and early, a reason that's true (usually more value delivered), a transition that softens the jump for loyal customers, and an internal brief so every rep can answer the angry reply.
What This Skill Produces
- The customer announcement — clear increase, honest reason, effective date, what's not changing
- Grandfathering / transition terms — how existing customers are handled (locked price window, phased, or notice period)
- The FAQ — the hard questions ("why now," "can I lock in," "I'll cancel") with real answers
- The internal brief — talking points and the discount/save guardrails so support and sales are aligned
Required Inputs
Ask for these if not provided:
- The change — old price → new price, which plans, and when it takes effect
- The real reason — new capabilities, cost pressure, repositioning (the honest one, not a spin)
- Customer segments — new vs existing, annual vs monthly, enterprise vs self-serve — terms differ
- The transition — are existing customers grandfathered, phased, or given notice? What's the policy?
- Guardrails — what reps can offer to save an account, and what they can't
Framework: A Price Increase That Holds
- Lead with the number. Say the increase in the first lines; hiding it reads as shame and breeds distrust.
- One true reason. Ideally "we've added X, Y, Z since you signed" — value earns a price. Don't over-justify.
- Soften for loyalty. A price-lock window or phased ramp for existing customers turns a shock into a fair-notice.
- Give a clear date and choice. When it hits, and what they can do (renew early, switch plan, contact us).
- Arm the front line. Support/sales get the FAQ and save-rules before customers do — never after.
Output Format
Customer email
- Subject: [clear, not evasive]
- Body: the increase → the reason (value) → effective date → what's unchanged → their options → thank-you
Transition terms
- Existing customers: [grandfather window / phased / notice]. New customers: [effective immediately].
FAQ
| Question |
Answer |
| Why are prices going up? |
… |
| Can I lock in the current price? |
… |
| What if I want to cancel? |
… |
Internal enablement brief
- Talking points · objection responses · save guardrails (what reps may/may not offer)
Quality Checks
Anti-Patterns
- Burying the number in paragraph four — the fastest way to lose trust.
- Over-justifying with a wall of reasons — one true reason beats five defensive ones.
- Blindsiding support — angry replies with no talking points is a self-inflicted wound.
- No transition for loyal customers — a flat overnight jump maximises churn.
- Spin as the reason ("to serve you better") when the truth is cost — customers can tell.
Example Trigger Phrases
- "Announce a price increase to our customers."
- "Write the pricing change email and FAQ."
- "We're raising prices 15% — help me communicate it without a churn spike."
- "Draft customer and internal comms for new pricing."
1---2name: price-increase-announcement3description: Announce a price increase without triggering a churn spike — the rationale, grandfathering, effective dates, the FAQ, and the internal brief so support isn't blindsided. Use when asked to announce a price increase, write pricing change comms, raise prices to customers, or communicate new pricing. Produces the customer email, the FAQ with objection handling, the grandfathering/transition terms, and the internal enablement brief. A pricing-comms craft, not a discount.4---5
6# Price Increase Announcement
7
8A price increase is a trust event, and most are botched by burying the number, over-justifying, or blindsiding support the day the emails land. This writes the version that respects the customer: the increase stated plainly and early, a reason that's true (usually more value delivered), a transition that softens the jump for loyal customers, and an internal brief so every rep can answer the angry reply.
9
10## What This Skill Produces
11
12- **The customer announcement** — clear increase, honest reason, effective date, what's not changing
13- **Grandfathering / transition terms** — how existing customers are handled (locked price window, phased, or notice period)
14- **The FAQ** — the hard questions ("why now," "can I lock in," "I'll cancel") with real answers
15- **The internal brief** — talking points and the discount/save guardrails so support and sales are aligned
16
17## Required Inputs
18
19Ask for these if not provided:
20- **The change** — old price → new price, which plans, and when it takes effect
21- **The real reason** — new capabilities, cost pressure, repositioning (the honest one, not a spin)
22- **Customer segments** — new vs existing, annual vs monthly, enterprise vs self-serve — terms differ
23- **The transition** — are existing customers grandfathered, phased, or given notice? What's the policy?
24- **Guardrails** — what reps can offer to save an account, and what they can't
25
26## Framework: A Price Increase That Holds
27
281. **Lead with the number.** Say the increase in the first lines; hiding it reads as shame and breeds distrust.
292. **One true reason.** Ideally "we've added X, Y, Z since you signed" — value earns a price. Don't over-justify.
303. **Soften for loyalty.** A price-lock window or phased ramp for existing customers turns a shock into a fair-notice.
314. **Give a clear date and choice.** When it hits, and what they can do (renew early, switch plan, contact us).
325. **Arm the front line.** Support/sales get the FAQ and save-rules *before* customers do — never after.
33
34## Output Format
35
36### Customer email
37- Subject: [clear, not evasive]
38- Body: the increase → the reason (value) → effective date → what's unchanged → their options → thank-you
39
40### Transition terms
41- Existing customers: [grandfather window / phased / notice]. New customers: [effective immediately].
42
43### FAQ
44| Question | Answer |
45|---|---|
46| Why are prices going up? | … |
47| Can I lock in the current price? | … |
48| What if I want to cancel? | … |
49
50### Internal enablement brief
51- Talking points · objection responses · save guardrails (what reps may/may not offer)
52
53## Quality Checks
54- [ ] The new price and effective date are in the first few lines
55- [ ] The reason is true and value-led, not padded with spin
56- [ ] Existing-customer transition terms are explicit
57- [ ] The FAQ answers the cancel/lock-in questions honestly
58- [ ] The internal brief ships alongside (not after) the customer comms
59- [ ] Save guardrails are defined so reps don't improvise discounts
60
61## Anti-Patterns
62- **Burying the number** in paragraph four — the fastest way to lose trust.
63- **Over-justifying** with a wall of reasons — one true reason beats five defensive ones.
64- **Blindsiding support** — angry replies with no talking points is a self-inflicted wound.
65- **No transition for loyal customers** — a flat overnight jump maximises churn.
66- **Spin as the reason** ("to serve you better") when the truth is cost — customers can tell.
67
68## Example Trigger Phrases
69- "Announce a price increase to our customers."
70- "Write the pricing change email and FAQ."
71- "We're raising prices 15% — help me communicate it without a churn spike."
72- "Draft customer and internal comms for new pricing."
gabrielmoreira