When Should You Hire Your First IT Person?

We should be upfront about the conflict of interest here: we're an IT services company, so "don't hire, outsource to us" is the self-serving answer. It's also usually the right one for small businesses — but not always, and the cases where it isn't are worth being clear about, because putting someone in a role that doesn't have enough work in it is bad for everybody.

Headcount is the wrong trigger

The common rule of thumb is that you hire IT somewhere around fifty employees. It's not a terrible heuristic, but it measures the wrong thing. What actually drives the decision is how much of your technology work is specific to your business rather than generic.

Patching, backups, email, Wi-Fi, new-hire setup, endpoint protection — that work is essentially the same at every business of your size, which is exactly why it's cheap to buy from someone who does it all day. A custom application, an integration between your systems, a compliance regime with real audit requirements, machinery with a computer attached — that work is specific to you, and specific work is what justifies a salary.

The signals that actually point to hiring

• You have software specific to your business that someone needs to understand deeply — not just keep running, but change.
• You're in a regulated industry where evidence, documentation, and audit response are ongoing work rather than an annual scramble.
• Someone needs to be physically present most days — a production floor, a lab, equipment that can't wait for a scheduled visit.
• Your technology decisions are now strategic enough that you want someone in the room when they're made, not consulted afterwards.
• You have genuinely outgrown response-time expectations that an outside provider can meet at a price you want to pay.

Notice that only one of those is about size. Two of them can be true at fifteen people, and none of them may be true at eighty.

The signals that look like hiring but aren't

These are the ones that lead to a hire that doesn't work out:

• "We're spending a lot on IT support." Compare against a fully loaded salary — wage plus payroll taxes, benefits, equipment, training, and the cover you need when they're on holiday or leave. It's usually a bigger number than the invoice you're comparing it to.
• "Things keep breaking." A hire doesn't fix an underlying problem — old hardware, no patching discipline, a network that was never set up properly. It just puts someone closer to it.
• "Nobody responds fast enough." That's a service-level conversation, and often a cheaper one to have than a hiring conversation.
• "Our office manager is drowning in tech tasks." Real problem, and a genuine cost. But it's usually solved by taking the work off them, not by adding a headcount.

The one-person problem

Worth thinking about before you post the role. A single in-house IT person is a single point of failure with no cover, no second opinion, and nobody to escalate to. They take holidays. They get sick. They eventually leave, often taking the only complete understanding of your systems with them, because documentation is the first thing to slip when one person is doing everything.

They're also isolated in a way that's genuinely hard on the person: no colleagues in their discipline, limited exposure to problems outside your four walls, and a skill set that narrows over time. Good IT people often leave small-business solo roles for exactly that reason, which makes the retention problem structural rather than a matter of paying more.

The middle option most people skip

The choice isn't binary. Co-managed IT — an internal person or existing employee handling day-to-day and the things specific to your business, with an outside provider covering monitoring, patching, backups, out-of-hours, and the specialist work — solves the cover problem and the isolation problem at once.

In practice it's often what a growing business should do first, and what a business that hired too early should do instead of hiring a second person.

A straight answer

For most small businesses in New Jersey under about forty people, with no custom software and no heavy compliance load, outsourcing is genuinely the better deal — not because outside help is magic, but because the work is generic and generic work is cheaper to buy than to employ.

Above that, or where the specific-work signals above are real, start with co-managed rather than a straight hire. And if you want to think it through with someone who'll tell you when hiring is the right call, we're happy to have that conversation — it isn't a sales pitch if the answer is that you should hire. You can also see what managed IT actually includes to compare like with like, or read about our own approach.