How to Compare Managed IT Quotes Without Getting Burned

You have two managed IT quotes on the desk. One is a little over half the price of the other. Both are a page long, both are priced per user per month, and both list roughly the same words — helpdesk, monitoring, backup, security, Microsoft 365. On the evidence in front of you they look like the same service at two very different prices. They almost never are.

This guide is the line-by-line version of that comparison: what the monthly number actually buys, which costs sit outside it, the eleven items worth checking in every proposal, and how to put competing quotes onto a single page so the arithmetic is honest. It is written by a provider — IT Rapid Support, based at 7810 Keele St in Vaughan — so read it with that in mind. The checklist works just as well against our proposal as anyone else's, which is rather the point.

Why Two Quotes for the Same Business Can Differ by 100%

Per-user pricing looks like a unit of measurement and behaves like a marketing decision. The number tells you the price of one unit; it tells you nothing about what a unit contains. Two providers quoting the same business can be counting different people, covering different devices, absorbing different amounts of risk, and drawing the boundary between "support" and "project" in completely different places. Scope is the whole game, and scope is the part of the quote that is usually written last and shortest.

The second mechanism is where each provider chose to put the money. Every managed agreement is a bet about how much work your environment will generate, and a provider who prices that bet cheaply has to protect the margin somewhere. None of it is dishonest. It only becomes a problem when you compare the two numbers as though they bought the same thing.

What a Managed IT Quote Usually Shows You — and What It Leaves Out

The per-user or per-device number

This is the figure everyone anchors to and the least comparable thing on the page. Ask each provider to define, in writing, exactly who counts as a user: shared floor accounts, contractors, seasonal staff, mailboxes with no human behind them, and the owner who barely logs in. Then ask what happens to devices — the servers, firewalls, switches, access points and unattended machines that do not map to a person but still need patching and monitoring. Two providers can quote the same twenty-five staff and be pricing a materially different amount of work.

The line items that are almost always missing

The costs that surface after signature are consistent enough to list. Onboarding and discovery, usually a one-time fee and sometimes a substantial one. After-hours and weekend labour. Project work — migrations, office moves, new site builds — billed separately from the monthly fee. Hardware procurement, often carrying a margin that is never itemised. Third-party licences, which may be resold at markup or passed through at cost. And, at the far end of the relationship, offboarding: what it costs to get your documentation and backup data out if you leave. A quote that shows none of these is not a quote without those costs. It is a quote that has not shown them to you yet.

"Unlimited support" and what it actually excludes

Unlimited is the most overloaded word in this industry. In most agreements it means unlimited remote helpdesk during business hours, for supported systems, up to a fair-use cap that appears further down in the service schedule. Work outside those boundaries — after hours, on site, on unsupported software, or beyond the cap — is billed. That is a normal structure and worth nothing against you if you know about it. The question to ask is simple: is there a cap, what is it, what is the rate beyond it, and how often do clients our size go over?

The Eleven Things to Compare Line by Line

1. What counts as a covered device versus a billable one. Get the full inventory the price is built on — every user, device, server, site and network device included, and everything on your network that is not. Most renewal disputes are scope disputes, and they are almost always traceable to a list nobody wrote down at the start.

2. Coverage hours, and what happens at seven o'clock on a Friday. An answering service that logs a ticket for Monday morning is sold with the same two words as an engineer who fixes the problem at midnight. Ask who picks up outside business hours, what they can resolve without escalating, and whether after-hours work is charged on top. Our guide to why a 24/7 helpdesk matters covers the difference in practice.

3. Response commitment — target or contract term. There is a real distinction between a number a provider aims at and a number they are accountable for. Ask which one you are being given, what the conditions are, and what happens when it is missed. We deliberately do not publish a guaranteed response time as a marketing figure, and we will explain how triage and dispatch actually work instead. A number with no conditions attached to it is a slogan.

4. Whether security is inside the monthly fee or sold separately. Multi-factor authentication, endpoint protection, managed detection and response, email authentication and awareness training are the controls that matter most and the ones most often moved into an options column to keep a headline price down. Compare like for like by adding every optional security line back into the base fee. A security control that is optional is a security control that eventually lapses.

