Home › Case studies Case studies
FinOps case studies: what we did, and what it delivered
Three engagements, anonymized: no client names, no consumption data. For each, the context, what we put in place, and the result measured on the bill.
Visibility and governance
A large international group: taking back control of a bill nobody owned
Context Several business units, Azure and AWS, hundreds of applications. When we arrived, 35% of resources were tied to no application: part of the bill belonged to nobody.
What we did One mandatory tag, linked to the CMDB that holds owner, cost center and environment A dashboard refreshed daily, by application and owner A monthly SteerCo with forecast, savings and KPIs Standards and building blocks for FinOps by design Result 99.9% of resources tied to an application
On budget with budget freed up for other projects
One-tag tagging · FinOps governance
Data
A data platform: a quarter less spend in three months
Context A Synapse and Fabric platform whose bill grew every month, with development environments scheduled like production.
What we did Cleanup of legacy resources and unused node pools Synapse and Fabric reservations on the stable baseline Autoscaling of Fabric capacities Fewer refreshes and no schedules outside prod Result ≈ −25% monthly spend in three months
Performance monitored at every change
Cutting data costs
Non-prod and logs
Non-prod environments that cost as much as prod
Context Development and test VMs and VDIs running 24/7, and verbose logs enabled in non-prod without anyone knowing.
What we did Automatic Stop every evening and Start on demand on non-prod VMs and VDIs Log filtering, right retention and the right commitment tier Validation of configuration changes affecting logs Daily budget alerts on non-prod Result ≈ −90% on the compute of the VMs involved
≈ €240k a year avoided on a single log incident
Stop/Start and Start on demand · FinOps incidents: 5 real cases
Over €20M in savings delivered in total, from SMEs to CAC 40 groups. Your context is different? That is exactly where each engagement starts.