The technology stack that makes remote work actually work in South Africa

South African businesses proved during lockdown that remote work is technically possible. What most have not proven is that it is sustainable, secure and fair to the people doing it. The gap is not motivation — it is infrastructure, security, and a set of policies that account for load shedding, data costs and the fact that not everyone has uncapped fibre at home.

1.The baseline stack

Every remote-capable business needs four layers: identity and access (who can access what, from where), communication (chat, video, async), collaboration (shared documents, project tracking), and security (endpoint protection, VPN or zero-trust, data loss prevention).

For most SA SMEs, Microsoft 365 Business Premium or Google Workspace Business Plus covers the first three. Security is where most under-invest.

2.Connectivity — the great equaliser

A remote-work policy without a connectivity strategy is a prayer. South African realities: not everyone has fibre; mobile data is expensive; load shedding kills routers and ONTs. The business needs to decide whether to subsidise connectivity, provide mobile data, or require a minimum connection standard — and budget accordingly.

A R500/month connectivity allowance per remote worker is cheaper than an office desk and is the single highest-impact investment in remote productivity.

3.Security is the non-negotiable

Remote workers expand your attack surface. The minimum: MFA on everything (not optional, not SMS-only), managed devices or MDM (personal laptops accessing company data need endpoint protection), a VPN or zero-trust network access for anything internal, and data classification so people know what cannot leave the corporate environment.

The POPIA angle: if personal data is processed on a home device and that device is compromised, you have a breach — and the Information Regulator will ask what controls were in place. "We trusted our staff" is not a control.

4.The tools that earn their keep

• Chat: Microsoft Teams or Slack. Pick one, enforce it, retire email for internal communication.
• Video: Teams, Google Meet or Zoom — whichever is bundled with your productivity suite. Do not pay for a separate tool.
• Project management: Asana, Monday, Linear or Notion. The tool matters less than the habit of using it.
• Document collaboration: SharePoint/OneDrive or Google Drive. Real-time co-editing eliminates version-control chaos.
• Time tracking: Only if your business genuinely needs it. Surveillance tools destroy trust faster than they improve productivity.

5.Load shedding and the home office

A UPS for the router and laptop is a R2,000–R4,000 investment that gives 2–4 hours of continued work. For extended outages, mobile data becomes the fallback. The business should have a clear policy: during scheduled load shedding above Stage 4, is the expectation that people work through it, shift their hours, or take the time?

Ambiguity on this point is the number-one source of remote-work resentment in South African teams.

6.The policy comes before the tools

A remote-work policy covers: who is eligible, what equipment and connectivity the business provides, working hours and availability expectations, security requirements, data handling rules, and what happens during extended infrastructure outages. Write it, get legal to review it (employment law and POPIA), and communicate it before you roll out the tools.

A good policy protects both the business and the employee. A missing policy protects nobody and generates conflict.

The bottom line

Remote work in South Africa is a connectivity and security challenge, not a tools challenge. Fix the infrastructure, enforce security, write the policy, and give people a fair connectivity allowance. Everything else is optimisation.

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