CYBER FORENSICS · PRIVACY & AI · LEGAL TECHNOLOGY · MANAGED ITCall us 24/7: (289) 582-9930
Guide

How to Buy IT Support in the GTA: 2026 Buyer's Guide

The buying process from first conversation to signed contract, in six steps. It covers what to write down before you call anyone, how to define ticket priorities, what to get in writing, and how to compare quotes without being steered by the cheapest line.

4 min readManaged IT

Reviewed by the ITRS security team · Last updated

Before you call anyone: write a one-page brief

Providers quote what you describe. If you describe nothing, each one quotes a different scope and the numbers cannot be compared. One page is enough.

  • Headcount, number of locations, and who works remotely.
  • Devices: laptops, desktops, phones, servers, printers, network gear, and roughly how old they are.
  • Systems: Microsoft 365 or Google Workspace, accounting software, line-of-business apps, phone system.
  • Data you hold that would trigger a breach report or a client complaint if exposed (health, legal, financial, personal).
  • The three things that went wrong in the last year and what they cost you.
  • What you want to stay in-house, if anything.

The six steps

  1. 1. Shortlist three providers

    Use referrals from businesses like yours and check that each one regularly supports your size and systems. Our guide to the kinds of IT company helps you avoid comparing a break-fix shop with a security firm.

  2. 2. Run the same meeting with each

    Use the scored evaluation sheet so you compare answers, not personalities.

  3. 3. Ask for a written quote against your brief

    Same scope, same headcount, exclusions listed. Anything quoted 'per user' should say which devices and services each user includes.

  4. 4. Compare quotes line by line

    Put them through the quote checker and our quote comparison guide, which covers 36-month total cost and the line items that tend to be missing.

  5. 5. Read the contract

    Term, renewal, notice, exit assistance, data return, liability and insurance. The contract guide has the clauses to look for.

  6. 6. Plan the switch

    Credentials, documentation and overlap with the old provider. See how to switch IT providers.

Define ticket priorities yourself

Response-time promises mean nothing without agreed definitions. Write the definitions into the contract and ask each provider to fill in its target times. Compare those targets across quotes, and ask how they are measured and reported.

PriorityDefinition to put in the contractExampleProvider's target (they fill in)
P1 Critical
Business stopped or security incident in progress
Nobody can access email; ransomware note on screen
Blank
P2 High
A team or key system is impaired, no workaround
Accounting software down; one office offline
Blank
P3 Normal
One person affected or workaround exists
Laptop slow; printer offline
Blank
P4 Request
Planned change or question
New starter Monday; add a shared mailbox
Blank

Get these in writing

Verbal assurances in a sales meeting do not survive the first dispute. Make sure each of these appears in the proposal or contract.

  • Scope: every service included, and an explicit list of exclusions.
  • Priority definitions and target times, and what happens if targets are missed.
  • Monthly reporting contents (patching, backups and last restore test, tickets, security alerts).
  • Who owns accounts, licences, domains and documentation, and how they are handed over at exit.
  • Security responsibilities: who handles an incident, who notifies you, and what they may do without asking.
  • Insurance carried by the provider, with amounts.
  • Rates for out-of-scope work and how projects are quoted.

Signs you are being sold rather than advised

A quote that arrives before anyone has asked about your systems. A long minimum term for a business that has never worked with the provider. A 'security bundle' with no explanation of what it monitors or who responds. A refusal to show you a sample monthly report. None of these is fatal alone, but two together are worth walking away from.

See how our managed IT plans are structured and our managed IT support practice, or go straight to IT support across the GTA.

If you are a very small office

Under about ten people with cloud tools, a full managed contract may be more than you need. Read what a small business should expect from IT support and the signs you have outgrown break-fix before signing a multi-year agreement.

How long this should take

For a 10 to 50 person office, allow four to six weeks from brief to signature: a week to shortlist, two weeks of meetings and quotes, a week on the contract. Then plan a few weeks of overlap with your current provider so credentials and documentation change hands properly.

Talking to us

Send us your one-page brief and we will reply with questions or a written proposal against it. If you already have quotes from others, we are happy to say plainly whether ours is the right fit.

Keep reading

Related reading.

Next step

Want this handled for your business?

Tell us your users, devices and sites. We are staffed 24/7 and reply with next steps. Quotes are built from your environment, not a price list. Active incident? Call (289) 582-9930, 24/7.