%20--%3e%3cstyle%20type='text/css'%3e.cls-0%20{fill:%23FF9900;}%3c/style%3e%3cpath%20class='cls-0'%20d='m117.3%2084h-14.1l39.2-79h-24.8l-20.3%2041.7-20.5-41.7h-3.8l-20.3%2041.7-20.8-41.7h-24.3l41%2083.3h8.2l18.2-37.7%2018.3%2037.8h23.7v2.8h10.7v-10.5h-10.6v3.3h0.2zm3.3-74.7h15.2l-28.9%2057.1-7.2-14.9%2020.6-42.2h0.3zm-69.3%2074.9-37-75h15.1l20.8%2042.4-5.8%2011%204.1%201.6%2016.9-33.9%207.2%2015.7-18.4%2038.1-2.9%200.1zm44.5-0.1-28.2-58.9%207.4-14.8%2029.6%2060.8-6.1%2012.9c0%200.1-2.7%200-2.7%200zm27.9%200.6v2.8h-3.1v-2.8h3.1z'/%3e%3c/svg%3e)
$2.3M taken out of annual cloud spend, without slowing delivery
Cloud bills arrive monthly and aggregated, which puts weeks between a decision and its cost. By the time anyone asks why the number moved, the change that moved it is several sprints back and nobody remembers making it.
- $2.3M reduction in annual cloud spend
- Delivered through a multi-cloud FinOps programme
What made it hard
Cloud bills arrive monthly and aggregated, which puts weeks between a decision and its cost. By the time anyone asks why the number moved, the change that moved it is several sprints back and nobody remembers making it.
Multi-cloud makes that worse rather than better: each provider reports differently, so comparing them means normalising the data before the conversation can even start. Cost work in that state tends to collapse into a one-off cleanup that quietly unwinds over the following year.
How it was done
Attribution before optimisation
Spend was attributed to the teams and services that caused it. Until people can see their own number, cost reduction is something done to them rather than by them.
Waste first, commitments second
Idle resources, oversized instances and forgotten environments were removed before any commitment was bought. Buying reservations for waste locks the waste in for a year.
The structural costs nobody owns
Data transfer, NAT and cross-zone traffic rarely have an owner and quietly bill forever. They are architecture decisions presented as a line item.
Built to hold
The point of a FinOps programme is that the saving survives the engagement. Visibility and accountability were left with the teams rather than in a consultant's spreadsheet.
Where it landed
$2.3M taken out of annual cloud spend across the estate.
Delivered as a programme rather than a cleanup, so the teams that generate the cost can see and act on it directly.
Bring us the version of this you are facing
A 45-minute call with the engineer who would run it. We will tell you what we would look at first, and whether it is a project at all.
Talk to an Engineer