Buying guide
How to choose IT support for a small business in South Africa
A useful support agreement defines ownership, response, routine work, security boundaries, and the exit path before the first incident. Compare the operating model rather than a monthly number alone.
Define the outcome
List the systems the provider will own or support, the users and devices covered, the business hours that matter, and the incidents that cannot wait until the next day. Include email, internet, Wi-Fi, accounting, backups, security, printers, phones, and line-of-business systems.
Separate project work such as a migration, office move, new Wi-Fi design, or security hardening from recurring support. Otherwise the monthly price will be difficult to compare.
Describe the environment
Record users, devices, locations, cloud services, domains, internet providers, critical applications, remote workers, and legacy systems. A provider cannot price or secure an environment that has not been described.
Note current pain points and the cost of an outage. A locked mailbox, failed backup, lost laptop, and slow printer do not require the same response or support model.
Compare the operating model
Ask who responds, where tickets are recorded, what response and resolution targets mean, how after-hours work is charged, and whether a named person remains accountable when a specialist or upstream provider is needed.
A low monthly fee can be reasonable if the scope is narrow and clear. The risk is an agreement that sounds broad but excludes the systems the business actually depends on.
Separate support from projects
Ask which tasks are included in recurring support and which are quoted separately: onboarding, tenant migration, new office setup, device replacement, backups, security response, website work, and vendor coordination.
Confirm project rates, approval thresholds, time tracking, travel, third-party licences, and what happens when a project changes the supported environment.
Check security and recovery
Ask how the provider manages multi-factor authentication, administrator access, device updates, endpoint protection, email security, backups, incident response, and restore testing. Confirm whether the business owns the accounts, backup environment, and recovery contacts.
A dashboard or security label is not evidence that the business can recover. Ask for the last restore or test result and the action taken when a control fails.
Keep control of the business
The business should retain ownership of domains, cloud tenants, administrator accounts, backups, documentation, licences, DNS, and recovery information. The provider may manage them but should not be the only person who can access or recover them.
Request a written onboarding checklist, access register, documentation standard, reporting format, and exit process before signing.
Test likely incidents
Ask what happens when email is compromised, a laptop is lost, fibre fails, a staff member leaves, a restore is needed, or a critical supplier is unavailable. Confirm who acts, how quickly, what the business must do, and what the event costs.
Compare the likely incident cost and downtime against the recurring fee. The most useful agreement is the one that remains understandable under pressure.
Use provider pricing as evidence, not a promise
InfoServ publishes a South African managed-IT pricing structure around users and devices and describes services such as endpoint protection, Microsoft 365 management, backup, and portal access. That helps define questions, but it is not a universal market rate or recommendation.
Check the current provider page and request a written proposal for the actual environment. Do not assume a service level, response time, or outcome that is not written into the proposal.
Sources and further reading
Back to all guides Compare support options Compare software Compare hosting