Cloud Reselling Pricing: How Finance Teams Can Defend Margins as Consumption Grows

Cloud consumption is growing. Your revenue is growing with it. But is the value you deliver to the customer growing at the same rate?

For cloud resellers and managed service providers (MSPs), consumption-based pricing can create a disconnect between revenue growth and the work required to serve a customer. Finance teams need to understand that disconnect—and be able to explain it during pricing negotiations.

This article explains the economics behind cloud reselling fees, compares four pricing models, and provides a practical framework for protecting margins without relying on cost arguments alone.

At a glance

• Consumption growth does not automatically justify proportional growth in reseller fees.
• Customers evaluate more than your costs: they also consider the value, risk and complexity you take off their hands.
• Four common approaches are consumption-based, cost-plus, fixed-fee and hybrid pricing.
• The strongest pricing model reflects the underlying service economics—not just the cloud bill.

1. Why consumption growth creates a pricing problem

Consider a cloud reseller charging a 2% fee on cloud consumption. A customer’s annual consumption grows from €10 million to €30 million. The reseller’s fee increases from €200,000 to €600,000—even if the workload required to manage the account has not tripled.

This is where a seemingly straightforward pricing model can become difficult to defend. A customer may accept that a larger cloud environment generates a larger bill, while questioning why the reseller’s compensation should increase at the same rate.

2. Why cost-based arguments are not enough

A common response is to explain that the reseller has higher costs. That may be true, but it is not always a convincing commercial argument.

If the customer’s cloud consumption triples while the reseller’s operational workload grows only modestly, a proportional increase in fees can look like an automatic revenue uplift rather than compensation for additional work or value.

Finance teams should distinguish three economic drivers:

• Revenue driver: the variable that determines how much the customer pays, such as cloud consumption.
• Cost-to-serve driver: the activities and resources required to support the account.
• Value driver: the business outcome, risk reduction or complexity the reseller helps manage.

A sustainable pricing model should make sense against all three. If revenue is tied to consumption but service effort is largely fixed, the pricing architecture deserves closer scrutiny.

3. What is the customer actually paying for?

Before negotiating the fee, define the service being provided. Cloud reselling can combine several activities, each with different cost and value drivers.

Transaction and billing management

This can include consolidated billing, invoice validation, usage allocation, reconciliation, payment administration and handling billing disputes. Some of these activities scale with transaction volume or account complexity; others may be largely fixed.

Commercial management

Customers may rely on the reseller for contract coordination, pricing discussions, consumption commitments, cloud-provider escalations and commercial planning. The workload may depend more on the number and complexity of agreements than on total consumption.

Governance, compliance and operational support

Support may include reporting, policy administration, compliance evidence, account governance and coordination across teams. The level of effort depends on the service scope, regulatory requirements and operating model.

These activities should not be treated as one undifferentiated service. Separating them helps finance teams identify which services scale with consumption, which scale with workload, and which represent a recurring fixed commitment.

4. Do not overlook risk and capital

Cost-to-serve is only part of the economics. Depending on the contractual arrangement, a reseller may also take on working-capital requirements, customer credit exposure and operational or contractual risk.

For example, if the reseller pays the cloud provider before collecting from the customer, growth in consumption can increase the amount of capital tied up in the business. If payment terms are long, the resulting financing requirement can become material.

Finance teams should therefore assess:

• Working capital: how much cash is required to fund the gap between supplier payments and customer receipts?
• Credit risk: who bears the loss if a customer pays late or defaults?
• Contractual exposure: are there commitments, minimum purchases or other obligations that remain even if customer demand changes?
• Operational exposure: who is responsible for billing errors, service coordination and dispute resolution?

Where these risks genuinely sit with the reseller, they can form part of the economic rationale for pricing. They should be quantified where practical, rather than used as generic justifications for a higher fee.

5. Four pricing models to consider

There is no universally best pricing model. The right choice depends on how service effort, customer value, risk and consumption behave as the account grows.

Model	How it works	Best suited to	Main risk
Consumption-based	Fee is a percentage of cloud spend or usage.	Services whose value or exposure scales meaningfully with consumption.	Fees can grow faster than service effort or perceived value.
Cost-plus	Defined service costs plus an agreed margin.	Services with measurable, attributable delivery costs.	Cost scrutiny and weak incentives to improve efficiency if poorly designed.
Fixed fee	Agreed recurring fee for a defined scope of services.	Predictable, relatively stable service requirements.	Scope creep or unexpected growth in workload.
Hybrid	Fixed fee combined with a variable component.	Accounts with both stable service requirements and consumption-related exposure.	More complex design, measurement and communication.

Consumption-based pricing

A percentage of cloud consumption is easy to understand and can align revenue with the scale of the customer relationship. It is most defensible when the underlying service, value or risk also scales with consumption.

However, the model can become difficult to justify when consumption grows because of a migration, a larger workload or higher usage, while the reseller’s service scope remains broadly unchanged.

Cost-plus pricing

Under cost-plus pricing, the provider identifies relevant delivery costs and adds an agreed margin. The approach can support transparent cost recovery, but requires clear rules for allocating overhead and defining the cost base.

It is also important to avoid equating higher costs with higher customer value. Customers may reasonably expect efficiency gains as the provider scales.

Fixed-fee pricing

A fixed recurring fee is appropriate when the service scope and expected workload are relatively predictable. It gives the customer cost certainty and makes the reseller’s revenue less sensitive to consumption fluctuations.

The agreement should define included services, service levels, assumptions and change-control mechanisms. Otherwise, growth in complexity can erode margins without a corresponding price adjustment.

Hybrid pricing

A hybrid model separates the stable cost of providing the service from the part that genuinely varies with consumption, workload or risk. For example, the contract might include a fixed account-management fee plus a variable charge linked to a defined consumption band or service metric.

The variable component should have a clear economic rationale. A hybrid model is not automatically better if it simply adds complexity without improving the alignment between price and service economics.

6. Should pricing be based on subscriptions or consumption?

The pricing metric matters as much as the pricing model. Total cloud consumption is only one possible proxy for the work and value involved in serving a customer.

Depending on the service, alternative metrics could include:

• Number of subscriptions, tenants or billing accounts managed.
• Number of invoices, billing entities or legal entities supported.
• Number of managed workloads or environments.
• Defined service tiers based on complexity, support requirements or governance scope.
• Consumption bands with different rates or minimum fees.

The objective is not to choose the most sophisticated metric. It is to choose one that customers can understand, finance teams can measure, and both parties can relate to the underlying service.

7. A five-step framework for finance teams

Use the following framework before changing a pricing model or entering a renewal negotiation.

Step 1 — Map the revenue drivers

Identify exactly how the current fee is calculated. Determine which variables drive revenue and how changes in consumption, customer scope or contract terms affect the result.

Step 2 — Model the cost-to-serve

Break down the activities required to support the customer. Estimate which costs are fixed, which vary with consumption, and which increase in steps when new accounts, workloads or service requirements are added.

Step 3 — Quantify risk and capital requirements

Assess working capital, credit exposure, contractual commitments and operational responsibilities. Include only those risks that are genuinely borne by the reseller and avoid double-counting them elsewhere in the margin model.

Step 4 — Compare alternative pricing scenarios

Model the current structure alongside realistic alternatives