The number of IT staff you need depends on three things: the hours of work the business generates, the skills that work requires, and the hours you need covered. Measure support and recurring work, add projects, divide by realistic available hours, then check skills and coverage separately. A staff-to-employee ratio is only a cross-check.
You have added employees, opened another location, and bought more software, but the IT team is the same size. Requests take longer and projects keep slipping. This guide shows how to work out whether you need another person, a different kind of person, or a different kind of help. It works for a first hire and for an established department.
Key takeaways
- Employee count alone does not tell you how many IT staff you need. Locations, applications, support hours, and projects matter as much.
- Count all the work, not just tickets: onboarding, administration, security tasks, vendors, projects, and management.
- Estimate available hours honestly. Nobody spends a full workweek on tickets and projects.
- Enough hours on paper is not enough. Check whether someone has the skills for hard problems and whether someone is available when the work happens.
- The answer is not always another hire. Specialist escalation, project help, or co-managed support can close a gap more precisely.
Is there a standard IT staff-to-employee ratio?
Not one you can rely on by itself. An IT staffing ratio compares the number of IT employees with the people they support, and published figures vary widely by industry, company size, and what gets counted. Before you use any benchmark, check its definitions:
- Does "IT staff" mean only help desk technicians, or does it include engineers, security, application support, developers, and managers?
- Are contractors and outside providers counted?
- Is the population measured in employees, active users, or devices?
Two companies with the same headcount can need very different teams. One may run standard laptops and a few cloud applications in a single office. Another may run shifts, specialized systems, shared devices, and several locations. Benchmark studies such as Avasant's IT staffing ratios report figures by industry and company size, which makes them useful as a cross-check once you have done your own workload count.
How do you measure IT workload?
Start with the work people can see. Review a representative month of support requests, including calls, walk-up requests, and direct messages that never became tickets. Otherwise the technician who records everything looks busier than the one who does not.
Group requests into a few categories, such as accounts, devices, applications, and network issues, and estimate the hands-on time each takes. Keep hands-on time separate from elapsed time. A ticket waiting two days for a vendor does not take two days of technician time, though it still needs follow-up.
Then count the work that does not look like support:
| Work area | What to include | Where to find the evidence |
|---|---|---|
| Employee support | Troubleshooting, requests, follow-up, and communication | Tickets and a short activity sample |
| Employee changes | Onboarding, departures, role changes, and equipment preparation | Hiring plans and completed requests |
| System administration | Maintenance, configuration changes, and account reviews | Schedules and task records |
| Security and recovery | Alert handling, patching, backup checks, and recovery tests | Responsibility agreements and work records |
| Vendors and licenses | Renewals, escalations, purchasing, and license administration | Contract calendar and invoices |
| Projects | Migrations, office moves, rollouts, and documentation | Approved project scope and estimates |
| Management | Planning, supervision, reporting, and coordination | Calendars and role descriptions |
Note which tasks an outside provider already covers, so you do not count them as internal demand. And look for repeat problems. If one recurring fault generates dozens of tickets, part of your staffing answer may be time to fix that cause.
How do you turn workload into a staffing number?
Divide the expected monthly work hours by the hours each person realistically has available for that work:
Staffing estimate = expected work hours ÷ available hours per person
Available hours are lower than scheduled hours. Take out leave, training, meetings, and administration, unless you already counted them as workload. Do not subtract the same meetings twice.
A worked example
The numbers below are made up to show the method. They are not an industry benchmark or a target.
| Monthly work | Hours |
|---|---|
| 240 support requests, about 30 minutes of hands-on work each | 120 |
| Onboarding, departures, and equipment preparation | 30 |
| Recurring administration and security checks | 45 |
| Vendor work and documentation | 20 |
| Approved project work | 50 |
| Total | 265 |
If each person has about 115 hours a month available for this work, the estimate is 265 ÷ 115, or about 2.3 people. That does not automatically mean hiring a third person. It means the current scope is more than two people can deliver. The options include moving defined work to a provider, cutting project commitments, fixing repeat causes, or adding internal capacity.
Change the inputs and the answer changes. Use more than one month, test a busier month, and include the work that keeps getting postponed. A team cannot show its full demand if important tasks never start.
Why isn't the number of hours enough?
A team can have enough hours on paper and still fail the business, for two reasons.
Skills. Ask who handles a complex network change, a serious security incident, or a failure in a critical application. If nobody on the team has that expertise, another generalist hire will not fix it.
Coverage. Ask who covers vacations and sick days, what happens when two locations need on-site help at once, and who responds when something critical fails at night or on a weekend. Map coverage by time of day and by responsibility. A workload estimate of 2.3 people says nothing about whether anyone is available at 7 p.m. on a Friday.
Do you need another hire or a different kind of help?
| What you find | What to consider |
|---|---|
| Routine support demand consistently exceeds capacity | Another support technician |
| Administration is the bottleneck | A systems administrator, or a defined administration service |
| Complex problems stall even when staff have time | Senior escalation or specialist help |
| One project is eating all spare capacity | Project support with a planned handover |
| Nobody sets priorities or manages the work | An IT manager or leadership support |
| Coverage gaps are the main issue | An after-hours or overflow coverage agreement |
An internal hire brings continuity and close relationships with employees. Outside support adds expertise or covers defined work without creating a full-time role for it. Co-managed IT combines the two: your team keeps the work it does well, and a partner takes defined responsibilities, with clear rules for who handles requests, who approves changes, which hours are covered, and when work escalates.
If you are sizing your first role, our guide on how to hire your first IT person turns the workload into a job description. If you already have a team, the internal IT maturity assessment helps find problems that another hire alone will not fix.
What this looks like in practice
A multistate real estate company we support has more than 250 employees and manages over 100 multifamily properties. Most property offices are far too small for their own technology staff, yet each still needs dependable internet, secure computers, clean wiring, and working cameras. Counting employees would miss the real need, which is coverage across more than 100 sites. The corporate team keeps oversight of standards, security, and priorities, while property offices have one clear place to bring local technology problems and on-site work is coordinated centrally. Read the multifamily real estate case study.
How do you make the case to leadership?
Show the evidence behind the request: current workload, postponed work, your capacity assumptions, skills gaps, and uncovered hours. Explain what the change would let the team accomplish.
Compare complete costs for each option. For an employee, include recruiting, employer costs, benefits, equipment, training, and tools. For a provider, include setup, recurring charges, exclusions, and the internal time still needed to manage the relationship. Then agree how you will judge the result, for example aging requests, repeat problems, onboarding readiness, and project progress. More staff should lead to a defined improvement, not just a bigger payroll.
How Compass can help
Compass is Spot On Tech's support for companies with their own IT staff, or companies building it. You can use it in any combination, one time or ongoing: a staffing and workload evaluation, help defining roles and hiring, tool selection and setup, escalation support at only the levels you need, after-hours coverage, or security monitoring.
If you are a New York or New Jersey business deciding whether to hire, talk with Spot On Tech. Bring your ticket history, your project list, and the hours you need covered.
Frequently asked questions
How many IT staff do we need for 100 employees?
There is no reliable single number, because locations, applications, support hours, and projects matter as much as headcount. In our experience, many 100-person offices on standard cloud systems run with one or two internal IT people backed by outside escalation and after-hours coverage. A 120-user healthcare facility we support runs with one internal IT professional plus co-managed support.
What is a good IT staff-to-user ratio?
A useful ratio comes from comparable organizations, with a clear definition of which roles are counted. Use benchmark studies as a cross-check against your own workload count, not as a target.
How do you calculate IT staffing needs?
Add up monthly hours for support, employee changes, administration, security, vendors, projects, and management. Divide by the hours each person realistically has available. Then check separately whether the team has the right skills and whether someone is available when work happens.
Does a growing ticket backlog mean we need to hire?
Not always. A backlog can come from too little capacity, but also from repeat incidents, missing expertise, vendor delays, weak prioritization, or unclear ownership. Check those causes before adding headcount.
Should we hire another technician or use co-managed IT?
Hire when there is steady work suited to an internal role. Consider co-managed support when the need is a mix of expertise, defined responsibilities, or coverage. Compare the same scope for both options and include the internal time each still requires.
