Hiring a second IT person costs well past the salary line. The Bureau of Labor Statistics puts the May 2025 national median for a network and computer systems administrator at $99,130, and BLS benefit ratios push the loaded cost closer to $142,000. Co-managed IT has no published starting price, because it gets scoped to the gaps your current person leaves.
This is the decision that actually lands on an owner’s desk. Not “should we outsource IT.” That one got settled years ago at most businesses the size we work with. The live question is narrower and harder. You already have one IT person. They’re underwater. Do you hire a second one, or do you put a team behind the one you have?
Both answers are defensible. Neither is cheap. What follows is the arithmetic, with the salary side pulled from federal wage data rather than from memory, and the co-managed side described honestly as the scoped thing it is. VJNetworks sells both fully managed and co-managed IT, so read the second half with that in mind and check the numbers anyway.
What a Second IT Hire Actually Costs
Start with published wage data instead of a number somebody remembers from a recruiter call. The BLS Occupational Outlook Handbook reports a May 2025 national median annual wage of $99,130 for network and computer systems administrators. For the support-desk side of the house, the computer support specialists handbook entry reports $76,220 for computer network support specialists and $61,860 for computer user support specialists, both May 2025 medians.
Those are wages. Wages are not what the hire costs you.
The BLS Employer Costs for Employee Compensation release for March 2026 found that among private industry workers, wages and salaries accounted for 69.9 percent of total compensation cost and benefits accounted for the other 30.1 percent. Apply that ratio to the medians above and you get a rough loaded figure for each role.
| Role You’d Be Hiring | Median Wage (BLS, May 2025, national) | Approximate Loaded Cost |
|---|---|---|
| Network and computer systems administrator | $99,130 | About $141,800 |
| Computer network support specialist | $76,220 | About $109,000 |
| Computer user support specialist | $61,860 | About $88,500 |
Two honest caveats before anyone puts that in a budget. The loaded column is arithmetic, not a BLS estimate. It divides each median by 0.699, which is the economy-wide private-industry wage share from that March 2026 release, so it’s a reasonable approximation and not a quote for your specific benefits package. And every figure here is national. If you want a Rockland, Westchester or Bergen number, BLS publishes metropolitan-area wage tables separately and that’s where to pull it from.
The order of magnitude holds regardless. A real second IT hire is a six-figure commitment before you have bought that person a single software license, a laptop, or a seat in whatever remote-access tool your first IT person already lives in all day.
The Costs That Never Make It Onto the Offer Letter
Salary and benefits are the part everyone models. The rest is the part that surprises people in month four.
- The search itself. Weeks of somebody’s time reading resumes, plus whatever a recruiter charges if the search stalls. That time comes out of the person who is already stretched.
- Ramp-up. A new hire does not know your network, your vendors, or why one accounting workstation has to stay on that old print driver. Getting them useful takes months, and most of the teaching falls on the IT person you were trying to relieve.
- Tools per head. Remote access, ticketing, documentation platforms and security tooling are usually licensed per technician. A second technician means a second set of seats.
- Coverage still has a hole in it. Two people is better than one. It is not the same as depth. When both are on vacation the same week, or one leaves, you are back where you started with a shorter runway.
- Specialization does not come free. Security work, compliance documentation and cloud identity configuration are their own disciplines. A generalist hire will need training and time to build them, and neither shows up on the salary line.
We wrote about the failure mode at the extreme end of this in our piece on the risks of relying on a one-man IT shop. Going from one to two narrows that risk. It does not close it.
Why Co-Managed IT Has No Sticker Price
This is the part where it would be easy to slide a tidy number in. It would also be wrong.
VJNetworks publishes a starting price for fully managed IT. That service starts at $995 a month, and our managed IT pricing guide for Rockland, Westchester and Bergen walks through what moves a business up from that floor. The reason a published floor works there is that fully managed covers roughly the same broad scope for every client. Whole environment, whole team, one number.
Co-managed IT is a different shape and it prices differently. The $995 floor belongs to the fully managed service and does not carry across. There is no equivalent published starting figure for co-managed, and that is deliberate rather than evasive.
The reason gets missed a lot. In a co-managed engagement we are not pricing your environment. We are pricing the difference between what your internal person already covers and what nobody covers. Two companies of identical size can need completely different work. One has solid help desk coverage and nothing on security. Another has security handled and no documentation, no tested restores, and no plan for the weeks their IT person is out. Same headcount. Different scope. Different price.
So the honest answer to “what does co-managed cost” is that it depends on what you already have, and we would rather assess it than guess at it. Our overview of how co-managed IT works in practice covers how the responsibility split gets written down before anyone quotes anything.

