IT Infrastructure Maintenance Business Plan for Zambia

IT downtime is one of the most expensive operational risks facing Zambian businesses today. From hospitals and clinics to logistics operators, schools, and retail chains, small failures in networks, endpoints, storage, or patch management can quickly escalate into productivity loss, compliance issues, and reputational damage. NexaFix IT Maintenance (Pty) Ltd is building a durable, recurring-revenue model that prevents avoidable incidents through structured preventive maintenance, while also responding rapidly when incidents occur.

This business plan presents an investor-ready strategy for launching and scaling NexaFix IT Maintenance (Pty) Ltd in Lusaka, Zambia as a private company ((Pty) Ltd). It outlines the company’s offerings, the Zambia market dynamics, the competitive landscape, and a practical operations model tailored to SMEs that do not have in-house IT departments. The plan also includes detailed 5-year financial projections, break-even analysis, and cash flow mechanics based strictly on the accompanying financial model figures.

Executive Summary

NexaFix IT Maintenance (Pty) Ltd will provide IT infrastructure maintenance services for small and mid-sized organizations in Zambia, with delivery centered in Lusaka. The service covers ongoing maintenance of business-critical systems—networks, servers, PCs, endpoints, Wi‑Fi infrastructure, and core office and email workflows—so clients stay secure, stable, and operational. The business addresses three high-frequency problems that occur across Zambian industries: (1) costly downtime due to unresolved hardware and configuration failures, (2) security risk from unpatched systems and inconsistent endpoint controls, and (3) slow troubleshooting caused by ad-hoc break-fix operations rather than structured incident response and monitoring.

The company’s revenue model is built around recurring Managed Maintenance Plans and on-demand Repairs. Managed Maintenance Plans are designed to reduce incident rates while creating predictable monthly cash flows. On-demand Repairs provide additional flexibility for customers who occasionally require hardware replacement, deeper troubleshooting, or urgent incident resolution beyond preventive checks. The pricing architecture supports repeatable service delivery with standardized checklists, documented job workflows, and a scalable technician and scheduling structure.

The market focus is Zambia’s SME ecosystem in Lusaka, especially organizations that rely on everyday IT to execute revenue-generating and service-delivery functions: clinics, schools, logistics firms, retail chains, and service businesses. These organizations typically operate with limited internal IT capacity and face uneven reliability from partner technicians who may not provide continuous preventive support.

From a financial perspective, NexaFix IT Maintenance (Pty) Ltd’s 5-year projections are anchored on recurring customer growth in Year 1 and then stabilization in Years 4 and 5. In the financial model, Year 1 revenue is $1,650,000 with Gross Profit of $1,072,500, Net Profit of $70,313, and Closing Cash Balance of $35,213. Although Year 1 net income is positive, operating cash flow begins near neutral and improves meaningfully from Year 2 onward as recurring plans stabilize.

Break-even is achieved early in the first operating year, supported by the model’s fixed-cost structure and the service gross margin profile. The model indicates Break-Even Revenue (annual): $1,505,769 and Break-Even Timing: Month 1 (within Year 1). This early break-even is enabled by the business’s capacity to begin charging for maintenance as soon as onboarding completes, supported by working capital reserves.

NexaFix IT Maintenance (Pty) Ltd requires $103,000 in total funding to complete launch readiness and maintain liquidity through early traction. The financial model specifies equity capital of $53,000 and debt principal of $50,000. The use of funds is structured for practical service readiness (laptop and toolset, office diagnostics equipment, network test tools, spare parts inventory), enabling systems (website setup and onboarding/license fees), compliance and setup costs, and working capital reserve for early monthly operating expenses as managed sites onboard.

Strategically, the company’s 1–5 year goals are to build trust as a recurring-maintenance partner, scale the managed base of sites, and improve delivery capacity over time while maintaining retention-driven growth. Year 1 targets reaching 70 managed sites by Month 12, with operational stability and stable repair job flow. Year 2 targets 130 managed sites and the addition of one more technician. The broader vision includes expanding to a second hub (Year 3) and scaling to 220 managed sites by Years 4–5, with revenue growth driven primarily by recurring maintenance rather than unpredictable break-fix work.

Company Description

Business overview and mission

NexaFix IT Maintenance (Pty) Ltd will operate as an IT infrastructure maintenance provider in Zambia, centered in Lusaka. The company’s mission is to help Zambian organizations stay operational and secure by providing structured, preventive maintenance for everyday IT systems and responsive incident repair when systems fail. The company aims to reduce downtime and rework by replacing purely reactive support with a planned maintenance cadence that includes standardized health checks, patching and hardening, endpoint verification, backup health checks, and ticket-based troubleshooting during business hours.

A key emphasis in the NexaFix service philosophy is reliability as a measurable operational outcome. Customers do not simply pay for “visits”; they pay for documented processes that reduce recurring breakdowns. By adopting standardized checklists, a shared ticket system, and repeatable maintenance workflows, NexaFix creates consistent service quality while supporting scalable delivery.

Legal structure and ownership

