Skip to main content

Beta candidates wanted About the beta

← All insights

Individuals

Cloud economics for sellers: what FinOps changes in discovery

ASTRA Ready editorial ·

Cover image for Cloud economics for sellers: what FinOps changes in discovery

A cloud proposal can look simple until the buyer asks, “What will actually drive our bill?”

That question is where product selling meets cloud economics.

The FinOps Foundation's State of FinOps 2025, presented on 20 February 2025, surveyed 861 respondents responsible for about $69 billion in public-cloud spend. The report says workload optimisation and waste reduction remained the top current priority, while allocation and accurate forecasting also ranked highly. [Source: FinOps Foundation, 20 February 2025.]

Those figures describe the survey population, not every cloud customer. The useful lesson for sellers is broader: buyers increasingly need to understand usage, cost ownership and value together.

Start with the meter

Before discussing savings, understand what is being measured.

Is the commercial unit a user, transaction, request, storage quantity, compute duration, data movement event or another meter? What period applies? Is the measurement average, peak, accumulated or committed?

Two offers can use similar language while charging for different things.

A seller who cannot explain the billable unit will struggle to explain the commercial consequence of customer behaviour.

Separate usage from commitment

A customer may consume less than expected and still owe a committed amount.

Another offer may be purely usage-based but have a different unit rate after a threshold. A third may bundle an entitlement with separate implementation or support.

Do not collapse those models into “pay for what you use.”

Write down the meter, period, minimum, threshold, owner and any unused commitment rule that appears in the commercial evidence. If a term is not stated, mark it unknown rather than filling the gap from experience.

Ask who owns the cost driver

FinOps is collaborative because cloud cost is created by technical and business decisions.

The FinOps Foundation's 2025 Framework update, published 20 March 2025, broadened the framework around technology-spending scopes and reinforced principles linking technology usage to ownership and business value. [Source: FinOps Foundation, 20 March 2025.]

For a seller, this means discovery should include ownership.

Who can change the workload? Who can change the commercial commitment? Who forecasts demand? Who approves an architecture choice that changes consumption? Who sees the bill early enough to act?

The person negotiating the contract may not control the usage that creates the charge.

Do not promise savings from a model alone

Sales teams often build a comparison from current usage and proposed usage.

That can be useful, but label it correctly.

A model is a model until the assumptions are observed in operation. If it assumes a lower consumption level, automated shutdown, different storage pattern or reduced manual effort, show that assumption.

Do not convert “modelled reduction” into “customer saving” before the operating change happens.

This is especially important in consumption services where the new product may also change user behaviour. A lower unit cost can still produce a higher bill if usage expands.

AI spend makes the same discipline more important

The State of FinOps 2025 reported that 63% of respondents were managing AI spending, up from 31% in the prior year's survey. [Source: FinOps Foundation, 20 February 2025.]

That does not tell a seller what one customer's AI workload will cost.

It does show why cost visibility, forecasting and allocation are becoming part of AI conversations as well as traditional cloud conversations.

If the AI use case is still experimental, ask what will be measured before claiming an economic result.

Discovery questions should become more commercial

Instead of asking only, “How much do you spend today?”, ask what creates the spend.

Which teams consume it? Which workloads are predictable? Which commitments already exist? What changes at a threshold? Which service is one-time and which recurs? Who owns exceptions? What would make the forecast wrong?

These questions help the buyer compare offers without pretending the seller can predict every future bill.

Cloud economics is not a finance-only topic. It is part of explaining what the customer is agreeing to.

A seller who can make the meter, period, owner and commitment visible is more useful than one who simply repeats the headline rate. That fluency also makes internal handoffs cleaner because finance, pre-sales and the account team are working from the same commercial model.

Next step: Strengthen cloud and commercial-economics judgment with the ASTRA Tech Sales Associate programme: https://www.astraready.com/programmes/

Sources