Building a Business Case and Financial Justification
In short A business case argues that a change is worth its cost and risk. A strong one compares realistic options, checks feasibility, separates hard numbers from soft benefits, and is revisited at every decision point until the benefits are delivered.
Based on: D. Paul, D. Yeates, J. Cadle (eds.), Business Analysis (BCS), 2nd ed., ch. 13 “Making a Business and Financial Case”; IIBA, BABOK® Guide v3, techniques Business Cases and Financial Analysis.
On this page
Key ideas#
A living document with decision gates#
The BCS book treats the business case as something you revisit at each decision gate: a checkpoint where the organization asks whether the project is still worth continuing. Typical gates: after the feasibility study, after requirements analysis, after solution design, before implementation, and at a post-project benefits review.
Options, including “do nothing”#
Separate business options (what the change must achieve) from technical options (how to deliver it). Generate ideas widely, then shortlist three or four; more is impractical to analyze properly. Options often differ in time, cost and scope: basic, basic plus extras, full. Always include do nothing. Sometimes it is the best choice; if not, spelling out the risks of inaction strengthens the case.
Feasibility#
- Business: fit with strategy, market timing, culture, existing processes and skills, legality.
- Technical: performance, reliability, security, scalability, compatibility, available skills, how proven the technology is.
- Financial: fits the budget, funding is available, acceptable return, cash flow and payback.
A force-field analysis lists the forces for and against an option. If the forces against are stronger, the option will not work in its current form.
Costs and benefits#
The BCS authors classify both on two axes: tangible or intangible (can it be credibly valued in money?) and immediate or longer-term. - Often forgotten costs: business staff time for fact-finding, testing and training; ongoing support. - Avoided costs count as benefits: compare the new solution not with zero, but with what you would spend anyway to keep the old one running. - Intangible benefits (satisfaction, better management information, flexibility): name them clearly but do not invent a money value. Inflated figures undermine trust in the whole case. - Use assumptions the organization already accepts, and stay conservative.
Structure#
Introduction; management summary (often the only part executives read: what was studied, the options, a clear recommendation and the decision needed); current situation; options; cost-benefit analysis; impact assessment; risks; recommendations; appendices. The BCS book suggests presenting benefits before costs.
How to apply it: a worked appraisal#
All figures are invented for The Workshop, a fictional bike-repair chain, for an online booking and parts-ordering system. Amounts are in thousands of US dollars ($k).
| Year 0 | Year 1 | Year 2 | Year 3 | Year 4 | |
|---|---|---|---|---|---|
| One-off cost | −140 | ||||
| Benefits | 70 | 70 | 70 | 70 | |
| Running costs | −15 | −15 | −15 | −15 | |
| Net cash flow | −140 | 55 | 55 | 55 | 55 |
| Cumulative | −140 | −85 | −30 | +25 | +80 |
One-off cost: development 120 plus business staff time 20. Benefits: front-desk time saved 30, fewer no-shows 25, lower parts stock 15.
1. Payback. Payback period = how long until the cumulative net cash flow turns positive. After year 2, 30 is still unrecovered; year 3 brings 55, so payback ≈ 2 + 30/55 ≈ 2.5 years. Easy to explain, but it treats $1 in year 4 as worth the same as $1 today.
2. Discounted cash flow and NPV. Money received later is worth less than money now, because you could invest it meanwhile. - Discount factor = 1 / (1 + r)^n: what $1 received in year n is worth today if money can earn r per year elsewhere. At r = 10%: 0.909, 0.826, 0.751, 0.683 for years 1–4. - Present value = net cash flow × discount factor: 55 × 0.909 ≈ 50.0 in year 1, then 45.4, 41.3 and 37.6. - NPV (net present value) = the sum of all present values, including the year-0 investment. 50.0 + 45.4 + 41.3 + 37.6 − 140 ≈ +34.3. A positive NPV means the project beats the 10% return available elsewhere.
On a discounted basis, cumulative value turns positive only in year 4, not year 3. The BCS book’s own example shows the same effect: discounting gives a more cautious and usually more realistic picture. (The book labels the investment year “year 1” with a factor of 1.000; same idea.)
3. Sensitivity analysis. Recalculate under different assumptions. At 15%, NPV ≈ +17.1; at 20%, ≈ +2.3. More telling: if benefits are 20% lower (56 a year instead of 70), NPV at 10% falls to ≈ −10.1. The decision hinges on the benefit estimates, so challenge those first.
4. IRR. Internal rate of return = the discount rate at which NPV is exactly zero. You find it by trial or with a spreadsheet function; here it is about 21%. If the organization can earn more than that elsewhere, the investment does not pay. IRR ignores scale: a small project can have a higher IRR yet earn less money. As the BCS authors note, most finance texts prefer NPV, while managers like IRR’s single number.
Benefits management#
The BCS book recommends three practices: - A benefits map, built right to left: business objective ← benefits ← business changes ← enabling changes. It usually has one IT stream and several non-IT streams (training, marketing), each with an owner. - Planned reviews at each gate, plus unplanned reviews after major change requests, stakeholder changes or shifts in strategy. - A benefits realization report, sometimes months after go-live. It triggers actions to capture missing benefits, shows whether the money was well spent, and improves future estimates.
Pitfalls#
- Comparing with zero → compare with doing nothing, including avoided costs.
- Pricing intangible benefits → describe them and let decision makers weigh them.
- Writing the case once → revisit it at every gate, and stop if it no longer holds.
Sources and further reading#
- D. Paul, D. Yeates, J. Cadle (eds.). Business Analysis, 2nd ed. BCS, The Chartered Institute for IT, 2010, ch. 13 “Making a Business and Financial Case”.
- IIBA. A Guide to the Business Analysis Body of Knowledge (BABOK® Guide), version 3. International Institute of Business Analysis, 2015, techniques Business Cases and Financial Analysis.