Blog / buying advice
How to read a managed IT services quote
Managed IT proposals price a relationship, not a thing. Here is how I read one: the unit of pricing, the exclusions page, and who owns the tooling.
A managed IT proposal is the hardest kind of quote to compare, because you are not buying a thing. You are buying a relationship with a price attached, and relationships are easy to describe vaguely.
Most of the proposals clients forward me have the same shape. A monthly number, a per-user or per-device rate, a page of reassuring language about proactive monitoring, and an appendix nobody reads. The appendix is the actual contract. Everything before it is marketing.
Here is the order I read them in.
Work out what the unit is
The first thing to settle is what you are being charged per. Per user, per device, per site, or a flat fee with a headcount band.
Per-user pricing sounds simple until you ask what counts as a user. Does a part-time bookkeeper who logs in twice a week cost the same as a full-time employee? What about a shared warehouse login, or a seasonal crew? Per-device pricing has the mirror problem: the quote covers twenty-two workstations today, and nobody mentioned the two servers, the NAS, the firewall and the four printers, which are usually billed separately at rates two or three times the workstation rate.
In Ontario I typically see per-user managed pricing land somewhere between roughly $100 and $250 CAD per user per month, and that range is so wide it tells you almost nothing on its own. The spread is not about quality. It is about what is inside the number. A $120 seat that excludes after-hours support, server coverage and security tooling can easily cost more over a year than a $200 seat that includes all three.
So before comparing two monthly figures, write down what each one actually covers. If the two lists are different, the two numbers are not comparable, and no amount of staring at them will make them so.
Read the exclusions before the inclusions
Every managed agreement draws a line between support and projects. Support is covered by the monthly fee. Projects are billed separately. That line is where the money moves, and it is almost always drawn in the vendor's appendix rather than discussed on the call.
The things that usually fall on the project side: anything involving new hardware, office moves, server migrations, email platform changes, cabling and physical installation work, and anything described as a "major" change. That is reasonable in principle. What is not reasonable is leaving the definition of "major" to the party that bills for it.
Ask for examples instead of definitions. If a workstation dies, is the replacement setup support or a project? If you add four staff, is onboarding them included? If your line-of-business software vendor pushes an update that breaks printing, who owns the fix, and is sitting on hold with that vendor billable time?
Physical installation almost never sits inside a managed contract, and it should not. Cabling, mounting, cameras and access points are project work with their own quote, which is the kind of job my company RelayPoint Technologies does across Southern Ontario. The point here is just to know which bucket a request lands in before you make it.
Response time is not resolution time
Nearly every proposal promises response times. Very few promise anything about resolution, which is the thing you actually care about.
A one-hour response target means someone acknowledges your ticket within an hour. It says nothing about whether your point-of-sale system works again today. That is not dishonest, and no sensible vendor will guarantee resolution on problems they have not seen yet. But you should know which promise you are getting.
Then check the small print around it. Whose business hours apply? Are the priority levels defined by you or assigned by them? If their own definitions decide what counts as urgent, the response target is a target they control both sides of.
Ask whose tooling it is
The monthly fee usually bundles software: remote monitoring, antivirus or endpoint detection, patching, email filtering, often backup. Convenient, and it is a real part of the value. It is also the part that walks out the door with the vendor.
Three questions settle it. Are these licences in your name or theirs? If the relationship ends, how long do you keep working systems while you transition? And if they hold your backups, how do you get your data out in a usable form, at what cost, and how quickly?
I have watched more than one business discover the answer to that last question during the week they were already unhappy. Settle it while everyone is still friendly.
Then look at the term
Onboarding or remediation fees are normal. A vendor inheriting a neglected environment has real cleanup to do before they can support it predictably, and if they have waived that fee entirely, ask what they are expecting to skip.
The term and the renewal clause matter more. Three-year terms with automatic renewal and a short cancellation window are common, and a good proposal will tell you plainly how to leave. I wrote separately about what to check before a technology contract renews, and the same reading applies here on day one rather than year three.
None of this requires technical knowledge. It is the same discipline you would apply to any service contract, which is roughly the argument I made about managing IT vendors when you are not technical.
If you have a managed services proposal on your desk and want someone who reads these every month to go through it with you, that is the kind of thing I do as a second opinion, quoted as a fixed fee or hourly depending on the size of the agreement. Get in touch and send it over.