A new 2026 benchmark report analyzed more than 50,000 IT support tickets across 30-plus organizations over 14 months. A lot of the headlines are about big IT departments, but strip those out and a handful of findings cut straight to what running technology looks like for a small business. They also line up with what we see every day: most IT pain is routine, speed matters more than people expect, and at a small headcount the math on support works very differently.
Here are the findings that actually matter if you run a team of 1 to 50 people, and what to do about them.
Most IT problems are routine, and that is the point
The tickets cluster in a few predictable buckets: software and applications (38% of all tickets), onboarding and offboarding (about 17%), and identity and access, meaning logins and permissions (about 16%). Just assigning people the apps they need accounted for roughly a quarter of tickets on its own.
For a small business, that is good news. Your IT problems are not exotic. They are the same dozen things over and over: someone needs access, an app is misbehaving, a new hire needs to be set up. Predictable work is work you can systematize, automate, or hand to someone whose job it is, instead of letting it land on whoever is closest to the problem.
One in five tickets stops someone from working
The report found that 22% of tickets are productivity-blocking: the person literally cannot do their job until it is fixed. The biggest culprits were permissions problems and login trouble.
This is where small teams feel it hardest. When you have eight people and one is locked out for an afternoon, that is a meaningful chunk of your workforce sitting idle, not a rounding error absorbed by a big department. The real cost of an IT issue is rarely the fix itself. It is the hour, or the day, that someone could not work while they waited.
Speed matters more than you would guess
The data on user frustration is striking. Tickets resolved in the 15-minute to 1-hour window saw a 97% improvement in user sentiment: people who started annoyed ended up satisfied. The median first response across the dataset was about 5 minutes. The lesson is not just that problems get fixed, it is that fixing them quickly is what keeps people happy and working.
Fast, consistent response is exactly what an informal setup struggles with. If "IT" is a co-founder answering between meetings or a friend who helps out when they can, response time is whatever is left over. That gap is where frustration and lost time pile up.
Setting up a new hire is the slow one
Onboarding stood out as the longest task by far. Getting a new employee fully set up ran to a median of roughly 76 hours of elapsed time, because it is not one task: it is creating accounts, granting the right access, assigning apps, and preparing hardware, often across several systems. Offboarding has the mirror-image risk, where access is left active after someone leaves.
For a growing small business that is hiring, this is the case for a written, repeatable onboarding checklist rather than rebuilding the process from memory each time. It gets people productive on day one and closes the security gaps that come from access nobody is tracking.
Automation resolves issues about 16 times faster
One of the sharpest numbers in the report: tickets handled with automation reached a median resolution of 4.4 hours, versus about 71 hours, nearly three days, without it. Roughly 30% of automated tickets were resolved within an hour, compared with under 4% when everything was manual. Interestingly, the first response time was about the same either way. The difference was entirely in how fast things actually got resolved.
You do not need an enterprise platform to benefit from this. Modern, well-configured tools handle the routine, repetitive requests, the password resets, the access grants, the standard setups, so the slow, manual handling is reserved for the genuinely unusual problems.
You do not need a full IT hire, you need coverage
Across the dataset, organizations ran a median of about 1.6 IT staff per 100 employees. Do that math for a business of 1 to 50 people and you land well under a single full-time person. Yet everything above still has to happen: routine requests handled, work stoppages cleared fast, new hires set up, the slow stuff automated.
That is the small-business bind in one line. The workload does not justify a full-time IT salary, but it absolutely needs fast, reliable coverage. Trying to split the difference with a part-time arrangement or a willing employee is what produces the slow resolutions and the frustration the report measures.