For most businesses with 30 to 80 seats, managed IT fits better than an in-house hire — not because it is cheaper in every case, but because one person cannot cover holidays, sick days, and security at once. An in-house hire wins when the workload is full-time and specialised, and break-fix is enough only when downtime barely costs you anything.
- Managed IT wins when: you need coverage beyond one person's hours, you handle sensitive data, or a resignation would leave you exposed.
- An in-house hire wins when: your IT workload is truly full-time, deeply tied to your own systems, and you can afford backup for absences.
- Break-fix is enough when: you have few systems, little sensitive data, and an outage costs you an afternoon, not a client.
- The deciding question: who is there on the worst day of your year — and what do they cost you when they are not?
The question behind the question · The three options, side by side · When hiring in-house genuinely wins · When managed IT genuinely wins · When break-fix is honestly enough · Eight questions that decide it · What the table can't tell you · Five questions owners actually ask · Decide on the worst day, not the best one
Owners rarely ask "managed IT or in-house?" because they enjoy org charts. They ask it because something already hurts: the person who "does the computers" is overloaded, or left, or was never really an IT person at all — just the most patient employee in the office. Or a quote came in, and it looked large next to a salary, and the obvious thought was: why not just hire someone?
That comparison is where most businesses go wrong, because a salary and a managed service are not the same shape of cost. A salary buys one person's hours. A managed service buys a team's coverage, its tooling, and its spare capacity. Neither is automatically the better deal. The honest way to choose is to look at what each one actually gives you on an ordinary Tuesday — and on the Tuesday everything breaks.
This page is written for businesses of roughly 30 to 80 seats, because that is where the decision is hardest. Smaller than that, and one good hire is usually more than you need. Larger, and you probably need both: an internal lead plus outside depth. In the middle, both options are plausible, which is exactly why the choice deserves a real look instead of a gut feeling.
Managed IT | In-house hire | Break-fix | |
|---|---|---|---|
What you pay for | A monthly service covering a team, its monitoring tools and its processes | One person's salary, benefits, training and tools | Nothing regular; a bill each time something breaks |
Cost drivers | Number of seats and sites, systems in scope, response-time expectations | Salary band, benefits load, recruitment cost, training, tool licences | Hourly rate, urgency, parts, and how long you wait |
Coverage hours | A team rota, including outside office hours depending on the agreement | One person's working hours, minus holidays and sick days | Whoever is free when you call |
When someone is sick or on holiday | Another team member picks the ticket up | Coverage drops to whoever is left — often nobody | Same as any other day: you call and wait |
Hiring and turnover risk | Carried by the provider, not by you | Carried entirely by you; a resignation can mean months of exposure | No hiring, but also no one who knows your systems |
Security tooling | Shared across many clients: monitoring, patching, backup checks, endpoint protection | Whatever you buy and maintain for one business | Usually installed only after an incident |
Depth of expertise | Several specialists: networks, cloud, security, backups | One person's strengths — and their blind spots | Whoever answers the phone that day |
Scaling up or down | Seats and services adjust with the business | Hiring and layoffs, both slow and expensive | No scaling question, because there is no relationship |
Response to a serious incident | A team that has handled the same incident elsewhere | One person, possibly facing it for the first time | A stranger, starting from zero, on your worst day |
Who owns the documentation | Should be documented as part of the service — ask for it in writing | Lives in one person's head unless you insist otherwise | Nobody, reliably |
Flexibility | A contract you can renegotiate or exit | An employment relationship, with all its obligations | Total flexibility, and total absence of commitment |
Read the table slowly, because one row matters more than the rest for a business your size: the holiday row. A single in-house hire takes roughly four to six weeks off a year, gets sick, and eventually resigns. During every one of those gaps, your coverage is whatever your remaining staff can improvise. A team does not have that gap. That single fact decides more of these decisions than price ever does.
There are businesses where an internal hire is clearly the right call, and pretending otherwise would be dishonest.
First, when the workload is genuinely full-time and specific to you. If you run specialised line-of-business software, custom integrations, or equipment that an outside team would take months to learn, a person who lives with those systems every day will beat a rota of generalists. Depth in your own stack is real value.
Second, when presence matters. Some workplaces need someone physically there — a warehouse floor, a clinic, a shop with tills and hardware that fails in person. Remote support can fix a lot, but it cannot reseat a cable or swap a dead switch. If your problems are mostly physical, hire for presence.
Third, when you are large enough to hire two. Two people cover each other's holidays, check each other's work, and halve the resignation risk. The danger zone is exactly one. If your budget stretches to a small internal team with outside help for the deep specialisms, that combination is often the strongest setup of all.
The real question isn't who is cheaper. It's who is still there on the worst day of your year — and what they cost you when they are not.
Managed IT wins on coverage, and coverage is what most 30–80 seat businesses are actually short of.
A team means the person who answers your ticket has seen your problem before, somewhere. It means patches, backups and licence renewals get checked on a schedule, not when someone remembers. It means a security incident at 7 pm is handled by someone whose job that evening is handling it — not by your office manager googling error messages.
It also wins on hiring risk. Recruiting IT staff is slow, and the good ones know it. Every month a role sits empty is a month your systems run without an owner. A managed service removes that vacancy from your critical path entirely: if one technician leaves the provider, your coverage does not change.
And it wins on honesty about cost. A salary looks simple until you add benefits, training, tools, recruitment fees, and the cost of the weeks nobody covers. A managed fee looks large until you add up what an outage, a breach, or a failed backup actually costs. Neither side of that comparison is free — but only one of them is usually written down in full before the decision is made.
One empty desk is the whole argument: coverage is a team, not a person.
Break-fix deserves a fair hearing, because for some businesses it is genuinely fine.
If you have a handful of systems, no sensitive client data, no regulatory obligations, and an outage costs you an afternoon of inconvenience rather than a lost client or a compliance problem, then paying a monthly fee for coverage you rarely use is wasteful. Call someone when it breaks, pay the bill, move on.
The warning sign is when "rarely" stops being true. If you are calling every month, if the same problem recurs, or if the person who fixes things keeps finding that backups were never checked and patches were never applied, you are no longer buying break-fix. You are buying neglect in instalments — and the final instalment usually arrives as a serious incident.
Answer yes or no. Keep count.
How to read your answers:
A table compares features. It cannot compare people. The best managed provider with a sloppy onboarding will feel worse than a mediocre in-house hire who cares. The best in-house hire with no documentation will hurt you more than any contract ever could.
So whichever direction you lean, ask the same three questions before you commit. Who documents your systems, and where does that documentation live? What happens, step by step, when the person responsible is unavailable? And what does the first 90 days look like — specifically, not "we'll get you set up"?
If a provider or a candidate cannot answer those three questions concretely, that is your answer, whatever the price.
Do I really have to choose, or can I do both?
You can, and at the top of the 30–80 range many businesses should. A common shape is an internal coordinator who knows your people and your processes, backed by a managed team for monitoring, security and coverage. The mistake is not mixing the two — it is paying for both while neither one clearly owns anything.
What happens when our one IT person goes on holiday or quits?
That is the question this whole decision turns on. With one person, the honest answer is usually "we cope" — which means someone unqualified improvises, or nothing gets done for two weeks. Ask any candidate or provider to describe their cover plan in writing. If the plan is a name and a hope, you do not have a plan.
Is managed IT just a call centre, or do they actually know our systems?
It depends entirely on the provider, which is why onboarding matters more than the sales call. A serious provider documents your network, your licences, your backup status and your recurring problems in the first weeks, and assigns people who know your account. Ask to see what their documentation looks like before you sign — a provider that cannot show you is telling you something.
How do I know if we are big enough for an in-house hire?
Size alone does not decide it; workload does. Write down every IT task from the last three months — support tickets, onboarding, patches, backup checks, licence renewals, projects — and estimate the hours. If the honest total is well under a full-time week, you are hiring a person to be idle half the time and absent at the worst moment. If it is over a full-time week, one person will burn out or cut corners. Both answers point somewhere useful.
What does break-fix actually cost when nothing is broken?
Nothing, that month. That is its appeal and its trap. The cost arrives later, in the form of unpatched systems, unchecked backups and undocumented fixes — none of which appear on any invoice until they fail together. If you stay on break-fix, pay separately for a periodic health check: backups tested, patches reviewed, licences counted. It is the cheapest insurance in this whole decision.
If this comparison is clarifying the decision, a free assessment will put real detail behind it: an inventory of your systems, your backup and patch status, and where your coverage gaps actually are. It costs nothing, and the findings are yours whether you act on them or not.
On a good day, all three options look fine. The hire is friendly, the provider answers quickly, nothing breaks. Decisions made on good days are how businesses end up with a single point of failure they only discover during a crisis.
So decide on the worst day instead. Picture the Friday afternoon when the server fails, the person who knows it is on a plane, and a client is waiting. Who picks up the phone? Who already knows your backups? Who has done this before? Whichever option gives you a good answer to that picture is the right one — even if it is not the cheapest line on the spreadsheet.
If this page left you somewhere in the middle — which is where most honest businesses land — our free assessment will put a real inventory and a real coverage picture behind the decision, so you are choosing from evidence instead of from a quote and a hope. No obligation attached to it, and the findings are yours to keep.
This page argues from cost drivers and coverage reasoning, not from third-party statistics: no salary benchmarks, savings percentages or industry figures are cited, because those numbers vary by city, role and year and would mislead more than they inform. The decision framework — the comparison table, the eight-question self-test and the "worst day" test — is Amen Security's own, built from managed IT work with Canadian and US small and mid-sized businesses.
- Reviewed: 2026-10-24
- Entity: Amen Security, Winnipeg, Manitoba, Canada — managed IT and web & app services for Canadian and US SMBs, on-site in Manitoba and remote across Canada and the US.
- Next review: when the admin's service or pricing information changes, or when a sourced, dated benchmark worth citing becomes available.
Your comment will be published after our team reviews it.
Keep reading
Managed IT in Winnipeg for 30–80 seat businesses: what to expect in 2026 — real support, on-site help across Manitoba, and a free assessment before you sign.
Cybersecurity costs in Canada, line by line for a 30–80 seat business: licences, monitoring, assessments and insurance readiness, with published 2026 ranges.
Unused licences, departed staff accounts, and Microsoft 365 security settings nobody finished turning on: what a cleanup fixes for Canadian SMBs in practice.