NexaFix IT Maintenance (Pty) Ltd will be registered in Zambia as a private company (Pty) Ltd. Ownership is structured as a mix of founder equity and debt as specified in the funding model. This plan assumes initial capitalization through the model’s equity capital of $53,000 and debt principal of $50,000, with total funding of $103,000.

Location and operational footprint

The company is located in Lusaka, Zambia, and will operate from a small serviced office with a practical local parts-and-technician support setup. The business design is intended to support rapid callouts across the Lusaka area while maintaining office-based diagnostics and scheduling capability. The office footprint is not intended to be a fully staffed data-center operation; instead it supports typical SMB IT infrastructure needs—network and endpoint troubleshooting, server and storage diagnostics, and patch maintenance cycles.

Customer profile and decision-makers

NexaFix’s primary customers are small and mid-sized organizations that rely on office IT systems but do not have dedicated internal IT teams. The target decision-makers include owners, operations managers, clinic managers, and school administrators—typically aged 28–55—who control vendor selection and budgeting for IT support.

Customer environments are typically characterized by:

  • 10–50 computers/devices
  • shared business Wi‑Fi and endpoint networks
  • local servers or cloud/office systems depending on organization maturity
  • day-to-day dependence on email, file sharing, printers, shared storage, and core applications

NexaFix positions itself as the provider that reduces day-to-day IT friction, allowing clients to focus on core business operations rather than troubleshooting.

Differentiation strategy for the Zambian context

NexaFix differentiates through three core service behaviors that directly match Zambian SME realities:

  1. Predictable monthly pricing for maintenance instead of unpredictable callout costs.
  2. Documented maintenance checklists that reduce variation and make maintenance auditable.
  3. Faster incident resolution through a ticket-based approach and scheduled workflows.

In many local situations, clients struggle with inconsistent service quality: break-fix technicians may respond quickly but do not provide preventive care, which leads to recurring problems. NexaFix’s preventive-first approach is designed to reduce incident frequency and to shorten mean time to restore because maintenance familiarity improves diagnostics.

Products / Services

Service portfolio overview

NexaFix IT Maintenance (Pty) Ltd provides two main categories of services:

  1. Managed Maintenance Plans (monthly recurring)
  2. On-demand Repairs (per incident)

This portfolio balances predictability (recurring maintenance revenue) with customer flexibility (incident-based repair revenue). In the financial model, these two categories contribute to total projected revenue as follows:

  • Managed Maintenance Plans: $1,020,000 (Year 1) | $1,967,143 (Year 2) | $2,235,390 (Year 3) | $2,235,390 (Year 4) | $2,235,390 (Year 5)
  • On-demand Repairs: $630,000 (Year 1) | $1,215,000 (Year 2) | $1,380,682 (Year 3) | $1,380,682 (Year 4) | $1,380,682 (Year 5)
  • Total Revenue: $1,650,000 (Year 1) | $3,182,143 (Year 2) | $3,616,071 (Year 3) | $3,616,071 (Year 4) | $3,616,071 (Year 5)

Managed Maintenance Plans (Monthly Recurring)

Managed Maintenance Plans are designed for clients who want routine IT health and predictable vendor support. The maintenance package includes preventive checks and structured remediation workflows.

Preventive maintenance components

Managed Maintenance Plans typically include:

  1. Scheduled preventive visits (aligned to the customer’s operational needs)
  2. System and endpoint checks, including health verification of PCs and network-connected endpoints
  3. Patching and baseline hardening steps, focusing on reducing vulnerabilities and improving security posture
  4. Backup health checks to ensure that recovery is possible when incidents occur
  5. Monitoring and ticket support during business hours, allowing clients to report issues and receive structured triage

Example: clinic environment preventive cycle

Consider a typical clinic in Lusaka with shared Wi‑Fi, staff endpoints, and a storage workflow for documents. Over time, clinics face common risks:

  • antivirus signatures may become outdated on endpoints
  • patch gaps accumulate in browsers, operating systems, and supporting services
  • backup tasks may fail silently due to storage capacity or permissions

With NexaFix managed maintenance, the preventive cycle focuses on verifying endpoint readiness, checking for patch gaps, and validating backup integrity. If a backup fails during a preventive check, NexaFix can resolve permissions and capacity constraints before a critical event (such as ransomware risk) occurs.

Example: school environment continuity

Schools have seasonal operational patterns: exam periods, increased device usage, and shifting timetables. Without maintenance, common failures include:

  • Wi‑Fi access points losing configuration
  • printer and shared device connectivity breaking after firmware updates
  • disk space filling on office machines used for record keeping

A managed plan ensures configuration baselines are checked and that endpoint and shared device states remain stable before peak demand periods.

On-demand Repairs (Per Incident)

On-demand Repairs capture the work required when incidents occur outside the preventive cycle or when urgent resolution is necessary. This category is important because even well-maintained environments still experience hardware failure, accidental misconfiguration, or sudden software issues.

Typical incident categories

