“I think we have unlimited support” and what the actual document says are often two different things. Here are the three pricing models, what should be named specifically, and what's almost always excluded.
I’ve sat through a lot of contract reviews where the business owner tells me “I think we have unlimited support,” and the actual document says something closer to “unlimited support for pre-approved issue types during business hours.” That gap between what people think they signed and what’s actually on the page is where most of the frustration in this industry comes from.
An IT support contract is the agreement governing how a provider delivers day-to-day technical support — the pricing model, who’s covered, when support is available, and what falls outside scope — as distinct from a broader managed IT agreement that also covers monitoring, security, and strategic planning.
“That’s what you asked for, but is it what you actually need? Those aren’t always the same thing.”
— Adam Bowles, Partner & CEO, ACT360
Let’s walk through what should actually be in the document, not just what the sales conversation implied.
The Three Pricing Models, and What Each One Actually Means
Almost every IT support contract is built on one of three models. Knowing which one you’re looking at tells you more than the price does.
| Model | How It Works | The Real Tradeoff |
|---|---|---|
| Per-incident (break-fix) | Pay for each issue as it happens, by the hour or a flat per-ticket rate | Cheapest when things are quiet, most expensive when they’re not — costs are unpredictable by design |
| Block hours | Prepay for a set number of hours at a discounted rate | Cost-effective only if you use close to what you bought; unused hours are usually a sunk cost, and running out mid-month means falling back to per-incident rates |
| Flat-rate (unlimited) | One monthly fee covers support within an agreed scope | Predictable cost, but “unlimited” almost always means “unlimited within scope” — the scope definition is doing all the work |
None of these is universally the “right” one. A business with genuinely light, occasional IT needs might be better served by block hours than paying for unlimited coverage it barely uses. A business that generates a steady stream of tickets is usually better off with flat-rate, since per-incident costs compound fast. The mistake is picking a model based on the sales pitch instead of an honest read of how much support your business actually needs.
What Should Be Named Specifically in the Contract
Beyond the pricing model, a contract worth signing names these things explicitly rather than leaving them implied:
- Exactly who’s covered. Named users, a headcount range, or “unlimited for the organization” — vague coverage is how disputes start.
- Exactly what’s covered. Devices, operating systems, specific software — if your business runs something unusual, confirm it’s named, not assumed.
- Hours of availability. Business hours only, extended hours, or 24/7 — and whether that changes the response commitment.
- Response time by severity. Not one blended number for every ticket, but the point is now well established: if it’s not broken down, it’s not really a commitment.
- On-site provisions. Whether site visits are included, limited, or billed separately, and under what circumstances one gets triggered.
If any of these five are missing from the actual document — not the sales deck, the document — that’s worth raising before you sign, not after the first dispute.
What’s Almost Always Excluded
Even a generous “unlimited” support contract draws a line somewhere. The most common exclusions:
New hardware and software licensing. Support covers maintaining what you have; it doesn’t usually cover buying what you don’t. If a laptop needs replacing, that’s typically a separate line item.
Project work. A network redesign, an office move, a platform migration — these get scoped and quoted separately from day-to-day support almost universally, even under a flat-rate model.
After-hours premiums. Unless you’ve specifically purchased 24/7 coverage, support outside business hours often carries a premium rate or isn’t included at all.
Training beyond basic troubleshooting. Walking someone through a password reset is support. Training an entire department on new software is usually a different conversation.
None of this is a knock on any particular provider. It’s just where the industry draws lines, and a contract that doesn’t say so out loud is setting up a disagreement later.
Cost predictability isn’t a small thing here, either. CFIB’s 2025 research on small business technology found that IT is one of the top three areas Canadian small businesses have invested in over the past three years, alongside accounting and cybersecurity — which means for a lot of businesses, this contract is already a meaningful line item. Knowing which pricing model you’re actually under is part of managing that spend, not just an administrative detail.
Questions Worth Asking Before You Sign
- Which pricing model is this, and what happens specifically when we exceed it?
- Who exactly is covered, and what happens if we hire five more people next quarter?
- What’s excluded, in writing, not just implied?
- What counts as an “incident” versus a “project” — and who makes that call?
- If we’re on block hours, what happens to unused hours at the end of the month?
Straightforward answers to these are a good sign. Answers that circle back to “don’t worry, we’ll take care of you” without specifics are worth pushing on.
What This Looks Like at ACT360
We don’t send a support contract until we’ve actually looked at how a business operates — that’s the Assess step in ACTION, and it’s there specifically so the scope we write down matches what a business actually needs, not a generic template. Named users, named coverage, response times broken down by severity, and a plain description of what’s excluded are all things we put in writing before anyone signs anything.
That’s also why every ACT360 managed IT engagement includes a 90-day exit clause. If the scope turns out not to fit, you’re not stuck arguing about a contract for the next two years.
Final Thought
Tools don’t fail. Ownership does. And a support contract without clearly named scope is a recipe for exactly the kind of ownership confusion that turns a minor issue into a drawn-out argument about whose fault it was. Read the actual document, not the pitch. It’s the least exciting part of choosing an IT provider and the part that matters most once something breaks.
T: 705-739-2281 E: [email protected]
