# Cloud cost decision record Copy one record per material architecture choice. Unknown is not zero. Example rates in the article are illustrative, not quotes. ## Decision and authority - Decision ID / date / expiry: - Service and business outcome: - Service owner (budget and customer promise): - Engineering owner (authority to change the system): - Finance partner (accounting and allocation basis): - State: Explore / Trial / Adopt. Record evidence for advancing: ## Business unit - Accepted unit definition, exclusions (retries, rejected work, tests): - Independent counter and reconciliation source: - Baseline period, timezone, volume; expected demand range: ## Reproducible cost model | Driver | Measured quantity | Contracted effective rate | Baseline cost | Proposed quantity/cost | Evidence / owner | |---|---:|---:|---:|---:|---| | Compute | | | | | | | Data services | | | | | | | Observability | | | | | | | Transfer | | | | | | | Shared allocation (not automatically avoidable) | | | | | | - Accounting basis, discounts, cash-vs-effective reconciliation: - Monthly totals and cost per 1,000 accepted units: - Avoidable recurring difference, excluding mere allocation shifts: - Implementation hours × internal rate, test costs, other one-time costs: - Simple payback = one-time cost / monthly recurring difference: - Sensitivity: halve the recurring difference; recompute payback: ## Service and evidence gates - Customer promise / percentile / load profile / observation period: - Retention and investigation requirements; authorising owner: - Trial scope and representative peaks: - Leading signals (quantity driver, queue age, trace coverage): - Failure trigger, observer, rollback action and tested recovery time: - Do not advance if any material gate remains unknown: ## Review - Actual versus modelled quantities and units: - Reliability and investigation evidence: - Denominator reconciliation; shared-cost double-count check: - Adopt / revise / revert decision, owner and date: - Reopen on demand, price, topology or retention-policy changes: ## Filled illustrative arithmetic (replace with measured inputs) - Volume: 12,000,000 accepted orders/month; 730 hours/month. - Workers: 8 × 730 × $0.20 = $1,168 baseline; (2 × 600 + 8 × 130) × $0.20 = $448 proposed; 2,240 proposed instance-hours; difference $720. - Database: 730 × $1.10 = $803; logs: 900 × $2 = $1,800 baseline, (900 − 600) × $2 = $600 proposed; difference $1,200. - Transfer: 2,000 × $0.08 = $160; shared allocation: $300 (unchanged, not avoidable). - Baseline: $1,168 + $803 + $1,800 + $160 + $300 = $4,231/month. - Proposal: $448 + $803 + $600 + $160 + $300 = $2,311/month. - Difference: $4,231 − $2,311 = $1,920/month (modelled, not realised). - Per 1,000 accepted orders: $4,231 ÷ 12,000,000 × 1,000 = $0.353 baseline; $2,311 ÷ 12,000,000 × 1,000 = $0.193 proposed (rounded). - Investment: 40 × $100 + $300 = $4,300. Payback: $4,300 ÷ $1,920 = 2.24 months; at $600/month difference, 7.17 months. - Sensitivity prompt above halves the difference to $960/month: 4.48 months; the article's $600 scenario is a separate, more conservative assumption. ## Evidence-state flow Explore → Trial → Adopt, never automatic. Explore: engineering and finance reconcile quantity × rate and independent accepted orders; unresolved retention authority or untested rollback blocks advancement. Trial: engineering uses limited scope over seven representative days; illustrative targets are 95% within 60s and 99% within 180s, plus investigation coverage and the agreed cost envelope. STOP on service-target breach or lost investigation evidence: engineering restores eight workers and required logs, records recovery and reopens Explore. Adopt: service owner signs with finance only when service AND cost gates pass; reopen on demand, rates, topology or retention-policy changes. Accessible brand SVG: ../img/cloud-cost-decision-flow.svg