# Business Case Template

## Cover Page

- ``Project Name``
- `Business Case`
- `Version`1.0``

## Revision History

| Date | Version | Description | Author |
| --- | --- | --- | --- |
| ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` |

## Ownership & Collaboration

- Document Owner: Project Manager
- Contributor Roles: Business Process Analyst, Requirements Reviewer
- Automation Inputs: Market analysis, cost estimates, revenue projections
- Automation Outputs: `business-case.md` with sections 1–6

## 1 Introduction

> Provide purpose, scope, terminology, references, and structure of the business case.

### 1.1 Purpose

### 1.2 Scope

### 1.3 Definitions, Acronyms, and Abbreviations

### 1.4 References

### 1.5 Overview

## 2 Product Description

> Summarize the product concept, problems it solves, and why development is justified (reference the Vision where
> appropriate).

## 3 Business Context

> Describe domain, market, customer segments, contractual environment, and background.

## 4 Product Objectives

> State strategic objectives, success criteria, and milestone outlook (schedule, risk considerations).

## 5 Financial Forecast

> Provide order-of-magnitude cost, revenue, and ROI projections, including assumptions and sensitivity analysis.

## 6 Constraints

> List significant constraints influencing scope, technology choices, compliance, or delivery obligations.

## Appendices (Optional)

> Include cost models, market research, or sensitivity analyses.

## Agent Notes

- Document financial assumptions so sensitivity analysis can be automated.
- Ensure objectives align with the current `vision.md` to avoid conflicting targets.
- Verify the Automation Outputs entry is satisfied before signaling completion.