Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Cloud and platforms

FinOps: controlling cloud costs without slowing teams down

In the cloud, spending is decided by those who deploy, not by those who control it. Our consultants help make cost visible to the teams that incur it and establish the rules that allow it to be optimised without holding back delivery.

Our principles

  • Every cost linked to an identified owner
  • Usage optimised before pricing commitments
  • A unit cost linked to activity, not just an invoice
In brief

FinOps is the practice that makes technical, finance and business teams collectively accountable for cloud spending, in order to link every euro consumed to the value it produces. Management Square consultants help your teams put in place visibility, cost allocation, optimisation levers and the routines that embed this accountability for the long term.

Scope

How we contribute

  1. Spending diagnostic

    Review of billing and usage data, identification of the main cost items, unallocated costs and gaps between forecast and actual.

  2. Tagging and allocation strategy

    Tagging rules, account structure, treatment of shared costs and the choice between simple showback and internal chargeback.

  3. Dashboards for each audience

    One view for technical teams (resources, anomalies), one for product owners (unit cost), one for finance (forecast, variances).

  4. Usage optimisation

    Rightsizing, shutting down unused environments, removing orphaned resources, storage lifecycle policies, review of costly architectures.

  5. Pricing commitment strategy

    Analysis of the stable share of consumption, choice of commitment level and term, tracking of coverage rate and utilisation rate.

  6. Governance and routines

    Roles, budgets, anomaly alerts, periodic cost reviews with teams, building cost into architecture decisions.

Page contents

Why the cloud bill escapes traditional budget control

FinOps was born of a simple observation: the cloud has changed who decides on spending. In a data centre, buying servers goes through a request, a quote and an approval. In the cloud, an engineer creates a resource in a few moments, and the cost runs from that point. The purchasing decision has dissolved into thousands of everyday technical actions.

The usual control tools are not suited to this. The annual budget discovers the variance after the fact. The invoice contains thousands of lines expressed in technical units that finance cannot link to a product. Teams, for their part, often do not know what their choices cost: they do not see the invoice.

The result is not always excessive spending. It is unexplained spending, which is more troublesome: no one can say whether the month’s increase reflects growth in activity or a forgotten test environment.

Visibility, allocation, optimisation: the three FinOps workstreams

Visibility means knowing what is spent, on what and for whom. It relies on the provider’s billing exports, on a readable account structure and on tags applied systematically. An optional tag is rarely applied: its enforcement must be automated at deployment time.

Allocation links each cost to an owner: a product, a team, an internal customer. The difficulty lies in shared costs (network, common platform, support, security), which must be distributed using a simple, accepted key. A perfect key that no one understands is worth less than an approximate key that everyone accepts.

Optimisation comes last, and that is a logical order. You can only usefully optimise what you know how to allocate, and it is the owners who know whether a resource can be reduced.

For the vocabulary and reference framework of the discipline, see our glossary entry on the definition of FinOps.

Usage, architecture, pricing: three levers not to be confused

Lever Examples Who acts Main risk
Usage Rightsize, shut down outside hours of use, remove orphaned resources, move cold data to cheaper storage The owning teams Degrading performance by reducing without measuring
Architecture Autoscaling, choosing pay-per-use services, reducing data transfers between zones Architects and product teams A development effort to be weighed against the benefit
Pricing Consumption commitments, interruptible capacity for tolerant workloads, contract negotiation FinOps team, procurement, finance Committing to usage that is set to fall

The order matters. A pricing commitment calculated on unoptimised consumption locks in the waste for its entire term. We therefore address usage first, then pricing on the share of consumption that has become stable.

Some items are regularly overlooked because they do not look like servers: outbound data transfers, log retention, backups, licences. Analytics platforms and artificial intelligence workloads deserve particular attention, because their cost often depends on the queries executed rather than on reserved resources. This point is addressed with the teams concerned in our data platform offering.

Our approach: making cost visible to those who incur it

Our consultants work within your teams; decisions remain yours.

Establishing a first accurate picture. Starting from the billing data, we reconstruct spending by product and measure the share that cannot be allocated to anyone. This unallocated share is the first indicator to bring down.

