How to Have the Cloud Cost Conversation with Your CFO

You have been asked to present cloud costs at the next executive meeting. If your first instinct is to pull up a dashboard showing EC2 instance types and S3 storage tiers, stop. That approach loses the room in 30 seconds.

The CFO does not care about your infrastructure. They care about three things: what are we spending, what are we getting for it, and can we spend less without hurting the business.

Speak Their Language

Finance operates in a different vocabulary than engineering. Translate accordingly:

• Not "We have 2,400 EC2 instances across 3 regions." Instead: "Our compute infrastructure supports $45M in annual revenue."
• Not "Our S3 costs increased 23% quarter over quarter." Instead: "Data storage costs grew proportionally with our 28% customer growth -- our cost per customer actually decreased."
• Not "We could save $200K by switching to Graviton instances." Instead: "We identified $200K in annual savings with no performance impact. Here is the 90-day implementation plan."

The pattern: connect every cost to a business outcome. Every savings opportunity to an implementation plan. Every trend to a strategic implication.

The Three Slides That Work

Slide 1: Cost-to-Revenue Ratio

Show cloud spend as a percentage of revenue over time. If you are spending 8% of revenue on cloud and the industry benchmark is 10-15%, you are already winning. If the percentage is stable while revenue grows, you are scaling efficiently. This is the single most important metric for a CFO.

Slide 2: Cost per Business Unit

Break down cloud costs by the teams, products, or business units that consume them. This is not a technical breakdown (compute vs. storage vs. network). It is a business breakdown: Product A costs $X and generates $Y in revenue. Product B costs $X and generates $Y.

CFOs understand P&L by business unit. Give them cloud costs in the same structure.

Slide 3: Savings Identified and Captured

Show two numbers: total savings identified in the period and total savings actually implemented. The gap between identified and captured tells a story about execution velocity. A large gap means you need more engineering capacity for optimization. A small gap means your FinOps practice is mature.

Include the top 3-5 specific savings actions, each with a dollar amount and implementation status.

Handling Common CFO Questions

"Why does cloud cost so much?"

Reframe: "Cloud costs are proportional to our business growth. We are spending X% of revenue, which is [below/at/above] industry benchmarks. Here is what we are doing to keep it efficient."

"Can we cut 20% from the cloud budget?"

Never say no outright. Instead: "We have identified $X in optimization opportunities that can be implemented over the next quarter without impacting operations. Beyond that, additional cuts would require trade-offs in [specific capabilities]. Here are the options."

"How do we compare to competitors?"

If you have benchmark data, use it. If not, use FinOps Foundation benchmarks for your industry vertical. A cost-to-revenue ratio below industry median is a strong position.

The Secret: Come with Answers, Not Data

The CFO does not want a 50-slide deck of cost breakdowns. They want three things:

1. Confidence that someone competent is managing cloud costs
2. Evidence that spending is proportional to business value
3. A clear plan for optimization with quantified impact

If you walk in with those three elements, the conversation takes 15 minutes and you leave with budget approval. If you walk in with dashboards, the conversation takes an hour and you leave with homework.

Intelligence over dashboards. It is not just a product philosophy. It is how you communicate with leadership.