PlaybookPrompts

Draft a price increase notice that retains rather than triggers churn

Business Strategy pricingretentioncustomer-communication

Price increase emails are one of the highest-churn-risk communications a company sends. This prompt builds the message around value delivered rather than cost going up, with specific handling for at-risk segments.

Prompt
You are a customer communication strategist. My company sells {{PRODUCT_OR_SERVICE_DESCRIPTION}}. We are raising prices by {{PRICE_INCREASE_DETAILS}} (e.g., '20% across all tiers, effective in 90 days'). The primary business reason for the increase is {{BUSINESS_REASON}}. Key value or improvements we have delivered since the last pricing change: {{VALUE_DELIVERED}}.

1. Write the main customer email announcing the price increase. Requirements: (a) lead with value delivered, not the price change, (b) state the new price and effective date clearly in the first third of the email—do not bury it, (c) keep total length under 250 words, (d) include one specific call to action.
2. Write a shorter version (under 100 words) for in-app notification or banner copy.
3. Write a separate email variant for customers who are already flagged as at risk of churning. This version should acknowledge their situation and offer a retention path if one exists, or set honest expectations if it doesn't.
4. List three objections customers are likely to raise in reply and write one-sentence responses a support rep can use.
5. Recommend the minimum notice period for this type of increase and note any legal or contractual considerations that could affect the timeline.

Do not write a message that feels like it is hiding the price change. Transparency reduces churn more than softening language does.
Variables to fill in
  • {{PRODUCT_OR_SERVICE_DESCRIPTION}}
  • {{PRICE_INCREASE_DETAILS}}
  • {{BUSINESS_REASON}}
  • {{VALUE_DELIVERED}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{PRODUCT_OR_SERVICE_DESCRIPTION}}{{PRICE_INCREASE_DETAILS}}{{BUSINESS_REASON}}{{VALUE_DELIVERED}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.