Cut your Google Cloud bill without cutting corners
Find where the money goes, fix the waste, and commit only to what you really use. With numbers you can show to finance.
Sound familiar?
- The bill grows every month and nobody can say why.
- Environments run all week, whether anyone uses them or not.
- Machines were sized for a launch two years ago.
- Committed use discounts sound good, but nobody wants to lock in the wrong thing.
What you get
Where the money goes
Spend broken down by service, project and team, with labels that make it stick.
Quick wins first
Idle resources, oversized machines, storage and registry cleanup, and logs you pay for but never read.
Rightsizing from real usage
Based on what your workloads actually use, not on guesses.
A commitment plan
Committed use discounts sized to your steady baseline, not your peak.
No more surprises
Budgets and alerts, so the next surprise is an email, not an invoice.
How it runs
Review
You show me what runs and where it hurts. I look at the real setup, not a slide deck.
Plan
A short written plan: what changes, in what order, and how long it takes.
Build
Small steps you can review and roll back, dev before prod.
Handover
Docs and a runbook so your team can run it, with me on call if you want.
Where I've done this
- About 35% lower infrastructure cost after moving a bank's on-prem applications to GCP and redesigning them for the cloud (HSBC).
- Kept a startup migration lean: a planned API gateway became routing GKE already had, a message queue waited until it was needed, and registry retention stopped storage growing forever.