Business Case and Project Selection: ROI, NPV and Payback Explained With Examples

Organisations always have more project ideas than money, people or attention. A well-run organisation therefore asks, before spending a rupee on delivery, should we do this project at all, and is it better than the alternatives? The tool for that decision is the business case, and the process is project selection. Project managers are often asked to help prepare the numbers, and even when they are not, understanding them helps you defend your project later.

What Is a Business Case?

A business case is a document that justifies investing in a project by comparing expected benefits with expected costs and risks. It answers: what problem or opportunity exists, what options are available, what will each cost, what do we gain and what is the recommended choice?

Contents of a Good Business Case

  1. Problem or opportunity: the business need in plain words, with evidence.
  2. Objectives: what success looks like, in measurable terms.
  3. Options analysed: including “do nothing”, which is always an option and sets the baseline.
  4. Costs: one-time (development, licences, hardware, training) and ongoing (support, subscriptions).
  5. Benefits: financial (savings, revenue) and non-financial (compliance, customer satisfaction).
  6. Risks and assumptions: what could change the numbers.
  7. Financial analysis: ROI, NPV, payback period or similar.
  8. Recommendation: the preferred option and why.
  9. Timeline and high-level approach: enough detail to judge feasibility.

Financial Measures

Return on Investment (ROI)

ROI = (total benefits − total costs) ÷ total costs. It is simple, but ignores the timing of cash flows.

Payback Period

The time needed for cumulative benefits to equal the investment. It is easy to understand and highlights liquidity risk, but ignores benefits after payback and the time value of money.

Net Present Value (NPV)

NPV converts future cash flows into today’s value using a discount rate, then subtracts the initial investment. A positive NPV means the project returns more than the required rate. It is the most rigorous of the three because it recognises that a rupee received next year is worth less than a rupee today.

Worked Example

A company considers a warehouse management system. The investment is ₹50 lakh now. It is expected to save ₹20 lakh a year for four years. The company’s discount rate is 10 per cent.

YearBenefit (₹ lakh)Discount factor at 10%Present value (₹ lakh)
1200.909118.18
2200.826416.53
3200.751315.03
4200.683013.66
Total8063.40
  • Simple ROI: (80 − 50) ÷ 50 = 60 per cent over four years.
  • Payback period: 50 ÷ 20 = 2.5 years.
  • NPV: 63.40 − 50 = ₹13.40 lakh, which is positive, so the project clears the 10 per cent hurdle.

If benefits are delayed or the rate is higher, the NPV could turn negative. That is why the business case should state the assumptions behind each number, and test them with a sensitivity check such as “what if savings are only ₹15 lakh a year?”

Non-Financial and Mandatory Projects

Not every project is justified by money. Compliance deadlines, security fixes and end-of-support upgrades are often mandatory. In these cases the business case compares ways of meeting the requirement at the lowest cost and risk, instead of proving a profit. Benefits such as improved customer experience can be described using measurable proxies, for example reduced complaint volume or faster response time.

Weighted Scoring Models

When projects compete, organisations often use a weighted scoring model. Criteria are chosen and weighted, each project is scored against them, and the totals guide the ranking.

CriterionWeightProject A score (1–5)Project B score (1–5)
Strategic alignment30%53
Financial return25%35
Risk (5 = low risk)20%42
Resource availability15%34
Urgency10%24
Weighted total100%3.703.55

Project A: 0.30×5 + 0.25×3 + 0.20×4 + 0.15×3 + 0.10×2 = 1.50 + 0.75 + 0.80 + 0.45 + 0.20 = 3.70. Project B: 0.90 + 1.25 + 0.40 + 0.60 + 0.40 = 3.55. Project A therefore ranks slightly higher despite its weaker financial return, because it scores well on strategy and risk. Scoring models are aids to discussion, not oracles; if the result surprises the committee, examine the weights.

Benefits Realisation

A business case is a promise. Assign an owner to each benefit, define how and when it will be measured and plan to check it after delivery. Without ownership, benefits quietly disappear after the project team disbands. We return to this in Project Closure and Lessons Learned.

Common Mistakes

  • Starting with the solution and working backwards to justify it.
  • Counting optimistic benefits while understating ongoing support costs.
  • Leaving out the “do nothing” option.
  • Never revisiting the business case when assumptions change.
Key takeaways
  • A business case compares options by benefits, costs and risk, including “do nothing”.
  • ROI is simple, payback shows speed of recovery, and NPV accounts for the time value of money.
  • Weighted scoring helps compare projects, but the weights deserve debate.
  • Name benefit owners and review the case at every gate.

Related Lessons