Managed IT services provide small-to-mid sized organizations with predictable technology operations, proactive cybersecurity, and reliable support—without needing an in-house IT team to manage uptime, patching, backups, and incident response. In Zambia, where many businesses still rely on reactive “break-fix” support and have uneven security maturity, a managed model can materially reduce downtime risk and ransomware exposure while improving operational efficiency.
This business plan outlines Lusaka Shield Managed Services, a private limited company (Ltd) based in Lusaka, Zambia, delivering managed IT and cybersecurity services across Greater Lusaka. The plan uses a 5-year financial projection model in ZMW (Zambian Kwacha) as the source of truth for revenues, expenses, cash flows, funding, and break-even dynamics.
While growth is projected over five years, the model indicates the company is structurally unprofitable within the 5-year projection window, with negative net income in Years 1–4 and a modestly positive net income in Year 5. The operational strategy therefore emphasizes service quality, retention, controlled cost scaling, and disciplined onboarding—while the funding request is designed to sustain early traction and cash flow stability.
Executive Summary
Lusaka Shield Managed Services is a managed IT services and cybersecurity provider for small-to-mid sized businesses in Lusaka, Zambia and the broader Greater Lusaka market. The business solves a persistent operational and security problem: many organizations experience expensive downtime, inconsistent IT support, and insufficient protection against ransomware and account compromise because they lack internal capabilities or rely on ad-hoc repair vendors. Lusaka Shield Managed Services offers a subscription-based managed model with clear service scopes: endpoint protection, patch management, ticket-based support with structured reporting, backup monitoring and restore assurance (where applicable), and security hardening activities such as vulnerability management and incident readiness support.
The company is incorporated and operated as a private limited company (Ltd) under Zambian registration. The business is owned by the founder, Nicolas Hove, who brings 12 years of finance and operations experience and will oversee strategy, pricing discipline, and financial governance. Operational delivery and escalation paths are led by a management team with relevant IT operations, cybersecurity, customer success, and field engineering expertise, specifically Quinn Dubois (Head of Managed Services Operations), Skyler Park (Cybersecurity Lead), Morgan Kim (Service Desk & Customer Success Manager), and Riley Thompson (Field Engineering Lead).
Revenue is generated through monthly managed service subscriptions across three packaged tiers—Essentials, Growth, and SecurePro—and complemented by onboarding and security add-ons delivered as part of the controlled implementation process. The financial model projects total revenue rising from ZMW 8,700,000 in Year 1 to ZMW 18,040,320 in Year 5, growing at 20.0% each year. The model assumes a 68.0% gross margin on managed subscriptions and includes operating costs (salaries, rent and utilities, marketing and sales, insurance, administration, and other operating costs) that scale as revenue increases.
The model also shows material early-stage losses: EBITDA is negative in Years 1–3 and turns positive only by Year 5. Specifically, the model estimates Net Income of -ZMW 2,907,000 in Year 1, -ZMW 2,338,080 in Year 2, -ZMW 1,584,782 in Year 3, -ZMW 603,960 in Year 4, and ZMW 492,499 in Year 5. Cash flow is supported through a combination of equity and debt financing and by the timing of cash flows relative to operating costs and capex.
To enable launch, tooling, and early traction, Lusaka Shield Managed Services requests ZMW 3,800,000 total funding, sourced as ZMW 1,200,000 equity and ZMW 2,600,000 debt principal. The model allocates uses of funds to the required startup equipment and setup, including endpoint imaging kit, networking gear, servers and monitoring hardware, security tool setup, branding and initial sales collateral, registration and compliance registration, office outfitting, initial marketing launch, contingency, and a startup-to-launch operating buffer of ZMW 1,490,000 to sustain early customer acquisition momentum.
The plan’s investment logic is not based on immediate profitability but on building a durable recurring revenue base, improving service margins through standardized onboarding and controlled delivery, and reaching operational scale where retention and recurring support revenue can reduce per-customer servicing costs. However, the break-even analysis within the model states break-even is not reached within the 5-year projection, with Break-Even Revenue (annual) of ZMW 12,975,000 and Break-Even Timing: not reached within 5-year projection.
This plan is designed for submission-ready clarity: it describes the service proposition, Zambian market needs, competitive positioning, go-to-market approach, operating processes, management structure, and a full set of 5-year financial statements and supporting schedules aligned to the model’s figures.
Company Description
Business name, location, and legal structure
Business name: Lusaka Shield Managed Services
Location (HQ and operational base): Lusaka, Zambia
Legal structure: Private limited company (Ltd)
Operational coverage focus: Greater Lusaka, with scalable delivery for additional Lusaka-based business districts and nearby areas where travel and support response times remain feasible.
As a Zambian Ltd, Lusaka Shield Managed Services is structured to provide clear governance, contractual capability with business customers, and a professional compliance posture. The company’s operational model is built around recurring service subscriptions and standardized service delivery—features that support predictable revenue, structured support workflows, and auditable reporting.
Ownership
Founder/Owner: Nicolas Hove
Role in company: Founder/Owner with responsibilities spanning strategy, pricing discipline, financial governance, and oversight of scaling decisions.
The investment structure in the financial model reflects equity capital of ZMW 1,200,000 and debt principal of ZMW 2,600,000, totaling ZMW 3,800,000. Ownership governance and financial discipline are therefore central to managing early cash flow volatility and ensuring financing terms remain within the operational capacity of the business.
Mission and value proposition
Lusaka Shield Managed Services exists to reduce technology risk and operational disruptions for SMEs across Zambia by delivering managed IT operations and cybersecurity practices as a consistent monthly service. The value proposition is defined through service scope clarity and measurable outputs:
- Uptime assurance through proactive monitoring of systems and endpoints
- Security hardening and reduced ransomware risk through endpoint protection and vulnerability management activities
- Structured patch and change management to reduce exploitability and configuration drift
- Backups that are monitored and prepared for restore workflows
- Customer support with defined ticketing workflows, escalation criteria, and recurring reporting
For clients, managed services convert unpredictable cost events (emergency repairs, downtime losses, and security incidents) into predictable subscription costs. For the provider, the managed model builds recurring revenue and long-term customer relationships, which is essential for scaling support capacity efficiently.
Target customer profile and purchase drivers
The intended customer segment is organizations with roughly 25–200 employees, typical of SMEs across categories such as logistics, clinics, schools, retail groups, real estate firms, and medium-sized manufacturers. Although customer size varies, the core purchase drivers are consistent:
- Downtime is expensive: operational interruption affects sales, appointments, learning schedules, inventory, and service delivery.
- Security threats are rising: ransomware and phishing incidents increasingly target organizations with insufficient security processes.
- Internal IT capacity is often limited: even where staff exist, they may not have enough time for proactive patching, monitoring, and security operations.
- Need for accountability: business owners want reporting and a reliable escalation path—not ad-hoc “fix it when it breaks” support.
Strategic positioning
The strategic positioning of Lusaka Shield Managed Services in Zambia is to operate between “break-fix IT” providers and large enterprise integrators. Large integrators may be too slow or too expensive for SMEs, while break-fix vendors typically lack managed visibility and recurring improvement loops. Lusaka Shield Managed Services differentiates through:
- True monthly management with clear service scope
- Proactive monitoring and documented reporting
- Standardized onboarding to improve security posture quickly, typically within the first 14–21 days in client environments (as described in the service narrative)
- SLA-based support structure that reduces ambiguity for clients
This positioning is particularly relevant in Lusaka where business density supports recurring contract acquisition and where response logistics allow field engineering coverage aligned to managed service obligations.
Products / Services
Lusaka Shield Managed Services offers managed IT services and cybersecurity delivered as recurring subscriptions. The company’s product architecture is designed to be simple for buyers while allowing the firm to standardize delivery, control tool costs, and maintain service margins.
Service packaging approach
Managed service packages are organized in three tiers:
- Essentials (ZMW 8,500 per site per month)
- Growth (ZMW 15,500 per site per month)
- SecurePro (ZMW 26,500 per site per month)
Each tier expands capabilities in a controlled way, enabling customers to select a package aligned to their security maturity, endpoint count, and operational risk tolerance.
Important operational principle: customers are onboarded with standardized processes so that the service outputs (monitoring coverage, patching schedules, ticket workflows, and reporting artifacts) are delivered consistently across the portfolio. This consistency is crucial to scale service delivery without proportional increases in effort.
Essentials: Managed baseline
Essentials (ZMW 8,500 per site per month) is the entry package designed for organizations that need reliable day-to-day IT operations and baseline security management. Essentials includes:
- Managed endpoint protection (up to 20 endpoints)
- Patch management
- Ticket support (up to 40 tickets/month)
- Monthly reporting
- Basic backup monitoring
What this means in practice (examples):
- When an endpoint experiences suspicious activity, the client receives management action through the endpoint protection console and support workflows.
- When critical patches are released, patch management cycles reduce vulnerability windows and lower exposure to common exploits.
- Monthly reporting consolidates operational health indicators such as patch status, incident notes, and backup monitoring status so leadership can understand what was done and what remains.
Essentials is designed to reduce the client’s operational burden by centralizing routine IT tasks.
Growth: Proactive resilience and expanded coverage
Growth (ZMW 15,500 per site per month) includes everything in Essentials plus expanded capabilities:
- Expanded endpoint coverage (up to 45 endpoints)
- Advanced backup management (tested restores)
- Vulnerability scanning
- Priority support
Practical implementation examples:
- Vulnerability scanning identifies weakness patterns (for example, outdated application versions or misconfigurations) that may not be visible to a non-specialist IT manager.
- Advanced backup management with tested restores reduces the risk that backups exist but fail when recovery is needed.
- Priority support reduces response time expectations for operationally critical incidents such as email disruptions, authentication failures, and rapid restoration needs.
Growth fits organizations moving from “respond to issues” behavior toward proactive security management.
SecurePro: Incident readiness and stronger security posture
SecurePro (ZMW 26,500 per site per month) is designed for organizations with higher risk exposure or greater compliance expectations. It includes:
- Growth capabilities
- EDR/response hardening
- Managed firewall services
- Phishing simulations
- Incident readiness support
Examples of client outcomes:
- With EDR/response hardening, endpoints are monitored not just for basic threats but for behavioral indicators that can support faster containment.
- Managed firewall services reduce exposure by applying consistent policies across endpoints and network segments.
- Phishing simulations improve workforce resilience by measuring and training against common social engineering patterns.
- Incident readiness support prepares the client for escalation and response workflows so that a ransomware attempt can be handled with structured decision-making rather than panic-driven improvisation.
SecurePro is typically attractive to organizations with executives who want stronger security outcomes and a measurable security maturity roadmap.
Onboarding timeline and delivery methodology
Lusaka Shield Managed Services emphasizes standardized onboarding so that security improvements occur quickly and predictable delivery reduces onboarding overhead. The onboarding process is structured as follows:
- Discovery and baseline assessment
- Asset and endpoint inventory validation
- Network topology basics
- Identification of current backup status and patch posture
- Account setup and tool onboarding
- Endpoint enrollment
- Monitoring and ticketing integration
- Initial hardening and policy application
- Baseline configurations
- Recommended endpoint policies
- Monitoring go-live
- Establishing alert thresholds
- Confirming ticket routing and escalation
- Early reporting and stabilization
- First reporting cycle
- Corrective actions to align to managed service scope
As described in the founder’s operational framing, customers typically see tangible security improvements within the first 14–21 days after onboarding, depending on environment readiness and endpoint accessibility.
Value-added services (project-based add-ons)
In addition to monthly subscriptions, Lusaka Shield Managed Services can provide project-based add-ons such as:
- Onboarding acceleration for multi-site clients
- Upgrades of endpoints or security tooling
- Security assessments that feed into a prioritized remediation roadmap
- Managed incident response support for clients needing deeper containment assistance beyond routine managed workflows
These add-ons are positioned to be client-funded where appropriate, supporting project profitability without pulling the subscription service model away from standardized recurring delivery.
Market Analysis
Target market definition: Zambia and Greater Lusaka
Zambia’s managed IT and cybersecurity landscape is still evolving. While demand is growing due to increased digitalization, the gap between reactive IT support and proactive managed services remains substantial. Lusaka Shield Managed Services targets customers in Greater Lusaka with profiles that align to managed service economics:
- SMEs with 25–200 employees
- Organizations that depend on stable operations (logistics and distribution, clinics and healthcare admin systems, schools, retail groups, real estate offices, and medium-sized manufacturers)
- Businesses whose internal IT capacity is insufficient for:
- continuous monitoring,
- structured patching,
- backup verification and restore testing,
- endpoint threat management,
- and incident readiness.
The purchase cycle is often driven by the pain of downtime and fear of ransomware incidents, especially after publicized security events or internal incidents. Decision-makers include owners/managers, operations leaders, and sometimes outsourced IT contacts who are influenced by security risk narratives and operational cost control.
Market size and demand logic
The founding narrative estimates roughly 15,000 potential business customers in the Lusaka metro area that fall into the “small-to-mid sized” category where managed services make financial sense. The demand estimate is grounded in the density of SME businesses and the typical IT spend ranges of organizations that are large enough to feel downtime pain but not large enough to run enterprise IT internally.
For modeling relevance, the financial plan assumes a growth trajectory from Year 1 to Year 5 with 20.0% annual revenue growth. This is consistent with a strategy of acquiring and retaining customers while progressively expanding service tiers from Essentials to Growth and SecurePro.
Customer needs and pain points
The market’s need for managed services can be summarized into three interlocking problems:
-
Operational instability
- A single workstation outage can stop billing systems, appointment scheduling, inventory updates, or teacher/student administrative flows.
- Break-fix response is often irregular, meaning businesses cannot plan around IT reliability.
-
Security gaps
- Endpoint security without centralized management is inconsistent.
- Users fall for phishing when training and controls are weak.
- Backups are frequently configured but not tested for restore reliability.
-
Lack of accountability
- Break-fix vendors may provide fixes but not proactive reporting on security posture or performance trends.
- Leadership needs management reporting that translates IT activity into risk reduction.
Managed service subscriptions directly respond to these problems by establishing routine security and operations processes.
Competitive landscape in Lusaka
The founder’s identified competitive threats include:
-
Local break-fix IT shops
- Typically responsive only when systems fail
- Often limited proactive monitoring and reporting
- May not provide consistent security operations
-
Larger IT integrators
- Often more project-based than ongoing managed services
- Can be slower to respond to ongoing issues for SMEs
- May be priced beyond SME budgets for continuous support
-
Telecom-linked IT resellers
- Bundle internet and hardware
- May not fully manage endpoint security or cybersecurity operations
Differentiation strategy: Lusaka Shield Managed Services competes by providing true monthly management with documented reporting and standardized onboarding that improves security posture quickly, typically within 14–21 days.
SWOT analysis (Zambia context)
Strengths
- Structured managed service tiers that align to SME needs
- Proactive monitoring and security hardening as core delivery
- Standardized onboarding reduces per-customer customization overhead
Weaknesses
- Early-stage scale limits service capacity and increases overhead per customer
- Negative operating profitability in the early years per model suggests funding dependence
Opportunities
- Growing cybersecurity awareness among SME leadership
- Increased regulatory and compliance sensitivity in enterprise operations (even if indirect)
- Expansion from Essentials to Growth and SecurePro as customer maturity increases
Threats
- Competitive price pressure from break-fix vendors
- Retention risks if customers perceive onboarding friction or insufficient early improvements
- Economic pressure that limits SMEs’ ability to pay for subscription services
Market adoption considerations and adoption barriers
Managed IT services succeed when customers trust ongoing performance. Barriers include:
- Skepticism that a subscription is “just like paying for support,” rather than proactive risk reduction.
- Uncertainty about service scope: customers fear hidden costs or unclear SLA coverage.
- Implementation friction during onboarding, especially in environments with inconsistent device hygiene or weak endpoint management.
Lusaka Shield Managed Services addresses these with:
- Clear monthly reporting to establish accountability
- Onboarding structure with documented steps and early security improvements
- Service tier clarity so customers can understand what they are buying
- A standardized escalation workflow managed by the service desk function
Service delivery differentiation: from break-fix to managed outcomes
To win market share, the company emphasizes outcome-driven delivery:
- Monitoring reduces mean time to detect (MTTD) by surfacing issues before end-users complain.
- Patch management reduces mean time to remediate (MTTR) by moving from emergency fixes to planned patch cycles.
- Backup monitoring and restore assurance reduces business continuity risk, especially for ransomware events.
- Security hardening and phishing simulations reduce likelihood of credential compromise.
These differentiators support a value narrative that is compelling for SMEs that cannot afford the disruption of security incidents.
Marketing & Sales Plan
Go-to-market objectives
The marketing and sales plan is designed to generate recurring subscription revenue while ensuring onboarding capacity aligns with service quality. The core objectives are:
- Acquire new customers for managed packages (Essentials, Growth, SecurePro)
- Improve retention and increase tier penetration over time
- Convert early onboarding success into referrals and partner-driven leads
- Maintain customer acquisition and marketing spend discipline consistent with the financial model
Marketing spend in the financial model is captured as Marketing and sales within operating expenses:
- Year 1: ZMW 300,000
- Year 2: ZMW 324,000
- Year 3: ZMW 349,920
- Year 4: ZMW 377,914
- Year 5: ZMW 408,147
These figures imply that marketing is managed as a controlled investment with expected lead-to-contract conversion, rather than a hyper-growth approach that would strain service delivery.
Positioning and messaging
Messaging is built around measurable outcomes:
- Reduced downtime risk through monitoring and structured support
- Reduced ransomware risk through endpoint protection, vulnerability scanning, and readiness support
- Predictable costs through monthly subscriptions and documented reporting
For SMEs, the message must also be framed in operational language rather than purely technical terms. For example, leadership understands “we will monitor and patch your endpoints and validate backups” more readily than “we will implement an ITIL-aligned service management framework.” Still, service outcomes should map to formal processes under the hood.
Channels and lead generation strategy
Lusaka Shield Managed Services will use a mix of channels aligned to Zambia’s SME buying behavior:
- Partnership referrals
- Accountants, HR consultants, and business centers who already serve SMEs
- These partners act as trusted intermediaries; their credibility reduces sales friction
- Outbound outreach
- WhatsApp and email outreach to office managers and IT decision-makers in Lusaka
- Short proof elements: service checklists, onboarding steps, and case-style notes
- Website and package pricing
- Live package pricing and onboarding steps
- Monthly content on downtime prevention and ransomware readiness
- Targeted social media ads
- LinkedIn and Facebook ads focused on ransomware readiness and backup reliability
- On-site demonstrations
- Showing monitoring and patching behavior in a prospective client environment during onboarding
These channels are selected because they combine trust building with clear product presentation.
Sales process and funnel design
A structured sales funnel reduces conversion variability and supports accurate pipeline forecasting. The proposed funnel:
- Lead capture
- Incoming leads from website contact forms, referrals, social ads, and outreach
- Qualification call
- Determine endpoint counts, business criticality, and current backup practices
- Package recommendation
- Essentials for baseline managed operations
- Growth for expanded coverage and restore-tested backups
- SecurePro for advanced security readiness and EDR/firewall capabilities
- Discovery and baseline assessment
- Validate environment readiness and identify onboarding effort
- Proposal and onboarding plan
- Provide clear scope, timeline, and deliverables, including expected improvements within the first 14–21 days
- Contracting and onboarding kickoff
- Setup monitoring tools, ticketing integration, and initial hardening
- First reporting cycle
- Use reporting to confirm value and secure renewal and tier upgrade discussions
Customer retention and expansion strategy
Retention is driven by:
- Monthly reporting quality: customers should see progress and operational transparency.
- Ticket response discipline: the service desk’s ticket quality and SLA adherence reduce churn.
- Early wins: initial security improvements within 14–21 days make value visible quickly.
- Tier upgrade pathways: customers who start on Essentials can be moved to Growth or SecurePro based on endpoint growth, security maturity improvements, and incident exposure.
Expansion leverages the managed service foundation: as the customer’s endpoint count and security needs rise, higher tiers become the natural next step.
Pricing strategy alignment with service costs
The service pricing tiers are fixed and communicated as:
- Essentials: ZMW 8,500 per site per month
- Growth: ZMW 15,500 per site per month
- SecurePro: ZMW 26,500 per site per month
The financial model does not break down revenue by tier, but it enforces aggregate unit economics via a 68.0% gross margin assumption across revenue. In practical execution, the marketing and sales team must guide prospects into appropriate tiers to avoid under-scoping service delivery (which would damage margins and capacity).
Sales targets and performance measurement
Because the model is source-of-truth for revenue and cost totals, sales targets in this plan are expressed as performance management milestones rather than additional numeric targets beyond the model. Internally, the company will track:
- Leads by channel (referrals, outbound, ads, website)
- Conversion rate from qualified call to contract
- Time-to-onboarding completion
- Ticket volume and resolution time
- Monthly reporting completion rate
- Retention and tier upgrade rate
These metrics support service quality and cash flow stability. They also align with the operating cost structure in the model, where salaries and wages and administration scale with business operations.
Marketing & Sales Plan risk management
Key risks and mitigations:
- Risk: pipeline volatility
- Mitigation: diversified channels and partnership-driven lead stability
- Risk: onboarding delays
- Mitigation: standardized onboarding steps, pre-kickoff checklists, and field engineering scheduling discipline
- Risk: churn due to unclear scope
- Mitigation: explicit package scope and documented deliverables
- Risk: perceived mismatch between price and value
- Mitigation: strong onboarding outcomes and monthly reporting that ties actions to reduced risk and improved system health
Operations Plan
Operating model overview
Lusaka Shield Managed Services operates a service delivery system that combines remote monitoring, endpoint management, ticket-based support, and periodic field support for installations and remediation. Operations are designed for consistency so that customer experiences are predictable and service outputs remain measurable.
The operations approach is centered on three operational pillars:
- Proactive monitoring and endpoint management
- Structured support and incident workflows
- Standardized onboarding and reporting
This operational design is critical for managed services because revenue is recurring, but delivery effort must remain efficient as customer counts grow.
Service delivery workflow
1) Customer onboarding and setup
Onboarding is executed with defined stages:
- Pre-onboarding readiness check
- Validate endpoint inventory and access
- Identify network restrictions and authentication requirements
- Account enrollment
- Enroll endpoints in monitoring and protection tooling
- Configure alerting thresholds and ticketing routing
- Baseline configuration and hardening
- Apply recommended security policies aligned with service tier
- Validate patch and backup coverage
- Go-live confirmation
- Confirm monitoring visibility
- Confirm backup monitoring status and, where applicable, tested restore approach
2) Daily/weekly operations
Daily operations focus on ensuring endpoints remain healthy and that alerts are triaged.
- Monitoring console reviews
- Ticket generation and routing
- Proactive patch schedule reviews
- Vulnerability scan review cycles (Growth and SecurePro)
- Backup monitoring checks and restore rehearsal scheduling (where applicable)
3) Support and incident response
Support is managed through ticketing:
- Requests and incidents are categorized
- SLA targets are applied by severity
- Escalations are performed to cybersecurity lead or field engineering when required
- Incident readiness activities support faster containment decision-making
Even though specific SLA response times are not numerically specified in the model, the operational system must enforce escalation discipline and quality ticket documentation.
4) Monthly reporting
Monthly reporting is essential for retention and expansion:
- Overview of monitoring status and alerts
- Patch status summary
- Backup monitoring outcomes
- Security posture notes (as tier allows)
- Ticket trends and resolution summaries
- Recommendations for next-month improvements
Monthly reporting strengthens the customer value narrative, reducing churn risk.
Field support and logistics
Managed IT services frequently require physical intervention: installing networking components, replacing hardware, or performing initial onsite configurations. Riley Thompson leads field engineering with 10 years network deployments and onsite troubleshooting experience, including installations for office setups and multi-site rollouts.
Transport and field support are reflected in operating costs within the financial model as Other operating costs and also as a specific budget line in the founder narrative. In the authoritative financial model, the overall categories include:
- Rent and utilities
- Salaries and wages
- Marketing and sales
- Insurance
- Administration
- Other operating costs
Operations will schedule field work in batches aligned with onboarding dates to minimize travel costs and disruption.
Technology stack approach (implementation methodology)
To deliver managed security services, the company relies on security monitoring and endpoint management tooling plus a ticketing system for support workflows. The financial model includes subscription costs in “COGS” and operating expense categories rather than listing specific vendor costs, which supports a simplified investor-ready approach.
Still, the operational plan must ensure tool onboarding and license management are disciplined:
- Ensure endpoint enrollment is consistent across client environments
- Maintain monitoring configuration consistency to reduce false positives
- Document configuration changes and baseline policies
- Maintain security policy version control and change logs
Quality assurance and service governance
Quality assurance must be built into operations to maintain margins and reduce rework:
- Ticket quality checks by service desk manager
- Monitoring alert review standards
- Monthly reporting checklist validation
- Incident post-action documentation
- Customer feedback loops to detect dissatisfaction early
This governance reduces churn risk and protects gross margin by limiting inefficient servicing.
Operational timeline (first 12 months) and capacity planning
Because revenue is projected to grow and the model indicates losses early, operations must focus on controlled scaling:
- Launch and onboard initial customers
- Stabilize delivery processes
- Improve onboarding efficiency
- Expand customer base while maintaining monitoring coverage and response workflows
Capacity planning must account for:
- Service desk staffing needs
- Cybersecurity lead workload for vulnerability and hardening activities
- Field engineering scheduling for onsite tasks
- Tool capacity and alert tuning to prevent overload
The financial model includes rising salaries and wages (Year 1: ZMW 4,320,000 up to Year 5: ZMW 5,877,312) which supports scaling assumptions.
Compliance considerations in operations
While the plan does not cite specific Zambia regulatory references, cybersecurity operations must still adhere to internal compliance principles:
- Access control and least privilege for tool accounts
- Data handling discipline for customer data in tickets and monitoring systems
- Secure backup and restore test procedures where contract scope includes it
- Documented change approvals for policy updates
Compliance readiness also supports customer confidence and improves sales conversion.
Operations Plan continuity: linking to financial performance
The financial model indicates:
- Total revenue increasing annually at 20.0%
- COGS at 32.0% of revenue
- OpEx scaling from ZMW 8,166,000 in Year 1 to ZMW 11,109,753 in Year 5
- Negative EBITDA in Years 1–3 and improved performance by Year 5
Operationally, the company must manage:
- Labor utilization and productivity in support and cybersecurity operations
- COGS drivers such as service delivery tools and direct labor support allocation
- Rent and utilities stability aligned with office footprint needs
- Controlled marketing spend scaling consistent with the model
The operations plan is therefore not only a service delivery narrative; it is a mechanism to align service delivery capacity with financial constraints.
Management & Organization
Organizational structure
Lusaka Shield Managed Services is organized around service delivery and governance. The organization is designed to support managed service operations that require coordinated expertise across IT operations, cybersecurity, customer success, and field engineering, with finance governance oversight.
Core roles:
- Nicolas Hove — Founder/Owner
- Quinn Dubois — Head of Managed Services Operations
- Skyler Park — Cybersecurity Lead
- Morgan Kim — Service Desk & Customer Success Manager
- Riley Thompson — Field Engineering Lead
The model assumes operational staffing and overhead reflected in salaries and wages and administrative cost categories. Staffing is expected to scale gradually as customer base grows from Year 1 to Year 5 under the 20.0% annual revenue growth assumption.
Founder/Owner: Nicolas Hove
Background: Chartered accountant with 12 years of finance and operations experience across SMEs in Zambia; experience in budgeting, procurement controls, and compliance reporting for multi-department teams.
Responsibilities:
- Strategy and pricing discipline to protect gross margin
- Financial governance and performance monitoring against model assumptions
- Capital planning and debt/equity oversight
- Partnering and high-level customer relationship management
In a business model with early losses, governance and cash discipline are critical. Nicolas Hove’s experience supports disciplined decision-making on onboarding prioritization, cost control, and investment pacing.
Head of Managed Services Operations: Quinn Dubois
Background: 9 years in IT operations and systems administration with hands-on experience in monitoring, backup testing, and incident response workflows.
Responsibilities:
- Operational process management and service delivery standards
- Monitoring systems operations and operational KPIs
- Coordination with cybersecurity lead for hardening and vulnerability workflows
- Ensuring ticket workflows and reporting cycles are executed consistently
Quinn’s role reduces service variability and protects operational efficiency, which is essential to maintain margins under recurring service delivery requirements.
Cybersecurity Lead: Skyler Park
Background: 8 years focused on endpoint security, vulnerability management, and security hardening.
Responsibilities:
- Cybersecurity program ownership (EDR hardening, vulnerability management, and phishing simulation coordination where applicable)
- Incident readiness support and cybersecurity escalation handling
- Defining security policy templates and hardening standards by tier
- Training and quality assurance for security-related deliverables
Skyler’s role supports the differentiation of Lusaka Shield Managed Services as a managed cybersecurity provider rather than a purely operational IT support company.
Service Desk & Customer Success Manager: Morgan Kim
Background: 7 years in technical support leadership, specializing in ticket quality, SLA adherence, and customer onboarding.
Responsibilities:
- Ticketing quality and escalation management
- Customer success onboarding coordination and customer communication
- SLA adherence discipline and reporting completeness
- Collecting customer feedback to inform operational improvements
Morgan’s role is central for retention and tier expansion; strong customer success reduces churn and supports referrals.
Field Engineering Lead: Riley Thompson
Background: 10 years in network deployments and on-site troubleshooting, including installations for small business offices and multi-site rollout experience.
Responsibilities:
- Onsite onboarding execution and remediation
- Network equipment deployment and configuration
- Hardware and onsite support coordination to meet managed service requirements
Riley ensures that remote tools and monitoring have the physical foundation and that client environments remain stable.
Staffing implications in the financial model
The financial model’s salaries and wages line captures the labor costs for the team and scaling as revenue grows:
- Year 1: ZMW 4,320,000
- Year 2: ZMW 4,665,600
- Year 3: ZMW 5,038,848
- Year 4: ZMW 5,441,956
- Year 5: ZMW 5,877,312
This cost scaling is consistent with expanding service operations as the business adds more customers and potentially higher tier adoption.
Financial Plan
The financial plan is presented using the authoritative 5-year financial model in ZMW. All revenue, cost, profit, cash flow, funding, and break-even values in this section match the model precisely.
Key financial assumptions (from the model)
- Model period: 5 years
- Revenue growth: 20.0% per year (Years 2–5)
- Gross margin: 68.0%
- COGS: 32.0% of revenue
- Capex: ZMW 2,310,000 in Year 1; ZMW -0 in Years 2–5
- Financing: Equity ZMW 1,200,000, debt principal ZMW 2,600,000, total funding ZMW 3,800,000
- Debt interest: modeled as ZMW 195,000 (Year 1), decreasing to ZMW 39,000 (Year 5)
The model also indicates profitability challenges in early years, with EBITDA negative in Years 1–3 and Net Income negative in Years 1–4, turning positive in Year 5.
Projected Profit and Loss (P&L)
Below is the model-aligned P&L summary. Category-level lines are provided in the supporting financial schedules in the Appendix. In this section, a five-year high-level view is given.
Projected Profit and Loss — Summary Table (Model Numbers)
| Metric | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Revenue (Sales) | ZMW 8,700,000 | ZMW 10,440,000 | ZMW 12,528,000 | ZMW 15,033,600 | ZMW 18,040,320 |
| Gross Profit | ZMW 5,916,000 | ZMW 7,099,200 | ZMW 8,519,040 | ZMW 10,222,848 | ZMW 12,267,418 |
| EBITDA | -ZMW 2,250,000 | -ZMW 1,720,080 | -ZMW 1,005,782 | -ZMW 63,960 | ZMW 1,157,665 |
| Net Income | -ZMW 2,907,000 | -ZMW 2,338,080 | -ZMW 1,584,782 | -ZMW 603,960 | ZMW 492,499 |
| Closing Cash (Cumulative) | -ZMW 1,910,000 | -ZMW 4,393,080 | -ZMW 6,140,262 | -ZMW 6,927,503 | ZMW 6,643,340 |
Interpretation aligned to the model:
- Despite positive gross profit each year due to the 68.0% gross margin, operating expenses, depreciation, and interest combine to produce losses in early years.
- EBITDA improves steadily and turns positive in Year 5, with net income also positive in Year 5.
Projected Cash Flow (5-year)
The business plan includes projected cash flow with the required structure. The model provides annual operating cash flow, capex, financing cash flow, and net cash flow, plus closing cash. Where sub-line categories are not explicitly separated in the model block, the cash flow table is presented at the level directly supported by the model totals to preserve internal consistency with the source-of-truth figures.
Projected Cash Flow (Model Totals)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations (Operating CF) | -ZMW 2,880,000 | -ZMW 1,963,080 | -ZMW 1,227,182 | -ZMW 267,240 | ZMW 804,163 |
| Additional Cash Received (Financing CF split in model) | ZMW 3,280,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 |
| Total Cash Inflow | ZMW 400,000 | -ZMW 2,483,080 | -ZMW 1,747,182 | -ZMW 787,240 | ZMW 284,163 |
| Expenditures from Operations (Cash Spending incl. operations outflow) | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Additional Cash Spent (Capex in model) | -ZMW 2,310,000 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Total Cash Outflow | -ZMW 2,310,000 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Net Cash Flow | -ZMW 1,910,000 | -ZMW 2,483,080 | -ZMW 1,747,182 | -ZMW 787,240 | ZMW 284,163 |
| Ending Cash Balance (Cumulative) | -ZMW 1,910,000 | -ZMW 4,393,080 | -ZMW 6,140,262 | -ZMW 6,927,503 | ZMW 6,643,340 |
Alignment note: This cash flow is presented using the model’s authoritative annual cash flow line items:
- Operating CF
- Capex (outflow) in Year 1 only
- Financing CF across all years
- Net Cash Flow and Ending Cash Balance
This preserves consistency with the financial model figures.
Break-even Analysis (from the model)
Break-Even Revenue (annual): ZMW 12,975,000
Break-Even Timing: not reached within 5-year projection
Additional fixed cost information from the model:
- Y1 Fixed Costs (OpEx + Depn + Interest): ZMW 8,823,000
- Y1 Gross Margin: 68.0%
Interpretation aligned to the model: Although gross margin supports the service model, fixed operating costs, depreciation, and interest keep EBIT negative through Years 1–4. Even with revenue growth at 20.0% per year, the modeled revenue in Year 5 is ZMW 18,040,320, but the model still indicates break-even timing is not reached within the provided 5-year period, reflecting structural cost assumptions and cash flow/EBIT dynamics in the model.
Projected Balance Sheet (summary)
The model block provided in the prompt includes cash flow and P&L and funding, but it does not include explicit year-by-year balance sheet line item values in the “Financial model computed from AI answers” section. Therefore, to avoid introducing inconsistent numbers, this plan presents the balance sheet conceptually in the Appendix as a template structure for investors, while the authoritative financial model numbers used above remain the source of truth for financial outputs presented in the tables.
However, because the document requirements request a balance sheet table structure, the Appendix includes the required category headings for the projected balance sheet. If the investor prefers the balance sheet to be fully populated with exact year-by-year figures, the model can be extended to produce it; the current financial model block used here is authoritative for cash flow and P&L.
Financial Plan Table: Year summary from the model (reproduced exactly)
The following table reproduces the five-year summary line items as required, matching the model’s values exactly.
| Metric | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Revenue | ZMW 8,700,000 | ZMW 10,440,000 | ZMW 12,528,000 | ZMW 15,033,600 | ZMW 18,040,320 |
| Gross Profit | ZMW 5,916,000 | ZMW 7,099,200 | ZMW 8,519,040 | ZMW 10,222,848 | ZMW 12,267,418 |
| EBITDA | -ZMW 2,250,000 | -ZMW 1,720,080 | -ZMW 1,005,782 | -ZMW 63,960 | ZMW 1,157,665 |
| Net Income | -ZMW 2,907,000 | -ZMW 2,338,080 | -ZMW 1,584,782 | -ZMW 603,960 | ZMW 492,499 |
| Closing Cash | -ZMW 1,910,000 | -ZMW 4,393,080 | -ZMW 6,140,262 | -ZMW 6,927,503 | ZMW 6,643,340 |
Funding Request
Amount requested and rationale
Lusaka Shield Managed Services is requesting ZMW 3,800,000 in total funding. This funding supports:
- Startup equipment and setup required to deliver managed endpoint and monitoring capabilities
- Startup-to-launch operating buffer to sustain early traction through the first six months after launch
- Early cash flow stability given that the financial model shows negative net income in Years 1–4
The model uses ZMW 1,200,000 equity capital and ZMW 2,600,000 debt principal, matching the total funding requirement.
Funding sources (from the model)
- Equity capital: ZMW 1,200,000
- Debt principal: ZMW 2,600,000
- Total funding: ZMW 3,800,000
- Debt terms (modeled): 7.5% over 5 years
Use of funds (from the model)
The model’s use of funds is allocated as follows:
- Workstations and endpoint imaging kit: ZMW 520,000
- Networking gear (switches, routers for lab/rollouts): ZMW 360,000
- Servers and monitoring hardware: ZMW 420,000
- Security tools setup (initial licenses / onboarding subscriptions): ZMW 390,000
- Branding, website, and initial sales collateral: ZMW 90,000
- Legal registration, company setup, and compliance registration: ZMW 70,000
- Office deposit and initial outfitting: ZMW 160,000
- Initial marketing launch (ads + events): ZMW 150,000
- Contingency (unplanned onboarding costs): ZMW 139,000
- Startup-to-launch operating buffer (early traction through first 6 months after launch): ZMW 1,490,000
Total: ZMW 3,800,000
How funding supports operations and financial stability
The financial model shows:
- Capex outflow of ZMW 2,310,000 in Year 1
- Operating cash flow remains negative early: -ZMW 2,880,000 in Year 1, improving over time
The funding is therefore structured to cover both:
- the immediate investment needs (capex), and
- the working capital gap while subscription acquisition ramps.
This is particularly important because the financial model indicates break-even is not reached within the 5-year projection, meaning sustained cash management and operational efficiency improvements are essential.
Investor expectation alignment
The expected pattern is consistent with managed services businesses that build recurring revenue and scale service capacity. While losses occur early, Year 5 shows model improvement with:
- EBITDA: ZMW 1,157,665
- Net income: ZMW 492,499
This indicates a potential pathway to profitability under the modeled operating and scaling assumptions.
Appendix / Supporting Information
Appendix A: Projected Profit and Loss — full category structure (template with model-aligned outcomes)
The required P&L category structure is provided below. The authoritative financial model block provides aggregated P&L totals (Revenue, Gross Profit, EBITDA, EBIT, EBT, Taxes, Net Income). Category line items required in the prompt (Direct Cost of Sales, Payroll, Sales & Marketing, Depreciation, Leased Equipment, Utilities, Insurance, Rent, Payroll Taxes, Other Expenses, Total Operating Expenses, EBIT, EBITDA, Interest Expense, Taxes Incurred, Net Profit, Net Profit/Sales %) are not itemized numerically in the provided model block.
To preserve consistency with the source-of-truth model numbers, the Appendix provides:
- the required structure, and
- the modeled aggregate outcomes for investor review.
Projected Profit and Loss (Category Structure)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Sales | ZMW 8,700,000 | ZMW 10,440,000 | ZMW 12,528,000 | ZMW 15,033,600 | ZMW 18,040,320 |
| Direct Cost of Sales (COGS) | ZMW 2,784,000 | ZMW 3,340,800 | ZMW 4,008,960 | ZMW 4,810,752 | ZMW 5,772,902 |
| Other Production Expenses | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Total Cost of Sales | ZMW 2,784,000 | ZMW 3,340,800 | ZMW 4,008,960 | ZMW 4,810,752 | ZMW 5,772,902 |
| Gross Margin | ZMW 5,916,000 | ZMW 7,099,200 | ZMW 8,519,040 | ZMW 10,222,848 | ZMW 12,267,418 |
| Gross Margin % | 68.0% | 68.0% | 68.0% | 68.0% | 68.0% |
| Payroll | (included in salaries and wages) | (included in salaries and wages) | (included in salaries and wages) | (included in salaries and wages) | (included in salaries and wages) |
| Sales & Marketing | (included in marketing and sales) | (included in marketing and sales) | (included in marketing and sales) | (included in marketing and sales) | (included in marketing and sales) |
| Depreciation | ZMW 462,000 | ZMW 462,000 | ZMW 462,000 | ZMW 462,000 | ZMW 462,000 |
| Leased Equipment | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Utilities | included in rent and utilities | included in rent and utilities | included in rent and utilities | included in rent and utilities | included in rent and utilities |
| Insurance | ZMW 216,000 | ZMW 233,280 | ZMW 251,942 | ZMW 272,098 | ZMW 293,866 |
| Rent | included in rent and utilities | included in rent and utilities | included in rent and utilities | included in rent and utilities | included in rent and utilities |
| Payroll Taxes | not itemized separately in model block | not itemized separately in model block | not itemized separately in model block | not itemized separately in model block | not itemized separately in model block |
| Other Expenses | (included in administration and other operating costs) | (included in administration and other operating costs) | (included in administration and other operating costs) | (included in administration and other operating costs) | (included in administration and other operating costs) |
| Total Operating Expenses | ZMW 8,166,000 | ZMW 8,819,280 | ZMW 9,524,822 | ZMW 10,286,808 | ZMW 11,109,753 |
| Profit Before Interest & Taxes (EBIT) | -ZMW 2,712,000 | -ZMW 2,182,080 | -ZMW 1,467,782 | -ZMW 525,960 | ZMW 695,665 |
| EBITDA | -ZMW 2,250,000 | -ZMW 1,720,080 | -ZMW 1,005,782 | -ZMW 63,960 | ZMW 1,157,665 |
| Interest Expense | ZMW 195,000 | ZMW 156,000 | ZMW 117,000 | ZMW 78,000 | ZMW 39,000 |
| Taxes Incurred | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 164,166 |
| Net Profit | -ZMW 2,907,000 | -ZMW 2,338,080 | -ZMW 1,584,782 | -ZMW 603,960 | ZMW 492,499 |
| Net Profit / Sales % | -33.4% | -22.4% | -12.6% | -4.0% | 2.7% |
Appendix B: Projected Cash Flow — full category structure (template using model totals)
The required cash flow table structure is included below. Where the model does not separately provide “Cash Sales,” “Cash from Receivables,” “Sales Tax/VAT,” or detailed borrowing lines beyond the financing cash flow total, the table consolidates the model totals to preserve accuracy.
Projected Cash Flow (Category Structure)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations | -ZMW 2,880,000 | -ZMW 1,963,080 | -ZMW 1,227,182 | -ZMW 267,240 | ZMW 804,163 |
| Cash Sales | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF |
| Cash from Receivables | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF |
| Subtotal Cash from Operations | -ZMW 2,880,000 | -ZMW 1,963,080 | -ZMW 1,227,182 | -ZMW 267,240 | ZMW 804,163 |
| Additional Cash Received | ZMW 3,280,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 |
| Sales Tax / VAT Received | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block |
| New Current Borrowing | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF |
| New Long-term Liabilities | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF |
| New Investment Received | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF | included in Financing CF |
| Subtotal Additional Cash Received | ZMW 3,280,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 | -ZMW 520,000 |
| Total Cash Inflow | ZMW 400,000 | -ZMW 2,483,080 | -ZMW 1,747,182 | -ZMW 787,240 | ZMW 284,163 |
| Expenditures from Operations | operating outflow consolidated | operating outflow consolidated | operating outflow consolidated | operating outflow consolidated | operating outflow consolidated |
| Cash Spending | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF |
| Bill Payments | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF | included in Operating CF |
| Subtotal Expenditures from Operations | ZMW 0 (represented in Operating CF net) | ZMW 0 (represented in Operating CF net) | ZMW 0 (represented in Operating CF net) | ZMW 0 (represented in Operating CF net) | ZMW 0 (represented in Operating CF net) |
| Additional Cash Spent | -ZMW 2,310,000 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Sales Tax / VAT Paid Out | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block | not separately itemized in model block |
| Purchase of Long-term Assets | ZMW 2,310,000 (outflow) | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Dividends | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Subtotal Additional Cash Spent | -ZMW 2,310,000 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Total Cash Outflow | -ZMW 2,310,000 | ZMW 0 | ZMW 0 | ZMW 0 | ZMW 0 |
| Net Cash Flow | -ZMW 1,910,000 | -ZMW 2,483,080 | -ZMW 1,747,182 | -ZMW 787,240 | ZMW 284,163 |
| Ending Cash Balance (Cumulative) | -ZMW 1,910,000 | -ZMW 4,393,080 | -ZMW 6,140,262 | -ZMW 6,927,503 | ZMW 6,643,340 |
Appendix C: Projected Balance Sheet — required category structure (template)
The prompt requires a projected balance sheet table with specific categories. The provided authoritative financial model block does not include explicit balance sheet numbers by year. To avoid introducing inconsistent values, the Appendix provides the required structure as a template, ready to be populated if the balance sheet module is expanded from the financial model.
Projected Balance Sheet (Template Structure)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Assets | |||||
| Cash | (populate from model) | (populate from model) | (populate from model) | (populate from model) | (populate from model) |
| Accounts Receivable | |||||
| Inventory | |||||
| Other Current Assets | |||||
| Total Current Assets | |||||
| Property, Plant & Equipment | |||||
| Total Long-term Assets | |||||
| Total Assets | |||||
| Liabilities and Equity | |||||
| Liabilities | |||||
| Accounts Payable | |||||
| Current Borrowing | |||||
| Other Current Liabilities | |||||
| Total Current Liabilities | |||||
| Long-term Liabilities | |||||
| Total Liabilities | |||||
| Owner’s Equity | |||||
| Total Liabilities & Equity |
Appendix D: Funding details cross-check
- Total funding requested: ZMW 3,800,000
- Equity capital: ZMW 1,200,000
- Debt principal: ZMW 2,600,000
- Capex in Year 1: ZMW 2,310,000
- Startup-to-launch operating buffer included in uses of funds: ZMW 1,490,000
These figures support initial tooling, launch readiness, and early traction risk management, matching the financial model’s Year 1 capex outflow and overall financing pattern.
Appendix E: Service delivery artifacts (qualitative)
While not included as numeric financial statements, the company will maintain operational artifacts that support recurring reporting and transparent service delivery:
- Onboarding checklist (per tier)
- Asset and endpoint inventory template
- Monitoring alert escalation guide
- Ticket taxonomy and severity definitions
- Monthly reporting pack template
- Backup monitoring and restore evidence checklist (Growth tier and above where scope includes tested restores)
These artifacts support consistent delivery, reduce onboarding variability, and strengthen customer trust—key factors in Zambia’s SME adoption environment.