M$Million Dollar Servicesby James Smith

Guide

How to price managed services: pricing models, tiers, margin, SLAs and fair use

A managed service is priced well when the unit fits the way the effort moves, the price is built up from what the service costs to serve, and the promises are written down. This guide covers the pricing models and when each fits, good-better-best tiers, pricing from cost to margin, service levels, fair use, onboarding fees and the annual price review.

Managed services pricing comes down to five decisions: the unit the fee is attached to, the tiers the service is packaged in, the price of each tier built up from what it costs to serve, the promises written into the agreement, and the date the price is next reviewed. Choose the unit well and build the price from the cost to serve rather than from a competitor’s list, and a managed service is the strongest recurring revenue a services firm can hold. Get either wrong and a few heavy clients quietly eat the margin the rest earn. The free MSP pricing calculator runs the arithmetic in this guide on your own numbers, and the Managed Services Pricing and Service Design Kit sets out the whole method, from the pricing model to the annual review.

This guide is written for the provider: a managed service provider running IT for small and mid-market businesses (users, devices, servers, sites, security, Microsoft 365 and backup), or a consultancy, agency or IT services firm adding a recurring service beside its project work. Every figure in the worked examples is invented and labelled as such.

The pricing models, and when each fits

There is one rule for choosing a model: price on a unit that moves when your effort moves and that the client can count. A unit that tracks your effort keeps the margin steady as the client grows or shrinks. A unit the client can count keeps the monthly invoice from becoming an argument. Every common model passes or fails on those two tests.

Model The unit Where it fits Where it breaks
Per user A named person who signs in each month, with their devices up to a stated number Most small and mid-market clients: office staff on laptops and Microsoft 365 Shared devices, and users with many devices, unless the number a user covers is written down
Per device A laptop, desktop, server or network device Estates where devices drive the work: shared terminals, warehouses, clinics, schools A laptop and a server priced as the same work, unless they are priced separately
Per site A location, its network and its connection Multi-site clients, as an add-on to a per-user or per-device price Rarely the whole price: a site says little about the people in it
Good-better-best tiers The same unit at three levels of service Nearly every MSP, as the packaging around one of the units above Tiers that differ only in hours, or more than three of them
All-inclusive One fixed fee for all in-scope support Clients who want a predictable monthly cost Becomes unlimited support unless a fair-use line is written down
A la carte Each service priced on its own: backup, security, Microsoft 365 management Clients with some IT of their own, and co-managed arrangements Gaps between services, and a total the client cannot compare
Per application or system A line-of-business system supported, such as a practice management system or an ERP Application-heavy clients, where a few systems rather than headcount drive the effort Needs a view of how demanding each system is that both sides accept
Retainer Recurring deliverables plus an included allowance of hours Consultancies, agencies and IT services firms adding a recurring service Unused hours, and a scope nobody wrote down
Block of hours Prepaid or metered time Small clients with irregular demand, and break-fix Pays you most in the month the client is least happy
Percentage of spend A share of what the client spends on licences, cloud or IT Resale margin on licences, kept on its own line As the service fee, it pays you more when the client spends more, whatever it costs you to serve them

Most MSPs combine them, and the surveys do not settle which unit leads: Kaseya’s 2023 Global MSP Benchmark found a combination of per user and per device the most common answer among its respondents, and MSP Success’s 2025 survey put per device ahead of per user. For most small and mid-market clients I would start with a price per user in three tiers, with servers and sites as add-ons. Clients think in headcount, a user’s laptop, phone and Microsoft 365 account come with them, and the add-ons stop a client with a room full of servers being priced as if it had none. Choosing the unit for your own clients, per user or per device, is where the MSP pricing model kit starts.

Value-based pricing is not a separate unit so much as a ceiling. The cost to serve sets the floor; what the service is worth to the client decides how far above the floor you can sell.

Per application, for application-heavy clients