Showback before chargeback. Each team receives a view of its costs, in its own terms. Showback alone often reveals forgotten resources that their owners remove of their own accord.

Introducing a unit cost. The total bill says nothing about efficiency. The cost per transaction, per case processed or per active user, on the other hand, can be compared from one month to the next. A rising bill with a falling unit cost is good news.

Establishing routines. A periodic review brings technical, product and finance together around variances and the decisions to be made. Anomaly alerts flag a drift within a few days instead of waiting for the month-end close.

Building cost into design. The cost estimate becomes part of the architecture file, and tagging is built in by default to the golden paths of the platform described in our DevOps and platform engineering offering.

FinOps and sobriety: where they converge, where they diverge

Cost and environmental footprint often move in the same direction. An oversized machine, an environment running at night with no users, data kept for no reason: eliminating them lightens both the bill and resource consumption.

The convergence is not complete. A pricing commitment reduces the price, not the usage. The cheapest region is not necessarily powered by the lowest-carbon electricity. Very cheap storage encourages keeping everything. Conversely, the footprint is not limited to the electricity consumed: manufacturing the equipment accounts for a share of it, which the bill does not reflect.

We therefore recommend tracking footprint indicators alongside cost indicators, bearing in mind that the data supplied by hosting providers rests on calculation methods that differ from one to another. Comparison over time, with the same provider, is more reliable than comparison between providers.

False economies

  • The one-off campaign. A reduction plan carried out once produces an effect, then spending climbs back up. FinOps is a continuous practice.
  • The central team optimising alone. Without knowledge of the applications, it reduces what should not have been reduced, or dares not touch anything.
  • Tagging by decree. A tagging rule without automated enforcement is only followed for a few weeks.
  • The bill as sole judge. Penalising a team whose spending grows with its activity discourages precisely what the business is seeking.
  • Migration without follow-up. The estimates made before a cloud migration must be compared with actual costs as soon as the first applications have been moved.

The indicators of an established FinOps practice

  • the share of spending allocated to an identified owner;
  • the share of resources correctly tagged;
  • the gap between forecast and actual spending;
  • the coverage rate of stable consumption by commitments, and the utilisation rate of those commitments;
  • the trend in unit cost of the main products;
  • the time between a cost anomaly appearing and it being dealt with;
  • the share of optimisation recommendations actually acted on by teams.

None of these indicators is a savings figure. Savings are a consequence. What we seek to establish is the organisation’s ability to explain its spending and to decide on it.

Typical work

What our consultants contribute to

Diagnostic report

Breakdown of spending, unallocated share, optimisation opportunities ranked by effort and by stake.

Tagging standard and allocation rules

The mandatory tags, their automated enforcement and the keys for distributing shared costs.

Cost dashboards

The views for each audience, their data sources and how they are calculated.

FinOps operating charter

Roles, routines, alert thresholds and decision rules on commitments.

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is FinOps?

FinOps is a cloud financial management practice that brings together technical teams, finance and the business. Its principle is that those who incur spending see the amount and are accountable for it. It does not aim to spend as little as possible, but to obtain the best value for every euro consumed.

What is the difference between showback and chargeback of cloud costs?

Showback means showing each team what it consumes, with no budgetary effect. Chargeback actually charges these costs to its budget. Showback is often enough to change behaviour and is a prudent first step. Chargeback requires reliable, accepted allocation; without it, it mostly generates disputes.

Should you commit to the provider to reduce the cloud bill?

Consumption commitments give access to reduced rates in exchange for a guaranteed volume or term. They are relevant for the stable share of usage, once waste has been removed. Committing before optimising amounts to guaranteeing the provider payment for resources you do not need.

Does FinOps also reduce the environmental footprint of the cloud?

In part. Removing unused or oversized resources reduces both cost and consumption. But the two objectives sometimes diverge: a pricing discount lowers the bill without changing usage at all, and the cheapest region is not necessarily the lowest-carbon one. Separate indicators must therefore be tracked.

Who should lead the FinOps approach in the organisation?

A small central team drives the practice, provides the data and manages pricing commitments. Optimisation decisions belong to the teams that operate the resources, because only they know the constraints of their applications. Finance and procurement are involved in forecasting and negotiation.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.