Business Case Writing

The business case is the document that justifies why a project should be funded and undertaken. It presents the rationale, expected benefits, costs, risks, and alternatives to decision-makers so they can make an informed go/no-go investment decision.

While the feasibility study asks "Can we do this?", the business case argues "Here's why we should." In PRINCE2, the business case is a living document reviewed at every stage boundary. In PMBOK, it feeds directly into the project charter.

Business Case Structure

A well-structured business case typically includes these components:

Executive Summary

A concise overview of the problem, proposed solution, expected benefits, and total cost. Decision-makers often read only this — make it compelling and complete.

Problem Statement

What business problem or opportunity drives this project? What happens if we do nothing? Quantify the pain: lost revenue, inefficiency costs, compliance risks.

Proposed Solution

The recommended approach. Describe what will be built or changed, at a high level. Link back to the feasibility study for technical details.

Alternatives Considered

What other options were evaluated (including "do nothing")? Why was the proposed solution selected over them? This shows due diligence.

Benefits

Both tangible (revenue increase, cost savings) and intangible (brand reputation, employee satisfaction). Quantify wherever possible.

Cost Estimate

Total cost of ownership: development costs, operational costs, maintenance, licensing, training, and decommissioning of old systems.

Financial Analysis

ROI, NPV, payback period, and/or IRR. The numbers that prove the investment is sound. Sourced from the feasibility study.

Risks & Mitigations

Key risks that could derail the project and planned mitigation strategies. Show that risks have been thought through, not ignored.

Timeline

High-level delivery schedule with major milestones. When will benefits start being realized?

Recommendation

A clear, actionable recommendation: proceed, proceed with conditions, or do not proceed. Include the decision needed from the audience.

Types of Benefits

Benefits are the core of the business case. Categorizing them helps stakeholders understand the full value picture:

Tangible Directly measurable in financial terms. Revenue growth, cost reduction, time savings. Example: "Reduce processing time by 60%, saving $200K/year."

Intangible Real but hard to quantify. Improved customer satisfaction, brand perception, employee morale, competitive positioning.

Strategic Long-term organizational advantages. Market positioning, regulatory compliance, capability building, enabling future initiatives.

Writing Tips

1. Know Your Audience

Executives want the bottom line: cost, benefit, risk, timeline. Technical leads want feasibility details. Financial controllers want the numbers. Tailor the emphasis — not the content — to who will read and approve it.

2. Quantify Everything You Can

Vague benefits like "improve efficiency" are weak. Strong business cases say: "Reduce order processing from 48 hours to 4 hours, enabling same-day fulfillment and projected 12% increase in customer retention." Even intangible benefits can be bounded with estimates.

3. Be Honest About Risks

A business case that shows only upside is not credible. Acknowledging risks and presenting mitigation strategies builds trust with decision-makers. They know nothing is risk-free — they want to know you've thought it through.

4. Include the "Do Nothing" Option

Always present the cost of inaction. What happens if we don't do this project? Lost market share? Regulatory penalties? Continued inefficiency? The "do nothing" cost is the benchmark against which all other options are measured.

5. Keep It Concise

A business case is not a novel. Most effective business cases are 5–15 pages, with detailed financial models in appendices. Lead with the executive summary and make every section earn its place.

Business Case Lifecycle

The business case is not a one-time document — especially in PRINCE2, where it's reviewed throughout the project:

Stage	Business Case Activity
Pre-Project	Outline business case created to justify starting formal initiation
Initiation	Detailed business case developed with full financial analysis
Stage Boundaries	Reviewed and updated — is the project still justified given what we now know?
Closure	Final review — were benefits achieved? Plan for post-project benefits realization

The business case answers the most fundamental question any sponsor asks: "Why should I give you this money?" A strong business case doesn't just present numbers — it tells a story. It connects a real business problem to a concrete solution, backs it with evidence, and paints a clear picture of the return. Projects with weak or absent business cases are the first to be defunded when budgets tighten. Make yours bulletproof.