5. Backup: what is covered, how often, and whether restores are tested. Microsoft runs a shared-responsibility model, so mailboxes, OneDrive, SharePoint and Teams are your data to protect, not Microsoft's to retain indefinitely. Ask what is backed up to separate storage, what the retention period is, and — the single most useful number in any IT agreement — the date of the last successful test restore. Our backup and disaster recovery guide sets out what a defensible answer looks like.

6. Who owns the tooling, the tenant and the data if you leave. If the provider owns your Microsoft 365 tenant, changing provider becomes a migration rather than a handover. Confirm in writing that your organisation is the legal owner of the tenant and the domain, that you hold a global administrator account of your own, and that documentation and backup data are returned in a usable format on termination.

7. Onboarding cost and how long it takes. Onboarding is real work: discovery, documentation, agent deployment, and fixing whatever gets found in the first fortnight. A quote showing a monthly fee and no onboarding line has either absorbed that cost into the monthly figure or has not planned it. Ask which, what onboarding includes, how long it runs, and which remediation is inside it rather than billed on top.

8. Project work: hourly, blended, or included. Every managed agreement has a boundary between routine support and project work, and a good quote draws it explicitly. Ask for three concrete examples of work that would be billed as a project rather than covered, plus the project rate. Vague boundaries get argued about during the migration, which is the worst possible moment.

9. Licence handling — resold at margin, or at cost. Microsoft 365 and third-party licences can be passed through at cost, bundled invisibly into the per-user price, or resold with a markup. All three are legitimate; only one of them is obvious from the quote. Price your licence count at list and compare the difference, so you know what you are paying for the convenience.

10. Contract length, auto-renewal and the exit clause. Auto-renewal with a short notice window is common and entirely legal. The problem is discovering it four days after it renewed for another year. Ask for the term, the notice period, whether it renews automatically, and what it costs to leave early.

11. Who actually answers the phone, and from where. Ask where the helpdesk sits, whether first response is a technician or a dispatcher, how escalation works, and whether the same team handles both your systems and your security alerts. A split between the people who run the environment and the people watching it is where incidents fall through, and it rarely appears anywhere on a price sheet.

Where the Cheaper Quote Gets Its Price

This is the section most provider-written comparison guides skip, because it is uncomfortable in both directions. Written plainly, there are only a handful of places the money comes from, and none of them is magic.

• Narrower coverage hours. Business-hours support with an after-hours answering service costs a fraction of a genuinely staffed overnight desk.
• Security unbundled. Moving MFA enforcement, endpoint detection, email authentication and awareness training into optional line items can take a meaningful percentage off the headline figure.
• A capped or offshore-only helpdesk. Both are legitimate models. Both change what your staff experience on the fourth call of a bad week.
• No strategic time. Cheaper agreements often contain no scheduled review, no roadmap and no budget planning, which means nothing improves between incidents.
• Junior-only first and second response. Every provider triages with generalists. The difference is how quickly a senior engineer becomes reachable, and whether that escalation is inside the fee.

None of these makes a provider the wrong choice. A ten-person office with no servers, no regulated data and predictable hours may be well served by exactly that model, and paying for enterprise-grade coverage it will never use is its own kind of waste. The mistake is buying the cheaper structure while believing you bought the other one.

Put Both Quotes on One Page: Cost Over Thirty-Six Months

Monthly rate is the wrong unit for this decision. Managed IT agreements run for years, the one-time costs land unevenly, and the cheaper monthly number frequently loses over a full term once onboarding, security add-ons and project labour are counted. Build the comparison as total cost over thirty-six months instead: multiply the monthly fee by thirty-six, add onboarding once, add every security line item you would have to buy anyway, add a realistic annual figure for project work, and add the cost of getting your data back at the end.

The arithmetic is unglamorous and it changes decisions. A quote at $3,600 a month with security included, no onboarding fee and two included project days a year is $129,600 over the term. A quote at $2,900 a month plus $8,000 onboarding, $600 a month of security add-ons and every project billed at a day rate is $134,400 before a single migration — and it is the one that looked twenty percent cheaper on the front page. Use your own numbers; the point is that the front page is not the comparison.

