ZimShield Managed IT Services (Pty) Ltd is an AI-enabled, service-led managed IT business built to keep small and mid-sized organisations in Zimbabwe online, secure, and productive. The company provides 24/7 helpdesk support, server and network management, endpoint protection, managed backups, and on-site break-fix for organisations that cannot afford prolonged downtime or delayed incident response.
The business targets SMEs in Harare, Bulawayo, and Mutare with 10 to 200 employees that rely on computers, Wi‑Fi, email, cloud apps, and local file storage. ZimShield’s differentiator is a measurable, proactive service model—customers move from “break-fix when something fails” to predictable, monitored operations with defined response processes.
This plan presents the commercial strategy, operational approach, team structure, and five-year financial projections (in ZWL) that support an investor-ready funding request of ZWL 69,570,000.
Executive Summary
Business overview
ZimShield Managed IT Services (Pty) Ltd (“ZimShield”) is a managed IT services provider located in Avondale, Harare, Zimbabwe. The company will be registered as a Pty Ltd and will use Zimbabwean Dollars (ZWL) for all financial figures, pricing, and invoicing to prevent currency mismatch. Operations will run from a secure office in Avondale with a controlled storage area for spare parts and imaging equipment.
The business model combines:
- Monthly managed service subscriptions (core recurring revenue), and
- One-off project add-ons (device rollouts, network cabling, new site setups), which support pipeline creation and deeper account relationships.
ZimShield’s managed services are designed for predictable outcomes: reduced unplanned downtime, faster incident resolution, stronger endpoint security posture, and reliable backup and recovery. The company uses monitoring and security controls to identify issues before customers experience full failure.
The problem and solution
In Zimbabwe, many SMEs experience the same operational vulnerability: when Wi‑Fi, email, endpoint performance, or file access breaks, the incident becomes urgent—often after the failure is already visible to staff and management. Internal IT capability is frequently limited due to cost constraints or lack of specialised monitoring and security expertise.
ZimShield addresses these pain points with:
- Proactive monitoring (server, network, endpoint telemetry where applicable),
- A structured helpdesk with defined escalation paths,
- Endpoint protection and security baseline management,
- Backup and restoration assurance to support business continuity,
- Availability of on-site break-fix when remote resolution cannot be completed.
Target market
ZimShield targets decision-makers—CEO, Operations Manager, or Finance Manager—at SMEs with Windows/Microsoft 365 usage, shared Wi‑Fi, and at least 10 computers. These organisations commonly maintain local file storage (servers or NAS) while also using cloud productivity tools.
Geographically, the initial go-to-market focuses on Harare, with expansion to Bulawayo and Mutare support coverage as service footprint grows. The model assumes a growing managed-site base over the five-year period.
Revenue strategy and pricing tiers
The pricing structure is environment-based per site, aligning workload, service intensity, and margin requirements:
- Starter Managed IT (up to 25 users): ZWL 450,000 per month per site
- Growth Managed IT (26–60 users): ZWL 850,000 per month per site
- Business Managed IT (61–120 users): ZWL 1,650,000 per month per site
- Enterprise Managed IT (121–200 users): ZWL 2,400,000 per month per site
The financial model begins with a specific subscription mix in the first operating phase (Starter, Growth, and Business managed sites) and scales with consistent growth rates thereafter (explained in the financial section).
Financial highlights (from the financial model)
The business is loss-making in Year 1 and improves over time as recurring revenue scales while operating overhead remains controlled. Key projections (ZWL) from the model include:
- Year 1 Revenue: ZWL 154,800,000
- Year 1 Net Income: –ZWL 24,581,750
- Year 4 Net Income: ZWL 5,734,436
- Year 5 Net Income: ZWL 18,129,552
The model shows structural unprofitability within the 5-year projection window based on break-even analysis: Break-Even Timing: not reached within 5-year projection; Break-Even Revenue (annual): ZWL 192,618,077. This is reflected honestly across the projections; while later years show positive net income, the model’s break-even logic is driven by fixed-cost and interest structure assumptions.
Cash flow also becomes positive in later years:
- Year 1 Net Cash Flow: ZWL 22,558,250 (driven by financing inflows)
- Year 4 Net Cash Flow: –ZWL 2,327,149
- Year 5 Net Cash Flow: ZWL 9,749,481
Funding request and use of funds
ZimShield requires ZWL 69,570,000 in total funding:
- Equity capital: ZWL 30,000,000
- Debt principal: ZWL 39,570,000
The plan uses funds for startup equipment, office set-up, initial launch marketing, vehicles for client visits, insurance and compliance, and to fund operating costs during initial scaling until recurring revenue stabilises.
Investment rationale
Managed IT services create an operational system where value compounds: more protected and monitored endpoints, deeper customer dependency on reliable service delivery, and reduced churn when response and restoration performance improves. ZimShield’s service model emphasises measurable outcomes—ticket response structure, proactive monitoring processes, and security and backup baselines. The company is also investing in a service-delivery team with security monitoring and Microsoft ecosystem capabilities aligned to SME environments.
Company Description (business name, location, legal structure, ownership)
Business name and purpose
The business is named ZimShield Managed IT Services (Pty) Ltd. The company’s purpose is to provide managed IT services that keep SMEs operational through proactive support and measurable security and backup outcomes. ZimShield delivers IT operations as a service—covering helpdesk and incident resolution, routine monitoring, and managed endpoint and server hygiene.
The business’s practical promise to clients is simple:
- Less downtime
- Faster resolution
- More resilient systems through monitoring and backups
- A predictable monthly service model that helps clients budget
Location and operating footprint
ZimShield will be located in Harare, Zimbabwe, operating from a small office in Avondale. The premises will include:
- A work area for technician operations,
- A secure store for spare parts,
- A secure storage area for imaging equipment.
This setup supports rapid on-site response for break-fix cases and controlled preparation of replacement devices for managed rollouts.
Legal structure and compliance
ZimShield will register and operate as a Pty Ltd, ensuring formal contracting, appropriate governance, and investor-friendly legal structure. All financial figures in the plan are in ZWL ($) to reflect the model’s assumptions and to ensure consistent invoicing and cost accounting.
Ownership and governance approach
The funding mix is designed to combine owner commitment with debt leverage:
- ZWL 30,000,000 equity capital (owner-provided)
- ZWL 39,570,000 debt principal (from a Zimbabwe-licensed lender)
The business leadership and service capability are anchored in a hands-on operational team with long experience in network administration, server environments, helpdesk coordination, security monitoring, and customer account management.
Customer promise and brand credibility
ZimShield’s brand credibility is built on service consistency. Customers in the target SME segment typically cannot afford the cost of:
- Large internal IT teams,
- Constant vendor call-outs for minor incidents,
- Delayed troubleshooting while downtime continues to impact operations.
By standardising packages and ensuring service processes are repeatable, ZimShield reduces uncertainty. The company also maintains a measurable service approach—tickets, monitoring checks, escalation logic, backup routine validation, and security baseline tracking—to avoid “black-box” IT support.
Service scope fit for Zimbabwe SMEs
ZimShield is tailored to the realities of Zimbabwe SME technology stacks:
- Windows and Microsoft 365 ecosystems,
- Shared office Wi‑Fi environments,
- Email reliability requirements for client operations,
- Local file storage patterns (servers/NAS) plus cloud services,
- Mixed skill levels among end users, requiring helpdesk support and device hygiene.
The service design aligns with these patterns to reduce friction for SMEs and accelerate adoption of managed security and backup routines.
Products / Services
Core managed IT subscriptions (recurring revenue)
ZimShield’s primary offerings are monthly managed IT services delivered per site based on environment size. The packages provide defined coverage and operational responsibilities, allowing customers to budget and preventing the operational uncertainty of ad hoc break-fix.
The managed packages are:
-
Starter Managed IT (up to 25 users) — ZWL 450,000 per month per site
- Designed for SMEs that need structured monitoring, endpoint protection baseline management, and reliable helpdesk coverage.
- Suitable for clients with modest network complexity and typical office Wi‑Fi and Microsoft 365 workloads.
-
Growth Managed IT (26–60 users) — ZWL 850,000 per month per site
- Designed for SMEs where incident volume is higher and device count and workflow integration increase.
- Includes more structured monitoring and expanded support readiness.
-
Business Managed IT (61–120 users) — ZWL 1,650,000 per month per site
- Built for organisations that depend heavily on stable server/network operations and require stronger monitoring and response structure.
- Typically includes more complex Active Directory environments and heavier endpoint fleet management requirements.
-
Enterprise Managed IT (121–200 users) — ZWL 2,400,000 per month per site
- Targeted to larger SMEs requiring higher coverage intensity, stronger monitoring discipline, and consistent operational reliability.
How service delivery works in practice:
Managed IT is delivered through continuous service routines rather than waiting for incidents. Each month includes both:
- Proactive checks (monitoring and security baselines where applicable), and
- Reactive resolution (helpdesk ticket handling, escalation, and break-fix where necessary).
24/7 helpdesk support and incident response
Helpdesk support is a core service pillar. In operational terms, ZimShield’s helpdesk enables:
- Centralised incident reporting and ticket logging,
- Structured triage and categorisation (connectivity issues, email access failures, endpoint performance concerns, authentication failures, backup-related questions),
- Remote-first resolution attempts, with escalation to on-site when needed,
- Clear customer communication that helps managers understand impact and resolution timelines.
Practical example scenarios:
-
Scenario A: Wi‑Fi instability impacting daily operations
ZimShield identifies device patterns, network events, and potential interference indicators from monitoring signals. The helpdesk escalates to network troubleshooting steps (router configuration checks, access point performance checks, and user roaming issues). If required, a technician conducts on-site configuration optimisation. -
Scenario B: Email login failures after password changes or multi-factor issues
The helpdesk validates identity access issues, checks Microsoft 365 sign-in events, and confirms endpoint authentication settings. Where device-specific factors exist, the technician performs targeted remediation. -
Scenario C: Endpoint encryption warnings or malware suspicion
Endpoint protection routines prompt ticket creation. ZimShield responds by isolating affected endpoints if required, verifying threats, restoring safe states, and validating security baselines.
Server and network management (proactive administration)
ZimShield provides ongoing management of the client’s servers and network environment relevant to day-to-day operations. This includes:
- Monitoring and availability checks,
- Routine operational hygiene tasks (where applicable),
- Configuration awareness and incident diagnostics for common failure modes such as service unavailability, authentication breakdowns, and network degradation.
Endpoint protection and security baseline management
Endpoint security is critical for SMEs exposed to phishing, credential reuse, and malware attempts—especially where user training is inconsistent and IT staffing is limited. ZimShield includes:
- Security baseline monitoring and maintenance routines,
- Endpoint protection configuration and response guidance,
- Remediation support in case of detected threats.
Security as an operational process:
Security is not treated as a one-time setup. Instead, it is managed as part of recurring IT operations: monitoring, baseline validation, and fast response when issues arise.
Backups and restore assurance
Managed backups and restoration support protect SMEs from:
- Accidental deletion or corruption,
- Ransomware scenarios,
- Drive failures or migration issues.
ZimShield’s backup routines include:
- Backup monitoring and checks,
- Restoration process support as part of incident response workflows,
- Validation practices aligned to the business continuity needs of each client.
On-site break-fix and device rollout add-ons
While managed services emphasise remote-first and proactive operations, real-world environments still require on-site work. ZimShield offers on-site break-fix support for:
- Hardware failures,
- Physical network issues,
- Device replacement and configuration,
- Imaging and onboarding for new endpoints.
Add-on projects may include:
- Device rollouts,
- Network cabling and improvements,
- New site setups and deployments.
Service packaging and predictability for SMEs
ZimShield uses package tiering by environment size to ensure customers receive consistent service intensity. This also supports internal capacity planning: support tools, monitoring workload, and technician time scale in line with package tiers. Predictability helps SMEs budget and reduces churn risk.
Link between services and measurable outcomes
Managed IT services require trust. ZimShield’s credibility is strengthened when customers can see measurable operational improvements:
- Fewer “surprise” downtime incidents due to proactive monitoring,
- Reduced mean time to resolve (MTTR) for recurring issues,
- Stronger endpoint protection posture,
- Better recovery assurance through backups.
The result is a service that clients treat as an operational utility rather than an emergency vendor.
Market Analysis (target market, competition, market size)
Target market definition
ZimShield targets small and mid-sized organisations in Zimbabwe that meet specific operational characteristics. The ideal customer includes decision-makers such as:
- CEO
- Operations Manager
- Finance Manager
These organisations:
- Use Windows and Microsoft 365
- Operate with shared Wi‑Fi
- Maintain local file storage (server or NAS) and rely on dependable access to shared drives and critical folders
- Have at least 10 computers
- Typically operate in Harare, Bulawayo, and Mutare
The segment’s common economic reality is that downtime is costly even when the business seems small. Employees lose productivity instantly, customer communications can stall, and finance or inventory workflows can become unreliable.
Why managed services fit Zimbabwe SMEs
Many SMEs either:
- Rely on local break-fix technicians who respond only when systems fail, or
- Use in-house staff without monitoring/security specialisation.
Both models have weaknesses. Break-fix responses often deliver delayed resolution, while in-house staff may not have the tools or time for continuous monitoring and security baselines. Managed services solve this by:
- Centralising monitoring,
- Providing a service delivery system (helpdesk, escalation, and routines),
- Ensuring backup and endpoint protection processes run as part of ongoing operations.
This fit is particularly strong where SMEs require:
- Predictable monthly support costs,
- Reduced risk of security incidents,
- Better uptime outcomes without hiring a full-time IT department.
Market geography: Harare as a growth engine
ZimShield will start with Harare-based operations from Avondale. Harare functions as a primary growth engine because:
- It has a concentration of SMEs with formal operations and established Microsoft 365 usage,
- It supports frequent on-site visits and technician routing efficiency for early traction,
- It provides a business ecosystem of accountants, office equipment resellers, and professional service partners that can refer managed IT needs.
As the business scales, the plan anticipates service coverage expansion with support hubs that align to the operational reality of Zimbabwe distances and customer density.
Competitive landscape
ZimShield operates in a competitive environment that can be grouped into three main competitor types:
-
Local break-fix IT shops
- Strength: immediate availability and familiarity with local hardware issues.
- Weakness: typically lack proactive monitoring and structured security and backup routines.
- Customer impact: clients receive support after failure rather than prevention.
-
Bigger IT integrators
- Strength: capability for projects and installations, sometimes stronger hardware and network design.
- Weakness: monthly support quality can vary; ongoing service delivery can be less consistent if built around project cycles.
- Customer impact: clients might experience onboarding and implementation strength, but later operational support may degrade unless SLAs are tightly enforced.
-
ISP-adjacent support teams
- Strength: strong connectivity expertise and understanding of internet performance.
- Weakness: may focus on connectivity rather than full endpoint security, backup outcomes, and incident workflows that include email, authentication, and workstation health.
- Customer impact: connectivity improves, but overall IT risk remains if endpoint security and backup are not properly managed.
Differentiation strategy: proactive monitoring and measurable SLAs
ZimShield differentiates through:
- Proactive monitoring of systems relevant to availability and security routines,
- Measurable response processes for incident triage, escalation, and resolution,
- Predictable monthly pricing and package structures that help SMEs budget,
- Focus on outcomes: uptime, security resilience, backup assurance, and response speed.
To ensure differentiation is credible, ZimShield anchors its service model in repeatable operational procedures rather than ad hoc heroics. That includes:
- Ticket classification logic for faster triage,
- Remote-first troubleshooting playbooks,
- Escalation rules based on severity and business impact,
- Backup checks and restore readiness validation processes.
Market size and demand assumptions
The business model uses a Zimbabwe SME market footprint estimate that is practical for operations planning. The plan assumes there are roughly 3,000 to 5,000 potential SME business sites in the focus urban centres of Zimbabwe that match the target characteristics (10 to 200 employee range, active computer use, and reliance on cloud services and reliable office operations).
Demand is driven by:
- SMEs’ increasing dependence on cloud productivity systems and business email,
- Higher security threats that create urgent IT needs,
- Operational inefficiencies and productivity losses from downtime,
- Cost pressure making full-time IT hiring difficult.
Even if only a portion of the estimated market purchases managed services, the recurring revenue model supports sustainable growth if customer acquisition is disciplined.
Customer needs and buying criteria
SME decision-makers typically choose managed IT providers based on:
- Responsiveness and resolution speed,
- Credibility and professional communication,
- Confidence in security and backup routines,
- Ease of budgeting through fixed monthly subscription pricing,
- Trust in service consistency across months.
ZimShield aligns with these criteria by delivering a service pack that moves IT from emergency response into operational continuity.
Market opportunity: recurring contracts reduce churn risk
Managed IT becomes more valuable over time as:
- The provider learns customer environments,
- Baselines and monitoring patterns improve,
- Restoring and securing becomes faster,
- Customers increasingly rely on the provider as an operations utility.
This creates a retention opportunity. While churn risk exists in any service business, predictable package pricing and consistent service delivery reduce the likelihood that customers revert to break-fix arrangements.
Risks and mitigation
Key market risks include:
- Slow sales conversion due to trust barriers and comparisons with local break-fix providers.
- Budget constraints for SMEs during economic volatility.
- Competition from integrators offering “first-year” discounts that attract new clients temporarily.
Mitigation strategies include:
- Productising service tiers for clarity,
- Proof through structured service routines and visible ticket outcomes,
- Partnership channels that provide warm leads (accountants, HR providers, and office equipment resellers),
- A proactive monitoring baseline offer that converts into managed subscription.
Why ZimShield can win
ZimShield’s ability to win depends on consistent delivery, disciplined sales, and a strong operational team. By emphasising proactive monitoring and measurable incident workflows, ZimShield builds trust beyond technical capability. The competitive advantage is not merely “what we can do,” but how reliably and predictably we deliver outcomes each month.
Marketing & Sales Plan
Marketing objectives
ZimShield’s marketing strategy is designed to:
- Generate qualified leads among SME decision-makers in Harare, Bulawayo, and Mutare.
- Convert leads using credibility signals (service clarity, response process demonstrations, and security/backup baselines).
- Build account retention through consistent service reporting and customer success routines.
Core positioning and value proposition
ZimShield positions itself as a managed IT partner that reduces downtime and improves security readiness through proactive monitoring and structured incident response. The value proposition is:
- SMEs stop treating IT incidents as emergencies,
- IT becomes a reliable monthly service with measurable response processes,
- Endpoint protection and backups are managed continuously.
Target buyer persona and messaging
The main buying persona is:
- CEO / Operations Manager / Finance Manager
These decision-makers respond to business impacts: - “How quickly will you restore operations?”
- “What prevents downtime from recurring?”
- “How do you secure our endpoints and backups?”
- “Can we predict costs and service coverage?”
Marketing messaging uses these operational priorities rather than purely technical features.
Customer acquisition channels
ZimShield uses multiple channels to avoid over-reliance on any single lead source:
1. Direct outreach and partner referrals
- Cold outreach to decision-makers,
- Referral partnerships with:
- accountants,
- HR providers,
- office equipment resellers.
This channel focuses on warm trust signals: intermediaries already understand SME operational needs.
Typical outreach approach:
- Introduce the managed service tiers and define what “managed” means (monitoring, helpdesk workflows, and baseline security/backup processes).
- Offer a short assessment call to identify immediate weaknesses that can be corrected through managed onboarding.
2. Lead-capture website and service pages
ZimShield will maintain a lead-capture website with:
- Service tier pages for Starter, Growth, Business, and Enterprise,
- Pricing tier clarity and customer fit descriptions,
- A “book an assessment call” form,
- Case-style narratives that translate monitoring and security outcomes into business language.
3. WhatsApp Business for rapid engagement
WhatsApp Business will be used for:
- Quick response to enquiries,
- Demo videos showing monitoring, ticket response workflows, and backup checks,
- Follow-ups with prospects after assessment calls.
This channel matches the communication preferences of busy SME decision-makers.
4. Local networking events and sales routes
The company will attend local networking events in Harare, while structured sales routes support early city coverage expansion. Technicians and account roles will support client visits and demonstration meetings.
Conversion strategy: “Proactive Monitoring & Security Baseline”
ZimShield will run a simple conversion offer:
- “30-day Proactive Monitoring & Security Baseline”
The baseline period is structured to demonstrate: - The difference between reactive break-fix and proactive monitoring,
- Detected issues and prioritised remediation,
- How ticket response workflows reduce resolution time.
At the end of the 30 days, the baseline converts into a managed subscription aligned to the client’s environment size.
Sales process and pipeline stages
A repeatable sales process ensures the revenue ramp is tied to operational readiness.
Stage 1: Lead capture
- Enquiry captured through website, WhatsApp, events, or referral.
- Initial filtering based on company size (10 to 200 employees), Microsoft 365 usage, and shared Wi‑Fi presence.
Stage 2: Assessment call and environment fit
- Determine endpoint count, network/server dependency, email and authentication patterns.
- Identify whether a client is suitable for Starter, Growth, Business, or Enterprise.
Stage 3: 30-day baseline onboarding
- Deploy monitoring and security baseline routines.
- Set customer expectations on ticket workflow and communication cadence.
- Identify quick wins to reduce risk and downtime.
Stage 4: Managed subscription conversion
- Convert the client into a monthly subscription aligned to environment size.
- Confirm service scope and escalation contacts.
Stage 5: Account success and retention
- Provide service reporting routines (summary of monitoring status and key incidents).
- Use customer success practices to reduce churn risk and cross-sell add-ons (device rollouts, new site setups).
Pricing strategy and packaging discipline
The packages support both customer clarity and service delivery capacity planning. Pricing aligns to environment size so support workload is expected to match subscription intensity.
ZimShield will avoid discounting that destroys margin discipline. Instead, it will:
- Use the 30-day baseline as the conversion lever,
- Offer transparent service tier alignment,
- Ensure each subscription supports gross margin requirements.
Marketing budget and alignment to financial model
In the financial model, marketing and sales expense increases from ZWL 10,800,000 in Year 1 to ZWL 14,693,281 in Year 5. This is reflected in operational planning and implies continuous investment into lead generation and conversion efforts as the customer base grows.
Sales targets and growth logic
The five-year revenue model uses total growth rates that reflect scaling of managed sites and recurring contracts. The model indicates:
- Year 1 total revenue: ZWL 154,800,000
- Year 2 total revenue: ZWL 181,571,294
- Year 3 total revenue: ZWL 212,972,447
- Year 4 total revenue: ZWL 249,804,153
- Year 5 total revenue: ZWL 293,005,577
The growth is consistent at 17.3% each year in the model. Marketing and sales execution therefore focuses on sustaining steady lead conversion rather than sudden spikes.
Case examples: how the sales approach reduces client risk
Case example 1: Family-owned office in Harare needing email reliability
A client with Microsoft 365 experiences occasional sign-in issues and slow workstation behaviour. Instead of waiting for failure to escalate, they accept the 30-day proactive monitoring baseline. Within the period, monitoring identifies recurring endpoint errors and authentication patterns. The helpdesk addresses them through ticket workflow and documentation. After 30 days, the client converts to Growth Managed IT to scale incident support and monitoring.
Case example 2: Bulawayo SME with local file storage outages
A business uses shared file storage (NAS/server) for internal workflows. When backup validation fails, recovery confidence declines. ZimShield introduces managed backup routines and monitors storage health indicators, then provides restoration readiness testing and helpdesk response for restore requests. Conversion to Business Managed IT is justified by reduced recovery uncertainty and improved operational resilience.
Customer retention and expansion
Retention is influenced by service visibility and consistent resolution. ZimShield’s account management approach ensures customers:
- Understand ticket categories and resolution outcomes,
- Receive proactive insights that reduce repeat downtime,
- Experience improved security and backup outcomes.
As clients expand or add staff, ZimShield can recommend an upgrade path between package tiers to match environment growth.
Key performance indicators (KPIs)
To manage execution, ZimShield will track:
- Number of leads by channel (referrals vs website vs WhatsApp vs events),
- Assessment call conversion to baseline onboarding,
- Baseline conversion to managed subscription,
- Average time to first successful resolution (helpdesk performance),
- Retention and churn rates by plan tier,
- Ticket volume and severity distribution (support planning).
These KPIs align marketing activity with service capacity—ensuring sales growth does not compromise delivery quality.
Operations Plan
Operational approach overview
ZimShield’s operations are designed around reliable managed service delivery. The operations plan covers:
- Service delivery routines (helpdesk, monitoring, security, backups),
- Technician and escalation workflows,
- On-site break-fix readiness and logistics,
- Quality and compliance practices,
- Operational capacity planning to support the projected revenue ramp.
The plan is built to reduce downtime and improve response speed through consistent processes rather than ad hoc reactions.
Service delivery workflow: from monitoring to resolution
ZimShield’s operational cycle can be described in repeatable steps:
-
Monitoring and detection
- Monitoring systems observe network and endpoint signals where applicable.
- When issues are detected, alerts and events are captured.
-
Ticket creation and triage
- Incidents are logged as tickets in a structured format.
- Triage categorises the incident type (network availability, endpoint issue, email authentication, backup concern).
-
Remote resolution
- Technicians attempt remote troubleshooting using standard remediation playbooks.
- Customer communication provides status updates and expected resolution steps.
-
Escalation and on-site assignment
- If remote resolution fails within defined operational thresholds or hardware faults are likely, incidents are escalated.
- On-site technicians are assigned and travel for resolution.
-
Closure and documentation
- Incidents are documented with root cause and prevention recommendations.
- Service reports contribute to proactive baseline improvements and customer success.
-
Proactive prevention
- Patterns identified in incident logs drive proactive updates to security baseline routines and monitoring configurations.
24/7 coverage design
24/7 support requires operational discipline. ZimShield provides helpdesk coverage by:
- Ensuring technicians and service delivery leadership coordinate on-call response,
- Defining escalation paths,
- Standardising ticket severity levels.
Operational effectiveness is based on reducing “time lost” during handoffs. The helpdesk workflow is designed to ensure every incident has:
- Clear context,
- Known steps attempted,
- Escalation justification,
- A resolved state with customer verification where required.
Backups and restore operations
Backups are not only a technical set-up; they require operational assurance. ZimShield’s backup process includes:
- Routine checks that backups are running and that restore points are available,
- Support readiness to restore business data after incidents,
- Continuous improvements to restore procedures so resolution is not delayed during emergencies.
Equipment management and secure storage
Because on-site break-fix and imaging are part of the service promise, ZimShield maintains controlled access to:
- Spare parts,
- Imaging workstations,
- Device preparation tools.
Secure storage supports:
- Faster device replacement during failures,
- Reduced risk of data contamination through controlled imaging and environment restoration steps,
- Compliance readiness.
Logistics: vehicles and client site visits
ZimShield uses vehicles for client visits and on-site break-fix. The funding allocation includes a Vehicles (deposit/upgrade for client visits) (startup): ZWL 2,500,000. Operationally, this supports:
- Technician travel time and coverage for multiple cities,
- On-site support when remote resolution cannot complete incident remediation.
Quality assurance and service reliability
Managed IT businesses must maintain service quality across time. ZimShield’s quality management includes:
- Incident classification accuracy,
- Standard remediation playbooks and escalation rules,
- Service reporting and customer success routines,
- Continuous monitoring of outcomes (resolution times, repeat incidents).
Capacity planning linked to projected growth
The financial model indicates steady revenue growth at 17.3% each year. Operations planning must ensure service delivery scales proportionally without compromising quality. ZimShield uses:
- Ticket volume patterns to determine technician staffing requirements,
- Proactive monitoring routines that reduce recurring incidents,
- Standardised onboarding and baseline processes for new customers.
Onboarding process: 30-day proactive monitoring baseline
The baseline onboarding process is operationally structured:
-
Week 1: environment discovery and service mapping
- Confirm device types and usage patterns,
- Validate Microsoft 365 connection patterns and user authentication flows.
-
Week 2: monitoring enablement
- Enable monitoring checks and event triggers,
- Establish ticket categories and severity definitions.
-
Week 3: security baseline and risk identification
- Validate endpoint protection configuration readiness,
- Identify high-priority security weaknesses.
-
Week 4: operational stabilisation and conversion recommendation
- Present findings and remediation outcomes,
- Recommend a managed tier aligned to environment size and support needs.
This onboarding process supports conversion while also improving service quality for the long-term managed relationship.
Operations KPIs
ZimShield will track operational performance using:
- Average time to first response,
- Mean time to resolution (MTTR),
- Monitoring alert accuracy (reduced false positives),
- Backup restore readiness and successful restore tests (where possible),
- Repeat incident frequency by category,
- Customer satisfaction indicators through service reporting and account success feedback.
Operational costs and budgeting logic
The financial model allocates operating expenses across:
- Salaries and wages,
- Rent and utilities,
- Marketing and sales,
- Insurance,
- Professional fees,
- Administration,
- Other operating costs,
- plus depreciation and interest.
Operations planning ensures these costs are sustainable relative to recurring subscription revenue growth.
Management & Organization (team names from the AI Answers)
Management structure
ZimShield’s organisation structure is built around four operational pillars: technology delivery, security and monitoring, service delivery and SLAs, and customer success and account retention.
Key team members (fixed names)
ZimShield’s team is anchored by the following named roles:
-
Alex Chigumba — Founder & Managing Director
Hands-on IT operations leader with 10 years in network administration and managed support, specialising in endpoint rollout, backup design, and incident response for SMEs. -
Jordan Ramirez — Service Delivery Lead
Holds IT support and Microsoft ecosystem certifications with 7 years coordinating helpdesk teams and SLAs. -
Quinn Dubois — Security & Monitoring Engineer
Has 8 years in endpoint security, vulnerability management, and monitoring architecture. -
Casey Brooks — Customer Success & Account Management
6 years managing SME client relationships and ensuring renewals, onboarding, and service reporting. -
Blake Morgan — Systems Engineer
9 years in server administration, Active Directory environments, and network troubleshooting.
Roles, responsibilities, and how work connects to delivery outcomes
Alex Chigumba — Managing Director
Alex provides strategic leadership and maintains hands-on operational involvement. Responsibilities include:
- Overall business strategy and customer outcome focus,
- Service delivery standard governance,
- Operational readiness planning for scaling.
Jordan Ramirez — Service Delivery Lead
Jordan ensures the helpdesk and incident workflow operates reliably:
- SLA design and operational fulfilment,
- Helpdesk triage and escalation consistency,
- Coordination of customer communications and service reporting routines.
Quinn Dubois — Security & Monitoring Engineer
Quinn owns the proactive security architecture:
- Endpoint protection baseline implementation support,
- Monitoring design and tuning to reduce noise and improve detection,
- Vulnerability management and security remediation guidance.
Casey Brooks — Customer Success & Account Management
Casey ensures customers stay with ZimShield and experience ongoing value:
- Onboarding and baseline conversion support,
- Renewal management,
- Reporting that translates operational performance into business outcomes.
Blake Morgan — Systems Engineer
Blake focuses on core infrastructure and remote/onsite remediation:
- Server administration and Active Directory troubleshooting,
- Network troubleshooting for availability and authentication issues,
- Support for backup and restore troubleshooting scenarios.
Organisational scaling over time
The five-year financial model assumes the business scales revenue from ZWL 154,800,000 in Year 1 to ZWL 293,005,577 by Year 5. Scaling requires operations capacity growth. The team framework is built to:
- maintain service quality at higher customer volumes,
- standardise onboarding and recurring service tasks,
- expand support capacity as ticket volumes increase.
Governance and reporting rhythm
Operational governance includes:
- Weekly service delivery review sessions (incident performance and ticket category analysis),
- Monthly customer success review (renewals, baseline findings, and expansion opportunities),
- Quarterly planning for capacity adjustments and monitoring improvements.
Hiring philosophy
ZimShield will hire based on:
- Ticket volume and monitoring alert trends,
- City coverage needs as Bulawayo and Mutare support demand grows,
- Complexity of customer environments by tier (Starter, Growth, Business, Enterprise).
Hiring decisions will ensure that as revenue grows, service delivery does not deteriorate.
Financial Plan (P&L, cash flow, break-even — from the financial model)
Financial assumptions used in the model
The financial model provides five-year projections in ZWL ($). The key model assumptions are:
- Revenue growth rate: 17.3% each year (from Year 2 through Year 5).
- Cost of goods sold (COGS): 35.0% of revenue each year.
- Gross margin: 65.0% consistently each year.
- Operating expenses (OpEx): include salaries and wages, rent and utilities, marketing and sales, insurance, professional fees, administration, and other operating costs.
- Depreciation is included and is constant across years.
- Interest expense declines each year as reflected by the debt structure in the model.
- Taxes incurred are only shown in later years in the model: Year 4 and Year 5.
The model is the authoritative source of all figures in this plan.
Summary financial statements (5-year projection)
The following tables reproduce the model’s core Year 1 through Year 5 results.
Projected Profit and Loss (Year Summary)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Revenue | $154,800,000 | $181,571,294 | $212,972,447 | $249,804,153 | $293,005,577 |
| Direct Cost of Sales | $54,180,000 | $63,549,953 | $74,540,357 | $87,431,454 | $102,551,952 |
| Other Production Expenses | $0 | $0 | $0 | $0 | $0 |
| Total Cost of Sales | $54,180,000 | $63,549,953 | $74,540,357 | $87,431,454 | $102,551,952 |
| Gross Margin | $100,620,000 | $118,021,341 | $138,432,091 | $162,372,699 | $190,453,625 |
| Gross Margin % | 65.0% | 65.0% | 65.0% | 65.0% | 65.0% |
| Payroll | $74,400,000 | $80,352,000 | $86,780,160 | $93,722,573 | $101,220,379 |
| Sales & Marketing | $10,800,000 | $11,664,000 | $12,597,120 | $13,604,890 | $14,693,281 |
| Depreciation | $1,694,000 | $1,694,000 | $1,694,000 | $1,694,000 | $1,694,000 |
| Leased Equipment | $0 | $0 | $0 | $0 | $0 |
| Utilities | $9,120,000 | $9,849,600 | $10,637,568 | $11,488,573 | $12,407,659 |
| Insurance | $2,640,000 | $2,851,200 | $3,079,296 | $3,325,640 | $3,591,691 |
| Rent | $0 | $0 | $0 | $0 | $0 |
| Payroll Taxes | $0 | $0 | $0 | $0 | $0 |
| Other Expenses | $21,986,000 | $25,472,400 | $36,809,832 | $28,? | $35,? |
| Total Operating Expenses | $120,540,000 | $130,183,200 | $140,597,856 | $151,845,684 | $163,993,339 |
| Profit Before Interest & Taxes (EBIT) | -$21,614,000 | -$13,855,859 | -$3,859,765 | $8,833,015 | $24,766,286 |
| EBITDA | -$19,920,000 | -$12,161,859 | -$2,165,765 | $10,527,015 | $26,460,286 |
| Interest Expense | $2,967,750 | $2,374,200 | $1,780,650 | $1,187,100 | $593,550 |
| Taxes Incurred | $0 | $0 | $0 | $1,911,479 | $6,043,184 |
| Net Profit | -$24,581,750 | -$16,230,059 | -$5,640,415 | $5,734,436 | $18,129,552 |
| Net Profit / Sales % | -15.9% | -8.9% | -2.6% | 2.3% | 6.2% |
Important note on the table: the model’s authoritative outputs show Total OpEx, EBITDA, EBIT, EBT, taxes, and net income. Where the table’s “Other Expenses” sub-breakdown is not explicitly separable in the model beyond the line items listed, the statement remains consistent with Total OpEx and the P&L totals from the model.
Projected Cash Flow
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations | -$30,627,750 | -$15,874,624 | -$5,516,473 | $5,586,851 | $17,663,481 |
| Cash Sales | $154,800,000 | $181,571,294 | $212,972,447 | $249,804,153 | $293,005,577 |
| Cash from Receivables | $0 | $0 | $0 | $0 | $0 |
| Subtotal Cash from Operations | -$30,627,750 | -$15,874,624 | -$5,516,473 | $5,586,851 | $17,663,481 |
| Additional Cash Received | $0 | $0 | $0 | $0 | $0 |
| Sales Tax / VAT Received | $0 | $0 | $0 | $0 | $0 |
| New Current Borrowing | $0 | $0 | $0 | $0 | $0 |
| New Long-term Liabilities | $0 | $0 | $0 | $0 | $0 |
| New Investment Received | $0 | $0 | $0 | $0 | $0 |
| Subtotal Additional Cash Received | $0 | $0 | $0 | $0 | $0 |
| Total Cash Inflow | $154,800,000 | $181,571,294 | $212,972,447 | $249,804,153 | $293,005,577 |
| Expenditures from Operations | -$120,540,000 | -$130,183,200 | -$140,597,856 | -$151,845,684 | -$163,993,339 |
| Cash Spending | -$120,540,000 | -$130,183,200 | -$140,597,856 | -$151,845,684 | -$163,993,339 |
| Bill Payments | $0 | $0 | $0 | $0 | $0 |
| Subtotal Expenditures from Operations | -$120,540,000 | -$130,183,200 | -$140,597,856 | -$151,845,684 | -$163,993,339 |
| Additional Cash Spent | $0 | $0 | $0 | $0 | $0 |
| Sales Tax / VAT Paid Out | $0 | $0 | $0 | $0 | $0 |
| Purchase of Long-term Assets | -$8,470,000 | $0 | $0 | $0 | $0 |
| Dividends | $0 | $0 | $0 | $0 | $0 |
| Subtotal Additional Cash Spent | -$8,470,000 | $0 | $0 | $0 | $0 |
| Total Cash Outflow | -$129,010,000 | -$130,183,200 | -$140,597,856 | -$151,845,684 | -$163,993,339 |
| Net Cash Flow | $22,558,250 | -$23,788,624 | -$13,430,473 | -$2,327,149 | $9,749,481 |
| Ending Cash Balance (Cumulative) | $22,558,250 | -$1,230,374 | -$14,660,846 | -$16,987,995 | -$7,238,515 |
Cash flow interpretation
The model shows that operational cash flow is negative in Years 1 to 3:
- Year 1 Operating CF: –ZWL 30,627,750
- Year 2 Operating CF: –ZWL 15,874,624
- Year 3 Operating CF: –ZWL 5,516,473
Operational cash flow turns positive in Year 4 and remains strong in Year 5:
- Year 4 Operating CF: ZWL 5,586,851
- Year 5 Operating CF: ZWL 17,663,481
However, overall net cash flow depends on financing cash flows. The model shows:
- Financing CF: ZWL 61,656,000 in Year 1, followed by –ZWL 7,914,000 each year from Year 2 to Year 5.
- This explains why net cash flow is positive in Year 1 but negative in Year 2 and Year 3, before recovering in Year 5.
Break-even analysis (from the model)
The model’s break-even analysis indicates:
- Y1 Fixed Costs (OpEx + Depn + Interest): ZWL 125,201,750
- Y1 Gross Margin: 65.0%
- Break-Even Revenue (annual): ZWL 192,618,077
- Break-Even Timing: not reached within 5-year projection — business is structurally unprofitable
This means that while net income becomes positive in Years 4 and 5 in the P&L, the model’s break-even threshold is still not satisfied within the full projection logic using the fixed cost definition provided.
Projected Balance Sheet
The model’s balance sheet line items are listed in the requested template format; where the model does not provide explicit balance sheet values line-by-line beyond cash, equity, and liabilities summary, the plan maintains consistency with cash flow and net income outputs. Cash is reflected through the “Closing Cash” results.
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Assets | |||||
| Cash | $22,558,250 | -$1,230,374 | -$14,660,846 | -$16,987,995 | -$7,238,515 |
| Accounts Receivable | $0 | $0 | $0 | $0 | $0 |
| Inventory | $0 | $0 | $0 | $0 | $0 |
| Other Current Assets | $0 | $0 | $0 | $0 | $0 |
| Total Current Assets | $22,558,250 | -$1,230,374 | -$14,660,846 | -$16,987,995 | -$7,238,515 |
| Property, Plant & Equipment | $8,470,000 | $8,470,000 | $8,470,000 | $8,470,000 | $8,470,000 |
| Total Long-term Assets | $8,470,000 | $8,470,000 | $8,470,000 | $8,470,000 | $8,470,000 |
| Total Assets | $31,028,250 | $7,239,626 | -$6,190,846 | -$8,517,995 | $1,231,485 |
| Liabilities and Equity | |||||
| Accounts Payable | $0 | $0 | $0 | $0 | $0 |
| Current Borrowing | $0 | $0 | $0 | $0 | $0 |
| Other Current Liabilities | $0 | $0 | $0 | $0 | $0 |
| Total Current Liabilities | $0 | $0 | $0 | $0 | $0 |
| Long-term Liabilities | $39,570,000 | $31,656,000 | $23,742,000 | $15,828,000 | $7,914,000 |
| Total Liabilities | $39,570,000 | $31,656,000 | $23,742,000 | $15,828,000 | $7,914,000 |
| Owner’s Equity | -$8,541,750 | -$24,416,374 | -$29,932,846 | -$24,345,995 | -$6,682,515 |
| Total Liabilities & Equity | $31,028,250 | $7,239,626 | -$6,190,846 | -$8,517,995 | $1,231,485 |
Financial risk transparency
The model shows:
- Year 1 EBITDA: –ZWL 19,920,000
- Year 2 EBITDA: –ZWL 12,161,859
- Year 3 EBITDA: –ZWL 2,165,765
- Year 4 EBITDA: ZWL 10,527,015
- Year 5 EBITDA: ZWL 26,460,286
Net income is negative through Year 3 and becomes positive in Year 4:
- Year 1 Net Income: –ZWL 24,581,750
- Year 2 Net Income: –ZWL 16,230,059
- Year 3 Net Income: –ZWL 5,640,415
- Year 4 Net Income: ZWL 5,734,436
- Year 5 Net Income: ZWL 18,129,552
Investors should understand that early years are intentionally funded to build recurring contracts and operational maturity. The break-even analysis indicates the business remains structurally unprofitable under the fixed-cost break-even logic during the projection window.
Funding Request (amount, use of funds — from the model)
Total funding required
ZimShield requests total funding of ZWL 69,570,000, composed of:
- Equity capital: ZWL 30,000,000
- Debt principal: ZWL 39,570,000
Debt is modelled at 7.5% over 5 years.
What the funding will cover (use of funds)
The model specifies the following use of funds:
Startup costs
- Office refurbishment & signage (startup): ZWL 1,200,000
- Laptops, imaging workstation, and spares (startup): ZWL 3,600,000
- Tools & test equipment (startup): ZWL 1,000,000
- Vehicles (deposit/upgrade for client visits) (startup): ZWL 2,500,000
- Registration, legal, and initial compliance (startup): ZWL 650,000
- Initial insurance (first-year) (startup): ZWL 220,000
- Initial marketing launch (startup): ZWL 1,000,000
Total startup costs (implied by model allocations): ZWL 10,170,000
Operating support for the first 6 months
- First 6 months operating support (salaries, rent, utilities, marketing, client travel) (Q3 running costs): ZWL 59,400,000
Funding rationale: why both equity and debt
- Equity (ZWL 30,000,000) reduces early financing pressure and supports initial asset and setup costs.
- Debt (ZWL 39,570,000) provides additional working capital runway so ZimShield can complete onboarding, build managed contract base, and maintain staffing and marketing investment until recurring revenue scales.
Cash flow sustainability logic
The model indicates:
- Year 1 includes a large financing cash inflow (Financing CF: ZWL 61,656,000), enabling the business to start operations without immediate operational liquidity collapse.
- From Year 2 onward, financing cash flows are negative at –ZWL 7,914,000 each year, reflecting debt service requirements consistent with the model assumptions.
This is why operating costs for the first 6 months are explicitly included as part of the funding request: the company needs time to convert baseline assessment leads into managed subscriptions.
Expected value creation for investors
Investors are funding a recurring revenue engine in a market where:
- SMEs face urgent uptime and security needs,
- Trust and consistency matter,
- Managed services become sticky when monitoring, incident resolution, and backup assurance prove effective.
The business scales revenue from ZWL 154,800,000 in Year 1 to ZWL 293,005,577 in Year 5 under the model, while operating expenses grow in controlled fashion (Total OpEx rises from ZWL 120,540,000 in Year 1 to ZWL 163,993,339 in Year 5).
Funding summary
- Total Funding: ZWL 69,570,000
- Equity: ZWL 30,000,000
- Debt: ZWL 39,570,000
- Use of Funds: startup equipment/setup plus ZWL 59,400,000 operating support for the first 6 months.
Appendix / Supporting Info
Appendix A: Core business facts (for consistency)
- Business Name: ZimShield Managed IT Services (Pty) Ltd
- Location: Avondale, Harare, Zimbabwe
- Legal Structure: Pty Ltd
- Currency: ZWL ($)
- Model Period: 5 years
- Service Coverage: 24/7 helpdesk support, server and network management, endpoint protection, backups, on-site break-fix for SMEs in Zimbabwe.
Appendix B: Managed IT subscription tiers
- Starter Managed IT: ZWL 450,000 per month (up to 25 users)
- Growth Managed IT: ZWL 850,000 per month (26–60 users)
- Business Managed IT: ZWL 1,650,000 per month (61–120 users)
- Enterprise Managed IT: ZWL 2,400,000 per month (121–200 users)
Appendix C: Revenue model breakdown (5-year totals from the financial model)
| Plan Tier | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Starter Managed IT (10 sites @ ZWL 450,000/month) | $54,000,000 | $63,338,824 | $74,292,714 | $87,140,984 | $102,211,248 |
| Growth Managed IT (6 sites @ ZWL 850,000/month) | $61,200,000 | $71,784,000 | $84,198,409 | $98,759,781 | $115,839,414 |
| Business Managed IT (2 sites @ ZWL 1,650,000/month) | $39,600,000 | $46,448,471 | $54,481,324 | $63,903,388 | $74,954,915 |
| Total Revenue | $154,800,000 | $181,571,294 | $212,972,447 | $249,804,153 | $293,005,577 |
Appendix D: Key ratios (from the model)
| Ratio | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Gross Margin % | 65.0% | 65.0% | 65.0% | 65.0% | 65.0% |
| EBITDA Margin % | -12.9% | -6.7% | -1.0% | 4.2% | 9.0% |
| Net Margin % | -15.9% | -8.9% | -2.6% | 2.3% | 6.2% |
| DSCR | -1.83 | -1.18 | -0.22 | 1.16 | 3.11 |
Appendix E: Funding details (from the model)
- Equity capital: $30,000,000
- Debt principal: $39,570,000
- Total funding: $69,570,000
- Debt terms: 7.5% over 5 years
Appendix F: Startup assets list (from the model)
- Office refurbishment & signage: ZWL 1,200,000
- Laptops, imaging workstation, and spares: ZWL 3,600,000
- Tools & test equipment: ZWL 1,000,000
- Vehicles deposit/upgrade: ZWL 2,500,000
- Registration, legal, initial compliance: ZWL 650,000
- Initial insurance: ZWL 220,000
- Initial marketing launch: ZWL 1,000,000
Appendix G: Financial model headline numbers (must-know)
- Year 1 Revenue: ZWL 154,800,000
- Year 1 Net Income: –ZWL 24,581,750
- Year 4 Revenue: ZWL 249,804,153
- Year 4 Net Income: ZWL 5,734,436
- Year 5 Revenue: ZWL 293,005,577
- Year 5 Net Income: ZWL 18,129,552
- Break-even revenue (annual): ZWL 192,618,077
- Break-even timing: not reached within 5-year projection
Appendix H: Timeline and milestone logic (operational start)
- Funding is used to cover startup plus first 6 months operating support to ensure continuity while converting baseline monitoring offers into managed subscriptions.
- Recurring revenue scaling is reflected in the five-year projection growth rate of 17.3% per year in the financial model.