Product Lifecycle

The product lifecycle is the four-stage model of commercial life through introduction, growth, maturity, and decline, used to inform investment, pricing, and sunset decisions. Introduction covers launch and early adoption; growth covers rapid adoption, scale, and competitive entry; maturity covers slowing growth and pricing pressure; decline covers replacement by alternatives and eventual sunset. The framework was popularized by Theodore Levitt in his 1965 Harvard Business Review article "Exploit the Product Life Cycle" and has been adapted from physical-product marketing into software product management.

The four classical stages with their typical characteristics: introduction (low sales volume, high per-unit cost, focus on awareness and early adopters, often unprofitable; in software: MVP through early product-market fit), growth (rapid sales acceleration, cost per unit dropping, competitors entering, focus shifts to scale and capturing market share), maturity (slowing or flat growth, market saturation, competitive pricing pressure, focus shifts to retention, expansion within accounts, and operational efficiency), and decline (shrinking demand as newer alternatives or technology shifts capture share, focus is either harvest profits efficiently or pivot/sunset). Famous examples: Microsoft Office sat in maturity for two decades before the cloud shift to Microsoft 365 reset the curve. BlackBerry rode growth in the 2000s and crashed through decline in the 2010s as smartphones reshaped the category. Google Reader was sunset in 2013 mid-decline despite a passionate user base. The framework's biggest limitation: the stages aren't deterministic, and many products skip stages, restart from earlier stages after a pivot, or sit in maturity indefinitely (TCP/IP, the relational database, email). The sunset decision is where most companies underperform: they keep low-margin late-decline products alive too long because of customer commitments and lost-revenue fears, rather than reallocating engineering capacity to growth-stage bets.

Ryan's Take

The hardest decision in product lifecycle is the sunset. Companies hold onto declining products way past the point where killing them frees up capacity for something better, because killing customers' workflows feels worse than running a slowly-bleeding product. The honest math: every engineer on a declining product is an engineer not on a growth bet. The sunset hurts the customers using the old product; the failure to sunset hurts everyone else, including future customers of a product the team never gets to build. The clean way through is to set explicit sunset criteria upfront ("if revenue is below X by date Y, we sunset"), communicate the timeline with months of notice, and reallocate the capacity intentionally.

What founders get wrong: Assuming every product follows the curve. Many durable products sit in maturity indefinitely, especially infrastructure and standards (PostgreSQL, SMTP, the C programming language). Equally, many never reach growth at all and skip from introduction to a quiet sunset. The framework is a useful mental model, not a deterministic prediction of any specific product's path.

Related: [Product Strategy] · [Product Management] · [Product Launch]

FAQ

What is the product lifecycle? The staged model of a product's commercial life from introduction (launch and early adoption) through growth (rapid adoption and scale), maturity (slowing growth, market saturation), and decline (shrinking demand, replacement by alternatives). Used to inform strategic decisions about investment, pricing, positioning, and when to sunset.

Who developed the product lifecycle framework? Theodore Levitt popularized it in his 1965 Harvard Business Review article "Exploit the Product Life Cycle." The framework was originally developed for physical-product marketing and has been adapted into software product management, though with significant variation since software products don't follow the curve as predictably as consumer goods.

When should a product be sunset? When the engineering capacity tied up in maintaining it would produce more value reallocated to growth-stage bets, and when the cost of maintenance exceeds the revenue and strategic value of keeping it running. The clean approach is to set explicit sunset criteria upfront and reallocate capacity intentionally rather than holding declining products alive indefinitely.