Per application is one option worth knowing, not a default. Some clients, such as a professional practice built around one core system or a distributor that runs on its ERP, need little from you per head and a great deal per system. For them a monthly fee per supported system, set from the hours that system takes, tracks the effort better than headcount does. It needs two things the per-user model does not: an agreed view of how demanding each system is, and a review when a system changes. For an office of people on laptops and Microsoft 365, per user with add-ons is simpler to sell, simpler to count and just as fair.

Why not a percentage of the client’s spend

A service fee set as a share of what the client spends, on licences, on cloud or on IT in general, is easy to measure and tends to rise, which is why it persists. It is also the one model where the fee has nothing to do with the cost of serving the client. A client who cuts waste pays you less for the same work, and a client whose spend grows pays you more for none. Where you resell licences, keep the resale margin on its own line at its own terms, and price the service on a unit that tracks the work.

Building good-better-best tiers

Three tiers is the usual answer, and for good reason. Most clients choose the middle one, the bottom tier gives a price-conscious client a way in, and the top tier makes the middle look reasonable while catching the clients who want more. Design the middle tier first, as the service you want most clients on, then take things out for the bottom and add things for the top.

  • Each step adds something a client can name. Tested backups rather than monitored ones, security awareness training, out-of-hours cover, a named adviser who plans the client’s IT with them. A tier that differs only in hours asks the client to value your time, not the service.
  • The unit stays the same across the tiers. A price per user in every tier, so the client compares the service and not the arithmetic.
  • The bottom tier still makes money. It is the smallest service you are willing to run, priced at the same target margin as the others, never a loss leader you hope to upgrade later.
  • Every tier says what it excludes. Projects, new hardware, onboarding, licences and out-of-hours work, unless the tier includes them. The exclusions prevent more disputes than the inclusions.
  • Three is enough. A fourth tier usually splits the most popular one and makes the choice harder.

An invented three-tier design, with working names you would replace with your own:

In each tier Steady Assured Guided
Service desk, business hours Included Included Included
Patching and device monitoring Included Included Included
Backup Monitored Monitored, with a tested restore each quarter Monitored, with a tested restore each month
Security Endpoint protection and email filtering Adds security awareness training Adds a monthly security review
Account care A quarterly check-in A quarterly service review A monthly review and a yearly IT plan with a named adviser
Out-of-hours priority incidents At the rate card At the rate card Included
Price per user a month (GBP, invented) 69 94 132

Pricing from the cost to serve to the margin

The price starts from what one agreement costs to deliver each month, not from what a competitor charges. Four lines make the cost to serve for each seat:

  1. Labour. The modelled hours per user a month multiplied by your loaded cost per productive hour: the full yearly cost of employing an engineer divided by the hours they actually log to client agreements, not the hours they are contracted for. That puts your utilisation (utilization) inside the price, where it belongs.
  2. Tool stack. Every tool the tier includes, per seat, line by line: remote monitoring and management, endpoint protection, backup, email security, documentation.
  3. Overhead share. The service desk lead, training and internal systems that are not in the tool stack.
  4. Risk buffer. A small percentage for the month that goes wrong.

Divide the cost to serve by one minus your target margin and round up: that is the floor price. Only then check it against the market. The market check can move a price up; it never moves it below the floor.

In an invented example, a UK MSP loads an engineer at £41,070 a year and logs 1,226.55 of that engineer’s hours to client agreements, a cost per productive hour of £33.48. Its middle tier models 0.42 hours of labour per user a month and 2.5 hours of account care per client a month. For an invented client with 46 users:

Line, per user a month GBP, invented
Labour: 0.42 hours at £33.48 14.06
Account care: 2.5 hours at £33.48, spread across 46 users 1.82
Tool stack 17.60
Overhead share 4.80
Risk buffer: 5.5% of the lines above 2.11
Cost to serve 40.39
Floor price at a 57% margin: 40.39 divided by 0.43, rounded up 94

Servers and sites are priced the same way, as add-ons: £247 a server and £88 a site in this example. The client’s 46 users, 2 servers and 2 sites make £4,994 a month at a 57.0% agreement margin, and the same method prices the bottom and top tiers at £69 and £132 per user. These are the calculator’s defaults, so you can reproduce every figure and then replace them with your own.

