Skip to main content

Establish Cost Baseline

This playbook helps you create a shared, trusted baseline of cloud spend and KPIs that FinOps, finance, and leadership can use as a starting point for targets and optimization.

Confirm Data Readiness​

  • Verify that billing ingestion is configured and healthy for all in‑scope clouds.
  • Ensure allocation and business mapping are in place so spend can be reported by BU, application, team, and environment.

Choose Baseline Period and Scopes​

  • Select a representative period (for example, the last full 1–3 months) that reflects typical usage.
  • Decide which scopes to baseline, such as:
    • Overall organization.
    • Major BUs or portfolios.
    • Top applications or customers by spend.

Document any unusual events during the baseline period (large migrations, outages, promotions).

Define Baseline KPIs​

Using KPIs, pick a small set of metrics to establish:

  • Total spend by provider, BU, application, and environment.
  • Allocation quality (allocated vs. unallocated spend, shared‑cost proportions).
  • Commitment coverage/utilization and effective vs. on‑demand cost.
  • Waste and optimization potential (rightsizing, idle resources).

Keep the initial KPI set small so stakeholders can focus on what matters most.

Build Baseline Dashboards and Reports​

  • Create reports and dashboards that:
    • Show baseline KPIs for the chosen period and scopes.
    • Allow drill‑down into services, regions, and owners.
  • Validate numbers with finance and key application teams.
  • Adjust allocation, business mapping, or data quality issues uncovered during review.

For patterns and examples, see also Dashboards & Reporting and the Report & Dashboard Gallery.

Socialize and Lock the Baseline​

  • Present the agreed baseline to stakeholders (FinOps, finance, platform, product).
  • Document assumptions and any known limitations.
  • “Lock” the baseline period for comparison by:
    • Saving the underlying reports.
    • Capturing snapshots in dashboards or exported files.

Use the Baseline Going Forward​

  • Use the baseline as the reference point for:
    • Setting budgets and forecasts.
    • Measuring the impact of optimization and architecture changes.
    • Tracking progress in executive and program reviews.
  • Periodically update the baseline (for example, annually) as your environment and business evolve, but keep historical baselines for trend analysis.