IT support and management

Why it matters

Technology that is managed costs less than technology that is rescued. Updates applied on schedule prevent most security incidents, monitoring catches a failing drive before it fails, and documentation means a problem is fixed in an hour rather than rediscovered over a week. For a business of ten people, a day of downtime is a significant share of a month’s wages; a managed arrangement that prevents one such day a year pays for itself, and it gives the owner back the hours spent being the help desk.

What IT management covers

Good IT management is mostly routine. Devices and software are kept updated. Backups are monitored and tested. New staff get accounts and equipment on day one, and departing staff lose access the same day. Security settings such as multi-factor authentication are enforced rather than hoped for. Hardware is tracked and replaced before it fails. Licences are counted and matched to real users. And all of it is documented so that nothing depends on one person’s memory.

On top of the routine sits a small amount of planning: a view of what will need replacing or changing in the next year or two, a budget for it, and advice when the business is choosing new systems. A provider or staff member who only fixes things when they break is doing support, not management, and the difference shows up in how often things break.

• Patching and updates for devices, applications and network equipment.
• Monitoring of backups, security alerts, disk space and uptime.
• Starter and leaver process for accounts, devices and access.
• Asset and licence register kept current.
• Documentation of systems, passwords and procedures in a secure, shared place.
• Annual technology review and budget.

Choosing a support model

Doing it yourself works for a very small team with simple, cloud-based tools, provided someone actually does the routine work and the business accepts the risk of a slow recovery. A managed service provider, or MSP, is a company that looks after many small businesses’ technology for a monthly fee, usually priced per user or device, bundling monitoring, updates, a help desk and advice. In-house IT staff make sense when the business is large enough to keep them busy and to cover their leave.

Many businesses land on a hybrid: a provider for the routine and the after-hours, plus an internal person who knows the business and handles the day-to-day questions. Whatever the model, the test is the same: are updates, backups, access and documentation being done on a schedule, and does the business know who to call at 7 am on a Monday when nothing works?

The support cycle

Whether in-house or outsourced, effective support follows a loop. Systems are monitored so problems are seen early. Requests and incidents are logged in a ticketing system, not in text messages, so nothing is lost and patterns can be seen. Issues are prioritised by business impact and resolved against agreed targets. Each month the log is reviewed: which problems recur, which devices fail, which users need training. Those lessons feed changes that stop the same ticket being raised again.

The monthly review is where the value lives. A provider who sends a report showing tickets closed is reporting activity; one who tells you that half of last month’s tickets came from one old laptop, and recommends replacing it, is managing your technology.

Service levels and working with a provider

A service level agreement, or SLA, sets out what the provider will do and how fast. The useful parts are response and resolution targets by priority, support hours, what is included in the fee and what is billed separately, how security incidents are handled, and what happens to your documentation and accounts if you part ways. Read the exclusions carefully; projects, new equipment and after-hours work are commonly extra.

The relationship works best when the business holds its own keys. Administrator access to your cloud accounts, domain and network should be owned by the business and shared with the provider, not the other way around. Ask for the documentation to be stored where you can reach it, review the monthly report together and meet quarterly to talk about the year ahead rather than last week’s tickets.

How to set up IT support for a small business

1. Write down what you run Devices, applications, accounts, network equipment and who currently looks after each.
2. Decide the model Do it yourself with a routine, a managed provider, or a hybrid, based on size and tolerance for downtime.
3. Shortlist providers Two or three that serve businesses your size locally; ask the checklist questions and speak to their clients.
4. Agree the service levels Response and resolution targets, hours, inclusions, security handling and exit terms, in writing.
5. Keep your own keys Business-owned administrator accounts for cloud, domain and network, shared with the provider.
6. Set the routines Patching schedule, backup tests, starter and leaver process, monthly report, quarterly review.
7. Review the first quarter Compare tickets, downtime and response times against the agreement, and adjust.

Real-world example

A Darwin tour operator stops being its own help desk

Top End Expeditions runs guided tours with twelve staff, a booking system, point-of-sale at the depot and a fleet of tablets used by guides. The owner, Liam, handles IT himself. In peak season a tablet update breaks the guide app on the morning of three departures, the booking system’s payment integration fails for a weekend because an expired password nobody knew about, and Liam spends his busiest month on hold to vendors.

He engages a local managed service provider on a per-user monthly plan. They document everything, enrol the tablets in device management so updates are tested before release, move all logins to business identities with multi-factor authentication, set up monitoring for the booking and payment systems, and give staff a help desk number. The agreement specifies a one-hour response for anything that stops departures, and the business keeps ownership of every administrator account. The monthly report after the first quarter shows most tickets came from two ageing tablets, which are replaced. Liam gets his peak season back, and the provider’s fee is a fraction of what one lost weekend of bookings cost.

Common mistakes

• Break-fix by the hour Paying only when things fail means nobody is paid to prevent failure. Fixed-fee management aligns incentives.
• The provider holds the keys If the administrator accounts and documentation belong to the provider, you cannot leave and you cannot recover without them.
• Support by text message Requests sent to one person’s phone are lost, unprioritised and invisible. Insist on a ticketing system.
• No starter and leaver process Former staff with live accounts are a common breach. Access removal should happen the day someone leaves.
• Reading the report, skipping the review Ticket counts tell you little. Meet to discuss recurring problems and the plan to prevent them.

KPIs to track

• Tickets per user per month A steady fall shows management is preventing problems; a rise points to ageing equipment or training needs.
• Response and resolution against SLA The share of incidents handled within the agreed targets, by priority. Review monthly.
• Patch compliance Share of devices and systems with current updates applied. Target near 100 per cent within the agreed window.
• Leaver access removed same day Share of departures where all accounts were disabled on the last day. Target 100 per cent.
• Owner hours spent on IT Hours per month the owner or a non-IT staff member spends on technology problems. The number that justifies the fee.

Frequently asked questions

What does a managed service provider cost?

Most charge a monthly fee per user or per device that bundles monitoring, updates and help desk, with projects and equipment extra. Prices vary by region and scope, so compare at least two providers on the same inclusions.

At what size should I stop doing IT myself?

When the time you spend on it, or the risk of a slow recovery, costs more than a provider would. For many businesses that is somewhere between five and ten staff, or earlier if they handle sensitive data.

What is the difference between IT support and cybersecurity?

Support keeps things working; cybersecurity keeps them safe. Good providers do both at a basic level, but ask specifically what security monitoring, incident response and staff training are included.

Can a provider also help us choose new software?

Many will, and their knowledge of your setup is valuable. Be aware that some resell particular products, so ask whether they earn commission and seek independent advice for core system decisions.

Key takeaways

• Management prevents problems; support fixes them. You need both, on a schedule.
• Fixed-fee managed services align incentives better than paying by the hour for breakages.
• The business must own its administrator accounts and documentation, whoever provides support.
• Log every request in a ticketing system and review recurring problems monthly.
• Agree response targets, hours, inclusions, security handling and exit terms in writing.