Good IT support gives your team someone to turn to—and makes fewer things need turning to in the first place. Before comparing monthly prices, agree what you need someone to own.
A new colleague starts on Monday. Their laptop is ready, but their mailbox is not. Someone shares a login to get them working, a folder remains out of reach, and the office manager spends the morning chasing answers. Nothing dramatic has broken. Work has simply become harder than it needs to be.
For a small South African business, that is a useful place to start an IT conversation: the ordinary moments that waste time. A provider should be able to explain how they would handle those moments, what falls outside their service, and who will keep you informed.
Start with the work, then choose the support model
Write down the last five technology problems that interrupted your team. Add the recurring jobs: new starters, people leaving, software renewals and access reviews. That list is a better brief than “we need IT support”.
| Your situation | A sensible starting point |
|---|---|
| One clear problem, with an otherwise stable setup | A scoped, one-off intervention. |
| Recurring requests and nobody responsible for the basics | Ongoing support with explicit responsibilities. |
| An inherited setup nobody can explain | An assessment before agreeing a long-term service. |
| An internal IT person who needs help with a particular system | Specialist support that complements their role. |
These are starting points, not rules. A monthly arrangement can still exclude projects, equipment and out-of-hours work. Ask for a scope you can understand without a technical translator.
Ask who owns the everyday jobs
Use a simple onboarding and offboarding example during the conversation. Who creates the account? Who approves access? Who removes it when the person leaves? Who checks that business files remain available?
Microsoft’s employee departure guidance separates blocking access from preserving email and files. That distinction matters: deleting a licence or disabling a laptop is not the whole handover. Your provider should have a process that fits the tools you actually use.
Keep company ownership of your domain, cloud accounts and subscriptions clear. Give the provider appropriate administrative access rather than letting everything depend on one shared password. Record who can approve changes and how you would transfer support if you chose to leave.
Separate a quick reply from a useful resolution
“We respond quickly” leaves a lot unanswered. Ask what happens when one person cannot print, and what happens when the whole team cannot sign in. Which gets priority? During which hours? How will you hear about progress?
A response target usually describes acknowledgement or the start of work. It does not necessarily promise a fix within that time. Some faults depend on an internet provider, a software vendor or replacement hardware. What matters is that someone owns the next action and communicates it.
Remote support also has a physical limit. If a router fails or a laptop needs repair, establish who handles the on-site work, where they can help, and whether it costs extra. For distributed teams, include the practical realities of home connections and alternative access during an outage.
Compare the whole arrangement
Request a written breakdown of support fees, licences, once-off setup, project work, travel and after-hours charges. Confirm whether quoted rand amounts include VAT. Avoid judging two proposals on their headline monthly figure when one covers substantially more work.
Take these five questions into the meeting
- Which people, devices and applications are covered?
- What recurring checks happen without us logging a request?
- Who coordinates a problem involving more than one supplier?
- What costs extra, and who approves that cost?
- What documentation and access do we receive if we move?
A useful first step might be a small assessment and a short list of fixes. It need not be a migration or a long contract. The right arrangement should make the next working day easier to manage—and make responsibility clear when something does go wrong.