TRACKED CALLS / 24H1,284+12.4%SMS RECOVERIES / WK287+8.1%DEMAND REACTIVATION RESPONSE RATE41.0%+3.2ppAU + NZ CLIENTS LIVE512+11AVG QUOTE RESPONSE47 MIN-9 minISO 27001PLATFORMTRACKED CALLS / 24H1,284+12.4%SMS RECOVERIES / WK287+8.1%DEMAND REACTIVATION RESPONSE RATE41.0%+3.2ppAU + NZ CLIENTS LIVE512+11AVG QUOTE RESPONSE47 MIN-9 minISO 27001PLATFORM
GibsonFamily-Owned Sydney Lead Engine · Since 2006
1800 950 347Get a quote
LIVESANDBOXAI BUILDSCASE STUDYSYDNEY · MELBOURNE · BRISBANE · PERTH · AUCKLANDMon to Fri · 9am to 5pm AEST

Sandbox · How we ship AI builds repeatably and audit-cleanly

// Cloud spend audit + cleanup · client build

GCP Cost Optimisation

By Albert Triolo, Gibson Promotions ·
// THE BASICS

How do you audit and reduce Google Cloud costs?

A Google Cloud cost audit is a structured pass-by-pass review of every active resource in an account, designed to surface orphaned infrastructure, oversized reservations, and forgotten provisioning before the bill compounds further. Gibson Promotions productised a five-pass GCP audit methodology after a client's Cloud invoice arrived at four times its 18-month-ago level with no explanation. The first pass surfaced an orphaned Cloud Storage bucket from a 2024 migration. A second pass found a Compute Engine VM nobody could account for. A third found a BigQuery slot reservation oversized by six times for a use case that had ended. The methodology produces a material monthly spend reduction in a single audit cycle, then installs cost-watch alerting so the next 10 percent drift produces a Slack ping, not a quarterly shock.

“The first pass of a GCP cost audit always finds something the team forgot existed. An orphaned storage bucket from a migration. A VM from a prototype that shipped and never came back. A BigQuery reservation for a use case that ended. None of these are failures. They are the normal accumulation of speed. The audit closes them.”

Albert Triolo, founder of Gibson Promotions

“Cost-watch alerting is the insurance policy on the audit itself. Without it, the bill drifts for six months before anyone notices. With it, a 10 percent week-over-week spike produces a Slack ping in week one. The client gets the Monday-morning shock once. Then they never get it again.”

Albert Triolo, founder of Gibson Promotions
Cloud spend audit + cleanup · client build

GCP Cost Optimisation

how we-did-it

The client opened the email at 7am Monday. Google Cloud invoice. Four times the bill from eighteen months ago. The CFO wanted answers. The CTO wanted to keep building. Neither could explain where the money had gone. We started where any forensic accountant would: assume nothing, inventory everything. The first pass surfaced an orphaned Cloud Storage bucket from a 2024 migration. The second pass found a Compute Engine VM that nobody remembered provisioning. The third pass discovered a BigQuery slot reservation oversized by 6x for a use case that had ended a year prior. By the fifth pass the case was closed.

The five-pass method

  1. 01

    Inventory every active resource

    Every Cloud Run service, Compute Engine VM, Cloud Storage bucket, BigQuery dataset, Pub/Sub topic. Nothing assumed. Output: the full estate as a CSV.

  2. 02

    Tag prod vs dev vs orphaned

    Every resource gets a status: production, development, orphaned (no owner can be found, no traffic in 90 days, no recent deploy). The orphan column is usually the largest.

  3. 03

    Rightsize the keepers

    Cloud Run with min-instances accidentally pinned to 5. BigQuery slot reservations from a use case that ended a year ago. Compute Engine VMs on n2-standard-16 running 2% utilisation.

  4. 04

    Kill the orphans (with audit log)

    Every delete logged. Every owner pinged. 30-day grace window for anything ambiguous. Then close the door.

  5. 05

    Install cost-watch alerting

    Slack ping at +10% week-over-week. Budget alerts at 50, 75, 90% of monthly cap. Quarterly reaudit on the calendar.

Result. Material monthly GCP spend reduction in a single audit cycle. Cost-watch alerting installed so the next 10% drift produces a Slack ping, not a Monday-morning shock. The methodology, productised, is now part of the Sandbox playbook for every operator running on Google Cloud who has lost track of the bill.

Methodology productised. Single-pass audit fits in 1-2 weeks per environment.

‹ Back to all Sandbox builds

// THE ALTERNATIVES

How does a structured GCP audit compare with the alternatives?

  • Wait and review the monthly bill

    A 4x bill increase is what monthly review produces: a compounded surprise with no traceable cause per line item. By the time the invoice arrives, orphaned resources have been running for months and the window for easy recovery is gone.

  • Ask the team to self-audit

    Teams built the infrastructure and cannot objectively identify what is orphaned. Self-audits miss the resources nobody owns. The audit needs to be external to the build team, or at minimum methodical and script-driven rather than conversational.

  • Hire a cloud cost consultancy

    Correct category, but consultancies charge for discovery hours the five-pass methodology eliminates. Structured scripted inventory does the discovery in days, not weeks. The deliverable is the same; the cost and timeline are materially shorter.

  • Five-pass structured audit with alerting

    Material monthly GCP spend reduction in a single audit cycle. Orphaned resources deleted with a 30-day grace window and audit log. Keepers rightsized. Cost-watch alerting installed so the next 10 percent drift surfaces as a Slack ping, not a quarterly invoice surprise.

// FREQUENTLY ASKED

Frequently asked questions

What does a GCP cost audit involve?

A GCP cost audit is a structured review of every active resource: Cloud Run services, Compute Engine VMs, Cloud Storage buckets, BigQuery datasets, Pub/Sub topics. Each resource is tagged production, development, or orphaned. Orphaned resources are deleted with an audit log. Keepers are rightsized. Cost-watch alerting is installed at the close.

How much can a GCP cost audit save?

In the client engagement Gibson Promotions documented, a 4x bill increase traced to orphaned infrastructure and oversized reservations, including a BigQuery slot reservation 6 times the required size. The methodology produces a material monthly reduction in a single audit cycle. Results vary by estate size and how long the account has been running without a structured review.

What is the five-pass GCP audit method?

The five passes are: inventory every active resource, tag each as production, development, or orphaned, rightsize the keepers, kill the orphans with an audit log, then install cost-watch alerting. Each pass uses documented scripts built on gcloud and BigQuery. A single environment typically completes in 1 to 2 weeks.

How does cost-watch alerting prevent future bill shocks?

After the audit, alerting fires at plus 10 percent week-over-week growth and at 50, 75, and 90 percent of the monthly budget cap. A quarterly reaudit is calendared. The combination means future drift surfaces as a Slack ping in week one, not a Monday-morning invoice shock four months later.

Why do Google Cloud bills increase without warning?

Cloud bills compound because resources are provisioned and forgotten. Engineers pin Cloud Run to 5 minimum instances for peak load, traffic falls, the setting stays. Prototypes ship, the VM keeps running. Teams migrate storage, the old bucket stays open. None of these generate an alert. The bill grows silently until a methodical inventory is run.

// MORE ON THIS
// MORE SANDBOX BUILDS

Want one like this in your business?

Every Sandbox build started as one operator's bottleneck. Tell us yours.

A 30-minute diagnose call, no charge. We tell you whether it is a 48-hour build or something bigger, before you commit a dollar.