← Back to blog

FinOps for CTOs: Cutting Cloud Costs Without Sabotaging Team Velocity

Without governance, cloud spend grows around 30% per year, and dumb cutting backfires: locking engineers out of infrastructure saves pennies and burns days of productivity. Good FinOps follows an order: visibility first, surgical cuts second, culture over bureaucracy.

Visibility comes before any cut

Tag every resource with team, service, and environment. Untagged spend runs 10% to 25% of the bill, and nobody optimizes what they cannot attribute. AWS Cost Categories and GCP labels turn this discipline into enforced policy at resource creation.

Quick wins ranked by effort

  1. Rightsizing overprovisioned instances: typical waste sits at 30% to 40% of provisioned capacity.
  2. Deleting orphaned volumes, stale snapshots, and idle IPs: one afternoon of sweeping frees thousands per month.
  3. Scheduling dev and staging environments off-hours: 65% savings on those accounts.

Commitments without dead inventory

Reserved Instances and Savings Plans call for coverage near 70% of base load, keeping spikes on-demand. Blanket commitment looks like savings and turns into idle capacity once traffic shifts. Review against observed usage every quarter, never against sales projections.

Storage lifecycle policies

Lifecycle policies moving data to Infrequent Access and archive tiers cut storage bills 50% to 80%. Logs older than 90 days almost never justify hot storage prices. Configure automatic transition the day a bucket is born; retrofitting cost control later demands a full audit.

The velocity trap

Ticket processes for every instance change save pennies and burn days in queue wait. Automate guardrails instead: budget alerts per team, policy-as-code with Terraform or Open Policy Agent, hard limits on high-risk services. Engineers free inside guardrails deliver more than engineers stuck in a queue.

Culture moves what mandates miss

Show each team its bill on an internal dashboard, celebrate reductions, and make each squad's charge visible in internal reporting. Teams that see their own number resize infrastructure without outside pressure. A directive changes behavior while enforcement lasts; ownership changes it for good.

Review cadence

Run a FinOps review with leads every month and adjust commitments each quarter. Treat it like security hygiene: a continuous process with an owner and a metric, rather than an annual cost-cutting sweep. Cloud is the second-largest cost line at most companies, and it deserves the same rigor as headcount.

Facing this challenge in your company?

I help CTOs and engineering teams solve problems like this — with honest diagnosis and focused execution.

Schedule a conversation
Marc Reinan Gomes
Marc Reinan Gomes Staff Engineer & Consultant

14+ years building products, leading engineering teams, and helping companies scale with technical quality.

Share on LinkedIn