Should I hire an IT person or use a managed IT provider?
Updated October 30, 2026
If your IT work isn’t a full-time job, buying it as a service is usually the faster, more predictable choice. If it is, the answer is often both: a provider handles the routine basics, and your own person builds what’s specific to your business. Building in-house is more flexible and leaves you owning the know-how, but costs more in money, time, and management. Either way, keep administrator access in your own hands.
Steps
- Count the hours. Estimate the real weekly IT workload, including interruptions.
- Decide what you want to own. Tailored tools and know-how (build), or a faster, standard setup (buy).
- Price the in-house path: salary, benefits, tools, training, coverage for time off, and setup time.
- Price the managed path: the fee, what it includes, what’s excluded, and what you get if you leave.
- Weigh flexibility against speed for the next year or two.
- Consider doing both. Buy the basics, and build what’s specific to your business.
- Ask every option the same questions. Our buyer’s guide lists them.
Details
Build or buy
Build when your systems are unusual enough that tailoring pays off; buy when a standard setup does the job. Everything IT produces falls into two buckets: the work that keeps things running today, and what you’re left owning afterward, such as tools tuned to your business, documentation, automation, and a person who knows how it all fits together.
When you build in-house, the business owns that, and every future task gets easier. It costs more up front in money, time, and management, and the knowledge sits with one person unless it’s written down.
When you buy, you pay a provider for the result, not the system. You get a working setup sooner, but most of the tuning and know-how stays with the provider.
Keep the keys either way
Whichever path you choose, the business should hold its own administrator account for Microsoft 365, your domain, and anything that pays the bills. Ask in writing for documentation, administrator access, and your data back if you leave. A provider or employee can do the work; the keys should still be yours.
Why setup takes one person so long
A full toolset is a project, not a purchase. Someone has to choose the tools, license them, deploy them to every device, set the policies, set up backups and test a restore, route and handle security alerts, write it all down, and keep it patched. In our experience, one new hire usually needs well over a month, while still answering everyday requests.
What a managed fee often includes
Many providers include the base software: Microsoft 365 licensing, security tools, backup, monitoring, and patching, plus support and planning. That means less to buy and configure, and one bill. Ask for the written list and what’s excluded. Servers, network equipment, hardware, phones, and large projects are common exclusions.
Where flexibility matters
Flexibility is worth paying for if you have unusual software, custom automation, or a workflow that doesn’t fit standard processes. Then building, or a custom-scoped arrangement, fits better. For standard office needs, the speed and predictability of buying usually wins. Ask any provider what they will and won’t tailor.
A simple way to compare
Compare both paths over 12 and 36 months, and note who owns the know-how at the end of each.
- In-house: salary, benefits, tools, training, time to deploy and manage, and coverage when that person is away.
- Managed: the fee, one-time fees, exclusions, contract terms, and what you get if you leave.
If you already have an IT person
The goal isn’t to replace them; it’s to move the routine work so they have time for what moves the business forward.
- Hand off first: patching and updates, monitoring and alerts, backups and restore tests, endpoint security, and new-employee setup and shutoff.
- Keep and grow: knowing how the business really works, automating manual processes, planning for growth, training your team, and projects that save time or money.
Start by asking them, “What takes most of your week that you wish didn’t?” Let them choose what moves first, and agree up front on two or three projects the freed time is for, or new requests will fill it.
Where doing it yourself gets risky
- Comparing a salary to a monthly fee without counting tools, training, setup time, and time off.
- Underestimating how long one person needs to deploy and tune a full set of tools.
- Hiring one person and expecting the coverage of a team. If they leave, the knowledge leaves with them unless it’s written down.
- Expecting a provider to customize everything.
- Choosing a provider without asking what’s excluded, or what you get if you leave.
Signs it’s time for help
It’s time when the IT work has outgrown the person doing it, whoever that is.
If you or an employee handle IT on top of another job: it takes hours each week, a close call has happened, your team is growing, or an insurer or client is asking security questions you can’t answer.
If you have an in-house IT person: the signs show up in their workload long before an outage. It’s a workload problem, not a performance problem, and the person living it is often the last to say so.
- Everything is reactive, and projects slip because the day goes to requests.
- Updates, patches, and backup checks fall behind.
- Only one person knows how things are set up.
- The same problems keep coming back.
- Vacations are stressful, because nobody can cover.
- Security and improvement tasks keep getting pushed to “next week.”
That pile is technical debt: shortcuts, unfinished tasks, and undocumented setups that cost time every week. A busy person takes more shortcuts, which makes more work. The fix usually isn’t more pressure on one person; it’s moving the routine work somewhere else.
This week, write down the three IT tasks that take the most time, and who does them. Bring that list when we talk, and we’ll tell you honestly what makes sense to hand off.
Book a free 20-minute fit check