M02 Deck Outline: Financial Fluency

Deck purpose: Develop financial language fluency, not accounting expertise. Participants leave able to speak CapEx/OpEx, TCO, CoI, and TVO with a CFO without losing credibility or accuracy.

01Title

M02: Financial Fluency: Speaking the CFO's Language

Module title, session framing, facilitator
Core question: "Can you explain the financial case for your architecture to a CFO in under 2 minutes?"

02Opening Problem

The "Cloud Is More Expensive" Objection

Finance team runs an internal comparison: Azure costs more than the current data center
The comparison is technically correct, but it excludes facilities, staff, DR, refresh cycles, and licensing cliffs
The architect has 10 minutes with the CFO to make the asymmetric comparison visible
Discussion: what numbers do you need to walk in with?

This opening scenario establishes the stakes quickly. If participants have faced this objection before (most will have), the emotional resonance is immediate.

03Framing

Why Financial Fluency Is a Technical Skill

Architecture decisions are financial decisions because they commit capital, change operating cost structures, and carry risk
The CFO is the second decision-maker in any enterprise architecture deal, and usually not in the room for the technical reviews
An architect who cannot speak financial language is asking the CFO to trust a translation: one they can't verify
Fluency ≠ expertise: you don't need to be an accountant; you need to speak the categories and understand the logic

04Concept

CapEx vs. OpEx: More Than a Tax Question

CapEx: capital expenditure: purchased assets, depreciated over time, balance sheet impact
OpEx: operating expenditure: consumed costs, expense immediately, P&L impact
Why it matters: CapEx requires capital approval; OpEx comes from operating budget: different committees, different timelines, different flexibility
Cloud = OpEx shift by default; this is either a feature (budget flexibility) or a problem (loss of depreciation benefit), depending on the CFO
Architect's job: understand which posture this CFO prefers and frame accordingly

Two-column table: CapEx characteristics vs. OpEx characteristics. Four rows: approval process, budget source, reporting treatment, risk profile.

05Framework

Framework 1: Cost of Inaction (CoI)

CoI = the total cost of NOT making the change. The status quo has a price.
Four components: (1) Direct operational cost, (2) Risk exposure cost, (3) Opportunity cost, (4) Compliance cost
CoI reframes the question from "can we afford to modernize?" to "can we afford not to?"
The 3-year CoI often exceeds the migration investment, but only when all four components are included

CoI calculation example for a fictional customer: four-row table with estimated annual cost for each component. Totals row shows 3-year accumulated cost vs. migration investment.

Walk through a live example with the group: use round numbers. The goal is not a precise model; it is the concept that the status quo has a quantifiable cost that usually isn't on the CFO's comparison spreadsheet.

06Framework

Framework 2: TCO: The Symmetric Comparison

TCO (Total Cost of Ownership) comparisons fail when the on-premises column is incomplete
On-premises costs that are commonly excluded: hardware refresh cycles, facilities (power/cooling/space), staff allocated to maintenance, DR/BCP, end-of-life licensing uplift
The symmetric TCO adds these back. The comparison is not "Azure vs. your data center"; it is "Azure vs. what your data center actually costs"
Break-even: typically 18–36 months for most enterprise workloads when TCO is symmetric

TCO comparison table: 3 columns (On-Premises "stated", On-Premises "actual", Azure) × 8 rows (infrastructure, licensing, facilities, DR, staff, refresh, compliance, total). The gap between column 1 and column 2 is the conversation.

07Framework

Framework 3: TVO: Beyond Cost Reduction

TVO (Total Value of Ownership) captures what TCO cannot: the value created by the capability, not just the cost saved
Four value dimensions: (1) Speed-to-market acceleration, (2) Risk reduction, (3) Capability unlock (things you can now build that you couldn't before), (4) Unit economics at scale
TVO is the business case the CFO takes to the board: TCO is just the cost comparison
Architect's job: quantify at least one TVO dimension in dollar terms, not just describe it

08Program Metric

Program Metric 2: The Jargon-Free Test

Target: explain the financial case for an architecture to a CFO-equivalent audience using 5 or fewer unexplained acronyms in 90 seconds
Test: deliver the explanation; a peer counts every acronym; any unexplained acronym = 1 point against the score
The test is not just about language. It is about whether the explanation leads with business outcome or technical rationale
Score of ≤5 acronyms, business-outcome lead = "Ready"

Metric card: Jargon-Free Test. Green = ≤5 acronyms, business outcome lead. Yellow = 6–9 acronyms. Red = 10+ acronyms or technology-lead explanation.

09Exercise

The CFO Briefing: Live Practice

One participant plays CFO (non-technical; cost-focused; skeptical of vendor numbers)
One participant plays Architect and has 90 seconds to make the financial case for the Cascade Health migration
Observers count: acronyms, "so what?" moments, financial terms used correctly vs. incorrectly
Debrief: what did the CFO character need that the Architect didn't provide? What would have changed the conversation?

10Close

Application: Before Your Next Proposal

Run a 4-component CoI estimate for your current engagement, even with rough numbers
Build the symmetric TCO: add the costs the customer's Finance team probably excluded
Identify one TVO dimension you can quantify, not just describe
Practice the 90-second CFO brief on a colleague before the next customer meeting

Module 02: Financial Fluency for Architects