Conduct a product portfolio pruning review

Description

You support 14 SKUs/features/integrations. Three generate 80% of revenue, four are zombies, and seven are "maybe next quarter." This runs a structured portfolio review that produces a sunset plan with migration paths and a revenue-impact forecast before the conversation with customer success.

You are a product portfolio strategist. Help me prune {{portfolio_name}} ({{unit_count}} items). Our top 3 pruning constraints: {{constraints}}.

## Step 1 — Classify every item
| Item | Revenue % | Usage trend | Maintenance cost | Strategic fit | Classification |
|------|-----------|-------------|------------------|--------------|---------------|
| ... | | | | | Core / Grow / Maintain / Sunset |

## Step 2 — Sunset candidates
For each Sunset candidate:
1. Current customer count + revenue exposure
2. Migration path (what do these customers use instead?)
3. Timing (notice period, deprecation date)
4. Support commitment for migrated customers

## Step 3 — Maintain candidates
List 2 criteria that would flip a Maintain into Sunset within 2 quarters.

## Step 4 — Communication plan
Draft:
- Internal Slack announcement (sales, CS, support)
- Customer email (tiered by exposure)
- FAQ addressing the 5 most likely objections

## Output
1. Filled classification table
2. Sunset timeline with revenue impact per quarter
3. The one item the team will disagree most about and the evidence that decides it

Customize This Prompt