# Product Lifecycle Analysis — Quality Checklist

Use this checklist before delivering a lifecycle analysis report. Every item should be confirmed or explicitly noted as not applicable.

## Data Validation

- [ ] Sales data covers at least 6 months (12+ preferred)
- [ ] No unexplained gaps in time-series data
- [ ] Zero-revenue months investigated (stockout vs. true zero demand)
- [ ] Revenue figures reconcile with unit × price calculations
- [ ] Duplicate SKUs or product entries identified and merged
- [ ] Data source and extraction date documented
- [ ] Currency and time zone consistency confirmed

## Trajectory Calculations

- [ ] Month-over-month growth rates calculated for every product
- [ ] Revenue acceleration (second derivative) computed — not just growth rate
- [ ] Peak revenue identified for each product with date
- [ ] Distance from peak calculated as percentage
- [ ] Cumulative revenue curve shape assessed (convex/linear/concave)
- [ ] Growth rates use consistent time periods (not mixing weekly and monthly)
- [ ] Outlier months flagged and investigated before inclusion

## Stage Classification

- [ ] Every product assigned one of four stages: Introduction, Growth, Maturity, Decline
- [ ] Confidence level (High/Medium/Low) assigned to each classification
- [ ] Classification uses primary indicators first, secondary as supporting evidence
- [ ] No product classified solely on time since launch without trajectory confirmation
- [ ] Conflicting indicators documented with resolution rationale
- [ ] Products with insufficient data (<3 months) flagged rather than force-classified

## Edge Case Handling

- [ ] Seasonal products identified and classified using year-over-year or in-season data only
- [ ] Stockout periods excluded from trajectory analysis with documentation
- [ ] Promotional spikes discounted — underlying trend used for classification
- [ ] Platform migrations noted with combined or flagged trajectory
- [ ] Relaunched products treated as new introductions with historical ceiling noted
- [ ] External factors (competitor launches, algorithm changes) documented where relevant

## Strategy Recommendations

- [ ] Every classified product has at least three specific recommendations (pricing, marketing, inventory)
- [ ] Pricing recommendations include specific tactics, not just "adjust pricing"
- [ ] Marketing recommendations include channel priorities with budget allocation percentages
- [ ] Inventory posture specified (build/maintain/draw down/test) with rationale
- [ ] Product development actions included (line extension, refresh, bundle, sunset)
- [ ] Recommendations are stage-appropriate — no Growth tactics on Decline products
- [ ] Financial impact estimated for key recommendations (dollar value or directional)

## Transition Watch List

- [ ] Products showing early stage-shift signals identified
- [ ] Predicted next stage and estimated timeline provided
- [ ] Preemptive actions specified for each watched product
- [ ] Growth-to-Maturity transitions specifically monitored (most expensive to miss)
- [ ] Maturity-to-Decline transitions flagged with 60-90 day early warning
- [ ] Introduction-to-Growth graduations identified for scaling decisions

## Portfolio View

- [ ] Stage distribution table complete (count, % of catalog, % of revenue, % of margin)
- [ ] Portfolio health assessment included with status indicators
- [ ] Revenue concentration in Maturity+Decline calculated and evaluated
- [ ] Growth pipeline coverage ratio assessed (Growth revenue vs. Decline revenue)
- [ ] Projected revenue gap calculated for 6-month horizon
- [ ] Category-level breakdown provided if multiple product lines exist
- [ ] Portfolio balance commentary included with specific concerns

## Report Quality

- [ ] Executive summary leads with most critical finding and top priority action
- [ ] All tables sorted logically (by stage, then by revenue within stage)
- [ ] Trend indicators (↑↗→↘↓) used consistently throughout
- [ ] Methodology section documents classification rules and data exclusions
- [ ] Next steps are specific, assigned, and time-bound
- [ ] Report follows the output template structure
- [ ] No product left without an actionable recommendation