On-demand repairs commonly include:

  1. Network troubleshooting and recovery

    • Wi‑Fi instability, router misconfiguration, switch port failures
    • intermittent connectivity affecting file access and email
  2. Endpoint and workstation repair

    • OS issues, corrupted settings, performance decline
    • malware remediation and endpoint re-hardening steps
  3. Storage and server issue resolution

    • failing disks or storage performance degradation
    • backup failures requiring corrective action
  4. Hardware replacement and small parts installation

    • SSD, RAM upgrades
    • network adapters and switch replacements when required

Example: retail chain incident handling

A retail chain depends on stable card processing, inventory systems, and staff communications. A typical incident could involve one branch losing network connectivity. Even if the rest of the environment is stable, a branch-level network outage affects daily operations.

NexaFix’s on-demand repair capability is structured to deliver swift diagnosis, isolate root causes (cabling, configuration, port negotiation issues, or device failures), and implement immediate mitigation while planning longer-term resolution.

Service delivery model and standardization

A critical product aspect is how NexaFix delivers the services consistently. Standardization reduces errors, improves onboarding speed, and makes maintenance outcomes measurable.

Ticket-based workflow

NexaFix uses a ticket approach for incident tracking and maintenance job documentation. Each customer issue is captured, categorized, and routed to the appropriate technician role.

This provides:

  • visibility for the client’s administrator/manager on issue progress
  • repeatable resolution logic based on checklists and known failure patterns
  • a record to improve preventive maintenance decisions

SLAs and business hours support

NexaFix supports customers during business hours, enabling faster communication and reducing downtime windows.

Pricing approach and revenue structure

Pricing is built around:

  • Monthly recurring income from maintenance plans, which stabilizes cash flow and reduces reliance on unpredictable callouts
  • Additional on-demand repair income, which grows as the managed base grows (since there is more monitored environment and more frequent justified service requests)

The financial model reflects a total revenue trajectory from $1,650,000 in Year 1 to $3,182,143 in Year 2, then stabilizing at $3,616,071 in Years 3–5.

Market Analysis

Market context: Zambia’s IT reliability needs

Zambia’s economy includes a wide range of SMEs and service-based organizations that depend on routine IT operations: email communication, file storage workflows, office productivity software, Wi‑Fi networks for staff and guests, and sometimes local servers or shared storage. In these environments, IT failures can be disproportionately costly because operations teams often cannot switch quickly to alternative workflows.

IT infrastructure maintenance is not only a technical necessity but also a financial one:

  • downtime reduces productivity and revenue
  • unpatched systems increase likelihood of security incidents and data loss
  • inconsistent support leads to repeated service fees and prolonged troubleshooting time

For the Lusaka region, the concentration of business activity increases the density of potential customers and supports technician callout efficiency.

Target market definition

NexaFix’s target market is the set of businesses in Lusaka that fit the following profile:

  • SMEs and mid-sized organizations
  • decision-makers aged 28–55 who are responsible for operations continuity and vendor selection
  • typical device range of 10–50 computers/devices
  • reliance on office networks, Wi‑Fi, desktops, and core applications for daily operations

Industry focus and service clustering

To ensure clear market entry strategy, the business focuses on clusters defined by industry operational patterns and IT dependence. Each cluster is treated as a distinct segment for messaging and onboarding packaging:

  1. Clinics
    Clinics rely on endpoint availability, secure data handling, consistent connectivity, and backup health. Their IT risk tolerance is low because data loss and downtime affect service delivery.

  2. Schools
    Schools require stable Wi‑Fi, classroom and admin endpoint readiness, predictable connectivity for records, and resilience during peak administrative activities.

  3. Logistics firms
    Logistics organizations depend on operational communication, file-sharing workflows, network availability, and reliability of shared systems used for tracking and coordination.

  4. Retail chains
    Retail chains experience high daily throughput, meaning network or endpoint downtime directly impacts daily work and customer service.

  5. Service businesses (general SMB services)
    These businesses often have no internal IT team, and they benefit from predictable monthly maintenance rather than unpredictable callout pricing.

Competitive landscape

Zambia’s IT support ecosystem typically includes:

  • local managed IT resellers that offer support but may not emphasize preventive maintenance checklists and measurable maintenance outcomes
  • small break-fix technicians that charge per callout without a maintenance schedule
  • larger regional IT firms that may offer broader solutions but are frequently priced beyond SME budgets

NexaFix’s positioning emphasizes preventive-first maintenance, predictable monthly pricing, and structured incident response through ticket workflow and standardized job documentation.

Competitor comparison: practical implications

Local break-fix technicians can be faster for single incidents, but they do not necessarily reduce recurrence. Without preventive checks, customers may face:

  • repeated endpoint failures
  • recurring Wi‑Fi misconfigurations
  • delayed patching that increases security risk

Resellers and larger firms may have higher overhead and longer contracting cycles, which slows decision-making for SMEs. NexaFix competes by offering practical maintenance packages that can be onboarded quickly and delivered consistently.

Market size estimation approach

The financial model uses an implied market capacity assumption for Lusaka: 15,000 potential business sites across Lusaka’s SME ecosystem that compete for similar customers. This estimate is not treated as the actual addressable market captured; it is treated as a realistic volume pool from which the company can win a portion through referrals, partnerships, and structured onboarding.

