Why percentage-of-spend pricing quietly kills MSP FinOps practices

The incentive problem hiding in plain sight

A percentage-of-spend fee looks simple because it scales automatically with the estate. It also means the provider earns less after a successful optimisation programme and more when client waste grows. This article will examine why that tension becomes harder to explain as an MSP turns isolated cost reviews into a durable service line.

Outline

• Model the revenue drop that follows a successful first optimisation cycle.
• Separate the value of ongoing operational discipline from the volume of Azure consumed.
• Compare fixed bands, per-tenant fees and outcome-linked components.
• Protect gross margin by standardising discovery, prioritisation and evidence gathering.
• Give account teams a renewal story based on avoided waste and delivery cadence.

A healthier commercial unit

The expanded article will argue for pricing against a stable operating unit, such as a managed-spend band or portfolio tier, rather than taking a direct share of the bill. The MSP can still acknowledge complexity as the estate grows, but its margin no longer depends on cloud costs moving in the wrong direction.

What clients should be buying

Clients are not buying a monthly PDF or a promise that every pound of waste will disappear. They are buying continuous detection, qualified engineering judgement, safe execution and evidence that changes produced the expected result. A pricing model should make that operating system easy to understand and renew.