A mid-market SaaS platform on Google Cloud and Azure sees its bill grow faster than its usage. Here is how we would find the leaks and give teams ownership of their spend.
Example scenario. This page describes a typical engagement and how we would approach it. It is not a description of a specific client and it contains no client results. The measures below are what we would track, with targets agreed with you up front.
A mid-market SaaS platform runs on Google Cloud and Azure. Its monthly infrastructure spend keeps rising faster than usage. Machines were sized for old peaks, disks outlived the machines they belonged to, and nobody owns the bill.
We would deploy OpenCost on the production and staging Kubernetes clusters to attribute cost to namespaces and teams, then isolate the leaks: oversized requests, idle workloads and orphaned disks. Alongside the fixes, we would give each team direct visibility of its own spend, with labels, budgets and a short monthly review, so ownership stays with the people who can act.
Monthly cloud spend per environment and per team, and the share of spend found to be waste, tracked from the first week. A saving only counts once the change is live and stability and performance are unchanged.
Related: FinOps Consulting for Cloud Cost Optimisation, the free 3C - Cloud Cost Calculator, and the articles FinOps cloud waste checklist and Cloud waste audit: a checklist you can run this week.
Tell us how your platform runs today and we will suggest where to start, even if it is a small step.