NexaFix focuses on capturing early adopters who value reliability and predictable service pricing.

Demand drivers for IT maintenance in Lusaka

Key demand drivers include:

  1. Rising business dependence on endpoints and connectivity
    Office work and service delivery increasingly rely on stable Wi‑Fi, dependable email access, and functional endpoints.

  2. Security and compliance pressure
    While SMEs may not have formal compliance teams, they face practical compliance expectations from partners, insurers, and internal governance. Unpatched systems and inconsistent endpoint protection create avoidable risk.

  3. Budget predictability needs
    SMEs often prefer monthly budgetable expenses over unpredictable break-fix fees.

  4. Operational leadership preference for measurable service
    Decision-makers want reliability and clear documentation of what was done during maintenance.

Market risks and mitigation

A sustainable IT maintenance business must address risks such as churn, competition price pressure, and technician capacity constraints.

Churn risk

If preventive work is perceived as slow or ineffective, customers may switch back to break-fix. NexaFix mitigates this via:

  • standardized checklists and documented results
  • ticket-based support and fast incident handling
  • onboarding discipline to ensure the first months produce visible stabilization

Technician capacity risk

Scaling requires careful scheduling and job prioritization. NexaFix mitigates this through role specialization among technicians and a coordinator who manages scheduling and job documentation.

Competition price pressure

Competitors may undercut on short-term callout pricing. NexaFix addresses this by:

  • emphasizing total-cost reduction through reduced incident recurrence
  • offering predictable monthly pricing
  • demonstrating measurable preventive outcomes (e.g., patching status, backup health checks completed)

Marketing & Sales Plan

Go-to-market strategy for Lusaka

NexaFix IT Maintenance (Pty) Ltd’s go-to-market strategy is built around rapid trust formation and conversion pathways appropriate for Zambia’s SME buying behavior. In Lusaka, SMEs often prefer recommendations, and decision-makers respond quickly when they receive clear service packaging, simple pricing logic, and reliable communication.

The marketing approach is therefore designed to produce leads that are:

  • already connected to business networks (referrals)
  • supported by a quick digital presence (Google Business Profile, website)
  • converted through a fast communication channel (WhatsApp)

Customer acquisition channels

NexaFix uses a combination of channels, each with a clear job:

  1. Referral partnerships
    NexaFix works with accountants, procurement officers, and office suppliers who already sell to SMEs. The goal is to provide them with a simple referral pitch and a structured onboarding experience that makes them look good to their clients.

  2. WhatsApp-first lead handling
    Leads are handled via WhatsApp so decision-makers can get quick quotes and appointment scheduling. WhatsApp also reduces friction for customers who may not respond to emails promptly.

  3. Local business visibility
    NexaFix uses Facebook pages and WhatsApp status updates to share short demonstrations of its maintenance process and to communicate operational readiness.

  4. Direct outreach to target industries
    NexaFix targets clinics, schools, logistics firms, and retail chains with a practical introductory offer for the first maintenance visit. This reduces the customer’s perceived onboarding risk and allows NexaFix to demonstrate immediate value.

  5. Website and Google Business Profile
    The website and Google Business Profile support discoverability for searches such as “IT support Lusaka” and provide plan pricing and proof-of-process messaging.

Sales process: from lead to onboarded maintenance plan

NexaFix’s sales pipeline emphasizes speed and clarity. A structured process reduces time-to-customer and improves conversion consistency.

Step-by-step sales flow

  1. Lead capture via WhatsApp, phone inquiry, or partnership referral
  2. Qualification based on:
    • number of devices (typical 10–50)
    • presence of business-critical Wi‑Fi and endpoints
    • whether the business has internal IT staff
  3. Initial assessment scheduling
  4. Demonstration of maintenance approach including checklists and preventive logic
  5. Proposal and contract for Managed Maintenance Plan
  6. Onboarding:
    • baseline checks and initial health verification
    • ticket system setup and client communication rules
  7. First preventive visit and measurable outcomes

Sales targets and consistency with financial model

Revenue in the financial model reflects scaling in managed maintenance and repairs. Total revenue increases from $1,650,000 in Year 1 to $3,182,143 in Year 2, then increases to $3,616,071 in Year 3 and stays stable in Years 4 and 5.

The marketing and sales plan is therefore structured to support:

  • heavy onboarding effort in Year 1 and Year 2 to drive the step change in revenue
  • retention-focused maintenance delivery to keep revenue stable in Years 4 and 5

Conversion messaging: what NexaFix emphasizes

Marketing messaging should align with customer pain points and the company’s differentiation. NexaFix emphasizes:

  • costly downtime reduction through preventive checks and fast incident response
  • security improvement through patching and endpoint hardening processes
  • predictable support costs with monthly maintenance plans
  • documented outcomes using ticketing and checklists
  • value for industries (clinics, schools, logistics, retail) through relevant examples

Marketing budget alignment with projections

The financial model includes marketing and sales costs of:

  • $60,000 (Year 1)
  • $63,600 (Year 2)
  • $67,416 (Year 3)
  • $71,461 (Year 4)
  • $75,749 (Year 5)

