Why Finland is lagging on FinOps and what to do about it.

Let’s address the elephant in the room: FinOps isn’t thriving in Finland. And this should come as a surprise.

Finland is usually ahead of the curve on technology. We adopt new tools early, migrate fast, experiment boldly and rarely hesitate to try out whatever the cloud ecosystem throws at us. Yet when the conversation turns to FinOps, everything suddenly slows down.

Over the past few years, I’ve sat with organisations across Finland and the wider Nordics. Some spend tens of millions of euros annually on cloud. Some are modernising critical national systems, running large‑scale data and AI programmes. And still, when I ask whether they’re practicing FinOps, the answer is usually: “No, but we’ve been thinking about it.”

We’re cloud‑mature, digitally progressive… and yet oddly hesitant about the one capability that makes cloud sustainable long‑term.

So why is that? And what’s finally changing?

Lift‑and‑shift migrations

A big part of the issue goes back to how Finnish organisations moved to cloud in the first place. Too often, migrations were essentially relocations. Lift‑and‑shift. A neat re‑hosting exercise dressed as transformation.

If you don’t modernise, you don’t unlock cloud economics. You just take your old architectural problems and give them a new postcode. And when your cloud estate still behaves like on‑prem, FinOps feels optional because nothing about the environment is built for dynamic optimisation.

Cost visibility is kept top secret

One of the strangest patterns I see is how restricted cloud cost data still is. In many organisations – public and private – only one person in finance has full visibility. Engineers don’t see it. Product teams don’t see it. Some cloud teams barely see it.

And if people can’t see costs, they can’t own them. The paradox is the people who create the costs and could fix them aren’t aware they exist.

FinOps is built on transparency. Without visibility, you’re running cloud with the lights off.

Let’s not open Pandora’s box

Here’s the emotional truth behind it: looking at cloud costs can feel scary.

There’s this unspoken belief that the moment you start digging into cloud costs, you’ll uncover a massive, unmanageable mess – and people don’t want to be the ones who bring that news upstairs. So instead, things stay comfortably chaotic and comfortably hidden.

FinOps is resisted because it threatens the illusion that everything is fine. Yet the longer you stay in that illusion, the more expensive it gets to see the reality.

Governance like in the “on‑prem days”

Even when companies adopt cloud‑native services, their governance remains stubbornly traditional. Approval chains. Siloed roles. Architecture reviews that treat cloud resources like physical hardware. And the consequence?

FinOps feels like an alien concept in a structure that hasn’t evolved to support it.

Why 2026 is a FinOps tipping point

For years, it was possible to look the other way. Cloud costs were rising, but not fast enough to force real change. That’s no longer the case. In 2026, several pressures have converged:

Cloud bills are too big to ignore

Idle resources. Forgotten disks. Logs from 2015 that no one deleted. They cost money and accumulate year by year. They don’t behave like fixed on-prem budgets. And finance teams are understandably asking tougher questions.

AI has blown a hole in the budget forecasts

A single over‑provisioned AI experiment or leaked API key can turn into a €150k invoice. AI forces organisations to confront the fact they don’t have cost guardrails in place.

Economic realities are kicking in

Public institutions have undergone redundancy negotiations, hitting harsh reality. And suddenly, saving €1M in cloud spend isn’t abstract. It’s 20 jobs saved including maybe yours. Cost governance becomes human.

Together, they’ve created a tipping point – one where FinOps is no longer a “nice to have”, but a practical necessity.

“How much will this save us?”

I hear this in every sales conversation. The truthful answer? I don’t know, or not until we understand your architecture, culture, tooling and maturity.

FinOps isn’t a product. It’s not a magic percentage. It’s a capability. If you want the savings, you need the capability. That’s the trade‑off.

Where to start in simple steps

What you need is not a revolution but a starting point.

Step 1: Get a C‑level sponsor

Without leadership buy‑in, everything else becomes much harder.

Step 2: Build cultural alignment

You need small nudges toward shared accountability. In commercial organisations, KPIs and bonus incentives help – people pay attention to what affects them directly.

In the public sector, job security can be a motivator. If saving a million avoids 20 redundancies, that resonates deeply.

Step 3: Start small: crawl, walk, run

Pick one application team. One workload. Implement something small, learn from it, and grow from there. Once the seed starts to bloom, the organisation begins to change from the inside.

Step 4: Gently increase transparency

Not everyone needs to see the full cloud bill. Developers only need cost visibility for their own applications. But giving people access to relevant data sparks curiosity and ownership.

Finland is getting ready for the leap

Finland is just arriving at the moment where FinOps becomes unavoidable. Cloud maturity, AI expansion and economic pressure have all converged to make cost governance a strategic necessity. Some organisations have already started.

The patterns are clear and the path forward is far simpler than people think. Because once the mindset shifts, the rest follows naturally.

If you’re ready to take the first step, now is exactly the right time.