Phase 2: Optimize
Waste elimination
The easiest savings come from eliminating waste: unattached EBS volumes, idle load balancers, stopped instances with attached storage, unused elastic IPs, and oversized development environments running 24/7 when they are only used during business hours. Typical savings: 10-20% of total spend.
Rightsizing
Analyse CPU, memory, and network utilization to identify oversized instances. AWS Compute Optimizer, Azure Advisor, and GCP Recommender provide automated rightsizing recommendations. Target instances with average CPU below 20% or memory below 30%. Typical savings: 15-30% on compute costs.
Commitment discounts
Purchase Reserved Instances or Savings Plans for steady-state workloads. AWS Savings Plans offer 20-40% savings with 1-year commits, 30-60% with 3-year. Azure Reservations save 40-72%. Start with Compute Savings Plans for flexibility, then layer specific reservations for stable workloads.
Phase 3: Operate
Budget alerts and governance
Set budget alerts at 80%, 90%, and 100% of monthly targets per team. Implement automated actions: notify team leads at 80%, escalate to management at 100%, and optionally restrict non-essential resource creation above budget. Review budgets monthly and adjust quarterly based on business growth.
Regular cost reviews
Weekly: automated anomaly review (flag unexpected increases >10%). Monthly: team cost review (each team reviews their spend trends). Quarterly: commitment rebalancing (adjust reserved capacity to match workload changes). Annually: architectural review (identify structural optimization opportunities).
How Opsio Implements FinOps
- Tagging and visibility: We implement tagging strategies and build cost dashboards across all cloud platforms.
- Optimization: We identify and execute quick wins (waste, rightsizing) then implement commitment strategies.
- Culture change: We train engineering teams, establish review cadences, and build accountability models.
- Ongoing governance: Monthly cost reviews, quarterly commitment rebalancing, and continuous anomaly detection.
Frequently Asked Questions
How much can FinOps save?
First-year savings typically range from 25-40% of cloud spend. Ongoing savings of 15-25% are maintained through continuous optimization. The FinOps Foundation reports that mature FinOps organizations waste 20% less than average.
Who should own FinOps in our organization?
FinOps works best as a cross-functional practice. A FinOps team (or person) coordinates between engineering, finance, and leadership. Engineering owns day-to-day optimization. Finance owns budgeting and reporting. Leadership owns prioritization decisions. Opsio can serve as your external FinOps function.
Do I need FinOps tools?
Start with native tools (AWS Cost Explorer, Azure Cost Management, GCP Billing). Add third-party tools (CloudHealth, Apptio, Spot by NetApp) when you outgrow native capabilities — typically when managing $100K+/month across multiple cloud accounts.