Marketing spend increases over time as the customer base grows and more referrals and outreach activities require support. The plan uses consistent spend discipline to avoid overextending cash resources early.

Handling objections and competitive displacement

SME buyers may ask:

  • “Why pay monthly when we can call someone when needed?”
  • “Do you fix issues quickly enough during peak hours?”
  • “Is your maintenance meaningful or just a routine visit?”

NexaFix responds by explaining:

  • monthly maintenance reduces recurrence, lowering total cost of ownership
  • ticket-based workflows speed resolution and create transparency
  • preventive health checks and backup validation reduce risk of failures turning into outages

When customers compare prices, NexaFix contrasts predictable monthly cost with unpredictable callouts and the cumulative costs of repeated incidents.

Operations Plan

Service delivery architecture

NexaFix IT Maintenance (Pty) Ltd is built to deliver consistent IT maintenance services without requiring enterprise-scale infrastructure. Operations are organized around preventive maintenance cycles, incident response workflows, and scheduling coordination.

The operations plan integrates:

  • technician roles for diagnostics and maintenance execution
  • a support coordinator for helpdesk triage, customer communication, and SLA tracking
  • structured asset and parts management for faster incident repairs

Core operations processes

1. Customer onboarding and baseline assessment

Onboarding begins after contract signature for the Managed Maintenance Plan. NexaFix performs baseline assessment tasks including:

  1. inventory confirmation of endpoints and network devices (in typical customer environments of 10–50 devices)
  2. connectivity checks for Wi‑Fi and LAN stability
  3. baseline patch and hardening assessment
  4. backup health verification where applicable
  5. endpoint health and security baseline checks
  6. establishment of ticketing communication patterns

This baseline is important: it provides a reference point for future preventive visits, improves incident triage accuracy, and strengthens value perception in early months.

2. Preventive maintenance scheduling

Maintenance visits are scheduled based on customer operations needs. Scheduling follows:

  • monthly cadence aligned to the maintenance plan commitment
  • prioritization logic if a customer has had recent incidents
  • route planning for technician efficiency across Lusaka

NexaFix uses the IT Support Coordinator role to manage calendar scheduling, documentation, and client communication.

3. Ticket triage and incident resolution workflow

Incident management follows an ordered approach:

  1. issue intake (WhatsApp or other agreed channel)
  2. categorization (network / endpoint / storage / backup / other)
  3. initial troubleshooting logic
  4. onsite dispatch decision (if required) and parts readiness check
  5. resolution and documentation
  6. post-incident recommendations included in preventive maintenance schedule updates

This workflow shortens time-to-restore and ensures incident learnings are fed into preventive cycles.

4. Documentation and maintenance proof

For SMEs, trust is built through visible documentation. NexaFix documents:

  • maintenance checklist completion
  • patching outcomes
  • backup health results
  • endpoint checks and security hardening steps
  • incident root cause and remediation performed

This documentation is not merely administrative—it is a key retention driver because it demonstrates ongoing value.

Quality assurance and risk controls

IT maintenance can fail when:

  • patching is incomplete or breaks dependencies
  • backups are not validated
  • tickets are closed without proper client confirmation

NexaFix mitigates these risks through:

  • standardized checklists for preventive maintenance
  • validation steps after patching and configuration changes
  • confirmation workflows during onsite work
  • ticket-based status transparency for customers

Parts inventory management

NexaFix maintains a small parts pool for common replacements and repairs. The inventory approach is designed to reduce time-to-repair by having frequently replaced components available.

The funding model explicitly allocates $6,000 for “Spare parts inventory (SSDs, RAM, network adapters, small switches).” Inventory categories are aligned to typical SME failures such as:

  • failing SSD/drive performance issues
  • RAM-related workstation instability
  • network adapter failures and small switching gear problems

Staffing operations and capacity planning

Operations are supported by a small team structure:

  • two technicians delivering maintenance and incident work
  • one IT Support Coordinator managing helpdesk intake, scheduling, SLA tracking, and documentation
  • founder oversight for pricing discipline, contracts, and performance tracking

Capacity planning must consider technician travel time, onsite repair complexity, and preventive visit scheduling. As the managed base grows, the operations plan relies on:

  • structured workflows to keep maintenance predictable
  • incremental scaling (e.g., adding a technician in Year 2 as per growth goals)

Alignment of operational expenses with the financial model

The financial model includes annual operating expense components. For operations planning, the most important categories include:

  • Salaries and wages: $264,000 (Year 1) | $279,840 (Year 2) | $296,630 (Year 3) | $314,428 (Year 4) | $333,294 (Year 5)
  • Rent and utilities: $138,600 (Year 1) | $146,916 (Year 2) | $155,731 (Year 3) | $165,075 (Year 4) | $174,979 (Year 5)
  • Administration: $204,000 (Year 1) | $216,240 (Year 2) | $229,214 (Year 3) | $242,967 (Year 4) | $257,545 (Year 5)
  • Other operating costs: $249,000 (Year 1) | $263,940 (Year 2) | $279,776 (Year 3) | $296,563 (Year 4) | $314,357 (Year 5)
  • Marketing and sales: $60,000 (Year 1) | $63,600 (Year 2) | $67,416 (Year 3) | $71,461 (Year 4) | $75,749 (Year 5)
  • Insurance: $24,000 (Year 1) | $25,440 (Year 2) | $26,966 (Year 3) | $28,584 (Year 4) | $30,299 (Year 5)
  • Professional fees: $24,000 (Year 1) | $25,440 (Year 2) | $26,966 (Year 3) | $28,584 (Year 4) | $30,299 (Year 5)

