In-House IT vs MSP vs IT Contractor: Which Fits Your Office?
By Zach Launey, President, NRVPC
The short answer
In-house IT gives you a person who owns every system you run. A managed service provider (MSP) takes ongoing responsibility for a defined set of your systems for a flat monthly fee, covering about 90% of day-to-day operations. An IT contractor gives you hours you buy as needed. The fit depends on how many of your systems run on a standard toolset. NRVPC is a managed service provider (MSP) based in Fairfax, Virginia. We provide unlimited support on company-owned computers for organizations of 20 to 500 employees, with a 12-minute average response time.
What is the difference between in-house IT, an MSP, and an IT contractor?
The three models differ in who owns the work and how you pay for it.
In-house IT is an employee. People on your payroll own every system you run and are in the building when something needs hands. You pay a salary whether the month is quiet or busy.
A managed service provider (MSP) is a team on a flat monthly fee. As we wrote in our 2024 post on IT support companies, MSPs "focus on automation, workflows, and providing an expertly-crafted software stack that is quick to configure." The full definition is in what is a managed service provider. The MSP owns the standard layer: devices, firewall, email platform, monitoring, security, and help desk.
An IT contractor bills hourly. From the same post: "Contracted IT Support usually bills in prepaid hours. Their clientele receives a certain amount of support per month, with overages costing more." This is the model people usually mean by break-fix.
Whichever you choose, the test is the same one we set in 2024. Your support company should keep every system patched, prevent problems and fix them quickly when they occur, maintain and test your backups, be pleasant to work with, and understand your systems well enough to help the company grow.
When does hourly IT support make sense?
Hourly support fits an office with a short list of needs and a long list of unusual systems.
At NRVPC we have held since 2024 that the contractor model is not inferior. It fits when:
- You have fewer than about 20 users and the monthly work would not fill a managed fee.
- Most of your need is project-shaped: a move, a migration, a new phone system.
- Someone internal already handles daily questions and you only need a specialist for the hard ones.
- Your systems are mostly ones an MSP cannot automate, and you want to pay only for hours spent on them.
The trade is predictability. With prepaid hours, a busy month costs more than a quiet one, and the incentive to prevent problems rests with you rather than the provider. That gets harder once the team passes about 20 users and the same questions start repeating.
When does a managed service provider make sense?
A managed service provider makes sense when your office can run on a standard set of tools and you want the cost of support to stop moving month to month.
Two arguments carry the model. We wrote them in 2024, and they hold:
- "Any business model that relies on things breaking to bill hours is a bad business model."
- "Something that is serviced regularly will have less problems and cause less downtime."
Under a flat fee, the provider earns more when your office runs quietly, so the provider's incentive lines up with yours. At NRVPC, 24/7 monitoring detects issues in an average of 8 minutes, and 63% of issues are resolved remotely within the hour, because the tools are in place before the ticket arrives.
The decision rule we gave business owners in 2024 is the one we still use: "If you want your business to run on a specific set of provided tools, an MSP is your best bet. However, if you have multiple systems that can't be automated and you need help administering them, hire in-house or get an IT contractor."
NRVPC's monthly fee is set per user, in two plans; the current prices are on our pricing page. An NRVPC agreement runs one year and renews automatically unless the price changes by more than 5%; leaving takes 30 days' notice. The itemized scope is in what is included in managed IT services.
When does in-house IT make sense, and can it work alongside an MSP?
In-house IT makes sense when the work fills a full-time role and enough of it is specific to your business that no outside toolset covers it. For an office running a custom application or several locations with their own equipment, that role pays for itself in ownership.
The gap in a one-person IT department is coverage. One administrator cannot watch monitoring around the clock, take every help desk call, run quarterly security audits, and still do the projects only they can do.
Co-managed IT is the arrangement where an internal IT lead keeps the line-of-business systems and an MSP takes the standard layer around them. It works when the split is written down, so both sides know who owns the firewall, who owns the EHR, and who takes the call at 9:00 on a Monday morning.
NRVPC works this way today. We hold co-managed contracts alongside a client's in-house IT, alongside other IT providers, and alongside a parent company's IT department.
What about systems that do not fit a flat fee?
Every office has systems that no standard toolset covers. The question is not whether the flat fee can include them; it is where the boundary is drawn.
In 2024 we wrote about one of our healthcare clients: "We manage their phone system with call queues and ring groups, vaccine refrigerators and freezers that require Department of Health audits, Square payment terminals, and multiple locations with key fob access. We are not just resetting passwords – we are managing multiple complicated systems that require human intellect."
At the time we read that list as a reason the flat fee could not work. Read again, it is a description of scope depth, and scope is something you define. Here is how NRVPC draws the line today.
The flat fee covers the minimum managed scope for every client: all company-owned computers, the firewall (Sophos, SonicWall, or UniFi), the email and productivity platform (Microsoft 365, Google Workspace, or a local domain), user onboarding and offboarding, network security monitoring and response, and unlimited help desk. That layer looks the same in a law firm and a medical practice, which is why it can carry one price.
Above that layer, specialized systems get a defined relationship. For healthcare clients, NRVPC coordinates with the EHR vendor and manages the network, devices, and access those systems depend on, without owning the vendor's system itself. The same applies to phone systems, cameras, and payment terminals: the vendor owns the platform, and NRVPC manages everything it touches.
Work that goes past support becomes a project. Anything that takes 8 hours or more, or multiple engineers, is scoped and billed separately. A second location's key fob rollout is quoted before it starts, so the monthly fee stays the monthly fee. Daily work is unlimited, big work is quoted, and vendor relationships are named. The healthcare page covers this in more detail: managed IT for healthcare providers.
What does switching models cost?
Switching costs time more than money, and most of that time is spent in the first quarter.
Expect these line items whichever direction you move:
- Documentation. Every password, license, vendor contact, and network diagram changes hands. When a client leaves, we hand over the documentation and repair notes, and help the incoming IT company gain access to every system.
- Standards. NRVPC's security standards apply to every client: MFA on all email and VPN, managed endpoint security on every computer, encryption on devices holding sensitive data, no end-of-life equipment, all servers under warranty. A hardware purchase to meet that bar is quoted as a project.
- Tools. Moving from contractor to MSP usually adds monitoring and endpoint agents; moving from MSP to in-house means buying licenses the provider used to carry.
- Continuity. Moving from in-house to an MSP works best when the outgoing person's knowledge is captured first, or when they stay on as the internal lead in a co-managed arrangement.
The return is the part that does not move. Once a client is on a flat fee, the cost of support stops changing with the month, which is what lets NRVPC commit to quarterly business reviews with leadership and a 3-year technology roadmap.
Moving to NRVPC, onboarding takes 30 days, and after that a new or departing employee's account is set up or removed within an hour of you telling us, automated in most cases through a Microsoft or Google form.
How does NRVPC compare on each line?
NRVPC runs the MSP model with the boundaries described above. The table shows the three models side by side, with NRVPC's column filled in from our published terms.
| Line | In-house IT | MSP (typical) | IT contractor | NRVPC |
|---|---|---|---|---|
| How you pay | Salary plus benefits and tools | Flat monthly fee, often per user | Prepaid hours, overages billed | One predictable monthly fee per user, in two plans (see the pricing page) |
| What is covered | Whatever the employee owns | A defined scope of devices, network, platforms | Whatever you point them at | Unlimited support on all company-owned computers, firewall, email platform, onboarding and offboarding, security monitoring, help desk |
| Response | Immediate on site; gaps on leave | Set by SLA | When hours are available | 12-minute average response in business hours |
| Monitoring | Business hours, one person | Usually 24/7 tooling | Usually not included | 24/7 monitoring, 8-minute average detection, 63% of issues resolved remotely within the hour |
| Who does the work | Your employee | Provider's team, location varies | Named individual or small firm | Local Northern Virginia engineers, direct access, one-hour on-site response across the Washington, D.C. area |
| Projects | In-house, capacity permitting | Usually quoted separately | Billed as hours | Work of 8 hours or more, or multiple engineers, quoted separately |
| Strategy | Depends on the person | Varies by provider | Rarely included | Quarterly business reviews, 3-year roadmap, hardware refresh budgeting, independent vendor evaluation |
| Best fit | Offices with systems no toolset covers and enough work to fill a full-time role | Offices that run on a standard toolset | Under 20 users, or project-shaped needs | 20 to 500 employees on company-owned computers, an office in Northern Virginia, Northwest Washington DC or Bethesda |
NRVPC keeps the toolset tight (Windows-primary, Mac supported with clear expectations, Microsoft 365 or Google Workspace, a Sophos, SonicWall, or UniFi firewall) and keeps the engineers local. The proof is retention. As we wrote in 2024, "We've kept clients for 10 years." The full scope is on the managed IT services page, and IT consulting covers the roadmap side. To put NRVPC's column next to any other provider's, use how to choose an MSP.
Key takeaways
- In-house IT owns everything, an MSP owns a defined scope for a flat fee, and an IT contractor sells hours. The difference is who carries the incentive to prevent problems.
- The rule we published in 2024 still decides it: standard toolset, choose an MSP; many systems that cannot be automated, hire in-house or a contractor.
- Systems that do not fit a flat fee are handled by drawing the boundary: minimum managed scope inside, named vendor relationships alongside, projects of 8 hours or more quoted separately.
- Co-managed IT pairs an internal lead who owns the line-of-business systems with an MSP that owns monitoring, help desk, patching, and security standards.
- NRVPC runs the MSP model: one predictable monthly fee per user, in two plans, with a 12-minute average response and 63% of issues resolved remotely within the hour.
Frequently asked questions
Is an MSP cheaper than in-house IT?
For most offices of 20 to 500 employees on a standard toolset, yes, because one managed fee buys a team and a toolset rather than one salary. One salary buys one person who cannot cover monitoring, help desk, and projects at once. With custom systems and a full-time workload, the comparison gets closer, and a co-managed split is often the better answer.
What is the difference between break-fix and managed services?
Break-fix bills hours when something breaks; managed services bills a flat fee to keep things from breaking. Under managed services the provider earns the same in a busy month as a quiet one, so the monitoring, patching, and security standards that keep the month quiet are included in the fee.
What is co-managed IT?
Co-managed IT is an arrangement where your internal IT lead and an MSP split the work in writing. The internal lead usually keeps the line-of-business systems, and the MSP takes monitoring, help desk, patching, onboarding and offboarding, and the security standards. NRVPC holds co-managed contracts alongside in-house IT, alongside other providers, and alongside a parent company's IT.
How long does it take to switch to an MSP?
At NRVPC, onboarding takes 30 days: every device comes up to the security baseline, your environment is documented, and your team is introduced to the help desk. Ask any other provider for its own number in writing.
Does NRVPC still work as an IT contractor?
No. NRVPC's model is managed IT services on a flat monthly fee, with project work of 8 hours or more quoted separately. The hourly model still fits some offices, and the hourly section above says which. For offices on a standard toolset, the flat fee is the model we recommend and the one we run.
Which model fits your office?
Bring your list of systems to an IT assessment and we will tell you which ones sit inside the flat fee, which get a named vendor relationship, and which are projects. The answer might be that your current model is the right one.
Or email sales@nrvpc.com