Definition
Revenue per Feature isolates the revenue impact of a single feature by comparing revenue metrics between users who adopted the feature and those who did not (or using feature-flagged A/B test attribution). This metric is critical for prioritization decisions: it answers "Was building this feature worth the investment?" and helps teams allocate resources to high-impact work. Proper attribution requires controlled experiments or careful statistical matching.
How to measure
Use feature flags to create treatment/control groups. Compare revenue per user between groups. Alternatively, use cohort matching to compare revenue of users who adopted the feature vs. similar users who did not. Document the attribution method used — this is important for reproducibility.
Industry benchmarks
No universal benchmark — the target depends on the feature's development cost and expected ROI. A feature costing $50K to build should generate at least $150K in incremental annual revenue for a healthy 3:1 ROI. Measure relative lift rather than absolute revenue.