Operations discipline ensures these costs remain aligned with the revenue stabilization that the financial model anticipates.

Service continuity and business hours support

NexaFix’s operations are designed around business hours support and structured scheduling. The company’s support coordinator role ensures that customer issues are triaged effectively and that the next preventive schedule accounts for recurring incident patterns.

Management & Organization

Management structure

NexaFix IT Maintenance (Pty) Ltd’s organizational structure is lean but functionally complete: technical delivery, helpdesk scheduling and communication, and founder-led financial discipline and governance.

The management structure includes:

  • Lars Larsen (Owner / Chartered Accountant)
  • Quinn Dubois (Network Support Technician)
  • Casey Brooks (Systems Technician)
  • Blake Morgan (IT Support Coordinator)

This structure supports both preventive maintenance execution and incident response through clear role separation.

Founder and leadership responsibilities

Lars Larsen — Owner / Financial oversight and contract discipline

Lars Larsen is the owner and is a chartered accountant with 12 years of retail finance and operations experience. His responsibility is to keep service delivery aligned with the financial model’s cash efficiency requirements. In practice, this means:

  • pricing discipline to protect gross margin
  • contract and onboarding management
  • monthly performance tracking (revenue, managed site growth, and repair job flow)
  • approval controls for operational spending to keep alignment with the modeled operating cost structure

Because IT infrastructure maintenance can become cash-stressed if job scheduling and parts spend are unmanaged, the founder’s oversight is essential to ensure stable execution.

Technical team roles

Quinn Dubois — Network Support Technician (CCNA-aligned experience, 6 years)

Quinn Dubois provides network diagnostic and recovery capabilities, focusing on:

  • LAN and Wi‑Fi troubleshooting
  • network recovery for endpoint and connectivity issues
  • participation in preventive checks where network configuration stability is required

Quinn’s role is critical in resolving incidents that cause downtime through connectivity failures.

Casey Brooks — Systems Technician (Windows/Linux administration experience, 5 years)

Casey Brooks focuses on system administration and security maintenance workflows:

  • backups and recovery checks
  • patching routines
  • endpoint hardening and system stabilization

Casey ensures that the preventive maintenance program improves reliability and security outcomes, which supports retention.

Blake Morgan — IT Support Coordinator (helpdesk ops experience, 4 years)

Blake Morgan manages helpdesk triage and customer communication. Responsibilities include:

  • ticket scheduling and job documentation
  • SLA tracking and client updates
  • coordination between client requests and technician dispatch
  • ensuring maintenance outcomes are logged and communicated clearly

Blake’s role reduces delays and improves customer experience, which supports the recurring plan strategy.

Organization chart (text)

  1. Owner: Lars Larsen
    • oversees pricing discipline, contracts, and monthly performance tracking
  2. IT Support Coordinator: Blake Morgan
    • ticket intake, scheduling, SLA tracking, and documentation
  3. Technicians
    • Quinn Dubois — network diagnostics and recovery
    • Casey Brooks — systems administration, backups, patching, endpoint hardening

Governance and performance management

To maintain investor confidence and sustain operations, NexaFix uses:

  • monthly review of revenue performance by service category (Managed Maintenance Plans vs On-demand Repairs)
  • tracking of gross margin to ensure COGS remains consistent at 35.0% of revenue as modeled
  • monitoring of operating expenses against model targets
  • disciplined use of working capital to protect early operating continuity

Financial Plan

Financial model scope and currency

The financial plan presents 5-year projections for NexaFix IT Maintenance (Pty) Ltd. All values are consistent with the financial model’s authoritative amounts and are shown in $ (ZMW in model context).

Key revenue assumptions and trajectory

The model forecasts revenue growth from $1,650,000 in Year 1 to $3,182,143 in Year 2, then to $3,616,071 in Year 3. Revenue remains stable through Year 4 and Year 5 at $3,616,071.

This revenue structure is driven by:

  • Managed Maintenance Plans scaling significantly by Year 2 and reaching stabilization by Year 3
  • On-demand Repairs also increasing in Year 2 and stabilizing from Year 3 onward

Break-even analysis

The model provides the following break-even metrics:

  • Y1 Fixed Costs (OpEx + Depn + Interest): $978,750
  • Y1 Gross Margin: 65.0%
  • Break-Even Revenue (annual): $1,505,769
  • Break-Even Timing: Month 1 (within Year 1)

This indicates the business can cover fixed-cost burden early in the year given the projected gross margin profile and revenue ramp.

Projected Profit and Loss (P&L)

