# Lifecycle stage assessment · [Offering, module, API version or dependency] · [Date] **Owner:** [PM] **Evidence window:** [e.g., last four quarters] **Next review:** [Date] ## Signals | Signal | Value | Trend | Source | |---|---|---|---| | ARR or usage growth against the market | | | | | Share of new bookings | | | | | Net revenue retention and gross churn (customers whose main use is this offering) | | | | | Active customers and usage trend | | | | | Gross margin and cost to serve | | | | | Support tickets per customer; on-call load | | | | | Engineering share against revenue share | | | | | Competitive parity (competitor bundles, general-purpose AI tools) | | | | | Dependency risk (models, platforms, protocols with published end dates) | | | | | Strategic fit (feeds or competes with the strategy) | | | | ## Assessment - **Stage:** Introduction / Growth / Maturity / Decline - **Confidence:** Low / Medium / High - **The one signal that would change this call:** - **Self-fulfilling risk:** what we'd stop doing if we call it this stage, and whether that would cause the decline ## Investment posture Invest / Sustain / Harvest / Retire. Reason in two sentences: ## Portfolio view (one row per offering) | Offering | Stage | Posture | Revenue share | Engineering share | Gap to resolve | |---|---|---|---|---|---| | | | | | | | ## Decision Agreed by [name] on [date]. Next review: [date]. If the posture is Retire, open a sunset decision memo.