What You Actually Buy Is Breadth
The salary comparison is the easy half, and on its own it undersells the thing. A second hire buys you more hours of the same coverage. A provider buys you a wider surface, and that difference is where most of the value actually sits.
One person can go very deep. They can learn your internal software better than any outside firm ever will, and that is genuinely worth having — nobody here would talk you out of it. What one person cannot do is have seen everything. More people means more coverage and, more usefully, more problems already met and solved before they landed on you. That is what shortens a bad week, and it is what you are buying for the money rather than another set of the same hours.
Then the unglamorous one, which decides more of these than it should. Your person takes holiday, and the coverage leaves with them. When somebody on our side takes holiday, the rest of the team is still there. That asymmetry appears nowhere on an offer letter and is the thing owners feel most sharply the first week it matters.
The Comparison Nobody Makes Correctly
Most owners compare a salary to a monthly invoice and stop there. That comparison is missing the two columns that actually decide it.
| Question | Second IT Hire | Co-Managed IT |
|---|---|---|
| What are you buying | One person’s hours and one person’s skill set | A team’s coverage across the specific gaps you scoped |
| What moves the cost | Seniority, local pay market, benefits package | How wide the gap is, what your person already owns |
| What happens when someone is out | The other one absorbs it, or it waits | Escalations route to the provider team regardless |
| How it changes when you grow | Step function, you hire a third person or you do not | Scope gets renegotiated, usually in smaller increments |
| Speed to useful | Months, including the search | Weeks, since the tooling and process already exist |
| Who owns the relationship with your users | Your team, entirely | Still your team, with overflow routed out |
Read the middle row again. That is the one that decides it for most of the businesses that call us.
When Hiring Is Genuinely the Better Answer
We are not going to pretend the answer is always us. Hire the second person when these things are true.
- Somebody needs to be physically in the building most days, because your work is hands-on with equipment, not just with software.
- You run a line-of-business application deep enough that owning it in-house is cheaper than paying anyone to learn it.
- Your ticket volume is genuinely a full-time job’s worth on its own, separate from projects and strategy.
- You are big enough that the third and fourth hire are already on the roadmap, and you want the internal bench.
If two or more of those are true, budget for the hire and use the BLS medians above as your starting benchmark.
When Co-Managed Wins the Math
The other pattern is more common in the 5 to 60 employee range we work in. It looks like this.
- Your one IT person is competent and you want to keep them. That is the whole premise. Co-managed is built around keeping them, not around replacing them later.
- The gaps are specialist gaps rather than volume gaps. Security tooling, compliance documentation, tested restores, cloud identity configuration.
- The strategy work keeps sliding. Nobody firefighting all day gets to a technology roadmap, which is why vCIO strategy and roadmapping is one of the first things clients hand over.
- Coverage risk keeps you up more than ticket backlog does. One resignation should not take your institutional knowledge with it.
For what it is worth on our side of it, the commitment VJNetworks holds itself to on anything routed to us is a 15-minute response standard during business hours, the same standard our fully managed clients get. Client retention has held at 97 percent across fully managed and co-managed engagements alike, and we have been doing this from a Rockland County base since 2004.
How to Actually Run the Comparison
Four steps. It takes an afternoon.
- Total the real hire cost. Take the BLS median for the role you would actually post, add the benefit load, then add tooling seats and the months of ramp-up before that person is productive.
- Write down what that hire will not cover. Be blunt. If the second generalist still leaves you without security depth or tested backups, those gaps survive the hire.
- Scope co-managed against the leftovers only. Not against your whole environment. Whatever your internal person already owns should never appear in a co-managed proposal, and if it does, ask why.
- Compare over twelve months, not per month. A monthly invoice next to an annual salary is a rigged comparison in both directions. Put both on the same clock.
If you are running that comparison across more than one provider, and you should be, our checklist for evaluating an MSP before you sign anything covers what to ask all of us. Pricing is one line on it.
Questions Owners Ask Us at This Fork
We’re a 25-person firm with one IT guy who is drowning. Second hire or co-managed?
Is co-managed IT just a cheaper way to say part-time IT person?
Why won’t you publish a co-managed starting price the way you publish one for fully managed?
Our IT person thinks this is step one of replacing him. Is it?
What if we hire and it does not work out?
Can we do both, hire someone and still use an outside team?
A free gap assessment looks at what your internal IT person already covers and prices only what is missing. About an hour, and you keep the findings whether you hire us or not.
Get Your Free Gap Assessment →
Serving Rockland, Westchester and Bergen since 2004 · 97% client retention · 15-minute response standard during business hours