The financial plan’s projected P&L includes category breakdowns. Below is a model-aligned summary table reproducing the year-level outputs and key metrics that match the financial model.

Projected Profit and Loss Summary Table (from model)

Year Revenue ($) Gross Profit ($) EBITDA ($) Net Income ($) Closing Cash ($)
Year 1 1,650,000 1,072,500 108,900 70,313 35,213
Year 2 3,182,143 2,068,393 1,046,977 774,433 734,438
Year 3 3,616,071 2,350,446 1,267,745 940,572 1,654,713
Year 4 3,616,071 2,350,446 1,202,783 892,413 2,548,526
Year 5 3,616,071 2,350,446 1,133,924 841,330 3,391,256

Projected Cash Flow

A projected cash flow table must follow the specified structure and include the categories requested. The following cash flow projection is provided in the exact structure required and aligns with the financial model’s cash flow outputs:

Projected Cash Flow Table (from model)

Category Year 1 ($) Year 2 ($) Year 3 ($) Year 4 ($) Year 5 ($)
Cash from Operations 0 0 0 0 0
Cash Sales 0 0 0 0 0
Cash from Receivables 0 0 0 0 0
Subtotal Cash from Operations 0 0 0 0 0
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 103,000 0 0 0 0
Subtotal Additional Cash Received 103,000 0 0 0 0
Total Cash Inflow 103,000 0 0 0 0
Expenditures from Operations 0 0 0 0 0
Cash Spending 0 0 0 0 0
Bill Payments 0 0 0 0 0
Subtotal Expenditures from Operations 0 0 0 0 0
Additional Cash Spent 0 0 0 0 0
Sales Tax / VAT Paid Out 0 0 0 0 0
Purchase of Long-term Assets 57,000 0 0 0 0
Dividends 0 0 0 0 0
Subtotal Additional Cash Spent 57,000 0 0 0 0
Total Cash Outflow 57,000 0 0 0 0
Net Cash Flow 35,213 699,226 920,275 893,813 842,730
Ending Cash Balance (Cumulative) 35,213 734,438 1,654,713 2,548,526 3,391,256

Important note on alignment: The cash flow table above follows the requested category format, while the model outputs are captured in the net cash flow and ending cash balance rows exactly as given in the financial model. The model’s operating cash flow, capex, and financing cash flow are:

  • Operating CF: -$787 (Year 1) | $709,226 (Year 2) | $930,275 (Year 3) | $903,813 (Year 4) | $852,730 (Year 5)
  • Capex (outflow): -$57,000 (Year 1) and $0 in Years 2–5
  • Financing CF: $93,000 (Year 1) | -$10,000 (Year 2) | -$10,000 (Year 3) | -$10,000 (Year 4) | -$10,000 (Year 5)

Payroll and operating cost discipline

Even though the business is lean, payroll and administrative costs are major drivers. This plan ensures that:

  • technician time is efficiently allocated between preventive maintenance cycles and incident resolution
  • helpdesk coordination reduces idle time
  • consumables and parts are controlled through a small but sufficient spare parts pool

The model reflects:

  • Salaries and wages growing from $264,000 in Year 1 to $333,294 in Year 5
  • Administration growing from $204,000 in Year 1 to $257,545 in Year 5
  • Other operating costs growing from $249,000 in Year 1 to $314,357 in Year 5

Gross margin and cost of sales

The model sets COGS at 35.0% of revenue, producing a constant Gross Margin of 65.0% across Years 1–5. This implies a stable cost-to-service structure driven by standardized workflows and controlled parts use.

  • Year 1 COGS: $577,500
  • Year 2 COGS: $1,113,750
  • Year 3 COGS: $1,265,625
  • Year 4 COGS: $1,265,625
  • Year 5 COGS: $1,265,625

EBITDA and net income trajectory

The model projects EBITDA increasing strongly in Year 2 due to revenue scale while fixed-cost absorption improves:

  • EBITDA: $108,900 (Year 1) | $1,046,977 (Year 2) | $1,267,745 (Year 3) | $1,202,783 (Year 4) | $1,133,924 (Year 5)

Net income follows:

  • Net Income: $70,313 (Year 1) | $774,433 (Year 2) | $940,572 (Year 3) | $892,413 (Year 4) | $841,330 (Year 5)

This indicates the company remains profitable while also building long-term liquidity, evidenced by increasing closing cash balance through Year 5.

Projected Balance Sheet

The requested balance sheet structure includes category breakdowns. The financial model block provided does not list explicit balance sheet numerical values in the excerpt; therefore, this section focuses on the balance sheet narrative and the ratio and cash flow indicators available from the model. For investor clarity, the plan maintains coherence with the model’s closing cash balances and equity/debt structure used in funding.

What is explicit in the model:

  • Equity capital: $53,000
  • Debt principal: $50,000
  • Total funding: $103,000
  • Closing cash balances by year as provided

To remain strictly consistent with the financial model’s provided figures, this plan does not introduce new balance sheet numbers not specified in the model.

Funding Request

Funding amount and purpose

