Time and Materials vs. Managed IT Services
There are really only three ways to buy IT support: pay by the hour when something breaks, pay a fixed monthly fee, or hire someone in-house. Most BC businesses we meet are on the first one and have never properly compared the other two.
Here’s how the three actually differ, where each one genuinely fits, and how to work out which suits your business.
Time and materials: pay when it breaks
You call someone when there’s a problem and pay an hourly rate, usually with a minimum callout and a premium for after-hours or on-site work.
Where it fits: very small teams, simple setups, and businesses that can genuinely tolerate a day of disruption. If you have a handful of staff, one cloud application and no server, a monthly contract may be more than you need.
Where it hurts: the incentives point the wrong way. Your provider earns when things break and earns nothing when they don’t, so nobody is paid to prevent the next outage. Budgeting becomes unpredictable — quiet quarters followed by an expensive month you didn’t plan for. And you’re in the queue behind contract clients at exactly the moment you can least afford to be.
Flat-fee managed IT: fixed monthly, defined scope
A predictable monthly fee, usually per user or per device, covering monitoring, patching, helpdesk, security tooling and planning.
What’s typically included: helpdesk support, 24/7 monitoring, patch management, endpoint protection, backup monitoring, vendor liaison, and a scheduled technology review.
What typically isn’t: hardware, third-party licences such as Microsoft 365 and line-of-business software, major projects like a server replacement or an office move, and cabling. Ask for these to be named explicitly before signing — “all-inclusive” rarely is.
Where it fits: the incentives flip. Once a provider is paid the same whether or not your server fails, preventing that failure becomes their interest as well as yours. You also get predictable budgeting and priority response.
Where it hurts: you pay in quiet months as well as busy ones, and a badly scoped agreement can exclude exactly the thing you needed.
In-house: hiring your own
An employee gives you deep knowledge of your business and someone physically present — genuinely valuable, and the reason larger organisations do it.
Where it hurts: one person is one person. They take holidays, they get sick, and eventually they leave — usually taking undocumented knowledge with them. They also can’t be expert in networking, security, cloud and telephony at the same time, and they still need the monitoring, backup and security platforms that a managed provider already licenses across its whole client base.
Below roughly 75 staff, most businesses find a hybrid works better: an internal person who knows the business, with a provider behind them for out-of-hours cover, specialist work and tooling.
How to work out which one fits you
Rather than comparing headline rates, compare total cost. Most businesses only count the invoices, which is why time and materials looks cheaper than it is.
- Add up last year’s IT invoices — all of them, including emergency callouts and hardware bought in a hurry at retail prices.
- Add the downtime. Staff affected × hours lost × your loaded hourly rate. This is the number nobody tracks, and it is usually larger than the invoices.
- Add the work that didn’t happen — the migration postponed twice, the backup nobody verified, the firmware never patched. These are real costs, just deferred ones.
- Add the scramble premium. Reactive purchasing means retail pricing and whatever is in stock, rather than planned replacement of the right equipment.
- Now compare against twelve months of a fixed contract, or the loaded cost of an employee plus the tooling they’d need.
Over three years the headline numbers usually land closer together than people expect. The gap opens in the items that never appear on an invoice: whether the outage happened at all, whether the backup restored when it was finally tested, and whether anyone was planning beyond next week.
Where the crossover usually sits
There’s no universal headcount at which a contract starts making sense, but the pressure builds when any of these are true:
- You run a server, or software that everyone depends on being available
- You have more than one site, or crews working somewhere you don’t own
- Downtime stops billable work rather than just inconveniencing an office
- You have compliance obligations or a cyber insurance policy with conditions
- Nobody currently owns the question “what needs replacing next year?”
Construction and trades businesses usually reach that point earlier than office-only firms, because an hour of downtime on site costs considerably more than an hour of downtime at a desk.
Questions worth asking before you sign anything
- What exactly is excluded, in writing?
- What’s the response time commitment, and what happens when it’s missed?
- Is after-hours support included or billed separately?
- Who owns the documentation and the administrative accounts — you or the provider?
- What does leaving look like if this doesn’t work out?
That last one tells you the most. A provider comfortable explaining how you’d leave is usually one you won’t want to.
If you’d like this comparison run against your actual numbers rather than generalities, we’re happy to do that — get in touch, or see what’s covered in our managed IT services.