The MSP Market in Nigeria
The managed IT services market in Nigeria is growing, but it's also fragmented. You'll find everything from one-person consultancies calling themselves MSPs to large enterprises with full 24/7 operations.
Choosing the wrong provider can be worse than having no provider at all. This guide helps you evaluate MSPs and make an informed decision.
What Makes an MSP Different from "IT Support"
Traditional IT Support:
- Reactive: You call when something breaks
- Hourly billing: The more problems, the more you pay
- No visibility: You don't know what's happening until it fails
- Variable costs: Surprise bills are common
Managed Service Provider:
- Proactive: Problems are prevented or caught early
- Fixed monthly fee: Predictable costs
- Full visibility: Regular reports show system status
- Aligned incentives: They benefit from keeping your systems healthy
When evaluating providers, make sure they're offering true managed services, not just rebranded break-fix support.
The 10 Questions to Ask Every MSP
1. "What's included in the monthly fee?"
Good answer: Clear scope document listing exactly what's covered—monitoring, patching, support hours, reporting, etc.
Red flag: Vague answers like "we handle everything" or "it depends."
Why it matters: Hidden fees destroy your budget. You need to know exactly what you're paying for.
2. "How do you handle incidents outside business hours?"
Good answer: Specific process—who monitors, response times, escalation procedures.
Red flag: "Call us and we'll figure it out."
Why it matters: Security incidents don't wait for business hours. Your provider shouldn't either.
3. "What tools do you use?"
Good answer: Named, established tools (they might not name specific vendors, but should describe capabilities).
Red flag: Reluctance to discuss their technology stack at all.
Why it matters: Professional tools enable professional service. Manual processes don't scale.
4. "Can I see a sample monthly report?"
Good answer: Yes, here's a redacted example showing the format and detail level.
Red flag: "We provide reports upon request" (meaning: they don't do regular reporting).
Why it matters: Reports prove work is being done and give you visibility into your security posture.
5. "What happens if we want to leave?"
Good answer: Clear exit process—notice period, data handover, documentation provided.
Red flag: Long lock-in periods, vague transition process, or reluctance to discuss.
Why it matters: Good providers earn your business every month. They shouldn't need to trap you.
6. "What certifications does your team hold?"
Good answer: Specific certifications relevant to the services offered (CompTIA, Microsoft, Cisco, security certifications).
Red flag: No certifications, or only sales/vendor certifications.
Why it matters: Certifications aren't everything, but they indicate commitment to professional development.
7. "Can I speak with current clients?"
Good answer: Yes, here are references you can contact.
Red flag: "We can't share client information" (for references, this is a weak excuse).
Why it matters: Real clients can tell you what working with this MSP is actually like.
8. "What's your response time for different issue types?"
Good answer: Defined SLAs—critical issues within X hours, high within Y hours, etc.
Red flag: "We respond as quickly as possible" without specifics.
Why it matters: Without defined SLAs, "as soon as possible" might mean tomorrow.
9. "How do you handle security incidents?"
Good answer: Documented incident response process—detection, containment, eradication, recovery, lessons learned.
Red flag: "We haven't had any incidents" (either very new, very small, or not looking).
Why it matters: Incidents will happen. You need to know they can handle them.
10. "What does onboarding look like?"
Good answer: Structured process—discovery, agent deployment, baseline assessment, documentation, training.
Red flag: "We can start monitoring tomorrow" (indicates no proper setup process).
Why it matters: Good MSPs need to understand your environment before they can protect it.
Red Flags to Watch For
Pricing Red Flags:
- Prices dramatically lower than competitors (unsustainable or missing services)
- Refusal to put pricing in writing
- Heavy reliance on "projects" for additional revenue
- Complex pricing tied to metrics you can't verify
Capability Red Flags:
- Can't explain their technology stack
- No defined processes or documentation
- One-person operation claiming 24/7 coverage
- No professional liability insurance
Relationship Red Flags:
- Pushes long-term contracts before you've tested the service
- Reluctant to provide references
- Poor communication during sales process (it only gets worse)
- Makes unrealistic promises ("zero downtime guaranteed")
The Evaluation Process
Step 1: Define Your Needs
Before talking to MSPs, document:
- How many endpoints (computers/devices) you have
- What systems are business-critical
- What compliance requirements you face
- What problems you're trying to solve
- Your budget range
Step 2: Create a Shortlist
Identify 3-5 MSPs through:
- Referrals from business peers
- Professional associations
- Online research
- Industry events
Step 3: Initial Conversations
Have introductory calls to:
- Explain your needs
- Understand their services
- Assess cultural fit
- Get ballpark pricing
Eliminate providers who don't listen or try to sell before understanding.
Step 4: Detailed Proposals
Request detailed proposals from 2-3 finalists including:
- Specific services included
- Pricing breakdown
- Onboarding timeline
- Sample SLA
- References
Step 5: Reference Checks
Contact at least 2 references per finalist. Ask:
- How long have you worked with them?
- How responsive are they to issues?
- What do the monthly reports look like?
- Have you had any security incidents? How were they handled?
- Would you recommend them?
Step 6: Pilot Period
Before committing long-term, negotiate a pilot:
- 3-month initial term
- Defined success criteria
- Option to continue or exit
What Good MSP Relationships Look Like
Communication:
- Regular check-ins (monthly or quarterly)
- Proactive notifications about issues
- Clear escalation paths
- Responsive to inquiries
Reporting:
- Monthly reports delivered on time
- Easy to understand format
- Actionable recommendations
- Trend analysis over time
Service:
- Issues resolved within SLA
- Root cause analysis provided
- Preventive measures implemented
- Continuous improvement visible
Partnership:
- Understands your business context
- Provides strategic advice
- Scales with your growth
- Treats your success as their success
The Bottom Line
Choosing an MSP is choosing a partner for your business's technology foundation. Take the time to evaluate properly. Ask hard questions. Check references. Start with a pilot period.
The right MSP will make your technology an asset instead of a headache. The wrong one will add problems instead of solving them.
Use the questions and criteria in this guide to separate the professionals from the pretenders.