ROI Calculation Template
Extracted from CloudOps-Runbooks business case structure. The specific numbers are project-dependent — the CALCULATION FRAMEWORK is reusable.
Purpose
Every significant initiative needs a business case. This template provides the structure for calculating ROI honestly — with validated inputs, not aspirational projections.
Structure
1. Investment Costs
| Cost Category | Description | How to Measure |
|---|---|---|
| Development | Engineering time × rate | Actual hours logged per sprint |
| Infrastructure | Cloud/tool costs incurred | AWS Cost Explorer, billing data |
| Tooling | License/subscription costs | Procurement records |
| Opportunity cost | What the team could have done instead | Backlog items deferred |
Rule: Use actual costs, not estimates. If the work hasn't started, use conservative estimates based on similar past work.
2. Value Delivered
| Value Category | Description | How to Measure |
|---|---|---|
| Cost reduction | Savings from optimisation | Before/after comparison with same time period |
| Time savings | Operational efficiency gains | Before/after time measurements for same tasks |
| Risk reduction | Compliance/security improvements | Audit findings before/after |
| Revenue enablement | Capabilities that unlock new revenue | Indirect — document the capability, not projected revenue |
Rule: Only include value that has been measured or can be measured within 30 days of implementation.
3. ROI Calculation
Total Investment = Development + Infrastructure + Tooling + Opportunity Cost
Annual Value = Cost Reduction + Time Savings + Risk Reduction
ROI = (Annual Value - Total Investment) / Total Investment × 100%
Payback Period = Total Investment / (Annual Value / 12)
4. Confidence Levels
Every ROI calculation should include a confidence qualifier:
| Confidence | When to Use | How to Present |
|---|---|---|
| Validated | Based on measured before/after data | "Validated: [number] based on [measurement]" |
| Estimated | Based on similar past projects | "Estimated: [range] based on [comparable]" |
| Projected | Based on modelling without validation | "Projected: [range] — requires validation" |
Rule: Never present projected numbers as validated. Always include the confidence qualifier.
Template
Executive Summary
- Initiative: [name]
- Investment: [total cost with confidence level]
- Expected value: [annual with confidence level]
- ROI: [percentage with confidence level]
- Payback: [months with confidence level]
Cost Breakdown
| Item | Amount | Confidence | Evidence |
|---|---|---|---|
| [cost item] | [amount] | Validated/Estimated/Projected | [evidence path] |
Value Breakdown
| Item | Annual Value | Confidence | Measurement Method |
|---|---|---|---|
| [value item] | [amount] | Validated/Estimated/Projected | [how measured] |
Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Value doesn't materialise | [L/M/H] | [description] | [mitigation] |
| Costs exceed estimate | [L/M/H] | [description] | [mitigation] |
| Timeline slips | [L/M/H] | [description] | [mitigation] |
Decision Options
| Option | Investment | Expected Value | ROI | Risk | Recommendation |
|---|---|---|---|---|---|
| Proceed | [amount] | [amount] | [%] | [L/M/H] | [rationale] |
| Defer | [opportunity cost] | [lost value] | N/A | [risk of waiting] | [rationale] |
| Cancel | [sunk cost] | $0 | Negative | [risk of not doing] | [rationale] |
Anti-Patterns
| Anti-Pattern | Why It Fails |
|---|---|
| Using projected savings as the headline number | Creates expectations that may not materialise |
| Ignoring opportunity cost in investment total | Understates true cost |
| Counting "potential" savings across all scenarios simultaneously | Scenarios have dependencies; total ≠ sum of parts |
| Presenting ROI without confidence level | Stakeholders can't assess reliability |
| Calculating ROI before implementation | Only post-implementation ROI is real |
Validation Checklist
Before presenting any business case:
- All investment costs use actual or conservative estimates
- All value claims include confidence level (Validated/Estimated/Projected)
- Evidence paths provided for validated numbers
- Risk assessment includes "value doesn't materialise" scenario
- At least two decision options presented (proceed + alternative)
- No projected numbers presented as validated
Origin: CloudOps-Runbooks executive business case structure. Dollar figures removed — the calculation framework is reusable for any consumer project business case.