Establish the baseline
Reconcile current actual cost by scope, service, charge type, and currency before declaring opportunity.
- Owner
- Finance / FinOps
- Cadence
- Monthly
- Verify
- Baseline ties to agreed billing data.
Preparing this Costframe view
Preparing this Costframe viewCostframe field guide
Cloud cost optimization reduces unnecessary spend while preserving the performance, resilience, security, and delivery speed the business needs. Strong programs sequence low-risk waste removal before rightsizing and commitments, attach available evidence and confidence limits to recommendations, and report estimates on a configured net-rate or provider-billed-cost basis where that evidence exists.
Framework
Remove orphaned or intentionally retired resources after dependency and retention checks.
Match capacity to observed demand using a representative window and workload-specific constraints.
Change architecture or service choice only when engineering effort, reliability, and migration risk justify it.
Apply reservations or savings plans to a stable baseline after accounting for existing coverage and planned change.
Implementation playbook
Reconcile current actual cost by scope, service, charge type, and currency before declaring opportunity.
Review unattached, empty, stopped-but-billing, unused, and expired resources with dependency checks.
Use sustained metrics and peak behavior to propose rightsizing; test before production rollout.
Evaluate commitments against the remaining stable baseline, using net economics and utilization risk.
Worked example
Separating these classes prevents dashboards from presenting every finding as money in the bank.
Evidence standard
Costframe separates observed evidence from inference. Every finding can show what was checked, what was unavailable, why confidence may be lower, and whether the action still needs approval.

Decision tree
If source data is missing or stale, record the limitation before quoting impact.
If no team owns the resource, assign ownership before opening a change.
Treat the number as estimated until follow-up billing evidence supports it.
Failure modes
FAQ
Use it as an operating framework, then verify the resource, owner, evidence freshness, and billing basis before approving work.
Reject or park the estimate when provider data is incomplete, confidence is low, ownership is unclear, or the action conflicts with migration, resilience, or compliance plans.
Document the evidence source, net/list basis, assumption, owner, approval state, and how follow-up cost sync will verify the result.
Put the framework to work
Costframe connects read-only, records the evidence behind each finding, and keeps list-price estimates separate from net savings.