FinOps Is Not a Finance Problem. It’s an Architecture Problem.
Everyone talks about FinOps as if it’s a finance problem.
I don’t think it is.
I think it’s an architecture problem.
The biggest cloud savings won’t come from buying another tool. They’ll come from making better architectural decisions.
Over the past year, I’ve written about identity, governance, AI, cloud, leadership, and digital transformation. On the surface, they seem like different conversations.
They’re not.
They all arrive at the same conclusion.
No one owns the architectural decisions that quietly create tomorrow’s costs.
That may be the biggest challenge facing enterprise IT today.
The Cost of Invisible Decisions
Storage may be the clearest example.
Walk into almost any enterprise and you’ll find years of completed projects, forgotten datasets, old backups, development environments, and snapshots quietly consuming premium storage. Nobody intended for it to happen.
It happened because no one designed a lifecycle strategy.
At the same time, many organizations have committed millions of dollars to cloud platforms through long-term consumption agreements. Those commitments provide purchasing advantages, but only if the organization actually consumes what it agreed to purchase.
On the surface, these look like unrelated problems.
One is about storage.
The other is about finance.
I think they’re the same architectural conversation.
FinOps Starts Before the Invoice
FinOps has traditionally been viewed as a way to analyze cloud bills after the money has already been spent.
I think that’s backwards.
The most important FinOps decisions happen long before the first invoice arrives.
They happen when architects decide where data lives.
How long it stays there.
Who owns it.
Whether it should move automatically between storage tiers.
How applications consume it.
Whether cloud commitments are considered during the design phase instead of six months later during a cost review.
Those are architecture decisions.
Not finance decisions.
Why AI Changes the Conversation
This is also why I believe AI and FinOps are becoming inseparable.
The data quietly increasing your storage bill today is often the same historical information your AI initiatives will depend on tomorrow.
Customer interactions.
Engineering documentation.
Contracts.
Operational history.
Knowledge bases.
Deleting everything reduces cost.
Keeping everything on premium infrastructure increases cost.
Neither strategy creates long-term value.
The better answer is designing an architecture that places information on the right storage at the right time while keeping it available when the business needs it.
That isn’t simply storage optimization.
It’s preparing your data foundation for AI.
Architecture Is the New Competitive Advantage
Technology vendors—including NetApp, Microsoft, AWS, Google Cloud, and countless others—provide excellent capabilities for storage lifecycle management, automated tiering, and cloud cost optimization.
But technology isn’t usually the limiting factor.
Architecture is.
Organizations don’t struggle because better tools don’t exist.
They struggle because no one owns the architectural decisions that connect infrastructure, finance, security, governance, and AI into one operating model.
That’s where leadership matters.
Someone has to own the outcome.
Someone has to ask whether today’s architecture still supports tomorrow’s business.
Because every decision compounds.
The architecture you build today becomes the invoice you receive tomorrow.
It becomes the data your AI models learn from next year.
It becomes the platform your business depends on for the next decade.
Fix the Foundation First
I’ve said it before, and I’ll keep saying it.
Cost is an architecture decision.
AI is an architecture decision.
Infrastructure is an architecture decision.
The organizations that win won’t optimize one layer.
They’ll design the entire foundation intentionally.