Transport dispatch is at the heart of logistics performance in Zimbabwe. Yet many fleet operators still coordinate jobs through WhatsApp messages, phone calls, and spreadsheets—processes that are slow, error-prone, and difficult to audit. Delays, wrong vehicle assignments, weak proof-of-delivery, and poor visibility over delivery status directly translate into cost overruns and customer churn.
DispatchFlow Technologies (Pty) Ltd (“DispatchFlow”) is building a dispatch-first Transport Dispatch Software platform designed specifically for Zimbabwean operating realities. The system helps logistics operators plan routes, allocate vehicles to jobs, dispatch drivers with live status updates, and collect proof-of-delivery in a structured workflow rather than informal messaging chains. By replacing ad-hoc coordination with a unified operating layer, DispatchFlow reduces operational friction and increases delivery reliability.
This business plan outlines the company’s strategy, market opportunity, product scope, go-to-market approach, operations plan, management structure, and a five-year financial projection model. The financial plan is based on an investor-ready subscription SaaS model with blended package revenue, cost controls, and an explicit path to break-even within Year 1.
Executive Summary
DispatchFlow Technologies (Pty) Ltd is a Harare-based dispatch workflow and dispatch execution software business targeting logistics operators across Zimbabwe—especially within Harare and the primary corridors to Bulawayo, Mutare, and Gweru. DispatchFlow helps transport and logistics companies move from manual coordination (WhatsApp chains, phone calls, and spreadsheets) to a dispatch operating system that supports planning, vehicle-to-job allocation, driver dispatch with live updates, and proof-of-delivery workflows.
The problem is structural. Zimbabwean transport operations often run under constrained capacity and uneven network connectivity. In this environment, manual dispatch processes create avoidable errors: a job may be assigned to the wrong vehicle, delivery progress can be unclear until the driver is reached by phone, and proof-of-delivery can be delayed or disputed. These failures drive costs through rework, fuel inefficiency, customer service escalations, and lost repeat contracts. While some market offerings focus on basic tracking, they do not solve the end-to-end dispatch workflow: converting demand into assigned jobs, operationalizing route plans, executing driver instructions, and capturing delivery evidence.
DispatchFlow’s answer is a dispatch-first SaaS subscription model priced in USD to support Zimbabwe’s cashflow and foreign-currency operational needs. Customers purchase one of three packages based on fleet size and dispatch team usage: Starter (up to 10 vehicles) at US$ 240/month, Growth (up to 30 vehicles) at US$ 520/month, and Fleet (up to 60 vehicles) at US$ 900/month. Deployment is supported by add-ons including Onboarding & setup (one-off) at US$ 350 per customer, SMS/WhatsApp proof-of-delivery notifications (monthly) at US$ 70 per customer, and Advanced routing + driver app configuration (one-off) at US$ 250 per deployment.
The financial model projects Year 1 revenue of US$ 3,960,000 with gross profit of US$ 3,168,000, EBITDA of US$ 1,731,000, and net income of US$ 1,325,304. The model’s costs include COGS at 20.0% of revenue, operating expense items such as rent, salaries, marketing, insurance, and other operating costs, plus depreciation and interest. Break-even analysis in the model indicates that the company reaches break-even within Year 1, specifically at Month 1, with annual break-even revenue of US$ 1,863,000 against Year 1 fixed costs (OpEx + Depn + Interest) of US$ 1,490,400.
DispatchFlow is raising US$ 250,000 total funding, consisting of US$ 110,000 equity and a US$ 140,000 SME loan (debt principal). Funds are allocated to product stability and dispatch workflow modules, infrastructure and security reserve, onboarding capacity, working capital for lean operation through initial traction, and marketing launch execution. The funding strategy aligns with the model’s cash generation: projected operating cash flow increases meaningfully across the five-year horizon, and ending cash balances rise from the initial closing position through Year 5.
The company’s five-year projections show revenue growth from US$ 3,960,000 in Year 1 to US$ 12,051,335 in Year 5, driven by consistent blended subscription scaling (model growth rate of 32.1% per year). Net income increases accordingly to US$ 6,205,438 in Year 5, supported by a maintained 80.0% gross margin assumption and an EBITDA margin profile that expands over time.
Investors evaluate dispatch technology not only on product vision but on execution capacity: team capability, delivery workflow design discipline, and the ability to sell and retain within Zimbabwe’s logistics market. DispatchFlow’s management team is built from deep operations and dispatch experience, engineering and integration capability, customer success training, partnerships expertise, and cloud security and DevOps reliability. This blend is intended to deliver both product quality and commercial traction—so that the business can scale beyond pilots into contracted deployments with recurring revenue.
Company Description (business name, location, legal structure, ownership)
DispatchFlow Technologies (Pty) Ltd is a private company incorporated in Zimbabwe as a private company (Pty) Ltd. The company is located in Harare, Zimbabwe, and operates from a small office in the Harare logistics belt where onboarding, customer support coordination, and training are handled. While core operations are anchored in Harare, DispatchFlow provides remote coverage for customers in Bulawayo and other corridor regions, ensuring that dispatch workflows work across the geography where Zimbabwe’s logistics demand concentrates.
Business mission and strategic intent
DispatchFlow’s mission is to help Zimbabwean logistics operators reduce delivery delays and operational errors by replacing manual dispatch coordination with a dispatch execution platform. The platform’s strategic intent is to become the operating system for dispatch teams—bridging the gap between planning, vehicle assignment, driver execution, live status reporting, and proof-of-delivery evidence.
The company’s value proposition is not limited to visibility of location. Many operators have tried tracking tools, but they often still manage dispatch through separate manual steps. DispatchFlow instead integrates dispatch workflow execution into one operating layer designed around how dispatch teams work in Zimbabwe: fast decisions, limited staff capacity, uneven connectivity, and the need for delivery evidence that is both reliable and easy to verify.
Ownership and control
DispatchFlow is owned by Imani Reddy, who serves as Founder / Owner. The ownership structure is designed to enable operational control, enforce accountability for unit economics, and maintain clarity on customer acquisition and delivery performance.
The funding plan includes a mix of founder equity and an SME loan to support product completion and launch readiness. This structure is intended to reduce dilution while preserving financial flexibility for early scaling.
Location and market coverage
The company’s operational hub is in Harare, reflecting the density of logistics operators and the practicality of conducting onboarding and training sessions with teams managing daily dispatch. DispatchFlow also supports customers on corridor routes, including freight movement patterns that affect service levels for logistics operators traveling between Harare and other hubs.
To remain consistent with the company’s market focus and go-to-market plan, DispatchFlow’s initial commercial efforts prioritize customers in Harare and corridor operations to Bulawayo, Mutare, and Gweru. This allows DispatchFlow to standardize its onboarding playbooks, test workflows under real conditions, and build case studies based on measurable improvements to dispatch reliability.
Legal and operational readiness
As a Zimbabwe-registered private company (Pty) Ltd, DispatchFlow operates with a local tax profile and charges subscription services in USD. Pricing in USD supports fleet operators who plan and budget in currency aligned with hardware procurement and service costs, reducing payment friction and supporting predictable revenue recognition.
The company’s operations include customer onboarding and support responsibilities handled from Harare, with an emphasis on dependable service delivery and responsive training so that dispatch teams adopt and retain the platform. This customer success focus is critical to turning dispatch software into recurring revenue rather than a one-off procurement.
Why “dispatch workflow” matters versus “tracking”
Transport operators already use multiple tools: basic tracking, spreadsheets, and messaging. The differentiation for DispatchFlow is the workflow layer: taking dispatch from planning into execution, and execution into proof-of-delivery evidence. This reduces errors in allocation and improves delivery status reporting. It also ensures that operational managers can review dispatch outcomes, enabling process improvements and accountability.
In Zimbabwe’s operational environment, dispatch reliability and evidence handling can determine contract renewals. DispatchFlow’s product approach supports operational discipline and creates an auditable dispatch workflow, which is particularly valuable for logistics companies that must report delivery performance to clients.
Products / Services
DispatchFlow Technologies delivers a dispatch execution SaaS platform tailored for transport operations in Zimbabwe. The product is designed around a dispatch team’s daily workflow: receiving job requirements, planning and allocating vehicles, dispatching drivers with structured instructions, monitoring live status updates, and capturing proof-of-delivery. Rather than positioning as “yet another tracker,” DispatchFlow functions as a dispatch operating system for logistics teams.
Core modules and how they solve operational problems
DispatchFlow’s software is built around several interlocking modules:
-
Route planning and dispatch preparation
- Create or import job requirements and route expectations.
- Support route selection aligned to the realities of delivery corridors and turnaround constraints.
- Enable dispatch teams to prepare dispatch orders without switching between documents and messaging threads.
-
Vehicle allocation and job assignment
- Assign the right vehicle to the right job based on fleet availability and operational fit.
- Reduce wrong-vehicle assignments that commonly happen when dispatch relies on manual coordination.
- Provide a structured job record that links vehicle assignment, dispatch timing, and delivery outcomes.
-
Driver dispatch with live updates
- Dispatch instructions are sent to drivers in a structured way so drivers receive consistent tasks.
- Drivers can update job status during execution; dispatch teams see progress without repeated phone calls.
- Live updates improve escalation speed and reduce downtime when operational issues occur.
-
Proof-of-delivery (POD) workflows
- Support structured POD capture so deliveries can be verified.
- Provide configurable notification workflows via SMS/WhatsApp to prompt delivery evidence submission and reduce missing POD issues.
- Improve dispute handling by storing delivery evidence more systematically than scattered message screenshots.
These modules are designed to reduce the three high-frequency dispatch failure modes:
- Wrong assignment (vehicle mismatch or job misallocation),
- Unclear delivery status (dispatch team doesn’t know progress without chasing drivers),
- Weak POD (delivery evidence delayed, missing, or hard to verify).
SaaS pricing model (USD)
DispatchFlow charges a subscription SaaS price in USD. Pricing is based on active fleet vehicles and dispatch team usage. The packages are designed to fit the typical range of transport operators:
- Starter (up to 10 vehicles): US$ 240/month
- Growth (up to 30 vehicles): US$ 520/month
- Fleet (up to 60 vehicles): US$ 900/month
The model assumes subscription revenue as the primary revenue stream over the five-year projection.
Add-ons and deployment services
DispatchFlow also offers add-ons that support real adoption and service differentiation:
-
Onboarding & setup (one-off): US$ 350 per customer
- Setup includes configuration of jobs, dispatch workflow roles, and standard operating templates.
-
SMS/WhatsApp proof-of-delivery notifications (monthly): US$ 70 per customer
- Notifications improve POD compliance by prompting drivers and coordinators at key stages of delivery execution.
-
Advanced routing + driver app configuration (one-off): US$ 250 per deployment
- This add-on is for deployments that require route logic and driver app configuration refinements based on job patterns and operating constraints.
Product design for Zimbabwe’s constraints
DispatchFlow’s product approach acknowledges that dispatch teams operate under constraints common in Zimbabwe, including:
- Inconsistent network connectivity, especially during corridor travel.
- Varied device capability among driver smartphones.
- Operational load peaks when dispatch teams must manage multiple jobs and driver escalations concurrently.
To address these realities, DispatchFlow’s software workflow is designed to deliver value even when communications are delayed, and to reduce the number of manual “catch-up” interactions dispatchers need to do. Structured status updates and POD evidence reduce the reliance on chasing drivers for the “latest update.”
Customer persona mapping and deployment fit
DispatchFlow’s target is organizations moving goods across corridors and within urban operational zones:
- Fleet owners that manage vehicles and require dispatch workflow standardization.
- Haulage companies managing multi-vehicle scheduling and proof-of-delivery requirements.
- Courier operators with high job frequency that need fast dispatch execution.
- Manufacturers with outbound distribution that require delivery status reporting and evidence.
In practice, the platform is most valuable for operators with enough operational complexity to feel friction from manual coordination. Operators typically have 10–60 active vehicles and 3–20 dispatch users, meaning the dispatch workflow is significant enough to justify process automation and traceability.
Competitive differentiation: dispatch execution layer
Competitors fall into two broad categories:
- Manual dispatch using WhatsApp and spreadsheets.
- Tracking-focused tools that show location but do not provide a unified dispatch workflow.
DispatchFlow differentiates by focusing on dispatch execution rather than location display alone:
- Job allocation is central, not an afterthought.
- Driver dispatch instructions are integrated into the workflow.
- Proof-of-delivery is built into operational evidence, not a separate ad-hoc process.
- Status updates are structured to support escalation and reporting.
Service readiness and customer adoption
DispatchFlow’s service model is designed to support customer onboarding and retention:
- Onboarding & setup ensure dispatch workflow templates align with how a customer currently runs.
- Customer success training reduces churn risk in early adoption.
- Proof-of-delivery notification add-ons increase reliability of evidence capture.
This approach matters because dispatch software only becomes valuable when teams consistently use it under real execution conditions. The product and support model therefore aim to ensure dispatch adoption becomes operational habit.
Market Analysis (target market, competition, market size)
Zimbabwe’s transport and logistics sector faces ongoing demand pressures: clients require reliable delivery windows, logistics providers must manage fuel and labor costs, and operational constraints create frequent disruptions. Dispatch reliability—allocation correctness, status clarity, and proof-of-delivery evidence—directly influences customer satisfaction and contract renewal decisions.
DispatchFlow’s market opportunity is defined by operators that manage multi-job logistics operations and feel pain from manual dispatch coordination and weak evidence processes. This includes fleet owners, haulage companies, courier operators, and manufacturers with outbound distribution needs.
Target market: Zimbabwean logistics operators
DispatchFlow’s ideal customers are transport and logistics businesses based in:
- Harare
- Corridors connecting to Bulawayo, Mutare, and Gweru
These organizations typically operate fleets in the range of 10–60 active vehicles and support dispatch teams with 3–20 users. Their decision-makers typically include:
- Fleet managers
- Operations managers
- Founders who oversee delivery performance and customer relationships
Their pain points align with dispatch workflow failures:
- Wrong vehicle assignments leading to delay and rework.
- Missing or delayed delivery status updates requiring repeated calls.
- Proof-of-delivery delays causing disputes and escalations.
Market sizing: available customer base
DispatchFlow estimates there are roughly 8,000 potential logistics operators in Zimbabwe that represent viable adoption targets for dispatch software. This estimate is based on business density patterns around major hubs and along main routes, combined with industry licensing presence that indicates an operational structure requiring dispatch coordination beyond minimal scale.
The market size calculation is best interpreted as addressable adoption potential rather than “all logistics businesses.” It includes operators above a workable size that benefits from a dispatch operating system. In Zimbabwe, adoption is often driven by operational pain and the ability to justify subscription costs through reduced delay costs and improved contract performance.
Market need: why dispatch workflow automation wins
For dispatch teams, the value of a dispatch system is measurable in:
- Reduced coordination time (less time spent on chasing updates).
- Reduced incorrect assignments (lower rework costs).
- Increased delivery reliability (better customer service outcomes).
- Improved evidence capture (fewer disputes and faster reporting).
In many operations, the cost of delays is not limited to direct cost. It includes:
- Customer penalties or reduced repeat business.
- Increased labor spent on manual follow-ups.
- Inefficient fuel utilization when vehicles are not deployed optimally.
DispatchFlow’s workflow design directly targets these cost drivers by making job allocation, status updates, and proof-of-delivery structured and traceable.
Competitive landscape
The competitive landscape for DispatchFlow can be considered in layers:
1) Manual dispatch (WhatsApp + spreadsheets)
Many dispatch teams still rely on:
- WhatsApp message chains between dispatchers and drivers.
- Spreadsheets tracking assignments and status.
- Phone calls for last-mile updates.
This category is inexpensive upfront but creates operational waste. It is also difficult to audit and measure performance consistently across teams.
2) Basic fleet tracking tools
Some tracking solutions show vehicle location but do not solve dispatch workflow end-to-end. Common gaps include:
- No integrated job-to-vehicle assignment workflow.
- No structured driver dispatch instructions.
- Proof-of-delivery still handled manually or through other systems.
For operators who already track vehicles, additional tracking can fail to address the root issue—dispatch execution.
3) Local fleet management providers
Local providers sometimes offer more tailored tools but may be limited in:
- Scalability across multiple teams and locations.
- Workflow depth.
- Integration capability for notifications and POD workflows.
Differentiation strategy
DispatchFlow’s differentiation is dispatch workflow depth and Zimbabwe-specific operational fit:
- Allocation correctness and workflow consistency.
- Driver dispatch with structured status update mechanisms.
- Proof-of-delivery workflows supported by SMS/WhatsApp notifications.
- An operating system designed around dispatch execution rather than only tracking.
DispatchFlow positions itself as the single dispatch layer that reduces the need for multiple tools. This lowers training overhead and reduces process fragmentation.
Market adoption dynamics and buying behavior
In Zimbabwe, software adoption for logistics operations often depends on:
- Immediate operational pain (delays and evidence problems).
- The ability to demonstrate quick ROI.
- Ease of onboarding and operational integration.
Decision-makers prefer tools that:
- Train quickly and do not disrupt daily operations.
- Provide visible improvements in dispatch outcomes.
- Support consistent proof-of-delivery and reporting.
DispatchFlow’s onboarding and support model is designed for adoption speed. This increases the probability that dispatch teams will use the system consistently once it is deployed.
Market sizing implication for business growth
The market is large enough to support multi-year growth, but adoption is incremental because:
- Operational change requires training.
- Dispatch teams need workflow habit formation.
- Proof-of-delivery becomes valuable only when drivers and dispatchers adopt consistent usage.
DispatchFlow’s growth plan focuses on converting dispatch teams into active users and ensuring retention by maintaining dispatch reliability and evidence workflows. The model assumes consistent revenue growth driven by scaling subscriptions and maintaining gross margin.
Industry risks and counter-arguments
The market has risks:
- Some operators may resist subscription costs during cashflow pressure.
- Adoption could be slower if connectivity challenges prevent consistent updates.
- Manual processes can be deeply entrenched.
Counter-arguments include:
- DispatchFlow’s value proposition is operational cost reduction, not “software for software’s sake.”
- Workflow design targets low-friction dispatch execution even under connectivity constraints.
- Proof-of-delivery and notification workflows increase tangible operational reliability, supporting conversion and retention.
These dynamics justify a go-to-market strategy that shows ROI quickly through onboarding success, live dispatch trial workflows, and case studies.
Marketing & Sales Plan
DispatchFlow’s marketing and sales plan is designed for Zimbabwe’s B2B logistics environment where relationships, demonstrations, onboarding reliability, and proof of ROI matter. The sales approach is execution-focused: it emphasizes workflow outcomes such as reduced delivery delays, correct vehicle assignments, and improved proof-of-delivery.
Positioning statement
DispatchFlow positions itself as a dispatch operating system for Zimbabwean logistics operators. The platform does not merely track vehicles; it enables dispatch teams to run dispatch operations end-to-end, reducing coordination errors and improving delivery evidence reliability.
Customer acquisition channels
DispatchFlow will acquire customers through a mix of direct sales outreach, partnerships, and industry visibility:
-
Direct outreach in Harare logistics parks and fleet offices
- Sales visits to logistics hubs support rapid discovery of operational pain and faster conversion.
- Sales conversations focus on dispatch failures: wrong vehicle assignments, lack of visibility, and missing POD evidence.
-
Referrals from early customers
- Customers can recommend DispatchFlow based on measured operational improvements.
- Referral incentives include discounted onboarding for every referral, reducing adoption friction for new customers.
-
Website with demo booking and Zimbabwe dispatch case studies
- A website supports lead capture and credibility.
- Demo booking reduces sales cycle friction by moving quickly to workflow demonstrations.
-
WhatsApp-led follow-ups and driver-manager training sessions
- WhatsApp is used tactically for follow-up and post-first-contact engagement.
- Driver-manager training sessions after first contact accelerate onboarding success by preparing teams for real workflow use.
-
Partnerships with fleet service providers and vehicle maintenance networks
- Partners already serve the same customer base and can refer operators needing dispatch workflow upgrades.
- This increases trust and shortens trust-building cycles.
Sales process: from lead to deployment
DispatchFlow’s sales cycle is structured as a progression through qualification, demonstration, onboarding planning, and launch.
Step 1: Lead capture and qualification
Potential customers are evaluated based on:
- Fleet size fit for Starter/Growth/Fleet packages (10–60 vehicles target range)
- Dispatch team size and operational complexity (3–20 dispatch users)
- Evidence pain (POD delays, missing proof, dispute frequency)
- Current dispatch method (WhatsApp, spreadsheets, fragmented tools)
Step 2: Workflow demonstration (dispatch execution, not tracking)
The demo includes:
- Creating and allocating jobs to vehicles
- Dispatching drivers with structured updates
- Capturing proof-of-delivery workflow
- Showing escalation and reporting logic
Demonstrations are designed around Zimbabwe corridor delivery patterns, reinforcing practical relevance.
Step 3: Proposal and package selection
Based on fleet size and dispatch user needs:
- Starter for smaller fleets up to 10 vehicles
- Growth for mid-sized fleets up to 30 vehicles
- Fleet for larger fleets up to 60 vehicles
Step 4: Onboarding & setup planning
Once a customer commits:
- DispatchFlow confirms device constraints and driver readiness.
- Setup aligns dispatch workflow templates with how the customer manages daily jobs.
- A pilot period is organized where dispatch teams run the workflow on actual jobs (to the extent feasible).
Step 5: Go-live and adoption monitoring
After go-live:
- Dispatch teams receive training and quick reference materials.
- DispatchFlow monitors status update adoption and POD completion patterns.
- If needed, the customer is offered onboarding add-ons like SMS/WhatsApp proof-of-delivery notifications or advanced routing configuration.
Marketing strategy: building trust with operational proof
Marketing is not only brand awareness; it is credibility-building. DispatchFlow emphasizes:
- Dispatch case studies demonstrating improvements in operational reliability.
- Short educational materials explaining how dispatch workflow automation reduces delays and errors.
- Demo booking and trial-oriented messaging to reduce perceived risk.
Retention strategy: turn initial adoption into recurring value
Retention drives the subscription model. DispatchFlow will retain customers by ensuring that:
- Live updates work reliably for dispatch teams.
- POD workflows are adopted consistently.
- Customer success supports drivers and dispatch managers during the first weeks.
Retention levers include:
- Training refreshers for dispatch teams.
- Responsive support when connectivity causes workflow disruptions.
- Proactive optimization based on customer feedback.
Sales targets and expected deployment cadence
DispatchFlow’s commercial plan focuses on onboarding and scaling subscription revenue through:
- Early traction with Harare-based operators
- Corridor expansion through Bulawayo and other hubs as references and case studies grow
The plan is consistent with the model’s Year 1 revenue requirements and the projected growth rates. The company expects to reach 40 active paying customers by end of Year 1, with growth continuing through recurring subscription expansion.
Pricing and value framing
Pricing is framed as operational cost replacement rather than discretionary IT spending:
- Starter: US$ 240/month supports early adoption for small fleets.
- Growth: US$ 520/month targets fleets requiring structured dispatch execution and more dispatch team coordination.
- Fleet: US$ 900/month supports larger operations with higher dispatch complexity.
Onboarding and optional POD notification add-ons are positioned as reducing delays and proof-of-delivery disputes—directly affecting customer satisfaction and repeat contract likelihood.
Marketing & sales execution budget in the model
The financial model assumes marketing and sales expense of US$ 54,000 in Year 1 with a gradual increase through the projection horizon, reflecting scaling sales activity and customer conversion efforts.
Within that budget scope, execution emphasizes:
- Sales travel
- Demo preparation
- Conversion events
- Continuous pipeline generation via partnerships and referrals
This plan remains aligned with the financial projection assumptions for operating costs and growth.
Key risks and mitigations
Risk: Slow adoption due to workflow change resistance
Mitigation:
- Training and onboarding templates reduce disruption.
- Proof-of-delivery workflows provide immediate operational value.
Risk: Customer churn if dispatch workflows don’t perform under connectivity constraints
Mitigation:
- DispatchFlow’s DevOps and support functions focus on uptime and workflow resilience.
- Driver-manager training improves correct workflow execution.
Risk: Competitive pressure from tracking-only tools
Mitigation:
- Product differentiation emphasizes workflow end-to-end.
- Demos show that dispatch execution and POD workflows provide distinct ROI beyond tracking.
Operations Plan
DispatchFlow’s operations plan covers how the company will build, deliver, support, and continuously improve the dispatch execution platform. It integrates software delivery with customer onboarding, reliable uptime, and responsive support—critical for a dispatch system used in time-sensitive logistics operations.
Operating principles
DispatchFlow operates under five operational principles:
-
Workflow reliability first
- Dispatch execution must work reliably and consistently.
- Status updates and proof-of-delivery must be dependable enough to reduce disputes.
-
Adoption-focused onboarding
- Implementation succeeds when dispatch teams adopt the workflow in daily operations.
- Training is treated as a core operational function, not a secondary activity.
-
Lean execution early
- Operations start lean and scale after traction.
- This helps preserve cash while achieving product stability.
-
Security and uptime discipline
- Dispatch operations rely on stable access to dispatch workflows.
- DevOps and security controls are essential due to operational criticality.
-
Customer success feedback loop
- Support insights inform product improvements and configuration guidance.
- DispatchFlow uses customer feedback to refine workflow templates.
Product development and infrastructure operations
DispatchFlow’s platform has several elements requiring operational discipline:
- Cloud hosting and infrastructure reliability
- Security and data protection
- Messaging services and proof-of-delivery notifications workflows
- Dispatch workflow configuration and driver app compatibility management
The operations team includes DevOps & Security capability to ensure uptime and resilience. The Head of Engineering ensures the platform maintains dispatch workflow integrity and supports feature refinement.
Customer onboarding operations
Onboarding is designed as a repeatable process that scales.
Onboarding workflow (high-level)
-
Pre-onboarding discovery
- Determine current dispatch method (WhatsApp/spreadsheets)
- Understand fleet and dispatch team roles
- Identify typical delivery corridors and job types
-
Configuration
- Configure job types and dispatch workflow roles
- Set up vehicle allocation logic within the customer’s operational style
- Prepare driver dispatch workflow access
-
Training
- Train dispatch managers and drivers using practical scenarios.
- Focus on daily dispatch actions: creating jobs, allocating vehicles, sending dispatch, updating status, and submitting POD.
-
Pilot execution
- Run real operational jobs through the platform.
- Confirm that dispatch status visibility improves and POD capture works as expected.
-
Go-live and optimization
- Adjust templates and workflows based on pilot results.
- Optionally configure notifications and advanced routing integration if needed.
Handling poor connectivity and operational friction
A dispatch system in Zimbabwe must handle imperfect network conditions. DispatchFlow supports operational continuity by designing workflows that:
- Reduce reliance on continuous connectivity for dispatch updates
- Enable structured status reporting when devices reconnect
- Ensure evidence capture supports proof-of-delivery even when communications are delayed
Support processes are designed to help dispatch teams recover quickly from connectivity-related disruptions. This operational resilience is important to avoid churn caused by frustration during the early adoption phase.
Customer support and service delivery
Customer support includes:
- Quick response to onboarding questions and workflow execution issues
- Ongoing QA and product support to ensure workflows function correctly
- Training and refresher sessions for dispatch managers
Support & QA capability ensures that dispatch workflow steps are stable. Customer Success & Training manages training quality and adoption monitoring.
Metrics used to manage operations
Operations are managed using dispatch and adoption metrics such as:
- Percentage of jobs that receive correct vehicle allocation without rework
- Driver status update completion rate within expected windows
- Proof-of-delivery completion rate
- Support ticket resolution time (for workflow issues)
- Customer activity levels (dispatch usage frequency)
These metrics connect directly to operational outcomes that matter for customers.
Use of office and remote operations
DispatchFlow runs from an office in Harare logistics belt to support training and onboarding. Remote coverage is used for customers in Bulawayo and corridor regions. This includes remote onboarding sessions, support calls, and periodic check-ins to maintain adoption.
Operational timeline and scaling approach
The company’s operational scaling is staged:
- Early stage: focus on product stability, onboarding readiness, and initial customer deployments.
- Traction stage: scale customer success and support responsiveness as deployments increase.
- Expansion stage: broaden support capabilities beyond Harare while maintaining consistent onboarding outcomes.
The financial model assumes a cost structure that scales across five years, with increasing operating expenses that remain consistent with projected revenue growth.
Quality assurance and security operations
Quality assurance and security operations are continuous:
- QA supports workflow correctness across dispatch execution steps.
- DevOps & Security ensures hosting stability and resilience.
- Security controls ensure that customer dispatch data and evidence are protected.
In dispatch operations, trust is essential. If a customer loses confidence in reliability, subscription renewals decline. The operations plan therefore places quality and security at the center of delivery.
Management & Organization (team names from the AI Answers)
DispatchFlow Technologies (Pty) Ltd’s management structure is built to match the business’s critical needs: dispatch operations expertise, software engineering depth, onboarding and customer success discipline, partnerships and go-to-market experience, and DevOps security reliability. The team is anchored by the founder and supported by specialized roles that support day-to-day execution and scaling.
Organizational structure
The operational workflow for DispatchFlow is designed around four core functions:
- Product and engineering delivery
- Dispatch operations and workflow correctness
- Customer onboarding, success, and training
- Sales partnerships and customer acquisition
- DevOps and security for uptime and resilience
The team is structured so that product quality, dispatch workflow reliability, and adoption success are managed consistently—reducing risk of churn and ensuring operational outcomes match customer expectations.
Key team members (roles and responsibilities)
Imani Reddy — Founder / Owner
- Responsible for overall strategy, pricing, unit economics, and customer acquisition strategy.
- Uses BCom Accounting background and 11 years of operations finance experience in logistics and retail supply chains across Southern Africa.
- Ensures the business remains focused on dispatch ROI and financial discipline aligned with subscription growth targets.
Jordan Ramirez — Head of Engineering
- Owns engineering delivery, architecture decisions, and dispatch workflow system implementation.
- Brings 9 years of software engineering experience and 5 years building logistics workflow systems, including API integrations for messaging and dispatch events.
- Ensures product stability and iterative improvements aligned with customer feedback.
Quinn Dubois — Product & Dispatch Operations Lead
- Owns dispatch workflow design and ensures dispatch operational correctness.
- Brings 8 years in transport operations, managing dispatch teams, driver escalations, and delivery performance reporting.
- Ensures the product aligns with how dispatch teams actually function under Zimbabwe operating conditions.
Casey Brooks — Customer Success & Training
- Owns onboarding execution and driver-manager training approach.
- Brings 7 years in B2B customer onboarding and training roles, with strong experience reducing churn for SMB SaaS deployments.
- Ensures adoption metrics remain strong and customers get value quickly.
Blake Morgan — Partnerships
- Owns partnerships strategy and business development with fleet service providers and logistics networks.
- Brings 10 years in logistics industry partnerships, connecting fleet operators with software, hardware, and service providers in Zimbabwe.
- Helps accelerate lead flow through trust-based referrals.
Morgan Kim — DevOps & Security
- Owns uptime, cloud infrastructure resilience, and security posture.
- Brings 8 years in cloud infrastructure and security, focusing on resilient hosting for mission-critical workflows.
- Ensures dispatch system reliability even under load and uneven connectivity scenarios.
Reese Johansson — Sales Executive
- Owns sales execution for B2B SaaS deployments.
- Brings 6 years in B2B SaaS sales with a track record in turning leads into contracted deployments for small and mid-sized operators.
- Runs pipeline generation and conversion execution aligned with budgeted marketing and sales cost assumptions.
Alex Chen — Support & QA
- Owns QA testing and customer support quality.
- Brings 7 years in QA and support operations, ensuring dispatch workflows work reliably under poor connectivity and device constraints.
- Works closely with DevOps and customer success to resolve issues quickly.
Governance and accountability
DispatchFlow’s governance is designed for fast decision-making:
- Founder leads strategy and ensures alignment with the financial plan.
- Engineering and dispatch operations lead enforce product quality standards.
- Customer success and support provide adoption feedback loops.
- Sales and partnerships deliver pipeline generation and conversion.
This structure reduces fragmentation and ensures that the platform remains aligned with customer dispatch needs.
Hiring and scaling approach
The operations and financial model anticipate scaling across five years. While early execution focuses on lean operations, the team approach supports:
- Hiring or expanding customer success and support as customer count increases.
- Scaling engineering only after product stability is established.
- Maintaining security and DevOps discipline throughout growth.
This scaling logic ensures that DispatchFlow can sustain reliability as the business grows.
Financial Plan (P&L, cash flow, break-even — from the financial model)
The financial plan is presented in a format suitable for investor review and is based on the authoritative five-year financial projection model. The currency is USD ($). The projections assume subscription SaaS revenue scaling and a cost structure that maintains consistent gross margin assumptions and controlled operating expense growth.
Key assumptions used in the model
The model uses the following key assumptions:
- Subscription revenue grows at 32.1% each year after Year 1.
- COGS equals 20.0% of revenue, producing a stable gross margin of 80.0%.
- Operating expenses grow as projected through salaries, rent/utilities, marketing/sales, insurance, and other operating costs.
- Depreciation and interest are included in the model to arrive at net income.
- Cash flow includes operating cash flow, capex outflows, and financing cash flow components.
Projected Profit and Loss (5-year summary)
Per the model, the following is the Year 1 / Year 2 / Year 3 summary table required for replication.
| Category | Year 1 | Year 2 | Year 3 |
|—|—:|—:|—::|
| Revenue | $3,960,000 | $5,230,343 | $6,908,204 |
| Gross Profit | $3,168,000 | $4,184,274 | $5,526,563 |
| EBITDA | $1,731,000 | $2,675,424 | $3,942,271 |
| Net Income | $1,325,304 | $2,074,164 | $3,077,738 |
| Closing Cash | $1,205,704 | $3,224,251 | $6,225,996 |
Full 5-year P&L highlights
The model provides the full five-year trajectory:
-
Year 1
- Revenue: $3,960,000
- Gross Profit: $3,168,000
- EBITDA: $1,731,000
- EBIT: $1,695,100
- EBT: $1,677,600
- Tax: $352,296
- Net Income: $1,325,304
-
Year 2
- Revenue: $5,230,343
- Gross Profit: $4,184,274
- EBITDA: $2,675,424
- Net Income: $2,074,164
- Closing Cash: $3,224,251
-
Year 3
- Revenue: $6,908,204
- Gross Profit: $5,526,563
- EBITDA: $3,942,271
- Net Income: $3,077,738
- Closing Cash: $6,225,996
-
Year 4
- Revenue: $9,124,313
- Gross Profit: $7,299,450
- EBITDA: $5,635,943
- Net Income: $4,418,504
-
Year 5
- Revenue: $12,051,335
- Gross Profit: $9,641,068
- EBITDA: $7,894,385
- Net Income: $6,205,438
Break-even Analysis
The model provides:
- Y1 Fixed Costs (OpEx + Depn + Interest): $1,490,400
- Y1 Gross Margin: 80.0%
- Break-Even Revenue (annual): $1,863,000
- Break-Even Timing: Month 1 (within Year 1)
This implies that the revenue generated early in the first year offsets fixed costs quickly due to strong gross margin and the model’s operational cost structure.
Projected Cash Flow (5-year projections)
Below is the structure for investor review, with amounts sourced from the model’s cash flow projection. (Values shown are totals, using the model’s calculated cash flow figures.)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations (Operating CF) | $1,163,204 | $2,046,547 | $3,029,745 | $4,343,598 | $6,094,987 |
| Additional Cash Received (Financing CF) | $222,000 | -$28,000 | -$28,000 | -$28,000 | -$28,000 |
| Total Cash Inflow | $1,385,204 | $2,018,547 | $3,001,745 | $4,315,598 | $6,066,987 |
| Expenditures from Operations (OpEx/operating outflows netted in Operating CF) | -$179,500 (Capex outflow shown separately in model) | -$0 | -$0 | -$0 | -$0 |
| Additional Cash Spent (Capex outflow) | -$179,500 | $0 | $0 | $0 | $0 |
| Net Cash Flow | $1,205,704 | $2,018,547 | $3,001,745 | $4,315,598 | $6,066,987 |
| Ending Cash (Cumulative) | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
To keep the cash flow representation consistent with the model’s totals, capex and financing are reflected using the model’s provided net financing and capex outflow values.
Projected Profit and Loss (expanded operating line items)
The model includes revenue, COGS, and detailed operating costs. The Year 1, Year 2, Year 3 line items implied by the model are summarized below in an investor-friendly structure.
Year 1
| Category | Amount |
|---|---|
| Sales | $3,960,000 |
| Direct Cost of Sales (COGS) | $792,000 |
| Other Production Expenses | $0 |
| Total Cost of Sales | $792,000 |
| Gross Margin | $3,168,000 |
| Gross Margin % | 80.0% |
| Payroll | $696,000 |
| Sales & Marketing | $54,000 |
| Depreciation | $35,900 |
| Leased Equipment | $0 |
| Utilities | $1,900 (included in operating costs line items; model classifies under rent and utilities total) |
| Insurance | $37,200 |
| Rent | included in rent and utilities |
| Payroll Taxes | included in salaries/statutory costs within OpEx |
| Other Expenses | $588,600 |
| Total Operating Expenses | $1,437,000 |
| Profit Before Interest & Taxes (EBIT) | $1,695,100 |
| EBITDA | $1,731,000 |
| Interest Expense | $17,500 |
| Taxes Incurred | $352,296 |
| Net Profit | $1,325,304 |
| Net Profit / Sales % | 33.5% |
Important note on presentation: The model’s detailed categorization aggregates several elements inside “Other operating costs” and “Rent and utilities.” The totals above align to model totals: COGS 20.0% of revenue, total OpEx $1,437,000 in Year 1, and resulting EBIT/EBITDA/net income figures.
Projected Balance Sheet (5-year projections)
The provided model does not explicitly break out a full balance sheet line-by-line schedule by year. However, it does provide cash positions (closing cash balances) and funding structure. To remain consistent with the authoritative model, the balance sheet portrayal below focuses on the major categories and ensures cash balances match the model closing cash.
For the purpose of the investor review format, the balance sheet categories are represented consistent with the model outputs.
Projected Balance Sheet (category format; cash is model-authoritative)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Assets | |||||
| Cash | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
| 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,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
| Property, Plant & Equipment | $0 | $0 | $0 | $0 | $0 |
| Total Long-term Assets | $0 | $0 | $0 | $0 | $0 |
| Total Assets | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
| 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 | $0 | $0 | $0 | $0 | $0 |
| Total Liabilities | $0 | $0 | $0 | $0 | $0 |
| Owner’s Equity | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
| Total Liabilities & Equity | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
This balance sheet format is consistent with the model’s cash-centric output. In practice, the company will have working capital movements (receivables, payables), but since the authoritative model does not supply explicit balance sheet balances by category, the cash position is the authoritative component.
Liquidity and debt service capacity
The model includes DSCR values:
- Year 1 DSCR: 38.04
- Year 2 DSCR: 63.70
- Year 3 DSCR: 102.40
- Year 4 DSCR: 161.03
- Year 5 DSCR: 250.62
These high DSCR values indicate strong projected ability to service debt from operating cash flow over time, assuming modeled revenue and expense performance.
Capital expenditure (Capex)
The cash flow model includes:
- Capex (outflow): -$179,500 in Year 1
- Capex: $0 in Years 2–5
This implies the business invests primarily upfront in launch readiness, consistent with the funding use allocation for development and infrastructure readiness.
Funding Request (amount, use of funds — from the model)
DispatchFlow Technologies (Pty) Ltd is requesting US$ 250,000 in total funding to support product completion, infrastructure readiness, customer onboarding capacity, and early lean operating runway.
Funding structure
The financial model specifies:
- Equity capital: US$ 110,000
- Debt principal: US$ 140,000
- Total funding: US$ 250,000
The model assumes debt is 12.5% over 5 years.
Use of funds (as defined in the model)
The funding will be allocated as follows:
- Completing product stability, dispatch workflow modules, and device compatibility: US$ 92,000
- Core infrastructure, security, and messaging services reserve: US$ 30,000
- Customer onboarding capacity (training, setup support): US$ 18,000
- Working capital for first 6 months operating lean before full hiring: US$ 95,000
- Marketing launch, sales travel, and conversion events: US$ 15,000
These allocations align with both product readiness and the go-to-market execution needed to reach subscription traction quickly.
Funding rationale: why this amount and timing
The requested amount is designed to:
- Complete critical engineering and workflow modules so that dispatch execution is reliable.
- Ensure infrastructure and messaging services support stable dispatch workflows and POD notifications.
- Provide sufficient onboarding capacity to convert customers successfully through training and setup support.
- Provide working capital for the first six months when the company operates lean before scaling fixed costs.
- Enable initial marketing and sales activity to secure early customers and create case study content.
Expected outcomes supported by funding
Within the financial model, DispatchFlow reaches break-even within Year 1 (Month 1). The funding allocation therefore serves as launch readiness and early execution capability—so that revenue generation begins early enough to cover fixed cost structure per model assumptions.
Appendix / Supporting Information
This section provides supporting information that reinforces product fit, customer adoption logic, market credibility, and the financial model consistency. It is designed to be investor-readable and to support due diligence requests.
Appendix A: Product offering overview (customer-ready summary)
DispatchFlow Technologies (Pty) Ltd offers:
- Transport Dispatch Software (SaaS)
- Route planning and dispatch preparation
- Vehicle allocation and job assignment
- Driver dispatch with live status updates
- Proof-of-delivery workflows
- Notification support via SMS/WhatsApp
Subscription packages:
- Starter (up to 10 vehicles): US$ 240/month
- Growth (up to 30 vehicles): US$ 520/month
- Fleet (up to 60 vehicles): US$ 900/month
Add-ons:
- Onboarding & setup (one-off): US$ 350 per customer
- SMS/WhatsApp proof-of-delivery notifications (monthly): US$ 70 per customer
- Advanced routing + driver app configuration (one-off): US$ 250 per deployment
Appendix B: Competitor and alternatives assessment
DispatchFlow’s competitors include:
- Manual dispatch systems (WhatsApp + spreadsheets)
- Basic fleet tracking vendors
- Local fleet management providers
DispatchFlow differentiates by delivering dispatch execution workflow end-to-end:
- Allocation, dispatch, status updates, and proof-of-delivery in one system.
- Designed for Zimbabwe operational realities where structured workflows reduce coordination chaos.
Appendix C: Management team credentials
- Imani Reddy (Founder / Owner): BCom Accounting; 11 years operations finance experience in logistics and retail supply chains across Southern Africa.
- Jordan Ramirez (Head of Engineering): 9 years software engineering; 5 years building logistics workflow systems including API integrations.
- Quinn Dubois (Product & Dispatch Operations Lead): 8 years transport operations, dispatch team management, driver escalation, delivery performance reporting.
- Casey Brooks (Customer Success & Training): 7 years B2B onboarding/training; churn reduction experience for SMB SaaS deployments.
- Blake Morgan (Partnerships): 10 years logistics partnerships in Zimbabwe connecting operators with service providers.
- Morgan Kim (DevOps & Security): 8 years cloud infrastructure and security; resilient hosting for mission-critical workflows.
- Reese Johansson (Sales Executive): 6 years B2B SaaS sales; turning leads into contracted deployments.
- Alex Chen (Support & QA): 7 years QA and support operations; reliability under poor connectivity and device constraints.
Appendix D: Financial model tables required for investor review
Projected Cash Flow (Category structure)
The cash flow tables below follow the required format categories. Since the authoritative model outputs do not provide a line-item breakdown for receivables, taxes received, and borrowing categories separately, those are reflected as zeros where not provided, while total cash flow uses the model-authoritative totals.
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations | $1,163,204 | $2,046,547 | $3,029,745 | $4,343,598 | $6,094,987 |
| Cash Sales | $0 | $0 | $0 | $0 | $0 |
| Cash from Receivables | $0 | $0 | $0 | $0 | $0 |
| Subtotal Cash from Operations | $1,163,204 | $2,046,547 | $3,029,745 | $4,343,598 | $6,094,987 |
| Additional Cash Received | |||||
| 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 | $222,000 | -$28,000 | -$28,000 | -$28,000 | -$28,000 |
| Subtotal Additional Cash Received | $222,000 | -$28,000 | -$28,000 | -$28,000 | -$28,000 |
| Total Cash Inflow | $1,385,204 | $2,018,547 | $3,001,745 | $4,315,598 | $6,066,987 |
| Expenditures from Operations | |||||
| 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 | |||||
| Sales Tax / VAT Paid Out | $0 | $0 | $0 | $0 | $0 |
| Purchase of Long-term Assets | -$179,500 | $0 | $0 | $0 | $0 |
| Dividends | $0 | $0 | $0 | $0 | $0 |
| Subtotal Additional Cash Spent | -$179,500 | $0 | $0 | $0 | $0 |
| Total Cash Outflow | -$179,500 | $0 | $0 | $0 | $0 |
| Net Cash Flow | $1,205,704 | $2,018,547 | $3,001,745 | $4,315,598 | $6,066,987 |
| Ending Cash Balance (Cumulative) | $1,205,704 | $3,224,251 | $6,225,996 | $10,541,595 | $16,608,582 |
Break-even Analysis (Model-authoritative)
- Y1 Fixed Costs (OpEx + Depn + Interest): $1,490,400
- Y1 Gross Margin: 80.0%
- Break-Even Revenue (annual): $1,863,000
- Break-Even Timing: Month 1 (within Year 1)
Projected Profit and Loss (Category format)
The model’s P&L line items for Year 1 are consistent with:
- Revenue: $3,960,000
- COGS: $792,000
- Total OpEx: $1,437,000
- Depreciation: $35,900
- Interest: $17,500
- Taxes: $352,296
- Net Income: $1,325,304
A Year 1 category-format investor table (as required):
| Category | Amount (Year 1) |
|---|---|
| Sales | $3,960,000 |
| Direct Cost of Sales | $792,000 |
| Other Production Expenses | $0 |
| Total Cost of Sales | $792,000 |
| Gross Margin | $3,168,000 |
| Gross Margin % | 80.0% |
| Payroll | $696,000 |
| Sales & Marketing | $54,000 |
| Depreciation | $35,900 |
| Leased Equipment | $0 |
| Utilities | $1,900 |
| Insurance | $37,200 |
| Rent | included in rent and utilities |
| Payroll Taxes | included in salaries/statutory costs |
| Other Expenses | $588,600 |
| Total Operating Expenses | $1,437,000 |
| Profit Before Interest & Taxes (EBIT) | $1,695,100 |
| EBITDA | $1,731,000 |
| Interest Expense | $17,500 |
| Taxes Incurred | $352,296 |
| Net Profit | $1,325,304 |
| Net Profit / Sales % | 33.5% |
Appendix E: Funding summary table
| Funding Source | Amount |
|---|---|
| Equity capital | $110,000 |
| Debt principal | $140,000 |
| Total funding | $250,000 |
| Use of Funds | Amount |
|---|---|
| Completing product stability, dispatch workflow modules, and device compatibility | $92,000 |
| Core infrastructure, security, and messaging services reserve | $30,000 |
| Customer onboarding capacity (training, setup support) | $18,000 |
| Working capital for first 6 months operating lean before full hiring | $95,000 |
| Marketing launch, sales travel, and conversion events | $15,000 |
| Total | $250,000 |
Appendix F: Five-year model highlights for due diligence
The model’s high-level five-year financial outcomes:
- Revenue grows from $3,960,000 (Year 1) to $12,051,335 (Year 5)
- Gross margin is 80.0% throughout
- Net income grows from $1,325,304 (Year 1) to $6,205,438 (Year 5)
- Cash ending balance increases to $16,608,582 by Year 5
- DSCR rises from 38.04 (Year 1) to 250.62 (Year 5)
These outcomes reflect consistent scaling in the model and indicate strong projected debt servicing capacity.