When does an SMB need its own IT service desk?

Most small businesses do not need a service desk in the technical sense. They need the things a service desk delivers: someone answering when IT breaks, tickets that do not get lost, a way to ask for new software without three emails and a follow-up. Whether that arrives via your own team or via a managed service provider is the real question.

The decision is not religious. It is financial and operational. Below the line where in-house makes sense, you are paying for staff you do not need. Above the line where outsourcing makes sense, you are paying retainer fees for work an in-house team would do faster. The trick is knowing which side of the line your business sits on.

The hidden cost of running IT on inbox and chat

Before either option enters the conversation, a lot of growing businesses just run IT support out of someone’s inbox. The office manager who is good with computers. The operations lead who happens to know Microsoft 365. The IT-savvy graduate who got drafted into helping everyone with their laptop.

This works until it does not. The breakpoint is usually around 20 to 30 staff, sometimes earlier. The signs are recognisable.

Tickets get lost in inboxes. Two people start helping with the same issue. Nobody has a record of what was tried last time, so the same problem gets diagnosed from scratch. The informal IT person is now spending two days a week on IT and getting blamed when they cannot keep up with their actual job. New starters wait three days for an account because nobody owns the request.

At this point the business has three real options. Hire dedicated IT staff. Outsource to a managed IT services provider. Or pretend the problem is not happening and watch productivity quietly bleed out. Most owners pick the third option for longer than they should.

Three signs you have outgrown the inbox

Your staff have stopped reporting small problems. When raising an IT issue is more painful than working around it, staff stop bothering. The printer that has not worked properly for six months. The slow laptop that the new analyst tolerates. The shared mailbox that keeps dropping access for one user. The cost of these unreported issues is real, just invisible.

Onboarding takes longer than it should. If setting up a new starter takes more than 90 minutes of someone’s time, your provisioning is broken. A new staff member should walk in, get a laptop with their accounts pre-configured, and be productive the same morning. If that is not happening, you do not have a service desk, you have a series of one-off favours.

Nobody can tell you how many tickets came in last month. If asked, the person doing the IT cannot give you a number. They will say “lots” or “the usual” or “more than last month”. Without a system, the workload is invisible. You cannot manage what you cannot measure.

Option A: run your own service desk

Going in-house means hiring at least one dedicated IT person, licensing a ticketing platform (Freshservice, Jira Service Management, or ServiceNow at the high end), and committing to the process work that keeps it running.

Real annual costs for an SMB running a one-person service desk in Perth:

• Salary plus on-costs. $80,000 to $120,000 fully loaded for one IT support engineer with three to five years of experience.
• Ticketing platform. $5,000 to $25,000 a year depending on tier and integrations.
• Endpoint and monitoring tools. $10,000 to $40,000 a year for RMM, antivirus, backup, and patch management.
• Training and certifications. $5,000 to $15,000 a year to keep skills current.
• Coverage gaps. One person cannot cover annual leave, sick leave, or after-hours incidents. Either you accept the gap or you hire a second person.

All-in for one in-house IT person with the right tools, you are looking at $120,000 to $180,000 a year. That number doubles if you need genuine coverage seven days a week or after hours.

What you get for it is responsiveness, deep knowledge of your specific environment, and someone who is fully focused on your business. What you do not get easily is breadth. One person cannot be expert in networking, Microsoft 365, cyber security, cloud architecture, and end-user support. They specialise, and the gaps show up at the worst time.

Option B: outsource to a managed IT services provider

Outsourcing to an MSP means paying a per-seat or per-device monthly fee for a team of specialists running your service desk on a shared platform.

Typical pricing for full-stack managed IT in Perth runs $120 to $250 per user per month for SMBs, depending on what is included. Cybersecurity-first MSPs sit at the upper end of that range because they bundle in Essential 8 controls, awareness training, and managed endpoint detection.

For a 30-person business, that is $43,200 to $90,000 a year, all in. For 60 people, it is $86,400 to $180,000. The math starts to look comparable to in-house once you cross around 60 to 80 staff, depending on tier and tooling included.

What you get for the money is a team of specialists rather than one generalist, 24/7 coverage if you pay for it, established processes that you do not have to build from scratch, and a platform that is already integrated and configured. What you give up is the level of immediate, hands-on familiarity that an in-house person delivers when they sit twenty feet from the problem.

For the practical detail on what we cover, see our managed IT support service page.

The math at different staff counts

The honest guidance, based on running service desks for Perth SMBs since 2003:

Under 30 staff: outsource. The math is not even close. You cannot keep one IT person busy enough to justify the salary, and you definitely cannot justify the tools they need around them.

30 to 80 staff: still usually outsource. The MSP economics are better through this range, and the breadth of skills you get from a team beats one specialist. The exception is if you have an unusually complex environment such as a regulated industry, custom line-of-business applications, or manufacturing operations.

80 to 150 staff: depends. This is the genuinely interesting zone. An in-house team of two becomes financially comparable to MSP pricing, and you start to get real value from internal context and dedicated focus. But you also have to manage a team, build processes, and own the tooling. Most businesses in this range underestimate the management overhead.

150+ staff: usually some in-house. At this size most businesses run a small in-house team for level one support and use an MSP for level two and three specialist work, project delivery, and after-hours coverage. Pure in-house works at this size, but the breadth question remains.

The variable that breaks these ranges is industry. A 25-staff law firm with sensitive document obligations needs more security investment than a 25-staff retail business. A construction company with site offices and field workers needs different IT infrastructure than a 25-staff professional services firm. The staff-count guidance is the starting point, not the final answer.

Why hybrid models usually fail

The “hire one person and outsource the rest” model sounds reasonable on paper and works in practice less than half the time we see it tried.

The pattern that fails is making the in-house person a peer of the MSP. They handle the easy stuff fast, but anything that needs the MSP gets stuck on their desk until they have time to triage it. Staff start avoiding the formal channel and going direct to the MSP, which then sends invoices the in-house person cannot reconcile. Ownership of incidents gets fuzzy. Both sides end up frustrated.

The pattern that works is treating the in-house person as the explicit customer of the MSP, not a peer. They are accountable for the IT experience the business sees. The MSP is their delivery arm. The in-house person spends most of their time on strategic work such as vendor management, project planning, and business engagement, and very little time on day-to-day tickets, which route straight to the MSP queue. This works because the roles are different rather than overlapping.

If you are considering hybrid, get clear about which model you are actually building before you hire. A virtual CIO is a different shape of in-house role than a service desk engineer, and the economics work better at smaller sizes.

What you should do now

Run an honest staff-count check. If you are under 30 staff and currently running IT out of someone’s inbox, you are below the line where in-house makes sense. Pick an MSP. Stop debating it.

If you are 30 to 80 staff, do the math both ways. Build out the real annual cost of one in-house IT person with the right tools, and compare it to MSP quotes for your size. The numbers usually surprise people. Account for coverage gaps, not just the salary line.

If you are over 80 staff, decide what model you are building. Pure in-house, pure outsourced, or explicit hybrid. Get the strategy right before you hire anyone or sign anyone.

If you want a second opinion on which side of the line your business sits on, book a free IT assessment with our team. We will look at your current setup, ticket volume, and growth plans, and give you an honest call on whether outsourcing makes sense for you. Greg Markowski runs our service desk operations and is ITIL certified. He will tell you straight if you are better off in-house.