How to choose the right IT support plan for a growing business

Choosing an IT support plan is one of the most consequential decisions a growing business makes. Get it right and technology becomes a competitive advantage. Get it wrong and you end up paying too much for too little - or worse, discovering gaps only when something breaks at the worst possible moment.

This guide walks through the main support models available in South Africa, what to look for in a provider, and how to match a plan to your current stage of growth.

The three main support models

1. Break-fix (reactive)

Under a break-fix arrangement, you call a technician when something goes wrong and pay per incident or per hour. There is no ongoing contract and no proactive monitoring.

When it works:

• Very small businesses (fewer than ten users) with simple setups
• Organisations with an internal IT person who only needs occasional backup
• Tight budgets where a monthly retainer feels premature

Where it falls short:

• No one is watching your systems between incidents, so small problems escalate silently
• Costs are unpredictable - a bad month can blow your budget
• The provider has no financial incentive to prevent problems, only to fix them
• Response times are best-effort with no SLA guarantees

Break-fix is the IT equivalent of only visiting the doctor when you are already sick. It is cheap in quiet months but expensive when things go wrong.

2. Managed IT (proactive)

A managed IT services plan is a fixed monthly fee that covers monitoring, maintenance, helpdesk support, and usually a defined scope of on-site visits. The provider takes ownership of your environment and is incentivised to keep it healthy because every incident costs them time.

Typical inclusions:

• 24/7 remote monitoring and alerting
• Patch management and software updates
• Helpdesk support with defined SLAs
• Regular health checks and reporting
• Vendor management (liaising with your ISP, software vendors, etc.)
• Strategic IT planning and budgeting (often called a virtual CIO or vCIO service)

When it works:

• Businesses with 15 to 500 users that depend on IT for daily operations
• Organisations without a full-time IT team, or with a small team that needs augmentation
• Any business where unplanned downtime has a measurable financial impact

This model pairs well with cloud architecture and engineering services when you are moving workloads off-premises and need ongoing optimisation.

3. Co-managed IT (collaborative)

Co-managed IT is a partnership between your internal IT team and an external provider. Your team handles the tasks they do best - typically user support and business-specific applications - while the provider covers areas where you lack depth, such as cybersecurity, cloud management, or after-hours monitoring.

When it works:

• Mid-market businesses with an internal IT manager or small team
• Organisations going through rapid growth where hiring cannot keep pace
• Companies with compliance requirements that demand specialist expertise

Where it shines:

• Your internal team keeps control and institutional knowledge
• The provider fills skill gaps without the cost of additional full-time hires
• Escalation paths are clear and contractually defined

What to look for in a support plan

Regardless of the model you choose, scrutinise these elements before signing.

Response and resolution SLAs

A service-level agreement (SLA) defines how quickly the provider must acknowledge and resolve issues at different priority levels. A typical structure looks like this:

Priority	Example	Response	Resolution target
Critical	Server down, all users affected	15 minutes	2 hours
High	Key application unavailable	30 minutes	4 hours
Medium	Single user cannot print	1 hour	8 business hours
Low	Feature request or non-urgent change	4 hours	5 business days

Ask for historical SLA performance data. Any provider worth considering will be able to show you their track record.

Scope and exclusions

Read the fine print. Common exclusions include:

• Projects and new deployments (often quoted separately)
• Hardware procurement (usually passed through at cost plus a margin)
• Third-party software issues outside the provider’s control
• After-hours support (sometimes an add-on)

Understand exactly what is in scope so you are not surprised by additional invoices.

Scalability

Your plan should accommodate growth without requiring a complete renegotiation. Ask:

• How is pricing structured - per user, per device, or flat fee?
• What happens when we add a new office or a significant number of users?
• Can we scale down if we need to?

Per-user pricing is the most transparent and aligns costs directly with headcount growth.

Security inclusions

At a minimum, a modern support plan should include endpoint protection, email filtering, and basic security monitoring. More mature plans bundle in vulnerability scanning, security awareness training, and incident response. If security is not included, you will need a separate engagement - and that gap is where breaches happen.

Reporting and transparency

You should receive a monthly report that covers:

• Ticket volumes and resolution times
• SLA compliance
• System health metrics (uptime, patch compliance, backup success rates)
• Recommendations for improvement
• Budget forecasts for upcoming projects

This reporting is your window into whether the provider is delivering value. If they resist transparency, that is a red flag.

Matching the plan to your growth stage

Startup or micro-business (1–15 users)

At this stage, a fully managed plan may feel like overkill. A lightweight managed offering - sometimes called “managed essentials” - that covers monitoring, patching, and remote helpdesk support is usually sufficient. Supplement with ad-hoc on-site support as needed.

Budget expectation: R 300–600 per user per month.

Growing SME (15–100 users)

This is where a comprehensive managed plan pays for itself. You likely have a mix of cloud and on-premises systems, growing compliance obligations, and enough users that downtime has a real financial cost. Invest in a plan with strong SLAs, proactive monitoring, and quarterly business reviews.

Budget expectation: R 500–1 200 per user per month depending on complexity and inclusions.

Mid-market (100–500 users)

Consider a co-managed model if you have internal IT staff, or a fully managed plan with a dedicated account team if you do not. At this scale, strategic alignment matters - your provider should be contributing to IT roadmaps, budgeting, and technology selection, not just keeping the lights on.

A managed IT provider at this level should also be advising on cloud strategy, cybersecurity posture, and compliance readiness.

Budget expectation: R 400–1 000 per user per month (economies of scale start to apply).

Questions to ask every provider

Before you sign, get clear answers to these:

1. What does your onboarding process look like? A good provider will audit your environment, document everything, and create a transition plan. Expect onboarding to take two to six weeks.
2. Who will be our primary contact? You want a named account manager or service delivery manager, not a rotating cast of strangers.
3. How do you handle after-hours emergencies? Understand the escalation path and any additional costs.
4. What tools do you use? RMM, ticketing, documentation, and security platforms should all be enterprise-grade.
5. Can you provide references from businesses similar to ours? Industry relevance matters. A provider experienced in retail has different strengths from one focused on professional services.
6. What is your exit process? If the relationship does not work out, how is the handover managed? Ensure your data and documentation are always accessible to you.

Avoiding common mistakes

• Choosing on price alone. The cheapest provider is almost never the best value. Low fees often mean thin staffing, slow response, and minimal proactive work.
• Ignoring cultural fit. Your provider’s team will interact with your staff daily. Communication style, responsiveness, and professionalism matter.
• Not defining success metrics. Agree upfront on what good looks like - SLA targets, user satisfaction scores, system uptime percentages - and hold both sides accountable.
• Signing a long contract without a trial. A three-month pilot or a contract with a 60-day exit clause protects you while the relationship is new.

Moving forward

The right IT support plan removes friction, reduces risk, and frees your team to focus on the work that generates revenue. Whether you are outgrowing break-fix, evaluating managed providers, or looking to augment your internal team, the key is to match the model to your reality - not to where you were two years ago.

Contact us to discuss which support model fits your business. We will start with an honest assessment of your environment and recommend a plan that makes sense for your size, industry, and ambitions.