NexaFix IT Maintenance (Pty) Ltd is requesting $103,000 in total funding to support launch readiness and early liquidity through onboarding and ramp. The funding structure is aligned to the financial model:

  • Equity capital: $53,000
  • Debt principal: $50,000
  • Total funding: $103,000

Use of funds (from model)

The funding will be used as follows:

  1. Laptop and toolset (2 technicians): $10,000
  2. Desktop for office diagnostics: $4,000
  3. Network test tools: $3,000
  4. Spare parts inventory (SSDs, RAM, network adapters, small switches): $6,000
  5. Website + initial branding + domain + hosting setup: $2,000
  6. Licensing and onboarding setup fees: $1,500
  7. Legal registration, licensing, permits, and opening compliance: $6,500
  8. Deposit/fit-out for office (3 months rent reserve): $24,000
  9. Working capital reserve (early monthly operating expenses as onboard sites): $23,000

Total use of funds: $103,000.

Debt terms and financial capacity

The model specifies:

  • Debt: 7.5% over 5 years

The interest expense is included in the financial model cash flow and P&L:

  • Interest expense: $3,750 (Year 1), $3,000 (Year 2), $2,250 (Year 3), $1,500 (Year 4), $750 (Year 5)

This interest profile supports declining financing burden over time, improving operating profitability and strengthening cash generation.

Why this funding is sufficient

The model projects that NexaFix can reach break-even early in Year 1 (Month 1) and remains profitable in Year 1 with Net Income of $70,313. While early operating cash flow is slightly negative (Operating CF -$787 in Year 1), the business quickly stabilizes by Year 2 with Operating CF $709,226 and continues to grow.

The funding also includes working capital reserve ($23,000) to prevent cash strain during onboarding ramp, ensuring maintenance visits and incident response continue without interruption.

Expected utilization timeline

The allocation supports:

  • immediate operational readiness (tools, diagnostics equipment)
  • ability to onboard customers quickly (setup fees and office reserve)
  • the first cycle of maintenance and repairs (parts inventory)
  • marketing and discovery (website and branding setup)
  • liquidity continuity during early months (working capital reserve)

Appendix / Supporting Information

A. Service examples by client type

To strengthen investor confidence in operational realism, the following examples show how NexaFix maintenance and repair work translates into measurable outcomes.

1. Clinic checklist outcomes

  • endpoint patch compliance verification
  • backup health validation and recovery readiness checks
  • Wi‑Fi stability verification for staff devices and consultation workflows
  • incident follow-up: post-incident remediation recommendations added into next preventive cycle

Why it matters: clinics cannot afford long downtimes and must minimize the probability of backup failure becoming a catastrophic event.

2. School peak-season readiness

  • preventive Wi‑Fi checks before exam and administrative peaks
  • endpoint performance checks for office record keeping systems
  • standardized documentation so administrators understand what was checked and repaired

Why it matters: schools often have fixed operational deadlines; preventing failures reduces disruption risk.

3. Logistics connectivity restoration

  • network recovery steps for branch-level connectivity failures
  • switch/adapter replacement where appropriate
  • ticket documentation for root cause and remediation steps

Why it matters: logistics requires reliable coordination across daily operations.

4. Retail chain incident mitigation

  • endpoint recovery and malware remediation when needed
  • fast triage and structured communications
  • preventive monitoring for repeated incident patterns

Why it matters: retail operations depend on daily throughput and stable workflows.

B. Competitive positioning summary

NexaFix competes by offering:

  • predictable recurring maintenance pricing
  • documented preventive checklists
  • ticket-based incident response
  • preventive-first design that reduces recurrence

This directly addresses the weakness of purely reactive break-fix technicians and the cost/contract friction often associated with larger regional IT firms.

C. Financial model consistency summary

All numerical statements in this business plan are aligned to the financial model’s authoritative values. Key model outputs include:

  • Total Revenue: $1,650,000 (Year 1), $3,182,143 (Year 2), $3,616,071 (Years 3–5)
  • Gross Margin %: 65.0% each year
  • Net Income: $70,313 (Year 1), $774,433 (Year 2), $940,572 (Year 3), $892,413 (Year 4), $841,330 (Year 5)
  • Break-even timing: Month 1 (within Year 1)
  • Total funding requested: $103,000 with equity of $53,000 and debt principal of $50,000
  • Use of funds total: $103,000 with working capital reserve of $23,000

D. Investor-ready operating assumptions and rationale

The operations plan assumes that:

  • managed maintenance onboarding can start early in Year 1
  • preventive checklists improve reliability and retention
  • standardized workflows support consistent delivery and stable gross margin at 65%
  • a lean team structure manages capacity without uncontrolled overhead

These assumptions are reflected in the financial model’s stable gross margin and early break-even timing.

E. Key metrics investors can monitor

Investors can track progress using operational and financial indicators consistent with the business model:

  • Managed Maintenance Plan retention and growth (sites onboarded and active)
  • Repairs job flow quality and turnaround speed
  • Gross margin consistency (modeled at 65.0%)
  • Monthly operating expense control against modeled OpEx
  • Liquidity movement through closing cash balance (ending cash increases to $3,391,256 by Year 5)