CASE STUDY

From Invoice to Accountability

How a Belgian financial institution rebuilt ownership of its Azure estate.

01 // CONTEXT

A Belgian financial institution running a 10M€+ Azure estate across critical workloads, in a highly regulated environment. The engagement ran with CTO, Finance, Platform, and Cloud & DevOps leads at the same table.

02 // THE PROBLEM WASN’T COST

Spend was escalating — but escalating spend was the symptom. Finance and Engineering were reading different numbers, so neither could act on them.

→Costs grew with limited visibility across departments.

→Budgets overran unpredictably, with low forecasting accuracy.

→No accountability model existed, which turned every cost conversation into friction between Finance and IT.

Nobody owned the number. That is not a tooling gap.

03 // WHAT WE BUILT

FinOps audit & allocation

Spend mapped across teams and services, tagged and attributed to named owners.

Curated reporting

Role-based views of usage, cost and variance, so Finance and Engineering read the same number.

Governance & optimization

Ownership, budgets, rightsizing and commitment coverage, under policy.

04 // WHAT CHANGED

ALLOCATION

mostly untagged→fully attributed to named owners

ACCOUNTABILITY

friction between Finance and IT→a shared model with named budget owners

FORECASTING

chronic overrun→spend within budget

COMMITMENTS

ad-hoc purchases→policy-driven coverage targets

CADENCE

an invoice explained after the fact→a standing quarterly review both sides own

05 // WHAT GENERALIZES

The sequence, not the savings. Allocation before optimization — you cannot defend a saving you cannot attribute. Accountability before automation — a guardrail nobody owns decays within a quarter. The order is what made it hold.

Recognize this pattern in your own estate?

DISCUSS THIS CASE STUDY