Choosing an MSP in South Africa — 12 Questions to Ask Before Signing

Why the wrong MSP is expensive

A weak MSP costs you three ways: direct spend that doesn't deliver value, hidden downtime and productivity drag, and — worst — a security posture you think is covered until the day it isn't. The right MSP isn't always the cheapest, but the wrong one will always be the most expensive.

The 12 questions to ask before signing

1. How do you earn your money? Fixed retainer aligned to prevention — good. Break-fix + project revenue when things go wrong — bad incentive.
2. What's your engineer-to-user ratio, and how many tickets does one engineer handle daily? If they can't tell you, they aren't measuring themselves.
3. Show me your SLA, and show me last month's actual SLA compliance report. The paper SLA is easy; the report is where honesty lives.
4. Who owns our data, credentials and documentation? Answer must be: you. Always. If they hold your Microsoft tenant admin credentials without giving you break-glass access, that's a lock-in trap.
5. How do you handle after-hours P1 incidents — with names? Get the names, numbers and escalation path. A shared inbox isn't a plan.
6. What's your security stack for your own business? If they don't run MFA, EDR and immutable backups internally, they can't credibly manage yours.
7. How often do you meet with your clients strategically, and what does that meeting produce? Quarterly business review with a written report is the minimum. If it's "we send you tickets", they're a helpdesk, not a partner.
8. What's your onboarding process and how long does it take? A proper 30-60-90 day onboarding with documented discovery and baseline is essential. "We'll figure it out as we go" is the wrong answer.
9. Which cyber insurance controls are already baked in? MFA, EDR, immutable backup, MDR — these should be default, not upgrade-priced.
10. Can I speak to two clients your size, one 2+ years in, one recently onboarded? If they hesitate or curate too carefully, ask why.
11. What happens if we want to leave? Show me the exit clause and data return process. A confident MSP will tell you exactly. A weak one will make it painful — which tells you why they're keeping clients.
12. What have you told a client "no" to recently, and why? Great MSPs push back. Order-takers don't. This one question reveals culture faster than any other.

Red flags in the answers

• Vague pricing — "it depends" without ranges after understanding your business.
• Refusal to provide references, or all references being brand new.
• Long contracts (36+ months) without commercial benefit.
• They hold your credentials without providing break-glass admin access.
• Every problem is somebody else's fault — the ISP, the software vendor, the users.
• They oversell certifications ("Microsoft Gold Partner!") but can't produce named engineers with matching skills.
• No account manager or vCIO layer — you only ever speak to the helpdesk.
• They can't produce a sample monthly report or QBR deck.

Green flags to look for

• They ask you more questions than you ask them.
• They walk you through their internal ticket, documentation and monitoring systems live.
• They volunteer things they don't do well — sign of maturity, not weakness.
• Their proposal describes outcomes and risks, not just line items.
• They talk about your business, not just their tech stack.
• They insist on a proper discovery/assessment before quoting the full scope.
• They show you a real client's monthly report (redacted).
• You leave the meeting with 2–3 concrete recommendations that would apply even if you didn't hire them.

Contract clauses that matter

• Term & termination. Fixed initial term (12–24 months typical), termination-for-cause with defined cure period, termination-for-convenience with fair notice (60–90 days).
• SLA & credits. Automatic pro-rata credits for missed SLA — no need to claim.
• Data ownership & portability. All your data returned in standard formats within 30 days of termination, at no additional cost.
• Credential handover. All admin credentials handed back to you at exit — with proof of MSP account deletion.
• Documentation. Full network diagrams, asset lists, licence inventories, procedures — kept current and shared quarterly.
• Change control. No material changes to your environment without written approval.
• Confidentiality & POPIA. Data-processing agreement, breach notification within 24 hours to you.
• Insurance. Professional indemnity and cyber liability cover, with named amounts and proof provided annually.

How to structure a graceful exit

1. Give written notice per contract, aim for 90-day transition.
2. Kick off a joint transition project with the incoming MSP — outgoing must cooperate contractually.
3. Documentation handover in weeks 1–2: diagrams, credentials, licence inventory, vendor contacts, ticket history.
4. Access parallel period in weeks 3–8: both MSPs have access, incoming shadows on live tickets.
5. Cutover in week 9–10: outgoing loses access, incoming owns operations.
6. 30-day warranty period: outgoing MSP still consultable for handover queries at reasonable rate.
7. Final wash-up: proof of credential deletion, final invoice reconciliation, references exchanged.

Frequently asked questions