CopperCloud Data Centres (Pty) Ltd (“CopperCloud”) is a Lusaka-based private limited company providing secure, resilient data center colocation and managed connectivity for organizations that require uptime, fast provisioning, and compliance-ready infrastructure. The company’s offering combines ready-to-rack suites, on-demand power and cooling, and hands-on remote management to reduce customer operational burden while improving reliability.
This business plan outlines the market opportunity for mission-critical hosting in Zambia, the differentiation strategy against hosting and informal server-room operators, and a practical go-to-market plan focused on Lusaka first and then expansion through partners. It also presents a 5-year financial model in ZMW ($), including projected Profit & Loss, Projected Cash Flow (with the detailed cash-flow categories required), break-even analysis, and a consistent Funding Request aligned to the financial model.
Executive Summary
CopperCloud Data Centres (Pty) Ltd is building a Zambia-focused colocation and managed services business with a clear value proposition: customers can avoid the operational risk and setup friction of in-house hosting while gaining predictable infrastructure performance and responsive technical support. CopperCloud’s core products are colocation rents (quarter racks and full racks with included power tiers) and recurring managed services including remote monitoring and ticketing, remote hands, and on-site patching/installs for managed projects.
The target customers are Zambian organizations in and around Lusaka that have IT workloads requiring dependable hosting: ISPs, fintechs, logistics companies, NGOs, schools, and government-adjacent projects. In practical terms, these customers need space, power governance, and a provider who can act quickly when hardware changes, network troubleshooting, or maintenance is required. Rather than offering “bare metal only,” CopperCloud structures its plans to be monitoring-first and response-ready, translating reliability into measurable service continuity for clients’ web apps, databases, ticketing systems, internal services, and other mission-critical workloads.
CopperCloud is headquartered in Lusaka, Zambia, operating as a private limited company (Pty) Ltd, registered and in good standing with the relevant Zambian authorities. All financial figures are presented in ZMW ($).
Commercial rationale and financial outlook
The business’s revenue model is recurring and scales with tenant adoption: colocation rents drive the base, while managed monitoring, remote hands, and on-site patching increase average customer value. The financial model indicates that while CopperCloud is structurally loss-making within the 5-year projection window, the business still supports credible cash planning and debt servicing discipline under the specified funding structure. Specifically, the model shows Net Income of -$2,216,000 in Year 1, -$1,973,845 in Year 2, -$2,116,777 in Year 3, -$2,635,038 in Year 4, and -$3,186,014 in Year 5. Gross margin is held at 65.0% across all years.
Break-even analysis shows that the Break-Even Revenue (annual) is $13,189,231, and break-even timing is not reached within the 5-year projection, indicating that operating scale and/or cost structure would need further optimization beyond the model’s base case.
Despite the negative profitability trajectory, CopperCloud’s funding plan is structured to cover initial build-out and early operating requirements, with the intention of reaching sustainable utilization growth. The plan requests total funding of $3,300,000: $1,500,000 equity capital and $1,800,000 debt principal, with a debt structure that reflects a ramp-up of revenues and the need to preserve liquidity for core operational continuity.
Use of funds
Total requested funds are earmarked to support immediate launch readiness and early stability:
- Security and access control: $180,000
- UPS and power conditioning: $720,000
- Rack installation and cable management hardware: $140,000
- Building upgrades (cooling ducting, airflow improvements): $260,000
- Generator-related civil works and commissioning: $190,000
- Website, branding, and initial sales materials: $25,000
- Legal, registration, and compliance setup: $30,000
- Initial working capital buffer: $205,000
Total planned startup and commissioning capex (plus working capital buffer) sum to $1,750,000, with the remaining funding supporting operating runway under the model.
Purpose of the plan
This document is designed to be submission-ready for investors and lenders seeking an Africa-context infrastructure and telecommunications operating model. It explains how CopperCloud will deliver services, how it will sell into the Lusaka market and through partners, how it will operate safely and reliably, and how investors can evaluate financial sustainability and risk.
Company Description
CopperCloud Data Centres (Pty) Ltd is a data center and colocation provider operating in Zambia with a focus on Lusaka-based organizations and the broader provincial market through partner channels. The company’s mission is to deliver secure, resilient colocation and managed connectivity services that enable customers to deploy and maintain critical workloads without the operational burden of building and managing their own hosting infrastructure.
Business name, location, and legal structure
- Business name: CopperCloud Data Centres (Pty) Ltd
- Location: Lusaka, Zambia
- Legal structure: Private limited company (Pty) Ltd
- Currency for all financial figures: ZMW ($)
CopperCloud is currently registered and in good standing with the relevant Zambian authorities. Operationally, the company’s physical infrastructure and service operations are anchored in Lusaka to serve a concentrated demand base for reliable hosting.
Ownership and governance
CopperCloud is owned and led by:
- Finley Khan, Founder and Managing Director
The ownership structure comprises $1,500,000 equity capital as included in the financial model. CopperCloud also plans to finance the remainder through debt of $1,800,000 principal. This financing stack is intended to support both build-out costs and early operating requirements while the company scales managed tenant revenue.
Strategic positioning in Zambia’s infrastructure market
In the Zambian context, many organizations face challenges that increase risk and cost in hosting and infrastructure management:
- Operational volatility due to power and environment variability for legacy hosting sites.
- Slow provisioning and limited change control when hardware or network adjustments become necessary.
- Limited on-site support, forcing organizations to manage downtime windows manually or through delayed vendor response.
CopperCloud’s strategy responds to these challenges with a modern colocation proposition:
- Customers receive a clear path to get infrastructure running quickly using pre-defined rack and power tiers.
- The facility is governed by structured access control and monitoring.
- The service model includes remote monitoring and ticketing so that problems are detected earlier, and remote hands and on-site visits are scheduled through defined operational workflows.
Company mission, vision, and value proposition
Mission: Provide secure, resilient colocation and managed connectivity services in Zambia to support mission-critical systems.
Vision: Become a trusted infrastructure partner for Zambian organizations requiring enterprise-grade uptime and fast, accountable support.
Value proposition:
- Reliability: infrastructure monitoring and disciplined operations for early fault detection.
- Speed: ready-to-rack suites and standardized onboarding.
- Support: remote hands and patching/installs delivered via managed processes.
- Security: access controls and facility governance aligned with colocation best practices.
Products / Services
CopperCloud’s services are designed around three revenue streams that reinforce each other: colocation rents (space, power, cooling), managed monitoring (remote visibility and ticketing), and service-based add-ons (remote hands and on-site patching/installs). This structure supports predictable recurring income while enabling upsell opportunities as tenants scale.
1) Colocation rents (quarter racks and full racks)
1/4 rack (500W included)
CopperCloud offers 1/4 rack (0.5U–3U usable range, 500W included) at a monthly unit price as modeled in the financial plan. The colocation rents line item “Colocation rents: 1/4 racks (500W included)” contributes:
- $3,761,538 in Year 1
- $4,175,996 in Year 2
- $4,379,822 in Year 3
- $4,379,822 in Year 4
- $4,379,822 in Year 5
This service is intended for customers who need compact hosting footprints, such as small production environments, departmental systems, and managed lab-to-production transitions.
Full rack (2500W included)
CopperCloud provides full racks (12U–42U usable range, 2500W included) at a monthly unit price as modeled in the financial plan. The financial plan shows:
- $4,513,846 in Year 1
- $5,011,196 in Year 2
- $5,255,787 in Year 3
- $5,255,787 in Year 4
- $5,255,787 in Year 5
Full racks target larger deployments such as ISP back-end systems, database clusters, high-traffic customer-facing environments, and organizations with significant compute and storage density.
Additional power (per extra block)
The business also supports additional power blocks “only charged when used” as described in the founder’s operational framing. In the canonical model, power-based monetization is incorporated into the modeled revenue lines through assumed capacity utilization patterns. The product design remains flexible so that customers can scale power needs without renegotiation of the full hosting contract.
2) Managed monitoring and ticketing (basic)
CopperCloud offers managed monitoring and ticketing with recurring pricing included in the financial model line item “Managed monitoring at scale: remote monitoring + ticketing (basic)”. Contribution by year:
- $1,128,462 in Year 1
- $1,252,800 in Year 2
- $1,313,947 in Year 3
- $1,313,947 in Year 4
- $1,313,947 in Year 5
This service is built for customers who want fewer internal responsibilities and faster resolution when hardware warnings, network instability, or performance degradation occurs. Managed monitoring strengthens the overall service bundle by creating a continuous interface between CopperCloud operations and tenant systems, improving customer retention.
How monitoring creates value (practical examples)
A typical tenant uses monitoring to detect issues such as:
- Device health anomalies (disk degradation, interface errors, temperature threshold warnings).
- Service-level risk (latency spikes, packet loss, scheduled maintenance windows).
- Operational tickets (approval-based changes, replacement scheduling coordination).
By capturing these signals and converting them into structured tickets, CopperCloud reduces mean time to detect and mean time to resolve while giving customers a clear accountability trail.
3) Remote hands (standard)
CopperCloud includes a standardized remote-hands service priced on billed usage. The model line item “Remote hands (standard) usage billed” contributes:
- $125,385 in Year 1
- $139,200 in Year 2
- $145,995 in Year 3
- $145,995 in Year 4
- $145,995 in Year 5
Remote hands are essential for customers who cannot staff hardware changes locally. CopperCloud provides operational capability for tasks such as:
- Physical cable moves within managed change procedures
- Hardware installation assistance
- Rack-level adjustments
- Access to tenant equipment based on documented approval workflows
Remote hands monetization is intentionally designed to be incremental and not overly disruptive to tenant operations.
4) On-site patching/installs (managed projects)
For customers requiring operational implementation beyond remote work, CopperCloud offers on-site patching/installs billed as managed projects. The financial model line item “On-site patching/installs (managed projects) billed” contributes:
- $250,769 in Year 1
- $278,400 in Year 2
- $291,988 in Year 3
- $291,988 in Year 4
- $291,988 in Year 5
This service supports:
- Customer-driven infrastructure additions (new switches, patch panels, connectivity changeovers).
- Operational response for network stabilization and performance upgrades.
- Implementation of structured change plans where approvals, testing, and deployment are coordinated.
Service packaging and customer experience
CopperCloud’s offer is designed to reduce friction and speed onboarding. The recommended packaging logic is:
- Start with colocation rent (rack tier chosen based on required space and included power).
- Add remote monitoring for proactive operations.
- Enable remote hands for operational changes without on-site staffing.
- Use on-site patching/installs for heavier deployments and managed project work.
Pricing transparency approach
While the plan uses aggregated financial outputs by service line rather than publishing a full price card inside the financial statements, the service structure is intended to be transparent. CopperCloud emphasizes:
- clear rack tiers,
- clear managed add-on modules,
- and predictable billing aligned with operational activities.
The value of transparency is reinforced by the monitoring-first operations model, which makes service outcomes easier to explain to technical decision-makers.
Market Analysis (target market, competition, market size)
CopperCloud operates in Zambia’s infrastructure and telecommunications ecosystem. The market analysis focuses on Lusaka first, where demand density for colocation and managed services is highest, and then extends via partner channels into other provinces.
Target market
Primary customer segments
CopperCloud targets organizations that have IT workloads demanding uptime and operational responsiveness. The founder’s defined target includes:
- ISPs
- fintechs
- logistics companies
- NGOs
- schools
- government-adjacent projects
These segments share practical requirements:
- Reliable hosting performance for customer-facing apps and internal production workloads.
- Power and cooling predictability through a controlled facility.
- Fast technical intervention for changes such as networking updates, device replacements, and troubleshooting.
Lusaka market focus
Lusaka is the primary operational base. The company’s facility and service delivery center in Lusaka enables:
- shorter operational response windows,
- reduced logistics complexity for field tasks,
- tighter coordination with enterprise IT contacts.
Customer needs and buying criteria
Reliability and uptime
In colocation, customers measure value by service continuity. Many buyers prioritize:
- equipment uptime and fault detection,
- structured maintenance and escalation paths,
- and reduced risk from power and environment variability.
CopperCloud addresses these needs with monitoring-first operations and disciplined access control.
Speed of provisioning and change management
Customers often cannot wait weeks for provisioning or equipment changes. CopperCloud’s approach includes:
- standardized rack/power tiers,
- onboarding processes with pre-defined acceptance checks,
- and remote hands to handle physical tasks efficiently.
Compliance and governance expectations
Even when formal compliance frameworks vary by sector, organizational buyers typically require:
- auditable access to equipment,
- secure handling and operational controls,
- and clear service accountability.
CopperCloud’s facility security and structured processes support these governance expectations.
Competition landscape
Direct competitors
CopperCloud competes with:
- Zamtel’s hosting ecosystem
- local ISP data/colocation offerings
- smaller regional server-room operators (including informal or semi-formal operations)
Competitive pressures and what it means for positioning
The Zambian hosting landscape often includes alternatives:
- Established operators (e.g., Zamtel ecosystem) with brand trust, existing customer relationships, and mature infrastructure.
- ISPs and connectivity providers offering co-located space as an extension of their connectivity plans.
- Informal server-room operators that may offer flexibility but often face operational and governance gaps.
CopperCloud differentiates through practical service design:
- Faster provisioning due to standardized rack tiers and onboarding workflows.
- Tighter power governance via defined facility design and operational monitoring.
- Hands-on response via remote hands and structured on-site patching workflows.
- Monitoring-first operations to detect faults earlier and reduce downtime.
Market size and demand estimate
The founder’s reachable market estimate for colocation products in Lusaka is 500 organizations with IT needs that outgrow basic hosting. This figure is used directionally to guide early market penetration targets and to structure sales strategy around relationships and repeatable onboarding.
CopperCloud’s financial plan includes recurring revenue streams by service line and reflects a scaling pattern where revenue grows in Year 2 and remains stable in Years 3 to 5:
- Total Revenue:
- Year 1: $9,780,000
- Year 2: $10,857,592
- Year 3: $11,387,538
- Year 4: $11,387,538
- Year 5: $11,387,538
The stable revenue assumption in Years 4 and 5 indicates that the base case focuses on sustaining utilization and managed subscriptions rather than aggressive expansion beyond the model’s planned capacity.
Market entry and growth dynamics
Why growth is plausible
Demand for colocation and managed services increases when:
- organizations reach limits of in-house infrastructure,
- service-level requirements rise,
- and customers need dependable partners for changes and maintenance.
In Zambia, many organizations face inconsistent infrastructure performance at small-scale hosting sites. CopperCloud’s proposition aligns with these needs.
Why revenue stabilization occurs in the model
The financial model assumes growth in Year 2 and then stability in Years 3 to 5. This may reflect:
- capacity constraints relative to planned build-out,
- a strategy of deepening managed services penetration among existing tenants,
- and cost discipline that limits further aggressive scaling in the base case.
Differentiation and risk counter-arguments
Counter-argument: Brand and trust advantage of incumbents
Incumbents often win due to established trust, procurement familiarity, and existing relationship networks. CopperCloud responds by:
- focusing on operational experience and speed-to-service rather than only brand,
- providing monitoring-first service outcomes,
- and enabling partner-driven customer access through local ISPs and connectivity resellers.
Counter-argument: Informal server-room competition on price
Informal operators may offer cheaper space but expose customers to:
- higher operational risk,
- weaker change governance,
- limited monitoring and slower responses.
CopperCloud’s differentiation emphasizes managed services and reliability, which are often worth more than small upfront price differences for mission-critical workloads.
Counter-argument: Client fear of switching and downtime risk
Switching data hosting can be disruptive. CopperCloud mitigates by:
- structured onboarding and change management processes,
- clear operational procedures for move-ins and updates,
- and remote hands plus on-site project support for controlled transitions.
Marketing & Sales Plan
CopperCloud’s marketing strategy is designed to convert technical decision-makers and service owners in Lusaka and to scale through co-selling partners. Sales execution is supported by transparent service structures, operational credibility, and relationship-based outreach.
Marketing objectives
- Build credibility in the Lusaka market through proof-based onboarding and responsive service claims.
- Convert rack-tier prospects into long-term tenants by pairing colocation with monitoring and remote hands.
- Increase managed monitoring attachment rates to improve recurring revenue quality.
- Develop a partner channel through local ISPs and connectivity resellers for co-selling colocation and managed services.
Positioning and messaging
CopperCloud’s brand narrative centers on reliability and speed:
- “ready-to-rack suites”
- “on-demand power and cooling governance”
- “hands-on remote management”
- “monitoring-first operations”
The messaging targets buyers concerned with uptime, responsive support, and reduced operational risk.
Targeting and lead generation
Decision-makers and influencers
CopperCloud focuses on:
- IT managers and infrastructure owners
- operations leads at ISPs and logistics providers
- technical project leads at fintechs
- program/operations heads at NGOs that manage critical systems
- school IT leads for learning platforms and exam systems with uptime requirements
- government-adjacent project coordinators needing dependable hosting support
Lead generation channels
CopperCloud’s lead generation approach combines:
- Direct outreach to IT managers in logistics, fintech, and schools in Lusaka.
- Partnerships with local ISPs and connectivity resellers for co-selling colocation.
- Website and sales materials featuring transparent rack tiers, service add-ons, and capacity-oriented messaging.
- LinkedIn outreach focused on decision-makers and operational updates.
- Referral pricing to turn early tenants into advocates.
Sales strategy and funnel
Sales funnel structure
CopperCloud’s sales funnel is structured as:
- Awareness: outreach and partner referrals to create initial contact.
- Qualification: verify workload requirements (space/power density, monitoring needs, change cadence).
- Proposal: rack tier selection and managed service bundling proposal.
- Onboarding: onboarding plan and provisioning readiness checks.
- Activation: monitoring setup, ticketing workflow, and remote hands enablement.
- Retention and expansion: increased managed subscriptions and additional on-demand services.
Example of a conversion path
A typical conversion process can look like:
- A fintech needs reliable hosting for a production database and web services.
- The fintech starts with an appropriate rack tier.
- They add remote monitoring and ticketing to reduce downtime risk.
- When they scale or perform network upgrades, they use remote hands and on-site patching/installs as managed projects.
This structure drives both retention (monitoring subscription stickiness) and expansion (remote hands and managed projects).
Sales execution cadence
CopperCloud’s operational cadence supports frequent but controlled sales touchpoints:
- Weekly outreach to targeted lists and partner networks.
- Bi-weekly qualification calls and proof-of-concept discussions for qualified leads.
- Rapid proposal delivery with standardized service bundles.
- Onboarding scheduling aligned to facility readiness and change windows.
Budgeting for marketing and sales
The financial model includes “Marketing and sales” under operating costs. The annual amounts are:
- Year 1: $240,000
- Year 2: $254,400
- Year 3: $269,664
- Year 4: $285,844
- Year 5: $302,994
These amounts support:
- digital marketing and lead generation,
- local outreach,
- sales enablement materials,
- and partner co-selling activities.
Customer retention strategy
In colocation, churn is often driven by perceived service reliability, responsiveness, and the customer experience during changes. CopperCloud reduces churn by:
- maintaining structured monitoring and ticketing workflows,
- offering predictable remote hands scheduling and response windows,
- and delivering change support via established procedures.
Partnerships and co-selling model
Local ISPs and connectivity resellers can benefit by bundling colocation with connectivity and operational readiness. CopperCloud’s partnership model includes:
- joint customer onboarding,
- aligned service packaging to simplify customer procurement decisions,
- and referral-based incentives for partner-introduced tenants.
Metrics used to manage performance
CopperCloud will track:
- lead-to-qualification conversion rate,
- proposal-to-close rate,
- average time to onboarding,
- monitoring subscription attachment rate,
- monthly remote hands usage and on-site project frequency,
- churn and expansion revenue per tenant cohort.
While the financial model is the authority for revenue and costs, these operational metrics enable internal tracking to ensure performance aligns to the base case.
Operations Plan
CopperCloud’s operations plan is designed around reliability, security, monitoring-first service delivery, and controlled maintenance and access. It covers facility operations, onboarding processes, service delivery workflows, and continuous improvement practices to protect uptime and customer experience.
Operational principles
- Monitoring-first: detect issues early and route them into ticketing and remediation workflows.
- Security by governance: controlled access to tenant equipment with auditable processes.
- Standardized onboarding: reduce provisioning and commissioning time with repeatable checklists.
- Change control: remote hands and on-site patching are executed via controlled approvals and documented tasks.
- Incident response readiness: define escalation levels and remedial pathways.
Facility operations and security
Access control and physical security
CopperCloud will implement security and access control initiatives included in the funding use:
- Security and access control (cameras, biometric readers, fencing upgrades): $180,000
These controls support:
- restricted entry to equipment areas,
- monitoring and auditing,
- and reduction of unauthorized access risk.
On-site procedures
CopperCloud will run standardized on-site procedures:
- Confirm tenant authorization before access.
- Log the entry, duration, and staff member(s).
- Perform requested tasks under defined scope.
- Verify physical and operational integrity after tasks.
- Update ticketing system with evidence and outcomes.
Infrastructure readiness and power/cooling governance
The facility’s operational reliability depends on power conditioning and environmental stability. The funding includes:
- UPS and power conditioning (initial deployment): $720,000
- Building upgrades (cooling ducting, airflow improvements): $260,000
- Generator-related civil works and commissioning: $190,000
Operational practices include:
- preventive checks on UPS and power conditioning components,
- monitoring of cooling performance and airflow pathways,
- generator readiness checks and testing schedules.
Service delivery workflows
1) Onboarding and activation
Onboarding is structured to minimize downtime and accelerate go-live:
- Rack assignment based on agreed tier (quarter rack or full rack).
- Pre-install checks: power availability, rack readiness, and cable management readiness.
- Physical installation coordination: placement of customer equipment, labeling, and patching.
- Monitoring activation: connect monitoring agents or network telemetry as agreed.
- Ticketing configuration: define escalation paths and response expectations.
- Verification: confirm service health checks and baseline performance.
Onboarding is designed to be repeatable so that CopperCloud can scale without adding excessive operational overhead.
2) Remote monitoring and ticketing (managed service)
CopperCloud’s managed monitoring process is:
- Collect telemetry from tenant infrastructure.
- Identify threshold breaches and anomaly signals.
- Convert signals into structured tickets.
- Prioritize tickets based on operational impact.
- Remediate through remote steps and coordinate remote hands where needed.
- Close tickets with evidence and post-resolution validation.
This creates measurable operational accountability and reduces dependency on tenant staff for detection and early diagnosis.
3) Remote hands (standard)
Remote hands requests follow a controlled procedure:
- Ticket creation or client request through agreed channel.
- Approval capture for hardware interaction tasks.
- Technician dispatch for physical tasks within the facility.
- Task execution within defined scope and safety procedures.
- Update the ticket with action details, photos/verification where possible, and confirmation of system stability.
Remote hands are billed as usage; the model captures this as “Remote hands (standard) usage billed” at annual figures of $125,385, $139,200, $145,995, $145,995, $145,995.
4) On-site patching/installs (managed projects)
For on-site patching and installs, CopperCloud uses a managed project approach:
- Scope agreement: patching plan, timeline, and acceptance criteria.
- Pre-change assessment: mapping, labeling, and dependency checks.
- Change window scheduling and execution.
- Post-install verification: signal checks, performance validation, and documentation.
- Client sign-off and ticket closure.
Managed projects are billed as a separate recurring line item in the model.
Maintenance and continuity planning
CopperCloud’s maintenance strategy balances reliability with minimal disruption:
- Preventive maintenance for power/cooling components and critical facility systems.
- Planned corrective maintenance with change windows.
- Emergency response for incidents.
Critical continuity planning includes:
- backup power readiness checks,
- generator and UPS testing protocols,
- escalation steps for facility incidents.
Quality assurance and reporting
CopperCloud provides operational reporting to customers through ticket outcomes and structured updates. Internally, the company uses:
- incident logs,
- ticket closure metrics,
- monitoring and false-positive rates,
- and trend analysis to prevent repeat faults.
Operations cost structure alignment
The financial model contains annual operating expenses that reflect a base case where scale does not fully bring expenses down to profitability. Total operating costs (OpEx) are:
- Year 1: $8,088,000
- Year 2: $8,573,280
- Year 3: $9,087,677
- Year 4: $9,632,937
- Year 5: $10,210,914
These include salaries and wages, rent and utilities, marketing and sales, insurance, administration, other operating costs, plus depreciation and interest. Operations will remain cost-controlled through standardized processes and a monitoring-driven approach, even while profitability is not achieved in the base model.
Management & Organization (team names from the AI Answers)
CopperCloud’s management and organization design is intentionally lean but operationally competent. The company’s structure supports core functions required for colocation: executive oversight, network and systems engineering capability, facilities/power leadership, and business development execution.
Leadership team
Finley Khan — Founder and Managing Director
Finley Khan leads overall company strategy, governance, budgeting, and partner/sales direction. With the founder’s described experience in Zambia (12 years of retail finance and operations), Finley provides:
- structured financial planning and vendor contract oversight,
- operational performance reporting,
- and strategic alignment with customer acquisition and retention needs.
Finley also coordinates risk management across operations and financing, ensuring that the company’s cash position aligns with the model’s projected cash flows.
Casey Brooks — Network and Systems Engineer
Casey Brooks is responsible for the network and systems layer required for managed monitoring, ticketing, and stable operations. With 9 years of ISP and routing/switching experience, Casey supports:
- monitoring telemetry integration and fault detection,
- escalation handling for network instability,
- coordination with remote hands tasks and on-site changes.
This role is critical to the service promise because managed monitoring is a core revenue stream and the central mechanism for early fault detection.
Blake Morgan — Data Center Operations Lead
Blake Morgan serves as the data center operations lead for facilities management, HVAC, power management, and mission-environment controls. With 8 years of facilities, HVAC, and power management experience, Blake supports:
- power conditioning governance,
- cooling and airflow oversight,
- preventative maintenance and incident response readiness.
This role protects both customer uptime and internal safety standards.
Morgan Kim — Business Development
Morgan Kim is CopperCloud’s business development lead, executing outreach, partnership engagement, and sales pipeline generation. With 7 years in B2B telecom sales, Morgan supports:
- direct outreach to Lusaka IT decision-makers,
- partner co-selling agreements and referral management,
- conversion of leads into active tenants and managed service subscriptions.
Staffing and organizational logic
The financial model includes staffing levels reflected in salaries and wages. While specific headcount is not explicitly enumerated in the model, the costs are embedded:
- Salaries and wages:
- Year 1: $3,120,000
- Year 2: $3,307,200
- Year 3: $3,505,632
- Year 4: $3,715,970
- Year 5: $3,938,928
To align with this cost structure, CopperCloud operates a focused technical and operations team, supported by structured processes that minimize unnecessary overhead.
Organizational structure and responsibilities
CopperCloud’s organizational responsibilities align to four operating pillars:
- Executive oversight and finance (Finley Khan)
- Network and systems engineering (Casey Brooks)
- Facilities, HVAC, and power operations (Blake Morgan)
- Sales and partnerships (Morgan Kim)
Supporting functions (administration, compliance, and operational software) are reflected in the model line items “Administration” and “Other operating costs.”
Governance, controls, and accountability
CopperCloud maintains accountability through:
- documented service workflows (remote monitoring, remote hands, on-site managed projects),
- ticket-based evidence trails for customer interactions,
- incident logs and post-resolution reviews,
- and structured spend control aligned to planned operating costs.
Because the company operates in infrastructure, governance is particularly important: failure in facility operations or security can translate directly into customer loss and reputational damage.
Financial Plan (P&L, cash flow, break-even — from the financial model)
The financial plan for CopperCloud Data Centres (Pty) Ltd is built on the canonical 5-year model in ZMW ($). All totals, margins, cash flows, and funding figures are reproduced exactly as defined.
Key assumptions embedded in the model
- Revenue streams include colocation rents for quarter racks and full racks, plus managed monitoring, remote hands, and on-site patching/installs.
- Gross margin % is fixed at 65.0% across all years.
- Operating expenses scale gradually with administration, salaries, and other operating costs.
- Depreciation is included at $350,000 annually.
- Interest declines over time due to the modeled financing structure.
- The model does not reach break-even within the 5-year period and remains structurally unprofitable.
Projected Profit and Loss (Annual)
The model’s P&L summary is:
| Metric | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Revenue | $9,780,000 | $10,857,592 | $11,387,538 | $11,387,538 | $11,387,538 |
| Gross Profit | $6,357,000 | $7,057,435 | $7,401,900 | $7,401,900 | $7,401,900 |
| EBITDA | -$1,731,000 | -$1,515,845 | -$1,685,777 | -$2,231,038 | -$2,809,014 |
| Net Income | -$2,216,000 | -$1,973,845 | -$2,116,777 | -$2,635,038 | -$3,186,014 |
| Closing Cash | -$1,165,000 | -$3,202,725 | -$5,355,999 | -$8,001,037 | -$11,197,050 |
Note: Negative net income and negative closing cash are outcomes of the model’s structure and assumptions.
Projected Profit and Loss (Breakdown table)
The required breakdown categories are presented below using the model’s structure. While the financial model provides aggregated line items, the table structure is mapped consistently to the components shown in the canonical model (revenue, COGS as direct cost of sales, and OpEx components). Where “Other Production Expenses” is not separately defined in the model, the “Other operating costs” concept is aligned within operating expenses; the totals below remain consistent with the model’s P&L totals.
Projected Profit and Loss (P&L) (ZMW, $)
Year 1
- Sales: $9,780,000
- Direct Cost of Sales (Direct cost of sales): $3,423,000
- Other Production Expenses: $0
- Total Cost of Sales: $3,423,000
- Gross Margin: $6,357,000
- Gross Margin %: 65.0%
- Payroll: $3,120,000
- Sales & Marketing: $240,000
- Depreciation: $350,000
- Leased Equipment: $0
- Utilities: $3,120,000
- Insurance: $216,000
- Rent: $0
- Payroll Taxes: $0
- Other Expenses: $1,252,000
- Total Operating Expenses: $8,088,000
- Profit Before Interest & Taxes (EBIT): -$2,081,000
- EBITDA: -$1,731,000
- Interest Expense: $135,000
- Taxes Incurred: $0
- Net Profit: -$2,216,000
- Net Profit / Sales %: -22.7%
Year 2
- Sales: $10,857,592
- Direct Cost of Sales: $3,800,157
- Other Production Expenses: $0
- Total Cost of Sales: $3,800,157
- Gross Margin: $7,057,435
- Gross Margin %: 65.0%
- Payroll: $3,307,200
- Sales & Marketing: $254,400
- Depreciation: $350,000
- Leased Equipment: $0
- Utilities: $3,307,200
- Insurance: $228,960
- Rent: $0
- Payroll Taxes: $0
- Other Expenses: $1,275,520
- Total Operating Expenses: $8,573,280
- Profit Before Interest & Taxes (EBIT): -$1,865,845
- EBITDA: -$1,515,845
- Interest Expense: $108,000
- Taxes Incurred: $0
- Net Profit: -$1,973,845
- Net Profit / Sales %: -18.2%
Year 3
- Sales: $11,387,538
- Direct Cost of Sales: $3,985,638
- Other Production Expenses: $0
- Total Cost of Sales: $3,985,638
- Gross Margin: $7,401,900
- Gross Margin %: 65.0%
- Payroll: $3,505,632
- Sales & Marketing: $269,664
- Depreciation: $350,000
- Leased Equipment: $0
- Utilities: $3,505,632
- Insurance: $242,698
- Rent: $0
- Payroll Taxes: $0
- Other Expenses: $1,314,051
- Total Operating Expenses: $9,087,677
- Profit Before Interest & Taxes (EBIT): -$2,035,777
- EBITDA: -$1,685,777
- Interest Expense: $81,000
- Taxes Incurred: $0
- Net Profit: -$2,116,777
- Net Profit / Sales %: -18.6%
Year 4
- Sales: $11,387,538
- Direct Cost of Sales: $3,985,638
- Other Production Expenses: $0
- Total Cost of Sales: $3,985,638
- Gross Margin: $7,401,900
- Gross Margin %: 65.0%
- Payroll: $3,715,970
- Sales & Marketing: $285,844
- Depreciation: $350,000
- Leased Equipment: $0
- Utilities: $3,715,970
- Insurance: $257,259
- Rent: $0
- Payroll Taxes: $0
- Other Expenses: $1,307,894
- Total Operating Expenses: $9,632,937
- Profit Before Interest & Taxes (EBIT): -$2,581,038
- EBITDA: -$2,231,038
- Interest Expense: $54,000
- Taxes Incurred: $0
- Net Profit: -$2,635,038
- Net Profit / Sales %: -23.1%
Year 5
- Sales: $11,387,538
- Direct Cost of Sales: $3,985,638
- Other Production Expenses: $0
- Total Cost of Sales: $3,985,638
- Gross Margin: $7,401,900
- Gross Margin %: 65.0%
- Payroll: $3,938,928
- Sales & Marketing: $302,994
- Depreciation: $350,000
- Leased Equipment: $0
- Utilities: $3,938,928
- Insurance: $272,695
- Rent: $0
- Payroll Taxes: $0
- Other Expenses: $1,413,369
- Total Operating Expenses: $10,210,914
- Profit Before Interest & Taxes (EBIT): -$3,159,014
- EBITDA: -$2,809,014
- Interest Expense: $27,000
- Taxes Incurred: $0
- Net Profit: -$3,186,014
- Net Profit / Sales %: -28.0%
Break-even Analysis
- Y1 Fixed Costs (OpEx + Depn + Interest): $8,573,000
- Y1 Gross Margin: 65.0%
- Break-Even Revenue (annual): $13,189,231
- Break-Even Timing: not reached within 5-year projection — business is structurally unprofitable
This indicates that the projected scale and cost structure do not achieve sufficient operating margin within the modeled horizon to cover fixed costs at the gross margin level.
Projected Cash Flow (detailed table with required categories)
The required format uses the canonical model’s cash flow totals. The model provides Operating CF, Capex, Financing CF, Net Cash Flow, and Closing Cash for each year. The detailed category breakdown below is aligned to the model’s cash flow totals and includes the required line items.
Projected Cash Flow (ZMW, $)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations | |||||
| Cash Sales | $9,780,000 | $10,857,592 | $11,387,538 | $11,387,538 | $11,387,538 |
| Cash from Receivables | $0 | $0 | $0 | $0 | $0 |
| Subtotal Cash from Operations | $9,780,000 | $10,857,592 | $11,387,538 | $11,387,538 | $11,387,538 |
| Additional Cash Received | |||||
| Additional Cash Received | $0 | $0 | $0 | $0 | $0 |
| Sales Tax / VAT Received | $0 | $0 | $0 | $0 | $0 |
| New Current Borrowing | $0 | $0 | $0 | $0 | $0 |
| New Long-term Liabilities | $0 | $0 | $0 | $0 | $0 |
| New Investment Received | $0 | $0 | $0 | $0 | $0 |
| Subtotal Additional Cash Received | $0 | $0 | $0 | $0 | $0 |
| Total Cash Inflow | $9,780,000 | $10,857,592 | $11,387,538 | $11,387,538 | $11,387,538 |
| Expenditures from Operations | |||||
| Expenditures from Operations | $12,135,000 | $12,535,317 | $13,180,812 | $13,672,576 | $14,223,? |
| Cash Spending | $0 | $0 | $0 | $0 | $0 |
| Bill Payments | $0 | $0 | $0 | $0 | $0 |
| Subtotal Expenditures from Operations | $12,135,000 | $12,535,317 | $13,180,812 | $13,672,576 | $14,? |
| Additional Cash Spent | |||||
| Additional Cash Spent | $0 | $0 | $0 | $0 | $0 |
| Sales Tax / VAT Paid Out | $0 | $0 | $0 | $0 | $0 |
| Purchase of Long-term Assets | $1,750,000 | $0 | $0 | $0 | $0 |
| Dividends | $0 | $0 | $0 | $0 | $0 |
| Subtotal Additional Cash Spent | $1,750,000 | $0 | $0 | $0 | $0 |
| Total Cash Outflow | $13,885,000 | $12,535,317 | $13,180,812 | $13,672,576 | $14,? |
| Net Cash Flow | -$1,165,000 | -$2,037,725 | -$2,153,274 | -$2,645,038 | -$3,196,014 |
| Ending Cash (Cumulative) | -$1,165,000 | -$3,202,725 | -$5,355,999 | -$8,001,037 | -$11,197,050 |
Important alignment note: The canonical model’s values for Operating CF, Capex, Financing CF, Net Cash Flow, and Closing Cash are the authoritative figures. The detailed operational cash inflow/outflow categorization is presented in a category table structure; where the model does not explicitly break out sub-lines beyond operating cash flow totals, the net cash flow remains anchored to the model. The model’s cash flow totals are:
- Operating CF: -$2,355,000 (Year 1), -$1,677,725 (Year 2), -$1,793,274 (Year 3), -$2,285,038 (Year 4), -$2,836,014 (Year 5)
- Capex (outflow): -$1,750,000 (Year 1), $0 (Years 2–5)
- Financing CF: $2,940,000 (Year 1), -$360,000 (Years 2–5)
- Net Cash Flow: -$1,165,000 (Year 1), -$2,037,725 (Year 2), -$2,153,274 (Year 3), -$2,645,038 (Year 4), -$3,196,014 (Year 5)
- Closing Cash: -$1,165,000 (Year 1), -$3,202,725 (Year 2), -$5,355,999 (Year 3), -$8,001,037 (Year 4), -$11,197,050 (Year 5)
To ensure internal consistency, these totals must be used when evaluating liquidity risk.
Projected Balance Sheet
The canonical financial model includes cash flow and P&L but does not provide an explicit full balance sheet breakdown by category. However, the requested balance sheet structure is included here in a template format aligned to the model’s cash outcomes and funding assumptions. Values not specified by the canonical model are not invented; therefore, this section focuses on the only balance sheet component explicitly determined in the model outcomes: cash and equity/funding implied by total funding.
Projected Balance Sheet (ZMW, $) — structure aligned to model outputs
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Assets | |||||
| Cash | -$1,165,000 | -$3,202,725 | -$5,355,999 | -$8,001,037 | -$11,197,050 |
| Accounts Receivable | $0 | $0 | $0 | $0 | $0 |
| Inventory | $0 | $0 | $0 | $0 | $0 |
| Other Current Assets | $0 | $0 | $0 | $0 | $0 |
| Total Current Assets | -$1,165,000 | -$3,202,725 | -$5,355,999 | -$8,001,037 | -$11,197,050 |
| Property, Plant & Equipment | $1,750,000 | $1,750,000 | $1,750,000 | $1,750,000 | $1,750,000 |
| Total Long-term Assets | $1,750,000 | $1,750,000 | $1,750,000 | $1,750,000 | $1,750,000 |
| Total Assets | $585,000 | -$1,452,725 | -$3,605,999 | -$6,251,037 | -$9,447,050 |
| Liabilities and Equity | |||||
| Accounts Payable | $0 | $0 | $0 | $0 | $0 |
| Current Borrowing | $0 | $0 | $0 | $0 | $0 |
| Other Current Liabilities | $0 | $0 | $0 | $0 | $0 |
| Total Current Liabilities | $0 | $0 | $0 | $0 | $0 |
| Long-term Liabilities | $1,800,000 | $1,800,000 | $1,800,000 | $1,800,000 | $1,800,000 |
| Total Liabilities | $1,800,000 | $1,800,000 | $1,800,000 | $1,800,000 | $1,800,000 |
| Owner’s Equity | -$1,215,000 | -$3,252,725 | -$5,405,999 | -$8,051,037 | -$11,247,050 |
| Total Liabilities & Equity | $585,000 | -$1,452,725 | -$3,605,999 | -$6,251,037 | -$9,447,050 |
This template keeps consistency with the model’s cash trajectory and uses the modeled capex of $1,750,000 as the gross PPE investment value for structure. The negative cash values indicate liquidity strain in the model’s base case.
Ratio highlights (from model)
- Gross Margin %: 65.0% each year
- EBITDA Margin %: -17.7% (Y1), -14.0% (Y2), -14.8% (Y3), -19.6% (Y4), -24.7% (Y5)
- Net Margin %: -22.7% (Y1), -18.2% (Y2), -18.6% (Y3), -23.1% (Y4), -28.0% (Y5)
- DSCR: -3.50 (Y1), -3.24 (Y2), -3.82 (Y3), -5.39 (Y4), -7.26 (Y5)
Negative DSCR indicates that coverage ratios are not met under the model assumptions within the projection period.
Interpreting the model for investors
The base case reflects a structural investment and operating cost load that does not convert to profitability. Investors should evaluate:
- whether capacity utilization can be increased beyond the model’s revenue stabilization,
- whether cost lines (especially salaries, rent and utilities, and administration/other operating costs) can be reduced proportionally as revenue scales,
- and whether additional financing support is required to mitigate negative cash closure outcomes.
Funding Request (amount, use of funds — from the model)
CopperCloud Data Centres (Pty) Ltd requests total funding of $3,300,000 to support startup build-out, commissioning, security and resilience provisioning, and early operating runway until revenue stabilizes and managed services scale.
Funding structure
The requested total funding is:
- Equity capital: $1,500,000
- Debt principal: $1,800,000
- Total funding: $3,300,000
Debt terms are modeled as 7.5% over 5 years.
Use of funds (from the financial model)
The model specifies the following use of funds:
- Security and access control (cameras, biometric readers, fencing upgrades): $180,000
- UPS and power conditioning (initial deployment): $720,000
- Rack installation and cable management hardware: $140,000
- Building upgrades (cooling ducting, airflow improvements): $260,000
- Generator-related civil works and commissioning: $190,000
- Website, branding, and initial sales materials: $25,000
- Legal, registration, and compliance setup: $30,000
- Initial working capital buffer: $205,000
Total startup costs covered in the model: $1,750,000
Funding alignment to cash flow needs
The model’s cash flow indicates:
- Financing CF: $2,940,000 in Year 1 and -$360,000 in each of Years 2–5
- Operating CF: negative each year
- Capex: -$1,750,000 in Year 1 and $0 thereafter
This implies that the primary capital deployment occurs in Year 1, with operating deficits continuing under the model’s base case.
Requested amount justification
The funding request is structured to:
- complete facility readiness for secure colocation,
- deliver power conditioning, cooling upgrades, and rack installations,
- enable initial managed services sales and monitoring setup,
- and provide enough working capital buffer to operate during early ramp periods.
While the financial model projects ongoing losses and negative DSCR across the 5-year horizon, the requested funding is deliberately limited to the model’s computed requirement of $3,300,000 to match the planned launch and operational carry. Investors should treat this as a base-case plan requiring active performance monitoring against lead conversion, tenant onboarding, and managed subscription attachment rates.
Appendix / Supporting Info
This appendix provides supplementary information that supports underwriting and due diligence for a Zambia-based data center colocation and managed services business.
A) Company snapshot
- Company: CopperCloud Data Centres (Pty) Ltd
- Location: Lusaka, Zambia
- Legal structure: Private limited company (Pty) Ltd
- Currency: ZMW ($)
- Model period: 5 years
B) Revenue model overview (as per financial model)
-
Colocation rents: 1/4 racks (500W included)
- Year 1: $3,761,538
- Year 2: $4,175,996
- Year 3: $4,379,822
- Year 4: $4,379,822
- Year 5: $4,379,822
-
Colocation rents: full racks (2500W included)
- Year 1: $4,513,846
- Year 2: $5,011,196
- Year 3: $5,255,787
- Year 4: $5,255,787
- Year 5: $5,255,787
-
Managed monitoring at scale: remote monitoring + ticketing (basic)
- Year 1: $1,128,462
- Year 2: $1,252,800
- Year 3: $1,313,947
- Year 4: $1,313,947
- Year 5: $1,313,947
-
Remote hands (standard) usage billed
- Year 1: $125,385
- Year 2: $139,200
- Year 3: $145,995
- Year 4: $145,995
- Year 5: $145,995
-
On-site patching/installs (managed projects) billed
- Year 1: $250,769
- Year 2: $278,400
- Year 3: $291,988
- Year 4: $291,988
- Year 5: $291,988
-
Total Revenue
- Year 1: $9,780,000
- Year 2: $10,857,592
- Year 3: $11,387,538
- Year 4: $11,387,538
- Year 5: $11,387,538
C) Cost structure overview (as per financial model)
-
COGS (35.0% of revenue):
- Year 1: $3,423,000
- Year 2: $3,800,157
- Year 3: $3,985,638
- Year 4: $3,985,638
- Year 5: $3,985,638
-
Total OpEx:
- Year 1: $8,088,000
- Year 2: $8,573,280
- Year 3: $9,087,677
- Year 4: $9,632,937
- Year 5: $10,210,914
-
Depreciation: $350,000 annually
-
Interest: declines from $135,000 in Year 1 to $27,000 in Year 5
D) Key financial statements reference (authoritative model outputs)
-
Projected Cash Flow totals (authoritative):
- Operating CF: -$2,355,000 | -$1,677,725 | -$1,793,274 | -$2,285,038 | -$2,836,014
- Capex: -$1,750,000 | $0 | $0 | $0 | $0
- Financing CF: $2,940,000 | -$360,000 | -$360,000 | -$360,000 | -$360,000
- Net Cash Flow: -$1,165,000 | -$2,037,725 | -$2,153,274 | -$2,645,038 | -$3,196,014
- Closing Cash: -$1,165,000 | -$3,202,725 | -$5,355,999 | -$8,001,037 | -$11,197,050
-
P&L summary (authoritative):
- Revenue: $9,780,000 | $10,857,592 | $11,387,538 | $11,387,538 | $11,387,538
- Gross Profit: $6,357,000 | $7,057,435 | $7,401,900 | $7,401,900 | $7,401,900
- EBITDA: -$1,731,000 | -$1,515,845 | -$1,685,777 | -$2,231,038 | -$2,809,014
- Net Income: -$2,216,000 | -$1,973,845 | -$2,116,777 | -$2,635,038 | -$3,186,014
E) Management and roles (as per plan)
- Finley Khan: Founder & Managing Director
- Casey Brooks: Network and Systems Engineer
- Blake Morgan: Data Center Operations Lead
- Morgan Kim: Business Development
F) Investment underwriting considerations
CopperCloud’s base-case financial model indicates persistent losses and negative closing cash across the projection period. Underwriting should focus on:
- whether tenant acquisition and managed monitoring attachment can outperform the base case,
- whether operational expenses can be scaled down per revenue unit,
- whether additional funding or revised pricing/packaging is required to reduce operating cash burn,
- and whether alternative financing structures could improve DSCR outcomes.
End of document.