Product Development Opportunity Cost with AI
The Real Cost of Your Feature Choices. AI-Enhanced Decision Making
Most product teams pick features by gut feel, missing the hidden costs of what they're not building. Opportunity Cost thinking reveals the true price of every product decision.
In this newsletter:
The Opportunity Cost Thinking Model
Why Your Feature Prioritization Sucks
The 3-Step Opportunity Cost Evaluation
Quick Start Prompt
Feature Opportunity Analysis Promot to break down the true costs of any product decision by identifying all alternatives and their relative values.
Cross-Functional Trade-off Alignment Prompt to help get your entire team aligned on opportunity cost decisions when different functions have competing priorities.
Template: Opportunity Cost Decision Framework
Use Case Example: SaaS Integration Feature
Implementation Tips
Brandable Workshop Kit [Coach Subscribers]
Not a Coach-level Subscriber? Find out about the Brandable Workshops…
The Problem You're Actually Solving
Sarah's product team just spent three months building a beautiful dashboard that executives requested. Usage is low, customer satisfaction hasn't moved, and they're behind on the core workflow improvements that support actually wanted.
Meanwhile, their main competitor shipped the exact workflow features Sarah's team planned to build next quarter. Now those features look like catch-up work instead of innovation.
Sarah realizes that when they chose to build a dashboard, they also chose not to build workflow improvements, not to enhance their core value proposition, and not to stay ahead of competitors. The dashboard not only cost engineering time; it cost market position.
Every product decision is also a decision about what you're willing to sacrifice.
The Thinking Model: Opportunity Cost
What it is: The value of the best alternative you give up when making a choice. In product development, every feature you build represents multiple features you don't build.
Origin: Economic principle dating to the 1800s, formalized by Austrian economist Friedrich von Wieser
Thinking shortcut:
"If we build this, what are we choosing not to build?"
"What's the best thing we're giving up, and is this choice worth more?"
🤬 Why Your Feature Prioritization Sucks (And How to Fix It)
Most teams' approach:
Collect feature requests from sales, support, executives, and customers
Score features on impact/effort matrices or RICE frameworks
Pick the highest-scoring features that fit in the sprint
Wonder why shipped features don't move key metrics
The Opportunity Cost approach:
For each potential feature, identify what else you could build with those resources
Quantify the value you're giving up with each alternative
Choose based on the best net value after accounting for what you're sacrificing
Ship features, knowing you made the best possible trade-offs
🛠 The 3-Step Opportunity Cost Evaluation
Step 1: Map Your Alternatives
Instead of evaluating features in isolation, list everything your team could build with the same resources. A "simple" dashboard might compete with user onboarding improvements, core feature enhancements, or technical debt reduction.
Step 2: Value the Trade-offs
Estimate the business value of each alternative, not just the effort required. What revenue, retention, or efficiency gains are you giving up by not building each option?
Step 3: Choose Your Sacrifice
Select the option where the value gained exceeds the value of the best alternative you're giving up. You're not just picking features; you're deciding what you're willing to sacrifice.
Quick Start Prompt
I need to prioritize product features using opportunity cost thinking. Help me evaluate trade-offs systematically.
Current situation: [Brief description of your product and team capacity]
Features under consideration: [List 3-5 features with brief descriptions]
Please help me:
Identify what alternatives I'm giving up with each choice
Estimate the relative value of each option and its alternatives
Determine which choice provides the best value after accounting for opportunity costs
Create a simple framework for explaining these trade-offs to stakeholders
Focus on the real costs of what I'm choosing not to build, not just what I am building.
Opportunity Cost Toolkit
Prompt 1: Feature Opportunity Analysis
This prompt helps you break down the true costs of any product decision by identifying all alternatives and their relative values.
I'm making a product development decision and want to understand the full opportunity cost, not just the immediate resource requirements.
Current Context: [Your product stage, team size, key constraints]
Decision: [Specific feature or initiative you're considering]
Resource Requirements: [Time, people, budget needed]
Alternative Options: [List other features/initiatives you could pursue instead]
Business Goals: [Your key metrics and objectives]
Please provide a comprehensive opportunity cost analysis:
ALTERNATIVE MAPPING: What are all the meaningful alternatives I could pursue with these same resources?
VALUE ESTIMATION: For each alternative, estimate potential impact on: Revenue (new/retained), User experience and satisfaction, Competitive position, Technical foundation, Team efficiency.
HIDDEN COSTS: What secondary effects might each choice have?
Opportunity costs of delays to other initiatives
Technical debt implications
Market timing risks
NET VALUE CALCULATION: Which option provides the highest value after subtracting the value of the best alternative I'm giving up?
DECISION FRAMEWORK: Create simple criteria for stakeholders to understand why this trade-off makes sense.
Be specific about quantifiable impacts where possible, and highlight assumptions that should be validated.
Prompt 2: Cross-Functional Trade-off Alignment
This prompt helps get your entire team aligned on opportunity cost decisions when different functions have competing priorities.
My cross-functional product team has different opinions about feature prioritization. Help me facilitate an opportunity cost discussion that gets past departmental preferences.
Team Composition: [List key stakeholders - PM, Engineering, Sales, Support, etc.]
Competing Priorities: [What each function is advocating for and why]
Resource Constraints: [Available development capacity, timeline]
Business Context: [Company stage, key challenges, market pressures]
Help me create alignment using opportunity cost thinking:
SHARED OPPORTUNITY FRAME: What business outcomes do all functions actually agree are most important? Frame alternatives in terms of these shared goals.
COST VISIBILITY: Make explicit what each function's preferred choice would mean giving up:
If we build sales' priority, what does engineering/support give up?
If we build engineering's priority, what does sales/customers give up?
VALUE QUANTIFICATION: How can we estimate the business value of each alternative and its opportunity costs in terms everyone understands?
TRADE-OFF SCENARIOS: Create 3 different approaches that optimize for different opportunity cost profiles:
Scenario A: Minimize revenue opportunity cost
Scenario B: Minimize user experience opportunity cost
Scenario C: Minimize technical opportunity cost
ALIGNMENT PROCESS: What decision-making process would help the team choose between scenarios based on current business priorities rather than functional preferences?
Focus on making opportunity costs visible and comparable across different types of value.
✅ Template: Opportunity Cost Decision Framework
Use this template to systematically evaluate any product decision:
Decision Criteria:
Highest Net Value (Direct Value - Opportunity Cost)
Acceptable Timeline Risk
Alignment with strategic priorities
🎯 Use Case Example: SaaS Integration Feature
Context: 50-person B2B SaaS company, 6 developers, choosing between building Slack integration, improving core analytics, or enhancing mobile app.
Traditional Approach: Score each feature on impact/effort. Slack integration wins because customers requested it and seems high-impact, low-effort.
Opportunity Cost Analysis:
Slack integration: +$15K MRR, but gives up analytics improvements (+$35K MRR) = -$20K net value
Analytics improvements: +$35K MRR, but gives up Slack integration (+$15K MRR) = +$20K net value
Mobile enhancements: +$25K MRR, but gives up analytics improvements (+$35K MRR) = -$10K net value
Result: Analytics improvements provide the best net value. Slack integration, despite being "requested," has the worst opportunity cost profile.
Key Insight: The loudest customer requests aren't always the best use of resources when you account for what you're giving up.
🧠 Implementation Tips:
Quantify everything: Assign dollar values, user counts, or other metrics to make opportunity costs comparable across different types of features
Consider timing: Opportunity costs change based on market conditions. What you give up building a competitive feature today might be different than next quarter
Include technical debt: Factor in how each choice affects your ability to build future features—some options preserve optionality while others limit it
This Week's Challenge
Pick one product decision your team is debating this week. Use the Quick Start Prompt to map out the real opportunity costs of each option.
Leave a comment and tell me what you discovered.