The 8 mistakes small businesses make when they sign an IT support contract, what each one ends up costing, and what to ask for instead before you sign.
TL;DR Most small business IT contract problems come from what nobody checked, not from what the contract says. Compare scope before price, define who counts as a user, find out which work is billed as a project, keep the admin accounts in the company’s name, and read the exit terms before you need them. Then look at the agreement again every year, because your business will have changed.
I’m Adam Bowles, Partner and CEO at ACT360. Most of the small business owners I meet didn’t sign a bad IT contract. They signed a reasonable one without knowing what to look for, usually on a busy afternoon, usually because the old provider had just let them down. Two years later they’re paying for things they don’t use and getting invoiced for things they assumed were included.
This article is for owners and office managers at businesses with roughly 5 to 99 people, where nobody on staff reads IT agreements for a living. If you want the dollar side first, our guide to what IT support costs a small business in Ontario has the numbers, and our small business IT services page shows how we support teams your size.
What Is an IT Support Contract, Really?
An IT support contract is the agreement that sets what your provider does for a fixed monthly fee, what gets billed on top, who owns your accounts and data, and how either side can end the relationship. The fee is one line. The rest decides what the relationship costs.
Most agreements have the same moving parts. There’s a scope of services, a pricing model (usually per user or per device), a list of exclusions, response commitments, a term and renewal clause, and termination terms. Some add a schedule for licences bought through the provider. Small businesses tend to read the first two and skim the rest, which is exactly backwards. Our article on what’s actually included in an IT support contract walks through the scope side in detail, so this one focuses on the mistakes.
Why Do Small Businesses Get Caught Out by IT Contracts?
Because the person signing usually isn’t the person who will live with the contract, and nobody on staff has read one before. Large companies have procurement and IT managers. A 12-person office has an owner with 20 minutes between client calls.
That’s most businesses in this province. Innovation, Science and Economic Development Canada counts 410,154 small employer businesses in Ontario (1 to 99 employees, as of December 2024), and small businesses make up 98.2% of employer businesses in Canada. Very few of them employ anyone whose job is technology.
The timing doesn’t help either. Owners usually go shopping for a new provider right after something went wrong with the old one. That’s a bad moment to read fine print, and providers know it.
What Are the Most Common IT Contract Mistakes?
The 8 mistakes we see most often are comparing price instead of scope, leaving “user” undefined, assuming projects are included, letting the provider hold the admin accounts, signing without an assessment, skipping the exit terms, misunderstanding licence commitments and never reviewing the agreement.
- Comparing the monthly price instead of the scope. A quote at $70 per user that excludes site visits, backups and security tools isn’t cheaper than one at $110 that includes them. It just moves the cost to the invoice you didn’t expect.
- Leaving “user” undefined. Does a part-time bookkeeper count? A shared front-desk computer? A summer student? If the contract doesn’t say, the first invoice will.
- Assuming projects are included. Replacing a server, moving files to the cloud or setting up a new office is almost always billed separately. That’s normal. Finding out after you’ve booked the move isn’t.
- Letting the provider hold the admin accounts. If the Microsoft 365 global admin, the domain registration and the firewall login all sit in the provider’s name, leaving gets slow and uncomfortable.
- Signing before anyone has looked. A quote built from a headcount and a device list is a guess. The gaps it misses come back later as change orders.
- Skipping the exit terms. Notice periods, early termination fees, auto-renewal and what the provider hands back when you go. These matter most on the day you’re least able to negotiate them.
- Buying licences without knowing the commitment. Annual Microsoft licences bought through a provider can’t simply be cancelled when someone leaves, so a short-term hire can leave you paying for a seat until the term ends.
- Never looking at the agreement again. The contract you signed for 8 people doesn’t fit 20. Without a yearly review, you keep paying for the old business.
None of these are exotic. They’re the ordinary result of signing something without a checklist.
What Does Each Mistake Cost, and What Should You Ask For Instead?
Most of these mistakes cost money slowly, through extra invoices and unused licences, or all at once, when you try to leave. Here’s what each one tends to cost and the one request that prevents it.
| Mistake | What it usually costs you | Ask for this instead |
|---|---|---|
| Comparing price, not scope | Extra invoices for work you thought was covered | A one-page list of what’s included and excluded, side by side with the other quote |
| “User” left undefined | Billing disputes as staff come and go | A written definition of a user, including part-time and shared computers |
| Assuming projects are included | A surprise quote right when you need the work done | Examples of what counts as a project and how projects are priced |
| Provider holds the admin accounts | A slow, awkward exit and a business that depends on goodwill | Admin accounts registered to the company, with the provider given access |
| No assessment before the quote | Change orders once the real setup shows up | An assessment of your environment before any final number |
| Exit terms skipped | Fees, notice periods or a stalled handover | Notice period, fees and the handover list in writing |
| Licence terms misunderstood | Paying for seats nobody uses | A licence schedule showing term, renewal date and cancellation rules |
| No review after signing | Paying for the business you used to be | A yearly review of users, licences and scope |
If you only make 2 of these requests, make the ones about admin accounts and exit terms. Everything else can be fixed mid-contract. Those two get much harder once you’re unhappy.
Who Should Own the Admin Accounts, Licences and Data?
Your business should. The provider needs enough access to do the work, but the accounts, the licences, the domain and the data should be registered to the company, so a change of provider is a change of access rather than a negotiation.
This isn’t only our opinion. The Canadian Centre for Cyber Security’s guidance on contracting with managed service providers recommends that organizations contractually keep legal ownership of their data and give providers only the access their responsibilities require. Its guidance for consumers of managed services adds a useful question to put to any provider, which is whether they can give you an audit trail of what their administrators do in your systems.
In practice, ask for 3 things in writing. Who holds the global admin account for Microsoft 365. Whose name the domain is registered in. And what the provider hands back on the way out, including passwords, documentation and network diagrams. If your current provider would struggle to answer those, our post on 5 red flags your IT contract has you locked in covers the warning signs, and what it costs to switch IT providers puts numbers on the move.
How Do You Read an IT Contract When Nobody on Staff Is Technical?
You don’t need to understand the technology to read the contract. Read it with the person who will deal with the provider day to day, and test every section against a real situation your business has had in the last year.
Picture the last 3 things that went wrong. The laptop that died before a deadline, the new hire who waited 2 days for an email account, the morning the Wi-Fi went down. For each one, find the clause that says who handles it, how fast, and whether it costs extra. If you can’t find it, ask.
A few other habits help.
- Ask for a sample monthly invoice, so you can see what a normal month looks like before the first real one.
- Ask how licences are bought, billed and cancelled, and when they renew.
- Ask who your contact is by name, and who covers when they’re away.
- Ask what the first 90 days look like, including what they’ll document about your setup.
Licences deserve the extra question. Under Microsoft’s New Commerce Experience policy, most subscriptions can only be cancelled for a prorated refund within 7 days of purchase. A provider should explain that before you add seats, not after.
Does a Cheaper Contract Mean Less Security?
Not automatically, but security tools are often the first thing left out of a low quote. Check whether multi-factor authentication, endpoint protection, patching and tested backups are inside the fee or listed as add-ons.
The Cyber Centre’s baseline cyber security controls for small and medium organizations is a good yardstick. It’s written for businesses your size, and a reasonable contract should cover most of it without a separate line item. If a quote is noticeably lower than the rest, hold it against that list before you hold it against your budget.
Where ACT360 Lands on These
Since we’ve spent this article telling you what to ask, here are our own answers.
- We assess before we quote. Assess is the first step of our ACTION methodology, so the price comes from your actual setup rather than a headcount.
- Our managed IT pricing is published at $80 to $150 per user per month for full service, or $75 to $120 remote-only, with Microsoft licences billed separately.
- You deal with a named contact, me or Jeffrey Bowles, rather than a rotating queue.
- Your systems, licences and data stay yours, and anything we build is yours too.
- Every Managed IT agreement includes a 90-day exit clause. That clause is specific to Managed IT. Projects and other services are scoped on their own terms.
We’d rather earn the renewal than rely on the contract to keep you.
Final Thought
A good IT contract is boring. It says plainly what’s included, what isn’t, who owns what and how you leave. If yours makes you nervous to read, that’s worth paying attention to before renewal season, not after.
If you’d like a second set of eyes on your current setup, book a free IT Readiness Assessment. It takes 30 minutes, there’s no obligation, and you’ll know where your technology stands and what to fix first. You can also call 705-739-2281 or email [email protected].
