Something went wrong!
Hang in there while we get back on track
Revenue-Weighted Enterprise Prioritization
Demonstrates revenue-weighted analysis with 5 requests totaling $455K. Shows how SSO/SAML requests from enterprise customers ($350K combined) should be prioritized over webhooks ($30K) despite equal request counts. Includes strategic recommendations.
Input
What you provide to the skill
Prioritize: request_id,title,description,source,customer,revenue
1,SSO login,Single sign-on,email,EntCo,200000
2,SAML auth,SAML SSO,sales,BigCorp,150000
3,Bulk export,Export data,support,MidCo,50000
4,CSV download,CSV download,email,SmallBiz,25000
5,API webhooks,Webhooks,slack,DevShop,30000
Output
What the skill generates for you
Feature Request Deduplication Report
Analysis Date: 2025-12-03
Total Requests Analyzed: 5
Total Revenue Represented: $455,000
Executive Summary
Duplicate Clusters Identified: 2
Unique Feature Themes: 3
Consolidation Opportunity: 40% of requests are duplicates
Revenue Consolidated: $375,000 across 2 major themes
Duplicate Clusters
Cluster 1: Enterprise Authentication (SSO/SAML)
Combined Revenue Impact: $350,000
Priority: HIGH
| Request ID | Title | Customer | Revenue | Source |
|---|---|---|---|---|
| 1 | SSO login | EntCo | $200,000 | |
| 2 | SAML auth | BigCorp | $150,000 | sales |
Consolidated Description:
Enterprise customers require single sign-on authentication capabilities, specifically SAML protocol support for seamless integration with their identity providers.
Recommended Action:
Create single feature: “Enterprise SSO with SAML Support”
Total Revenue at Stake: $350,000
Cluster 2: Data Export Functionality
Combined Revenue Impact: $75,000
Priority: MEDIUM
| Request ID | Title | Customer | Revenue | Source |
|---|---|---|---|---|
| 3 | Bulk export | MidCo | $50,000 | support |
| 4 | CSV download | SmallBiz | $25,000 |
Consolidated Description:
Customers need ability to export their data in bulk, with CSV format as the primary requirement for external analysis and record-keeping.
Recommended Action:
Create single feature: “Bulk Data Export (CSV)”
Total Revenue at Stake: $75,000
Unique Requests
Request 5: API webhooks
Revenue Impact: $30,000
Priority: LOW
Customer: DevShop
Source: slack
Description:
Webhook notifications for API events to enable real-time integrations.
Recommendation:
Keep as standalone feature request for API infrastructure roadmap.
Prioritization Recommendation
Priority 1: Enterprise SSO with SAML Support
- Revenue: $350,000 (76.9% of total)
- Customers: 2 enterprise accounts
- Effort: HIGH (8-10 weeks)
- Strategic Value: Enterprise market expansion
Priority 2: Bulk Data Export (CSV)
- Revenue: $75,000 (16.5% of total)
- Customers: 2 mid-market accounts
- Effort: MEDIUM (3-4 weeks)
- Strategic Value: Data portability, compliance
Priority 3: API Webhooks
- Revenue: $30,000 (6.6% of total)
- Customers: 1 developer-focused account
- Effort: MEDIUM (4-5 weeks)
- Strategic Value: Developer ecosystem enablement
Revenue-Weighted Insights
Top Revenue Driver:
Enterprise authentication represents 77% of revenue opportunity, driven by 2 high-value customers with similar technical requirements.
Quick Win Opportunity:
Data export functionality serves 2 customers for moderate effort, delivering strong ROI with 4-week estimated timeline.
Deduplication Savings:
By consolidating duplicate requests, engineering can focus on 3 features instead of 5, improving delivery efficiency by 40%.
Next Steps
- Validate technical scope for Enterprise SSO with both EntCo and BigCorp
- Confirm CSV export requirements with MidCo and SmallBiz
- Schedule discovery calls with top 2 revenue clusters
- Create consolidated tickets in product backlog with cross-references
- Notify requesters of consolidation and expected timelines
Methodology Notes
- Clustering based on semantic similarity and technical implementation overlap
- Revenue weighting applied to prioritization recommendations
- Source channels tracked for feedback loop optimization
- Duplicate detection threshold: >70% functional overlap
About This Skill
Deduplicate and cluster feature requests from multiple sources. Identifies duplicates using semantic similarity, merges related requests, clusters into themes, and reveals true demand signals.
View Skill DetailsMore Examples
Ambiguous Case Handling
Tests edge case where all 4 requests relate to 'notifications' but target different channels (mobile, Slack, email, real-time). Demonstrates proper ambiguous case flagging at 72% confidence rather than auto-merging, recommending manual review.
Basic Duplicate Detection
Simple 3-request example demonstrating core duplicate detection. Identifies that 'Slack integration' and 'Integrate with Slack' are semantically identical while keeping 'Dark mode' separate. Shows confidence scoring and demand ranking.