The division matters. Adding 57% to the cost gives £63.41 per user, which is a margin of only 36%. Markup is measured on the cost and margin on the price, and a managed service priced on markup falls short of its target on every agreement.

Set the target margin on your own cost definitions, then hold every agreement to it. Published figures vary, partly because sources count cost differently: Service Leadership (ConnectWise) reported an average managed service gross margin of 46.2% for the second quarter of 2024, while Kaseya’s metrics guide says there should be at least a 65% gross margin on each agreement. The 57% here is invented.

The price is only right on the day it is signed. Read every agreement’s margin and effective hourly rate each month afterwards: the fee less the tool stack, divided by the hours logged to it, compared with your rate card. In the example that is £152.10 an hour against a £120 card. When I ran DevOpsGroup, a price on managed work had to clear a margin floor I set before I would sign it. What I would add from the first day is time recorded against every client, because modelled hours are a guess until your own records replace them.

Service levels: response committed, resolution targeted

A service level agreement is the promise the price pays for, and the most common mistake is promising what you do not control. Commit to response: how quickly a person acknowledges a ticket and starts work on it, by priority. You control that. Publish resolution as a target and report against it. How quickly an issue is fixed depends on vendors, third parties, parts and the client’s own availability, and a committed resolution time turns every slow vendor into your breach.

Set priority from impact (how many people are affected) and urgency (how soon it hurts the business), and write the grid into the agreement so that priority is not argued ticket by ticket.

Priority Example Response, committed Resolution, target
P1 The business, a site or a key system has stopped 30 minutes 4 hours
P2 A team has stopped, or the business is badly slowed 1 business hour 1 business day
P3 One person is stopped or slowed, with a workaround 4 business hours 3 business days
P4 A request or a question 1 business day As scheduled

The times are invented; set yours from the staffing you can actually hold. State the hours of cover beside the grid, and what happens outside them: a priority 1 at two in the morning is covered by the top tier or charged at the rate card, never left to whichever engineer happened to see the email. If you offer service credits, tie them to response, cap them at a small share of the month’s fee and pay them as credit against the next invoice. Report every line every month, misses included. A client who sees the misses reported believes the hits.

Fair use: all-inclusive is not unlimited

All-inclusive means in-scope support is included within reason, and fair use makes “within reason” a line both sides can see. A useful line is the monthly hours at which the agreement’s effective hourly rate falls to your rate card. Below it, the fixed fee earns more than the same hours would at your standard rate; above it, the client is getting more hours than the fee buys. In the invented example, £4,994 less £914.80 of tools, divided by the £120 rate card, puts the line at 33.99 hours a month against 26.82 modelled.

A heavy month is noted, not billed. A client running above the line for several months in a row gets the data and a conversation first, because the cause is usually fixable: an ageing device fleet, a new-starter process nobody wrote down, a system that needs a project rather than a stream of tickets. The remedies come in order. Fix the cause, move the client to a tier that fits, and only then reprice, with the notice the agreement gives. Show the client every included hour, what was used and what it went on, so the conversation starts from shared numbers rather than a surprise invoice.

Onboarding fees

Taking a client into service is a project, and it should be priced as one. Discovery, documentation, deploying your monitoring, security and backup tools, taking over access and licences from the previous provider, and fixing what cannot be supported as it stands all take hours before the first monthly fee is earned. Price onboarding from its own hours as a fixed fee, deliver it as the first piece of work, and start the monthly service on a stated date once it is complete. Onboarding is also where the client first learns what working with you is like, so give it a checklist, a named contact and an end date.

Waiving the fee is tempting in a competitive sale and nearly always a mistake. It hides a cost in the first months of the agreement, so the client looks unprofitable just as you form a view of them, and it tells the client the setup had no value. If you need a concession to win the work, show the onboarding fee at its full price and the discount as a separate line, so the value of the work stays on the page.

The annual price review

