Vlad ZThe GCP account that took me longest to optimize wasn't the most expensive one I've worked with It...
The GCP account that took me longest to optimize wasn't the most expensive one I've worked with
It was the most fragmented
Eleven GCP projects. No consistent naming. No resource labels. Billing export not set up. No clear owner for five of the eleven projects
Total spend: $9,400 a month across the organization. But I couldn't tell you where $3,000 of it was going when I started because the visibility didn't exist
Before any optimization work happened, we spent a week on instrumentation
Billing export to BigQuery turned on. Resource labels applied to everything that could be labeled. Project ownership documented and communicated. Budget alerts set at the organization level and the project level
Just that week of work changed the conversation completely
Once you could see spend by project, by team, by environment - the questions got specific. Project 7 is using $1,400 a month, who owns it? Turns out: a contractor who left the company. What's running there? Three Compute Engine instances and a Cloud SQL database. For what? Nobody knew
We paused the instances and monitored for two weeks. Nothing complained. We deleted them and the database
$1,400 gone immediately
The rest of the optimization work was easier because the visibility was there. Every decision could be made with actual data. Every savings claim could be verified
The fragmentation itself was a cost. Not just the projects nobody was watching. The engineer hours spent being confused about the account, the slow incident response because nobody knew which project to look at, the inability to make architectural decisions because nobody had a clear picture of what existed
Visibility is not a nice-to-have. On GCP with multiple projects, it's the foundation everything else is built on