When to Hire IT Staff (And When One Person Isn't Enough)

Hire IT staff when a named person has to own IT risk decisions every day and the work is specific to systems only your company runs. Headcount is a weak trigger. One full-time hire covers about 21% of the year.

Ask five credible sources when a business should hire its first IT person and you get five different numbers. Spiceworks put it at 20 employees for a tech company and 70 for everyone else, back in 2013, and that figure still gets quoted. Other advice lands anywhere from 15 to 50, with 30 to 40 turning up often.

Those can't all be right.

They aren't wrong either. Before you write a job description, it helps to know what IT support services already cover and what genuinely changes at the point hiring becomes right. Each published number describes a real company that hired at that size and was glad it did. None of them describe yours. Two companies with 45 people can carry completely different IT exposure depending on what they run and who answers for it when it breaks, which is why the thresholds scatter instead of converging.

The threshold isn't a size. It's an ownership gap that happens to correlate with size. Correlation isn't cause.

When Should You Hire IT Staff?

Three things have to be true at the same time. Someone has to own IT risk decisions daily, the work runs on systems specific to your business, and the seat is funded for two years. Two out of three means wait. Not never. Wait.

None of that has anything to do with counting desks. A 30-person engineering firm running licensed simulation software on local workstations needs an owner sooner than a 90-person distributor running everything in Microsoft 365. Same size band. Different answer, because it isn't the same work.

Order matters here, too. Ownership without funding gets you an 11-month hire and a resignation letter. The budget quits first. Funding without specificity gets you someone doing commodity work you could have bought cheaper. And specificity without ownership is the most common version of all, where a company has genuinely unusual systems and a genuinely stretched office manager keeping them alive on institutional memory nobody wrote down.

That last one deserves a name, because it doesn't feel like a crisis. It feels like Tuesday.

Why Every Answer to This Question Is a Different Number

Ratio benchmarks don't settle it either. Across all sectors, the average is one IT worker for every 27 employees, and the same guide warns in the next breath that no single ratio fits, because company size, revenue, and sector all move it.

Read that again. The source publishing the average is telling you not to lean on the average. An average built from companies that different isn't a benchmark, it's a coincidence with a decimal point.

What drives the variance is how much of your technology is standard. A distribution company where 180 of 200 people use a browser, email, and a warehouse scanner needs very little dedicated support per head. A 50-person architecture firm where every seat runs Revit against a shared model, and a bad file lock stalls four people for an afternoon, needs a lot. The employee count is identical in the ratio math. The actual demand isn't close. Nowhere near it.

This is also where the two purchases get confused. Support and management aren't the same product, and IT support and managed IT differ in ways that change who you should be hiring, if anyone. Fixing things is a job. Deciding what should exist is another one. That's a separate hire. Companies feel the first one and buy for it, then wonder why the second one never got done. Nobody owned it.

The Trigger Is an Unowned Decision, Not a Headcount

A decision nobody owns is the real trigger. When a security question, a renewal, or an outage needs a call and no named person can make it, you have a governance gap. That gap is what hurts, and headcount only loosely predicts it.

Two federal frameworks say this plainly. NIST Cybersecurity Framework 2.0 added an entire GOVERN function in 2024, and its GV.RR-02 subcategory requires that "roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced." CISA's Cyber Essentials tells the business leader to select and support a Security Program Manager and to review and approve the incident response plan personally.

Notice what neither document says. Neither one says employee. Not once.

Both require a named, accountable owner with real authority. Whether that person is on your payroll, on a provider's payroll, or is you with a calendar reminder is a separate question, and the frameworks are deliberately silent on it. NIST even published a Small Business Quick-Start Guide in February 2024 for organizations with no cybersecurity plan at all.

So run the test on your own company. If your firewall subscription lapsed, who would know? If a director asked whether last night's backup restored cleanly, who answers, and how long do they need? If someone requested admin rights on a production server, who says no? Name the person for each. Out loud. It gets harder around the third question.

If it's three different people, you have a coordination problem, not a hiring problem. If it's nobody, you have the thing this post is about. And if the honest answer is that leadership doesn't have visibility into any of it, the seat you're missing may be strategic rather than technical, which is a case for a full-time CIO or a fractional version of one, not a support hire.

One Person Covers About 21% of the Year

Roughly 21% of the calendar year is what one full-time IT hire covers. A 40-hour schedule is 2,080 hours. Take out 25 days of paid time off and holidays, and about 1,880 working hours remain, against the 8,760 hours in a year.

Against a single 10-hour shift, one hire is 75% of the coverage you need. Against two shifts, 47%. Against the full year, 21%. Those percentages assume the person never sits in a meeting, never runs a project, and never spends a Thursday on a vendor call, which of course they will, so treat every figure here as the ceiling rather than the expectation.

And the gap isn't only about hours. A one-person IT department has what engineers call a bus factor of 1, meaning the whole function stops if that single person stops. Vacation stops it. Flu stops it. A competing offer stops it for longer. The replacement search rarely fits inside a quarter, and the institutional knowledge that lived in that person's head walks out with them.

Coverage done well looks specific and boring. A consumer products company in Long Beach got a ticket number and a written issue description in 3 minutes and a live technician on the phone inside 15, and the technician then taught the user to handle it herself and left written steps on her machine. That's a documented ticket, a staffed queue, and a user who no longer needs to call. One afternoon. A single hire on PTO delivers none of the three.

The Job You're Feeling Isn't the Job You'll Post

Whatever pain you're feeling is usually three different occupations, and the Bureau of Labor Statistics prices them separately. Blending them into one job description is how first IT hires go wrong before anyone is interviewed. Before the posting even goes up.

BLS supplies the loaded multiplier too, rather than a rule of thumb. Employer Costs for Employee Compensation put private-industry compensation at $46.89 per hour worked in June 2026, of which $32.82 was wages and $14.07 was benefits. Divide the total by the wage portion and you get 1.43x. Run that against the medians and the three jobs separate cleanly.

Wage medians are BLS May 2025 figures for support specialists and for network and computer systems administrators. Add recruiting, a laptop, tooling licenses, and training, and the real first-year number sits above the loaded column. We've broken the full comparison down elsewhere, including cost and risk side by side and how per-user pricing works once you're comparing quotes.

BLS projects employment of computer support specialists to decline 3% from 2025 to 2035, and network and systems administrators to decline 4%, even while CompTIA projects net tech employment growing 1.9% in 2026 and 185,499 new jobs. Growth is real. Just not here. The work in these two roles is consolidating into providers and automation instead.

You can still hire into a shrinking occupation and be right. Plenty of companies should. Do it knowing that the job you're posting is one the market is quietly reorganizing around, and that the 48,700 annual openings BLS projects for support specialists exist mostly through replacement rather than growth. Worth knowing going in.

Three Ways to Fill the Gap

There are three real options. Not two. Hire internally, buy the function from a provider, or split it, with an internal person owning what's specific to your business and a provider owning the commodity layer and after-hours coverage.

The third one gets skipped in almost every version of this conversation, which is strange, because for companies between 20 and 1000 users it's frequently the right answer. Consilien builds structured IT for exactly that range, translating technology decisions into business terms for CEOs, CFOs, and COOs who own the risk but don't want to become technical to manage it.

A split arrangement with a fuzzy boundary is worse than either pure model, because two parties both believe someone else is watching the backups. Write it down before anyone starts. All of it. We go deeper on how co-managed compares against fully managed, and what a co-managed IT boundary looks like when it's drawn properly.

When Hiring Really Is the Right Call

Hire internally when the work depends on knowledge that can't be transferred cheaply. Custom applications, a plant floor with equipment older than the network, a workflow nobody documented. Institutional memory has real value, and an employee accumulates it in a way a rotating queue can't. That's a genuine argument for hiring.

Compliance obligations push the same direction. When an auditor asks who owns a control, "our provider" is a weaker answer than a name on your org chart, and auditors for frameworks like CMMC and SOC 2 expect a named internal owner even where the execution is outsourced.

Some of you should close this page. If you're under 20 users on a standard Microsoft 365 stack with no compliance obligation, hiring a full-time IT person is almost certainly the wrong use of $88,400. A provider costs less and covers more hours. If you already have a CIO or an IT director and you're reading this about a second hire, you're solving a capacity question, not this one.

One caution on the numbers that get used to justify these hires. IBM's 2026 Cost of a Data Breach report puts the US average at $11.5 million, up 13%, against a global average of $4.99 million. That US figure is heavily weighted by large enterprises with regulatory exposure a 40-person manufacturer doesn't have. It is not your number, and anyone quoting it at you as though it were should be asked what the median looks like for your size. The direction of the trend is the useful part. The headline figure belongs to someone else.

How to Hire So the Seat Survives

Scope the job to one BLS occupation, not three. Decide whether you're buying ticket resolution, network work, or systems administration, and write the description for that. A posting that asks for all three attracts generalists who are junior at everything, and the strongest candidates read it as a company that hasn't thought this through. They apply elsewhere.

Fund it for two years. A 14-month runway produces a hire who leaves during your first real project, taking undocumented knowledge with them, and you restart at zero having spent six figures.

Break the bus factor before day one. Document credentials, vendor contacts, license renewals, and the recovery steps somewhere the CFO can reach without calling anyone. Then keep a provider relationship alive for escalation and coverage, even a small one, so a resignation is an inconvenience rather than an outage.

Hixson Metal Finishing does a version of this worth copying. They have their own IT Manager, Joel Poindexter, and they've kept a Consilien relationship running since January 2010 across infrastructure, help desk, and strategic advisement. "Consilien has a great depth of knowledge and experience throughout their team," Poindexter says, and a network upgrade in that period "provided a reliable backbone to run our systems with greater performance." Sixteen years, and an IT Manager on their own payroll today.

Before any of that, get a read on what you actually have. An IT assessment tells you which of the three roles your environment genuinely needs, which is a cheaper way to find out than a bad hire and a year of turnover.