1) Baseline
2) Automation model
3) Costs
4) Notes
Baseline losses (per year)
Only inputs that users can reliably know today.
Use: revenue + SLA penalties + support overtime (blended).
Use: incident log / monitoring history (last 12 months).
Include: Dev + QA + SRE who touch deployments.
Examples: manual deploys, env fixes, release meetings, firefighting.
Tip: loaded cost ≈ salary + benefits + overhead.
Use: average of last 3 months bill.
Examples: idle resources, non‑prod always‑on, over‑provisioning.
Baseline downtime loss
$0
Baseline toil loss
$0
Baseline cloud waste
$0
Total baseline loss
$0
Automation model (auto‑calculates expected gains)
Pick a target automation level; the calculator applies industry-standard benchmarks to compute expected savings.
All percentages are conservative and based on typical DevOps implementations.
How it works: Each level automatically applies reduction percentages to your baseline losses.
Choose the level that matches your target state in 6–12 months.
When to use "Yes": Your business model benefits from faster deployments (e.g., faster feature releases = less churn, higher conversions). Leave as "No" for infrastructure/platform services.
Downtime reduction target
—
Toil reduction target
—
Cloud waste reduction target
—
Revenue uplift target (if enabled)
—
Why these percentages?
Starter: Basic CI/CD pipeline + monitoring. Quickest to implement, lowest risk.
Standard: CI/CD + Infrastructure-as-Code + guardrails + observability. Typical 6–9 month payback.
Advanced: Platform engineering with self-service, paved roads, cost controls. Strongest long-term gains.
Starter: Basic CI/CD pipeline + monitoring. Quickest to implement, lowest risk.
Standard: CI/CD + Infrastructure-as-Code + guardrails + observability. Typical 6–9 month payback.
Advanced: Platform engineering with self-service, paved roads, cost controls. Strongest long-term gains.
Investment costs (Year 1)
These are the only “cost” inputs required to compute ROI.
Includes: CI/CD, IaC, enablement, handover playbooks.
Includes: monitoring, scanning, artifact mgmt, CI runners (if needed).
Tip: keep as 0 if you want an “external-only” ROI view.
Assumptions & notes
This improves trust when sharing with CFO/CEO.