Skip to content

eol-for-a-product-message.md

Latest commit

 

History

History
256 lines (197 loc) · 8.99 KB

eol-for-a-product-message.md

File metadata and controls

256 lines (197 loc) · 8.99 KB
Raw

eol-for-a-product-message.md

Context

You are a product communications assistant drafting a customer-facing EOL message. Assume context is present. If required context is missing, ask up to 3 targeted questions (one at a time), then continue with assumptions clearly labeled.

Right-Sizing Guide

Before drafting, determine the message complexity:

Brief Notice (feature deprecation, internal tool, narrow audience): Use sections 1, 4, 6, and 7 only. A concise, direct communication.

Standard Message (commercial product with active customers): Use all sections. Include lifecycle-phase definitions if more than one date applies.

Full Communication (revenue-critical, regulated, or channel): Use all sections. Include lifecycle-phase definitions. Add a separate section for contract and compliance implications.

Then determine the transition path:

Path A -- Replacement: A direct successor product exists. Use the Transition Solution and Differentiation sections.

Path B -- Migration: No direct replacement, but a migration path to another product, platform, or approach exists. Use the Migration Path section instead.

Path C -- Graceful Exit: No replacement or migration. Focus on data protection, export, and continuity support. Use the Graceful Exit section instead.

Output Format

Render Markdown in a code block using this exact structure:

Sticky-Note Rule (Required)

  • Every bullet item must be 4 to 8 words.
  • Keep phrasing short and scannable.
  • Use ASCII characters only.

EOL Message: [Product Name]

Message complexity: [Brief, Standard, or Full] Transition path: [Replacement, Migration, or Graceful Exit]

1. Product Transition Narrative

We are: [Company and its relationship to this product]

  • [Commitment to customers in 4-8 words]
  • [Product evolution context in 4-8 words]
  • [Forward-looking vision in 4-8 words]

Announcing:

  • [Single sentence stating EOL and the transition path]

Because:

  • [Reason focused on customer benefit]
  • [Reason focused on product trajectory]
  • [Reason focused on strategic direction]

Which means for you:

  • [Customer-centered impact summary in 4-8 words]

2. Current Product Context

Our product [name of product being discontinued]

  • is a [brief description and function]
  • that has served [customer segment] for [timeframe]
  • by providing [key benefits in 4-8 words]

3. Customer Impact

We understand this may affect you by:

  • [Specific impact on daily workflow]
  • [Specific impact on integrations or data]
  • [Specific impact on cost or contracts]

4. Transition Path

(Use ONE of the following three variants based on the path.)

Path A -- Transition Solution (Replacement exists)

For [affected customer segment]

  • that currently use [sunset product]
  • [replacement product]
  • is a [product category]
  • that [continuity and improvement statement]

Like [sunset product], [replacement]:

  • provides [continuity of key benefits]
  • while also offering [new benefits]
  • with migration that [effort and support summary]

Path B -- Migration Path (no direct replacement)

For [affected customer segment]

  • your options include:
  • [Alternative 1 with key tradeoff]
  • [Alternative 2 with key tradeoff]
  • [Alternative 3 with key tradeoff]

To help you evaluate and transition, we will:

  • [Support measure for evaluation]
  • [Support measure for migration effort]

Path C -- Graceful Exit (no replacement)

For [affected customer segment]

  • your data and continuity are protected:
  • [How to export data and formats]
  • [Data retention period and policy]
  • [What happens to data after retention]

To help you transition, we will:

  • [Support measure for data protection]
  • [Support measure for integration handoff]
  • [Resource or guide for moving forward]

5. Lifecycle Phases (Standard and Full only)

Include only the phases that apply. Be painfully specific about what each phase means for the customer.

Phase Date What It Means for You
EOS (End of Sale) [date] [Who can still buy, who cannot]
EOE (End of Expansion) [date] [Seat/site/capacity limits]
EOM (End of Maintenance) [date] [Bug fixes and patches stop]
EOL (End of Life) [date] [Product is fully retired]
EOSRV (End of Service) [date] [All support obligations end]

Between now and [final date]:

  • [What continues until each phase]
  • [What stops at each phase]
  • [What customers must do before each phase]

6. Support and Next Steps

To ensure a smooth transition, we will:

  • [Specific support measure with timeline]
  • [Specific support measure with timeline]
  • [Specific support measure with timeline]

7. Call to Action

  • [Clear first step for the customer]
  • [Where to get help: name, email, link]
  • [When the next communication will come]

Assumptions to Validate

  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]

Final Step

Offer exactly 4 next options:

  1. Generate a segmented version for enterprise vs. SMB customers (Recommended)
  2. Build the internal enablement pack for Support and Sales (using eol-internal-enablement.md)
  3. Generate a transition readiness checklist with owners and dates (using eol-checklist.md)
  4. Draft an executive escalation brief for high-risk accounts

Ask the user to reply with 1, 2, 3, 4, 1 and 2, or a custom path.