IT outsourcing in South Africa: how to get it right

IT outsourcing in South Africa ranges from a two-person managed services provider running your Office 365 to a multi-year application development contract with an offshore team. The principles for getting it right are the same at every scale: outsource the right things, write contracts that protect you, and retain enough knowledge internally to manage the relationship.

1.What to outsource

Good candidates: Infrastructure management (servers, networks, cloud), end-user support (helpdesk, desktop support), security monitoring (SOC services), application maintenance (bug fixes, minor enhancements), and specialised development (mobile apps, integrations, projects with a defined scope).

Bad candidates: Technology strategy (you are outsourcing your competitive advantage), vendor selection (the outsourcer will recommend themselves), data governance (accountability cannot be delegated), and architecture decisions (these shape your business for years).

The test: if losing this capability would make you unable to evaluate whether your IT partner is doing a good job, keep it in-house.

2.Contract structures that work

• Managed services (monthly retainer): Best for ongoing operations like infrastructure and support. Predictable cost, clear scope. Ensure the scope is genuinely defined — "all IT support" is not a scope.
• Time and materials: Best for development projects where scope is uncertain. You pay for hours worked. Manage actively or costs drift.
• Fixed price: Best for projects with clear requirements and a defined deliverable. The vendor takes the risk, which means they price it in. Expect 20–40% premium over T&M for the same work.
• Outcome-based: You pay for results (uptime, resolution time, user satisfaction). The most aligned model but the hardest to define properly. Works well for mature outsourcing relationships.

3.SLAs that measure what matters

An SLA that measures "response time" incentivises fast acknowledgement, not fast resolution. An SLA that measures "uptime" incentivises narrow definitions of downtime. Write SLAs that measure the outcomes your business cares about: resolution time by severity, user satisfaction scores, mean time between failures, and the business impact of incidents.

Include a regular review mechanism (monthly, not annually) and a clear escalation path. An SLA without a review cadence is a document, not a management tool.

4.IP and data ownership

The contract must state clearly: any intellectual property created for your business belongs to your business. Your data is yours and must be returned in a usable format at termination. Source code for custom development is yours and held in a repository you control.

These sound obvious. They are not in many South African IT contracts. Check yours.

5.The exit plan

Before you sign an outsourcing contract, plan how you would leave it. What data do you get back? What documentation exists? How long is the transition period? What does it cost?

An outsourcing relationship without an exit plan is a dependency. Dependencies are expensive to escape, and outsourcers know it.

The bottom line

IT outsourcing works when you outsource operations and keep decisions. Write contracts that protect your IP and data, define SLAs that measure outcomes, plan the exit before you sign, and retain enough internal capability to know whether you are getting value. The best outsourcing relationships are partnerships. The worst are dependencies.

General guidance based on experience. Your circumstances may differ — validate with qualified professionals.