Summary
Give us 30 minutes. Transform your cloud costs.
We will show you how to identify your savings opportunities and implement a simple FinOps governance model.
You want to launch FinOps, but without a vague “large-scale program.” The good news: an effective FinOps implementation can start within 30 days, provided you aim for a minimal viable governance model: visibility, responsibilities, rituals, and first quick wins.
This guide provides a week-by-week plan, including what needs to be done, who should be involved, and the deliverables to produce.
W1. Scoping & sponsors (objective: align and secure sponsorship)
1) Choose the right starting scope
Do not start with “the entire cloud.” Choose a manageable scope:
- 1 main cloud provider (AWS or Azure or GCP)
- 1 product / 1 BU / 1 platform team
- ideally: a significant spending area + cooperative teams
Golden rule: start small, prove the value, then expand.
2) Clarify the objective (and what FinOps is not)
Define 3 measurable objectives:
- Allocation: e.g. “90% of costs allocated within 30 days”
- Waste reduction: e.g. “-10% on the selected scope”
- Governance: e.g. “weekly ritual in place + shared KPIs”
And clarify the misunderstandings:
- FinOps ≠“a tool”
- FinOps ≠“blind cost cutting”
- FinOps = regular decisions based on cost + value
3) Assign sponsors and roles (minimum viable setup)
- IT/Engineering Sponsor (often Head of Engineering / CTO / Platform Lead)
- Finance Sponsor (FP&A / Finance Partner)
- 1 FinOps Lead (even part-time) to coordinate and orchestrate initiatives
W1 Deliverables
- 1 scoping document (scope, objectives, KPIs, timeline)
- Simple RACI (who decides / who executes / who validates)
- Rituals calendar (weekly + monthly)
Good to know
In 30 days, the goal is not to be “perfect,” but to establish a minimal viable governance model: allocated costs, identified owners, and rituals in place.
Start with a manageable scope (1 cloud + 1 product/team) to quickly prove value through measurable quick wins.
If you only had to track 2 KPIs at the beginning: % of allocated costs and realized savings (measured). The rest comes later.
W2. Tagging & costs (objective: make costs actionable)
Without reliable allocation, you are not doing FinOps: you are making assumptions.
1) Define a simple (and applicable) tagging convention
“Minimum viable” tags:
- product
- team
- env (prod / preprod / dev)
- owner
- cost_center (if needed)
Important: standardize values (controlled list). “Team=platform” must be written the same way everywhere.
2) Make compliance measurable
Set up a clear indicator:
- % of correctly tagged spend
- share of “unallocated cost” (costs not allocated)
3) Build a “product / team / env” view of costs
Even a simple dashboard is enough to start with:
- top services by cost
- top products/teams
- week-over-week variations
- unallocated costs
W2 Deliverables
- Tagging convention + rules
- “Showback” dashboard (cost by product/team/env)
- Tag compliance score + remediation plan
W3. Quick wins (objective: deliver visible and low-risk savings)
Quick wins give credibility to the program. But they must be repeatable and low-risk.
Typical quick wins (to prioritize)
- Non-prod shutdown outside working hours (scheduler)
- Cleanup of orphaned resources (volumes, snapshots, IPs, load balancers)
- Rightsizing on the top 10 resources (using 14/30-day observation windows)
- Storage optimization (storage classes, lifecycle policies)
- Limit “over-replication” and duplicate environments
Simple method
- List (top costs + anomalies)
- Qualify (risk, impact, owner)
- Execute (controlled change + rollback)
- Measure (net savings, not vague estimates)
W3 Deliverables
- Prioritized “quick wins” backlog (impact / effort / risk)
- Implemented changes + measured savings
- “Playbook” of repeatable actions (runbook)
W4. Rituals & KPIs (objective: make the approach sustainable)
The classic mistake: performing optimizations and then “moving on.” FinOps only works through consistent cadence.
1) Set up the weekly ritual (30 min)
Participants: FinOps Lead + Platform + Product/team representatives from the selected scope.
Agenda :
- variations and anomalies
- unallocated costs
- completed actions / actions to launch
- decisions and trade-offs
2) Define useful KPIs (cost + value)
Examples:
- % of allocated costs
- prod vs non-prod costs
- cost per transaction / customer / order (if available)
- realized savings (measured) + estimated “waste”
- coverage & utilization (if commitments are in place)
3) Establish a monthly trade-off review
This is where decisions are made on:
- budgets, commitments, optimization priorities
- performance vs cost trade-offs
- scope expansion
W4 Deliverables
- Weekly ritual template + standard meeting notes template
- “FinOps” KPI dashboard
- Escalation / trade-off process (who decides what)
FinOps is not only a platform/infrastructure topic. The real lever is the product itself: performance, features, quality, and time-to-market.
To establish:
- “Cost of feature”: estimate the cost impact of major initiatives
- “SLO vs cost”: explicitly arbitrate between performance and spending
- Share cost as a product KPI, not as a side topic
Immediate effect: fewer IT/Finance conflicts, more business-driven decisions.
Final deliverables (end of the 30 days)
At the end of the month, you should be able to demonstrate:
- Reliable cost allocation (or a clear roadmap toward it)
- Measured quick win savings
- A governance model in place (rituals + backlog + decisions)
- Shared and understood KPIs
- A 60/90-day roadmap (industrialization + expansion)
FAQ
The most effective model relies on a partnership between IT and Finance:
- an IT sponsor (CTO, Head of Engineering) to drive execution and standards,
- a Finance sponsor to frame budgets and cost visibility.
If you need to move quickly, start with an IT sponsor, then involve Finance as soon as cloud costs become actionable.
A FinOps implementation can start with a small team:
- a FinOps Lead (even part-time),
- a platform/infrastructure profile for execution,
- a Finance counterpart,
- a Product or Engineering representative.
The goal is to cover technical execution, financial control, and business decision-making.
How can FinOps be implemented in 30 days?
- scoping and defining the scope,
- setting up tagging and cost allocation,
- activating quick wins (cleanup, rightsizing),
- setting up rituals and KPIs.
This approach makes it possible to achieve quick wins while establishing sustainable governance.
It is recommended to start with a pilot scope: one cloud, one product, or one team with significant spending.
The goal is to quickly prove the value of FinOps through measurable quick wins, before expanding the approach across the entire cloud environment.
After 30 days, an effective FinOps initiative should enable:
- better cloud cost allocation,
- initial measured savings,
- governance rituals in place,
- shared KPIs,
- a clear roadmap for the next 60 to 90 days.
The goal is not perfection, but an operational foundation for managing costs sustainably.
