Why Companies Keep Zombie Products Alive Too Long

Most companies have products that should have been retired years ago. They persist for emotional reasons (the founder built it), political reasons (the team that maintains it would be reassigned), or fear reasons (what if the customers who depend on it leave entirely?). These zombie products consume engineering resources, complicate the product portfolio, confuse the market, and generate minimal revenue relative to their costs.

The sunk cost fallacy is powerful in product management. The more you have invested in something, the harder it is to walk away. But every dollar and every engineer-hour spent maintaining a declining product is a dollar and hour not invested in growing products. The opportunity cost of keeping zombie products alive is usually far higher than the direct cost.

The Five Signals That It Is Time to Sunset

1. Declining usage without a reversal path: If usage has declined for three or more consecutive quarters and you have no credible plan to reverse the trend, the market has spoken.

2. Maintenance cost exceeds revenue contribution: When the fully-loaded cost of keeping a product running (engineering, infrastructure, support, compliance) exceeds the revenue it generates, you are subsidizing existence rather than creating value.

3. Strategic misalignment: If the product no longer fits your company's direction — it serves the wrong market, requires the wrong technology, or competes with a newer offering — keeping it alive creates confusion internally and externally.

4. Security or compliance liability: Aging products on aging infrastructure become security risks. If the cost of maintaining security and compliance standards for a legacy product is growing faster than its revenue, the risk-adjusted economics argue for retirement.

5. Opportunity cost is quantifiable: If you can specifically identify what the product's engineering team would build instead and estimate the value of that alternative, you have a business case for sunset. "Free up four engineers" is weak. "Free up four engineers to ship the integration that three enterprise prospects are waiting for" is compelling.

Executing the Sunset Without Breaking Trust

How you retire a product matters as much as whether you retire it. Handled well, a sunset strengthens customer trust by demonstrating that you prioritize their long-term success over short-term convenience. Handled poorly, it destroys relationships and generates churn across your entire portfolio.

The keys to a trust-preserving sunset: announce early (give customers at least 6-12 months of notice), provide a clear migration path (to a replacement product, a competitor, or an export of their data), offer migration support (not just documentation, but hands-on help), and be transparent about the reasoning (customers respect honesty about strategic direction far more than vague corporate language).

Communicate directly to affected customers — not through a blog post buried on your website. Account managers should have personal conversations with key customers. Support teams should be trained on the migration path before the announcement goes public. Every touchpoint should reinforce that you are making this decision in the customer's long-term interest, not just your own.