How to Build a Business Case for a New Feature
A business case translates a product idea into investment terms that leadership can evaluate. It answers: should we spend engineering time on this, and what do we expect in return?
This guide covers how to build a business case that is rigorous enough to be credible but practical enough to complete in a day.
Step-by-step guide
Step 1: Define the problem and opportunity
Start with the user problem: who has it, how severe it is, and what evidence you have. Then quantify the opportunity: how many users are affected, what is the revenue impact, and what happens if you do not solve it.
Step 2: Estimate the cost
Work with engineering to estimate the cost: person-weeks of development, design time, QA time, and ongoing maintenance. Convert to dollars using fully-loaded cost (salary + benefits + overhead, typically 2x salary). This gives you the investment side of the equation.
Step 3: Project the return
Estimate the expected return: new revenue (if the feature unlocks deals), retained revenue (if the feature reduces churn), or efficiency gains (if the feature saves time). Use ranges: best case, expected case, worst case. Show the payback period: how many months until the return exceeds the investment.
Step 4: Assess the alternatives
What happens if you do not build this? What are the alternative approaches? Could you partner, buy, or use an existing tool instead of building? Showing that you considered alternatives strengthens the case.
Step 5: Make the recommendation
End with a clear recommendation: build or do not build, and why. Include the key assumptions that, if wrong, would change the recommendation. This shows intellectual honesty and gives leadership confidence in your analysis.
Common mistakes
Only showing the upside
A business case that only presents the positive scenario is not credible. Include risks, assumptions, and the worst-case scenario. Leaders trust PMs who show both sides.
Ignoring opportunity cost
Every feature you build means another feature you do not. Include what you are giving up by investing in this feature.
Tips
- Use a one-page format: problem, cost, return, recommendation
- Get engineering sign-off on the cost estimate before presenting
- Update the business case 90 days after launch with actual results
How Vantage helps
Vantage connects product analytics to PRD generation, making it easier to build evidence-based business cases. When you create a project in Vantage, analytics data and user research ground the spec in real business context.