Opportunity Cost
What is Opportunity Cost?
Opportunity cost is what you forgo by choosing one use of money, time or people over the best alternative use. It explains why a project with a positive return still needs to beat other options, especially when team time is scarce.
Updated November 2026 · 3 min read
Opportunity cost is the value of the best alternative you give up when you choose one option over another. Every choice to spend money, time or people on one thing is also a choice not to spend them on something else, and opportunity cost puts a value on that something else. If a team spends a quarter building feature A, the opportunity cost is what the best alternative use of that quarter would have delivered.
The idea is a foundation of economics, built on the fact that resources are limited. In business, it explains why "this project has a positive return" is not enough to justify it: the project should also beat the best other use of the same resources. For product and operations teams, the scarcest resource is usually people's time, which makes opportunity cost central to prioritization.
How to calculate opportunity cost
A simple formula: opportunity cost = return of the best option not chosen - return of the option chosen. When the chosen option is the best one, this difference is zero or negative, meaning the choice gave up nothing better. In everyday use, people often describe the opportunity cost simply as the value of the best alternative forgone.
Two rules keep the calculation honest:
- Compare only with the next best alternative. The opportunity cost is what the single best alternative would have delivered, not the sum of every alternative, because you could only have done one of them with the same resources.
- Use the same units and time period. Compare expected value over the same horizon, adjusting for risk where options differ in certainty.
Explicit vs. implicit costs
| Cost type | Meaning | Example |
|---|---|---|
| Explicit cost | Money actually paid out | Salaries, software licenses, contractor fees |
| Implicit cost (opportunity cost) | Value of the alternative use of resources already owned | Returns from the project the same engineers could have built instead |
Accounting records explicit costs. Opportunity costs never appear on a financial statement, which is why they are easy to overlook in planning.
Opportunity cost in product and operations
- Feature prioritization. Every item on the roadmap pushes something else back. Frameworks such as RICE make the comparison explicit.
- Customer requests. Building a custom feature for one large customer has an opportunity cost in work for the rest of the customer base.
- Technical debt. Time spent on fixes is time not spent on features, and time not spent on fixes slows future features. Both sides carry opportunity costs.
- Delay. Postponing a valuable project has its own cost, captured in cost of delay.
- Capital and budget. Money tied up in one investment cannot fund another, which is why finance teams compare projects against a required return. See cost of capital.
A hypothetical example
Consider a hypothetical SaaS company with one six-person engineering team available next quarter and three options, each needing the full team for the quarter:
- Option A: single sign-on for enterprise customers, expected to win deals worth $400,000 in new ARR.
- Option B: a new integration, expected to add $300,000 in new ARR.
- Option C: onboarding improvements, expected to prevent $250,000 in churned ARR.
If the company chooses A, its opportunity cost in the everyday sense is $300,000, the value of B, the best option not chosen. It is not $550,000 (B plus C), because the team could only have done one of them. Since A's expected value exceeds B's by $100,000, A is the better choice on these estimates. But the estimates carry different levels of confidence: C protects revenue the company already has and can see in its churn data, while A and B depend on new sales that have not happened. If the team discounts A and B to 60% confidence and keeps C at full value, their risk-adjusted values become $240,000 (60% of $400,000) and $180,000 (60% of $300,000). C, at $250,000, becomes the best option, and the decision changes. Opportunity cost analysis is only as good as the estimates behind it.
Common pitfalls
- Ignoring it entirely. Judging a project only on its own return hides better uses of the same resources.
- Adding up all alternatives. Only the best alternative forgone counts.
- Confusing it with sunk cost. Money already spent is gone whatever you choose next. See sunk cost fallacy.
- Forgetting time. People's attention and calendar time are often more constrained than budget.
- False precision. Opportunity costs rest on forecasts. Use ranges and confidence levels, not a single exact number.
Opportunity cost underpins prioritization, resource allocation and cost-benefit analysis. It is also the reasoning behind weighted shortest job first, which ranks work by the value lost while it waits.
Frequently asked questions
How do you calculate opportunity cost?
Opportunity cost equals the return of the best option not chosen minus the return of the option chosen. Compare only against the single next best alternative, not the sum of all alternatives, since the same resources could only have funded one of them. Measure both options in the same units over the same period, adjusting for risk where their certainty differs.
Is opportunity cost an explicit or implicit cost?
Opportunity cost is an implicit cost. Explicit costs are money actually paid out, such as salaries, software licenses and contractor fees, and they appear in accounting records. Opportunity cost is the value of the alternative use of resources already owned, such as what the same engineers could have built instead. It never appears on a financial statement, so it is easy to overlook.
How does opportunity cost affect product prioritization?
Every roadmap item pushes something else back, so the real cost of a feature includes what the team could have built instead. A positive return alone does not justify a project; it should beat the best other use of the same people's time. Frameworks such as RICE make that comparison explicit, and cost of delay captures what postponing valuable work costs.
Related terms
Cost of Delay (CoD)
The value lost for each unit of time work is not shipped.
Resource Allocation
Assigning people and budget to the work that matters most.
Participatory Budgeting
The people affected decide together how a shared budget is split.
Lean Business Case
A short, hypothesis-driven case with an MVP to test the idea first.