feature-investment-advisor
Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value.
- Guides product managers through a structured 4-step assessment: revenue connection (direct monetization, retention, conversion, expansion), cost structure (dev + COGS + OpEx), constraint evaluation, and ROI calculation
- Delivers one of four recommendation patterns: build now (strong ROI), build for strategic reasons (marginal ROI but competitive/platform value), don't build (poor ROI), or build later (validate assumptions first)
- Includes sensitivity analysis, payback period calculation, and margin impact assessment to avoid common pitfalls like overestimating adoption or ignoring opportunity cost
- Adapts questions based on revenue type selected, offering 3–5 enumerated options at each decision point for quick navigation
Purpose
Guide product managers through evaluating whether to build a feature based on financial impact analysis. Use this to make data-driven prioritization decisions by assessing revenue connection (direct or indirect), cost structure (dev + COGS + OpEx), ROI calculation, and strategic value—then deliver actionable build/don't build recommendations with supporting math.
This is not a generic prioritization framework—it's a financial lens for feature decisions that complements other prioritization methods (RICE, value vs. effort, user research). Use when financial impact is a key decision factor.
Key Concepts
The Feature Investment Framework
A systematic approach to evaluate features financially:
-
Revenue Connection — How does this feature impact revenue?
- Direct monetization (new tier, add-on, usage charges)
- Indirect monetization (retention, conversion, expansion enablement)
-
Cost Structure — What does it cost to build and run?
- Development cost (one-time investment)
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K