FinOps as an operating habit, not a quarterly exercise

Cloud cost programs often begin when a bill becomes uncomfortable. Teams identify a set of unused resources, negotiate a commitment, report savings, and then return to the delivery habits that created the cost. The next review produces the same surprise.

At PepsiCo, I led the corporate-site migration from Akamai Cloud to AWS, delivering more than $500K in savings, and led selected Azure and third-party-hosted application migrations to AWS. I also built FinOpsHub using Flexera-sourced cloud data, workload rationalization, and governance controls, contributing to more than $1.2M in year-over-year savings overall.

The durable lesson was that FinOps cannot sit beside engineering. It has to become part of how applications are owned and operated.

Begin with workload intent

Cost data becomes useful when it is connected to a workload, owner, environment, business purpose, service criticality, and demand pattern. A large resource may be appropriate for a critical peak. A small orphaned resource may still represent waste. The decision needs context.

I use workload rationalization to ask: Does this capability still need to exist? Is the current platform appropriate? Should we retire, retain, rehost, replatform, or redesign it? Cost optimization cannot compensate for a workload that no longer has a clear purpose.

Create trusted visibility

FinOpsHub was designed to bring Flexera-sourced cloud information into a governance view that leaders and application owners could use. The important step is not simply aggregating cost. It is creating a shared definition of allocation, trend, opportunity, action, owner, and realized value.

I distinguish an identified opportunity from an approved action and a verified saving. This prevents a theoretical recommendation from appearing as business value before the change is implemented and sustained.

Put cost into the operating rhythm

• Application reviewDiscuss consumption trend, anomalies, ownership, and actions alongside reliability and delivery.
• Architecture and migrationInclude operating cost, elasticity, observability, support, and exit considerations in platform decisions.
• Engineering backlogGive rightsizing, scheduling, storage lifecycle, and modernization work visible priority and acceptance criteria.
• Commercial governanceConnect commitments, licenses, partner deliverables, renewals, and forecasts to actual workload plans.
• Leadership reviewSeparate one-time savings, avoided cost, and recurring run-rate improvement so choices remain credible.

Protect reliability and flow

Optimization is not indiscriminate reduction. A decision that lowers cost but weakens resilience, security, user experience, or team flow may simply transfer the expense. I evaluate cost changes with service objectives, demand, recovery needs, deployment behavior, and support capability.

This is another reason FinOps and SRE work well together. Observability and capacity signals help teams understand whether resources match actual service behavior. Error budgets and reliability discussions create a balanced conversation about efficiency and risk.

Make ownership constructive

Cost transparency can create defensiveness if it appears only as a chargeback or leadership escalation. I prefer to give application teams enough context and agency to act. Platform and FinOps teams provide data, standards, and expert support; application owners make informed workload decisions and explain exceptions.

This approach creates accountability without turning every anomaly into blame. It also surfaces systemic improvements - better tagging, environment schedules, reusable architecture, deployment practices, or commercial controls - that benefit more than one application.

FinOps creates strategic value when cost is treated as an engineering signal, a product decision, and a leadership responsibility at the same time.

Closing perspective

The migration savings were important and measurable. The larger capability was the operating habit around them: trusted visibility, workload ownership, governance controls, rationalization choices, and follow-through.

That is how I lead FinOps. Do not wait for the quarterly bill to create urgency. Make cost part of architecture, delivery, service, and portfolio decisions every week - and verify that an action continues to deliver value after the spotlight moves on.

Professional note: This article reflects my leadership experience and personal perspective. Examples are intentionally generalized and do not disclose confidential company information.