Seven Things to Get in Writing Before You Sign — With Us or Anyone Else

These are deliberately vendor-neutral, and they mirror the checklist already published on our managed IT plans page rather than replacing it.

• Is helpdesk support genuinely unlimited, and if there is a cap, what is it and what is the rate beyond it?
• Outside business hours, does an engineer answer or a message service, and what can they resolve without escalating?
• Which security controls are in the base price, and which are an upsell?
• Are backups restore-tested, and what was the date of the last successful test restore?
• Who owns the Microsoft 365 tenant, the domain and the backup data, and what is returned if we leave?
• What is the term, the notice period, and the cost of leaving early?
• Give three concrete examples of work that would be billed as a project rather than covered by the monthly fee.

Any provider who will not answer those in writing has answered them.

Run the Quote You Have Through a Free Checker

We built a free managed IT quote checker for exactly this job. It walks twenty-two checks across support, security, backup, ownership and commercial terms, tells you which ones your quote covers and which are silent, and gives you the exact question to ask for each gap. Nothing is uploaded, there is no sign-up, and it does not ask who quoted you — you read your own proposal and mark each item off. It is genuinely more useful run against a competitor's quote than ours, because the gaps are the point.

If you would rather understand the number before you collect quotes at all, our guide to what managed IT support costs in Toronto breaks down the drivers, and how to choose a managed IT provider covers the evaluation side. If you are not yet sure which model you are buying, co-managed and fully managed IT are priced differently for structural reasons, and managed IT and managed security are not the same product regardless of how the quote is labelled.

Where IT Rapid Support Fits

We are a managed IT and cybersecurity provider working across the GTA from Vaughan, and we quote flat monthly pricing per user or per device rather than hourly rates. What sits inside that fee: a 24/7 helpdesk, monitoring and patching, Microsoft 365 and Azure administration, monitored backups, and the security baseline of multi-factor authentication, endpoint protection, managed detection and response, and email authentication through SPF, DKIM and DMARC. Security is inside the fee rather than beside it. Where PHIPA or PIPEDA obligations apply, we can help you meet them with technical controls; no provider can hand you compliance as a product.

If you have a quote in hand and want a second one built on the same scope so the comparison is real, get in touch or call (289) 582-9930 and we will price against the same inventory line for line.

Frequently Asked Questions

Why do managed IT quotes vary so much for the same business?

Because the unit is not standardised. Per-user pricing hides who is being counted, which devices are covered, whether security is included, what happens after hours, and where the boundary between support and project work sits. Two providers can quote the same headcount and be pricing genuinely different amounts of work. Normalise the scope first, then compare the numbers.

Is the cheapest managed IT quote ever the right one?

Yes, when the cheaper structure matches what the business actually needs — a small office, predictable hours, no servers, no regulated data. It is the wrong choice when you buy the cheaper structure believing you bought the fuller one. The test is not price; it is whether you can describe what the difference buys.

What should be included in the monthly fee?

Our position is that anything which must happen continuously belongs in the fee: helpdesk access, monitoring and patching, Microsoft 365 administration, monitored backups, and the security baseline. Project work, hardware and one-off migrations are reasonably billed separately. The structural argument for including prevention is straightforward — if prevention is billed hourly, the provider earns more when your environment is worse.

How long should a managed IT contract be?

Long enough that the provider can justify the onboarding investment, short enough that you are not trapped if the relationship fails. What matters more than the length is the notice period, whether it renews automatically, and the exit terms — specifically what documentation and backup data you receive, in what format, and at what cost. Our own plans are month-to-month.

Can I ask for a quote broken down per service?

Yes, and you should. A provider who can itemise helpdesk, security, backup, Microsoft 365 administration and project labour separately is a provider who knows what each part costs to deliver. A refusal to break it down is usually a sign that the bundle is doing work the itemisation would expose.

What does IT Rapid Support charge?

We do not publish a rate card, and we would treat any provider who publishes one before seeing your environment with mild suspicion. The figure is a flat monthly fee priced per user or per device, driven by how many people and sites you cover, how many servers you run, which coverage level you choose, and what you already have in place. The three coverage levels and what sits inside each are set out on our managed IT plans page, and an assessment produces the exact monthly number.