Context · B2B SaaS · Germany
Multi-cloud FinOps without a tool tax
Rightsized idle estates across AWS and Azure, introduced anomaly alerts, and tied spend owners to product teams - fixed-scope engagement.
- run-rate cloud waste cut
- 27%
- to first savings
- 4 wks
run-rate cloud waste cut
to first savings
Challenge
A B2B SaaS team ran meaningful load on AWS and a long-tail Azure estate from an acquisition. Finance saw rising run-rate; engineering lacked tagged ownership. A prior FinOps tool pilot added cost without changing behaviour.
Approach
Week one: billing exports, unused resources and commitment coverage on both clouds - findings ranked by euros and effort, not dashboard vanity metrics.
Introduced lightweight anomaly alerts and a monthly showback tied to product teams, not central IT.
Rightsized and decommissioned in fixed batches with rollback notes, so platform engineers kept control of production risk.
Outcome
Run-rate waste fell twenty-seven per cent within the engagement window; first savings landed in four weeks. Finance and engineering now share one owner map - no new SaaS FinOps platform required.
FAQ
Did you replace their FinOps tool?
No. We used native billing and tagging plus simple alerts. If a tool helps later, it should follow process - not the other way around.
Was multi-cloud required?
Both estates were in production. The work focused on waste and ownership across AWS and Azure; GCP was out of scope for this phase.