Feature Investment Advisor — Feature Investment Evaluation Advisor

Skill Overview

Feature Investment Advisor is a feature investment evaluation skill for product managers. It analyzes financial impact across four dimensions—revenue linkage, cost structure, ROI calculation, and strategic value—to help determine whether a feature is worth building.

Use Cases

1. Evaluating whether to build an individual feature: For example, deciding whether to build SSO/SAML for mid-market customers this quarter. After providing business data and cost estimates, you receive a mathematically supported build / don’t build recommendation.
2. Comparing the ROI and strategic value of multiple features: When the team has enough capacity to build only one major feature, compare candidate features’ investment returns and payback periods to prioritize them.
3. Stress-testing roadmap requests using financial logic: When business teams or management propose feature requests, quickly calculate their revenue impact and cost structure, determine whether they are worth scheduling, and provide decision-making support that can be communicated to stakeholders.

Core Capabilities

1. Revenue linkage analysis: Distinguishes between direct monetization (new pricing tiers, paid add-ons, usage-based billing) and indirect monetization (retention, trial conversion, expansion purchases), applying the appropriate quantitative formulas by type. For example, potential monthly revenue = number of customers × adoption rate × price; LTV impact = extension of customer lifetime × number of customers × ARPU × gross margin.
2. Cost structure and ROI calculation: Aggregates one-time development costs and ongoing COGS (infrastructure costs) and OpEx (support and maintenance costs), then calculates contribution margin, first-year ROI, and payback period. It proactively flags the risk of margin dilution when COGS exceeds 20% of expected revenue or when the payback period exceeds the customer lifetime.
3. Four types of structured recommendations: Combining financial and strategic value, it produces one of four recommendations: “Build Immediately,” “Build Strategically (Weak Financial Rationale),” “Do Not Build,” or “Validate Before Deciding.” Each recommendation includes the complete calculation process, key assumptions, risk warnings, and next validation steps.

Frequently Asked Questions

How do you determine whether a feature is worth the development investment?

Provide the feature description and basic business data—such as customer count, ARPU, monthly churn rate, gross margin, and estimated development cost. The skill will calculate revenue impact, cost structure, and ROI, incorporate strategic value such as competitive defense and platform enablement, and provide a mathematically supported recommendation. As a rule of thumb, directly monetized features with a first-year ROI above 3:1 and retention-focused features with an LTV impact above 10:1 are generally strong investment signals.

How do you evaluate the value of retention-focused features that do not generate direct revenue?

For features aimed at retention or conversion, the skill quantifies value through their impact on customer lifetime value (LTV). First, estimate the number of churned customers the feature could recover and the corresponding MRR loss avoided. Then multiply that amount by the customer lifetime to calculate the LTV impact, and compare it with the development cost to determine ROI. For example, if a feature reduces monthly churn from 5% to 4.5%, you can convert that improvement into the number of customers and amount of revenue retained annually, and then calculate the investment return. Features based purely on brand or experience, whose impact on retention cannot be measured, are not suitable for evaluation with this skill.

How does it differ from prioritization frameworks such as RICE? When should it not be used?

RICE scores features based on Reach, Impact, Confidence, and Effort, making it more suitable for relative prioritization. This skill focuses on the financial perspective, producing absolute estimates—such as revenue, margin, and payback period—as well as clear build recommendations. The two approaches are complementary rather than interchangeable.

It is not recommended for the following situations: the feature is a competitive necessity (table stakes); the problem has not yet been validated with users and should first undergo discovery research; the development effort is less than one week; or the impact is purely qualitative and cannot be quantified.