Opportunity Management
Organize, prioritize, and track product opportunities from customer feedback to shipped features. Make data-driven product decisions.
How Do You Turn Raw Feedback Into Action?
Raw customer feedback is overwhelming. Hundreds of signals from Slack, support tickets, sales calls, and surveys. How do you make sense of it all?
Ship transforms chaos into clarity. Our opportunity management system organizes feedback into actionable opportunities, helps you prioritize based on real data, and tracks progress from idea to shipped feature.
What Is an Opportunity?
An opportunity represents a customer need worth exploring. It’s not a feature spec or a user story. It’s the problem space — a concept rooted in Opportunity Solution Trees, a framework by Teresa Torres for structuring product discovery.
Opportunity Anatomy
┌─────────────────────────────────────────┐
│ Data Export & Integration │
├─────────────────────────────────────────┤
│ Status: Prioritized │
│ Signals: 23 │ Trend: ↑ Growing │
├─────────────────────────────────────────┤
│ Customers need to get data out of the │
│ system for external analysis and │
│ reporting. │
├─────────────────────────────────────────┤
│ Evidence: │
│ • "Need CSV export" - Customer A │
│ • "Can't connect to BI tool" - Cust. B │
│ • "Export for finance team" - Cust. C │
│ [+20 more signals] │
├─────────────────────────────────────────┤
│ [Send to Agent] [Create Linear Issue] │
└─────────────────────────────────────────┘
Opportunities vs. Other Concepts
| Concept | Focus | Example |
|---|---|---|
| Opportunity | Customer need | ”Data portability” |
| User Story | Solution | ”Export to CSV” |
| Issue | Implementation | ”ENG-123: Add CSV button” |
| Feature | Shipped result | ”CSV Export (v2.1)” |
Opportunities live upstream. They’re about understanding what customers need before deciding how to address it.
The Opportunity Lifecycle
1. New
Opportunities are created automatically when Ship clusters related signals. New opportunities appear in your dashboard for review.
Your job: Review the signals. Does this represent a real pattern? Is it relevant to your product?
2. Prioritized
After review, promote promising opportunities to “Prioritized.” These are needs you’ve validated and plan to address.
Your job: Compare opportunities. Which has the strongest signal? Which aligns with strategy? Which customers are affected?
3. In Progress
When you start working on an opportunity, whether that’s further research, design, or development, mark it “In Progress.”
Your job: Track progress. Create Linear issues. Hand off to AI coding assistants. Monitor for new related signals.
4. Shipped
When the feature addressing the opportunity is live, mark it “Shipped.” This closes the loop from feedback to feature.
Your job: Consider notifying customers who requested it. Review if the solution fully addressed the need.
How Does Data-Driven Prioritization Work?
Ship gives you real data to prioritize opportunities — moving beyond the gut-feel approaches that most product teams still rely on:
Signal Count
How many distinct pieces of feedback mention this need? More signals = more customers affected.
Opportunity A: 47 signals → High demand
Opportunity B: 3 signals → Niche need
Signal Trend
Is this need growing or stable? Trending opportunities might be worth addressing before they become critical.
Opportunity A: +12 signals this week ↑
Opportunity B: Stable for 30 days →
Customer Segments
Which customers are asking? Enterprise customers? Free users? At-risk accounts?
Opportunity A: 80% Enterprise customers
Opportunity B: 90% Free tier users
Source Distribution
Where is feedback coming from? Different sources carry different weight.
Opportunity A:
- 10 support tickets
- 5 lost deal reasons
- 3 churn reasons
Opportunity B:
- 15 Slack messages
- 2 internal suggestions
Working with Opportunities
Daily Review
Spend 5 minutes reviewing new opportunities:
- Any surprising patterns?
- New urgent needs?
- Signals that should be reclustered?
Weekly Prioritization
Spend 30 minutes comparing prioritized opportunities:
- Which should move to “In Progress”?
- Any deprioritize based on new info?
- Team alignment on priorities?
Sprint Planning
Use opportunities to inform sprint planning:
- Which opportunities are ready for development?
- Hand off to AI coding assistants
- Create Linear issues with full context
Features for Teams
Shared Workspaces
Your whole product team can access opportunities:
- PMs prioritize and manage
- Designers review for context
- Engineers understand customer needs
- Leaders track progress
Comments and Discussion
Discuss opportunities within Ship:
- Debate prioritization
- Share additional context
- Note concerns or constraints
Activity History
See the full history of an opportunity:
- When signals were added
- Status changes
- Comments and discussions
- Handoffs and issue creation
Integrations
Opportunities connect to your workflow:
Linear
- Create issues directly from opportunities
- Include all customer evidence
- Link back to Ship for context
Cursor / Claude Code
- Generate AI prompts from opportunities
- Include customer quotes and requirements
- Ship features faster
Slack
- Get notified of significant opportunity changes
- Share opportunities in channels
- Discuss with your team
How Do You Measure Opportunity Management Success?
Track your opportunity management effectiveness. For a deeper dive, see our guide on feature prioritization with AI signals:
Throughput
How many opportunities move from New → Shipped per month?
Cycle Time
How long from signal arrival to shipped feature?
Signal Coverage
What percentage of feedback becomes actionable opportunities?
Customer Impact
Are shipped features addressing real customer needs?
Best Practices
Don’t Over-Prioritize
Not every opportunity needs to be “Prioritized.” It’s okay to have many “New” opportunities. Focus your active attention on a manageable number.
Review Signals, Not Just Titles
AI-generated titles are helpful but not perfect. Click into opportunities and read the actual signals before prioritizing.
Update Status Regularly
Stale statuses make the system less useful. Update opportunities as they move through development.
Use Opportunities for Communication
Share opportunities with stakeholders to show the “why” behind product decisions. Customer evidence is more compelling than opinions.
Getting Started
Opportunity management starts automatically when you connect feedback sources:
- Connect Slack and/or Linear
- Signals flow into Ship
- AI clusters signals into opportunities
- Review and prioritize
- Hand off to development
- Track to shipped
No setup required for opportunities. They emerge naturally from your customer feedback.
Frequently Asked Questions
What is an opportunity in Ship?
How are opportunities different from user stories or issues?
Can I manually create opportunities?
How do I prioritize opportunities?
Can I track opportunity status through development?
How do I handle duplicate opportunities?
Can I share opportunities with my team?
What happens to opportunities after features ship?
Ready to ship faster?
Turn customer feedback into shipped features with AI-powered product management.
Start free trial →