Managed service model
Definition
Managed service model
A managed service model is the commercial structure behind a managed engagement: how scope is bounded, what the fee attaches to, what transition costs at each end, and how both sides judge whether it is working. It is the pricing, not the idea.
OA’s entry on managed services answers what the model is — a provider taking ongoing responsibility for a defined function. This page answers how one is structured, and when it is the wrong shape to buy at all.
Get the mechanics wrong and the label does nothing for you. Most disputes in year two trace back to three lines agreed in week one: the scope boundary, the unit the price attaches to, and what happens at exit.
Key takeaways
- Scope is defined by its exclusions as much as by its inclusions.
- The pricing unit decides which behaviour the provider is paid to produce.
- Transition is a cost at both ends, and the exit is the one nobody budgets.
- Without tracked savings, nobody can say whether the model worked.
How it works
Four commercial choices define a managed service model: the scope boundary, the pricing basis, the transition terms at each end, and the governance that reviews the result. Everything else in the contract hangs off those four.
The pricing basis matters most, because it decides what the provider is rewarded for doing more of.
| Pricing basis | Priced per | Fits when | Watch for |
|---|---|---|---|
| Per seat | Named user | Headcount is stable | Licences nobody uses |
| Per ticket | Resolved request | Volume drives the cost | Tickets split to lift the count |
| Per device | Endpoint managed | The estate is countable | Equipment outside the agreed list |
| Per outcome | Agreed result | The result is measurable | Arguments over what counted |
| Fixed monthly | The whole function | Scope is genuinely stable | Growth with no price review |
Scope is a boundary, not a list — write down what sits outside it, because the exclusions are what you will argue about. Name the volumes the price assumes and the point at which a volume change reopens the fee.
Price and promise travel together. A fee means nothing without a service level that defines what counts as late, how it is measured, and what the provider pays back when the number is missed.
Transition is a cost at both ends and only one of them usually gets priced. Budget the exit as well: knowledge transfer, tooling you do not own, data in the provider’s format, and a parallel run while the next team takes over.
Much of this market sits on cloud delivery. NIST Special Publication 800-145 defines cloud computing as on-demand network access to a shared pool of configurable computing resources, released with minimal management effort.
A cloud managed service wraps labour, tooling and accountability around that, which is why its pricing usually splits into a platform fee plus consumption you cannot fix in advance.
The commercial shape holds whether the function is technical or administrative — IT managed services and finance operations both price against a countable unit and a measured promise.
Measurement is the part buyers skip. Across 16 federal agencies, the US Government Accountability Office found they could not consistently track cloud spending and savings, so reported figures were likely understated.
That finding travels. If nobody owns the baseline, the quarterly review becomes a conversation about tickets rather than about whether the arrangement is still worth its fee.
Examples
The model takes different commercial shapes depending on what can be counted. Three engagements show how the pricing unit changes the behaviour it produces, and where the structure starts to strain.
A service desk priced per seat. A mid-market retailer in Poland buys first and second line support for 1,400 staff at a monthly rate per named user, with joiners and leavers trued up each quarter against an agreed band.
Claims handling priced per transaction. An insurer pays a fee per processed claim against an accuracy floor — the unit the buyer actually cares about. The contract caps rework at the provider’s cost, which stops speed being bought with errors.
Back office in a growth business. A Bogotá delivery team runs invoice processing on a fixed monthly fee. Volumes doubled in eighteen months, the fee did not, and both sides ended up renegotiating what should have been a banded price from the start.
The model stops fitting when the work is not repeatable, when demand swings beyond any sensible band, or when the scope boundary cannot be drawn without an argument. Project work and fully managed outsourcing of a whole function sit either side of that line.
Related terms
These terms sit beside the commercial mechanics on this page. Each one covers a different slice: what the model is, where it is applied, how the promise is drafted, and what happens when more than one provider is involved.
- Service level agreement clause: the drafting detail inside the promise, down to remedies and measurement windows.
- Multi-sourcing model: running several providers at once, which adds an integration question this page does not cover.
- Managed services: what the model is and what it covers; this page is how one is structured.
- IT managed services: the technology application of the same commercial shape.
- Service level: the measured promise the fee is attached to.
FAQ
What should the fee be attached to?
Attach it to the unit that best tracks the work and is hardest to game. Per seat suits stable teams, per ticket suits volume-driven support, and per outcome only works when both sides accept one definition of the result.
How long does transition take?
Expect a transition phase before the provider takes full control, and a second one at exit. Price both, and write the exit assistance obligation into the contract rather than negotiating it during a breakup.
When is a managed service model the wrong choice?
When the work is not repeatable, when the scope cannot be bounded on paper, or when demand swings so far that no price band holds. Those engagements usually belong in a project or a staffing arrangement.
Who should own governance on the buyer’s side?
One named person with budget authority, supported by whoever owns the affected process. Governance fails when the only buyer-side attendee at the review is the person who raises the tickets.
How do you tell whether the model is working?
Track the baseline you started from, the service levels met, and the cost per unit over time. Review those three together, because any one of them read alone will flatter the arrangement.
Compare managed service providers by scope and pricing basis in the Outsource Accelerator provider directory.
Independent
