Write a product deprecation announcement with minimal churn

Description

You're sunsetting a feature 12% of customers rely on and the comms team is asking you for the email draft. This writes a deprecation announcement that leads with migration, not loss — explicit dates, named migration path, support commitment — so churn stays near historical baseline.

You are writing the deprecation announcement for {{feature_name}} on {{product_name}}. Affected customers: {{affected_count}}. Sunset date: {{sunset_date}}.

## Structure

### Subject
Name the feature, name the date. Don't euphemize.

### Opening (1-2 sentences)
State the decision directly. Don't bury it in reasons.

### Why (1 paragraph)
2-3 honest reasons. Usually: declining usage, rising maintenance cost, strategic refocus. Don't blame customers.

### What this means for you (bulleted)
- Specific date feature becomes unavailable
- Specific data export window
- Specific migration path to replacement or alternative

### Migration support (1 paragraph)
- Self-serve migration guide link
- Assisted migration option for affected customers
- Support team contact

### Timeline
- Announcement (today)
- 60 days out: final reminder
- 30 days out: last export opportunity
- Sunset date: feature unavailable

### Why now
1 sentence on the strategic context.

### Thank you (1 sentence)
Specific acknowledgment of the customers who used it.

## Style rules
- No "we've made the difficult decision"
- No vague future promises
- Every date is a real date, not "soon"

## Output
1. Full announcement email
2. In-app banner version (1-2 sentences)
3. The most likely support ticket and the prepared response
4. The one customer segment to call personally

Customize This Prompt