feature-investment-advisor
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.
npx skills add deanpeters/Product-Manager-Skills --skill feature-investment-advisor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Evaluates whether to invest in a feature by analyzing revenue connection, cost structure, ROI, and strategic value, then delivers build/don't build recommendations with supporting math.
How it works
Follows a structured, interactive process that:
- Gathers feature description, target segment, and business context.
- Identifies revenue connection (direct monetization, retention, conversion, expansion, or none) and computes expected financial impact accordingly.
- Assesses cost structure: one-time development cost and ongoing COGS/OpEx, then derives contribution margin impact.
- Checks constraints and timing, adjusting urgency and priority based on triggers like competitive threats or capacity.
- Calculates ROI and assembles a decision recommendation with 3–4 options, including strong/weak/ignore-build patterns.
- Offers follow-up actions: view math, compare features, adjust assumptions, or export the summary.
When to use it
Use when financial impact is a key decision factor, especially for features with substantial development time (>1 engineer-month) or notable revenue/turnover considerations. Trigger scenarios include evaluating whether to build SSO, AI assistant features, or roadmap items with ROI relevance.
What it can touch
Tooling is driven by the included interaction prompts and calculations within the skill (no external tools invoked in this summary). The framework references:
- Development cost inputs (team size, time)
- COGS and OpEx inputs
- Revenue impact figures based on adoption, pricing, and revenue connection
- ROI and payback calculations
Caveats
The approach relies on user-provided inputs and assumed projections (adoption, pricing, churn impact). If inputs are uncertain, the framework suggests validating assumptions before proceeding; no guarantees of ROI or payback are provided.
## 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. ## Input **Works best with:** The feature you're deciding on, in a sentence or two. **Also useful:** Revenue connection (direct or indirect), rough cost inputs (dev time, COGS, ongoing OpEx), and the strategic argument being made for it. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The advisor opens by asking what the feature is and how it's supposed to make or save money. **Ex
- Purpose
- Input
- Key Concepts
- The Feature Investment Framework
- Anti-Patterns (What This Is NOT)
- When to Use This Framework
- Facilitation Source of Truth
- Application
- Step 0: Gather Context
- Step 1: Identify Revenue Connection
- Step 2: Assess Cost Structure
- Step 3: Evaluate Constraints and Timing
- Step 4: Deliver Recommendations
- Step 5: Allow Follow-Up Questions
What does the feature-investment-advisor skill do?
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill feature-investment-advisor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.