Labour and tool costs rise every year, and an agreement nobody reprices loses margin quietly until a large catch-up rise puts the client at risk. Write an annual review into every agreement, with a cap on the rise, and run it on a calendar rather than after the margin has already gone. Recompute every price from next year’s costs instead of picking a percentage in the room: the rise is what the model needs to restore the target margin, and never more than the cap.

In the invented example, pay lifts the cost per productive hour by 5.8% and tool prices rise 7.9%. Left alone, the middle tier’s margin falls from 57.0% to 54.4%. Recomputed, the price per user moves from £94 to £100 and the client’s fee from £4,994 to £5,316, a rise of 6.4%, inside an 8.5% cap, and the margin comes back to 57.2%.

Pass vendor price changes through under their own clause, separate from your own review, so a Microsoft 365 rise is never mistaken for yours. MSP Success’s January 2025 survey found that 42% of MSPs review prices annually and fewer than one in ten have automatic increases written into their contracts. The clause costs nothing to write and a great deal to leave out.

Before you send the proposal

Seven questions, answered on paper:

  1. Does the unit move with our effort, and can the client count it? If either answer is no, choose again.
  2. Is every tier priced from the cost to serve at the same target margin? The bottom one included.
  3. Does each tier add something the client can name? More hours alone is not a tier.
  4. Are response times committed and resolution times targets? With the hours of cover stated beside them.
  5. Is the fair-use line written down, and will the client see the hours?
  6. Is onboarding priced as its own fixed fee, with a service start date?
  7. Is the annual review in the agreement, with its cap and a separate clause for vendor price changes?

A pricing model is not a rate card, but it depends on one. Your cost per productive hour and your rate card come from the same cost base as a consultant day rate, and the free consulting rate calculator builds the card itself.

Where to go next

The Managed Services Pricing and Service Design Kit sets out the whole method for an MSP or a firm adding a recurring service: choosing the pricing model, building each tier from the cost to serve, service levels, fair use, onboarding and the annual price review, with a pricing model that returns the floor price and the margin of every agreement. The free managed services pricing calculator runs the same arithmetic on your own numbers. For how a managed service differs from a retainer, see what a monthly retainer is, and for how the revenue is counted, recurring revenue.

Questions

How much does an MSP charge per user?
It depends on what the tier includes and on your own costs, and published ranges are wide. For the UK, Compare the Cloud's 2026 procurement guide puts a basic tier at £30 to £50 per user a month, a middle tier at £50 to £80 and a top tier at £80 to £150, and Kaseya's 2023 Global MSP Benchmark found $50 to $100 a month the most common per-user band among its respondents. Use those as a check, not a method: build your own price from the cost to serve and your target margin, then compare.
What are the main managed services pricing models?
Per user, per device, per site, good-better-best tiers, all-inclusive, a la carte, per application or system, and, for a professional services firm, the retainer. Block hours and a percentage of the client's spend are sold too, though neither ties the fee to the cost of serving the client. Most MSPs combine them: a price per user in three tiers, with servers and sites as add-ons, is a common shape for small and mid-market clients and the default in this guide.
What should each managed services tier include?
Design the middle tier first, as the service you want most clients on, then take things out for the bottom tier and add things for the top. Each step should add something a client can name, such as tested backups, security awareness training, out-of-hours cover or a named adviser, rather than more hours. Keep the unit the same in every tier, price each at the same target margin, and say what each one excludes.
Should an MSP charge an onboarding fee?
Yes. Taking a client into service is a project: discovery, documentation, deploying your tools, taking over access from the previous provider and fixing what cannot be supported as it stands. Price it from its own hours as a fixed fee, deliver it as the first piece of work, and start the monthly service on a stated date once it is done. Waiving it hides a cost in the first months of the agreement and tells the client the setup had no value.
What should a managed services SLA commit to?
Commit to response times, because you control them: how quickly a person acknowledges a ticket and starts work, by priority. Publish resolution times as targets and report against them, because resolution often depends on vendors, third parties and the client. State the hours of cover, how priority is set and what happens outside those hours, and keep any service credits tied to response, capped and small.

Terms used here

Last updated 27 September 2026. Written by James Smith from notes, diaries and recollections; nothing here is a guarantee of results.