SamiTech Mobile Apps (Pty) Ltd is a South African mobile app development business focused on helping SMEs launch customer-facing applications with disciplined delivery, fixed-scope MVP builds, and ongoing support that improves measurable outcomes such as leads, bookings, orders, and retention. The company is positioned in Cape Town, Western Cape, and serves clients across South Africa with delivery and communication workflows designed to reduce uncertainty and avoid feature creep. This plan presents a clear go-to-market strategy, operational model, and a five-year financial projection that demonstrates sustainable growth and early break-even.
This business plan is built around a consistent revenue model: MVP App Builds at fixed scope and delivery timing, App Support & Improvements delivered as a monthly retainer, and Performance Add-ons that increase app capability and client engagement. The financial forecasts align to the company’s cost structure, staffing model, and ramp-up assumptions for Year 1 and growth thereafter.
Executive Summary
SamiTech Mobile Apps (Pty) Ltd (the “Company”) is a mobile app development provider in South Africa, headquartered in Cape Town, Western Cape. The Company is registered as a Proprietary Limited (Pty) Ltd, with Sami Andreev as Founder and Managing Director, supported by a delivery-focused team including developers, designers, QA, business development, and finance & admin capacity. The strategic intent is to serve SME decision-makers—typically owners and operations managers—who need a customer-facing app but lack time, budget discipline, or technical certainty to execute a large development project.
The problem: unclear scope and slow delivery for SMEs
Many SMEs in South Africa want mobile apps but struggle with three interrelated issues:
- Unclear scope and feature creep—initial ideas expand without a clear value hypothesis, increasing build duration and cost.
- Slow delivery—agencies and freelance developers often take longer than expected, delaying launch and market learning.
- Weak post-launch improvements—even when apps launch, ongoing improvements are inconsistent, leading to declining engagement and wasted spend.
These problems are particularly acute for businesses trying to compete for attention in high-usage metro ecosystems like Cape Town, Johannesburg, and Durban. SMEs require apps that work quickly, integrate with common business workflows (such as lead capture and messaging), and evolve based on measurable customer outcomes.
The solution: disciplined delivery and measurable outcomes
SamiTech’s delivery approach is built on three pillars:
- Two-week discovery sprints to clarify the business goal, success metrics, and the MVP feature list.
- Fixed-scope MVP app builds delivered in 8–10 weeks, reducing budget uncertainty.
- App Support & Improvements via a monthly retainer that includes updates, minor bug fixes, and feature tweaks based on client feedback and performance needs.
- Optional Performance Add-ons such as analytics setup and engagement modules (e.g., push notifications packs).
This model ensures clients can launch with confidence and improve post-launch—rather than paying for extensive build effort without validation.
Market opportunity in South Africa
The Company targets SME buyers who want customer-facing apps and have the budget to invest in a first version with clear ROI potential. SamiTech estimates a pool of 60,000 potential SME app buyers across Cape Town, Johannesburg, and Durban over a multi-year period based on SME concentration and likely adoption of customer-facing apps. The Company’s strategy is to focus on measurable outcomes and fast time-to-value to differentiate from competitors that are either priced inconsistently, deliver slower lead times, or provide limited support after launch.
Business model and revenue streams
The Company earns revenue from:
- MVP App Build (fixed-scope) at ZAR 95,000 per app (delivered in 8–10 weeks).
- App Support & Improvements (monthly retainer) at ZAR 18,000 per client per month.
- Performance Add-ons at ZAR 12,000 per add-on.
The Company’s financial model translates these offerings into a five-year forecast with consistent gross margins and strong operating leverage as recurring support contracts accumulate.
Financial highlights and break-even
The authoritative financial model projects:
- Year 1 Revenue: ZAR 4,850,000
- Year 1 Net Income: ZAR 1,360,501 (positive)
- Break-even Timing: Month 1 (within Year 1)
- Gross Margin: 59.0% each year
- Total funding required: ZAR 300,000 (equity ZAR 100,000, debt principal ZAR 200,000)
Projected growth continues across Years 2–5, reaching ZAR 10,263,500 in Year 5 revenue.
Funding request and intended use
The Company requests ZAR 300,000 to cover startup costs and operating buffer through the ramp-up to early traction. The planned uses are specified in the Funding Request section and are sourced directly from the financial model, including studio equipment, tools, legal and compliance, website and branding, initial marketing launch, and working capital reserves.
Company Description
Company overview
SamiTech Mobile Apps (Pty) Ltd is a South Africa–based mobile app development company providing customer-facing app solutions for SMEs. The business is headquartered in Cape Town, Western Cape, South Africa, and is designed to support clients across the country through structured delivery workflows, fixed-scope MVP packages, and a retainer-based support model.
Legal structure and ownership
SamiTech Mobile Apps (Pty) Ltd operates as a Proprietary Limited (Pty) Ltd. The Company is registered as a company entity, enabling formal contracting, invoicing, and operational stability for SME clients that value compliance and professional accountability. The ownership and leadership structure is:
- Sami Andreev — Founder and Managing Director (responsible for sales, delivery oversight, and client success)
- Supporting key roles in business development, development, design, QA, project coordination, client support, and finance & admin.
Mission and value proposition
SamiTech’s mission is to help SMEs build and scale mobile apps without wasting money on the wrong features. The Company’s value proposition centers on a delivery approach that reduces uncertainty through discovery sprints and fixed-scope builds, and maintains relevance post-launch through structured support and improvements.
For clients, this means:
- Predictable costs tied to fixed MVP scope.
- Predictable timelines supported by sprint schedules.
- A clear roadmap that ties improvements to measurable outcomes.
- Practical integrations with common tools and workflows that matter to SME operations.
Geographic focus and client footprint
While SamiTech is based in Cape Town, the customer acquisition strategy includes industries and decision-makers across South Africa. The outreach plan explicitly supports lead generation targeting SMEs in major metro markets—particularly where mobile usage is high and where customer-facing apps have a strong adoption path. The Company’s sales efforts also prioritize clients who need clarity quickly, which is why the discovery process and the proposal structure emphasize an MVP plan aligned with outcomes like lead capture, bookings, orders, and retention.
Competitive positioning in South Africa
The Company differentiates from competitors that either:
- deliver with less predictable pricing for SMEs (e.g., some agencies),
- extend lead times beyond SME affordability windows (mid-tier agencies with longer cycles),
- or provide cost advantages but inconsistent scope control and post-launch support (freelance developers).
SamiTech’s positioning is explicit: it competes on clarity and outcomes, not only on cost. Clients receive fixed-scope MVP delivery, retainer support with measurable improvement intent, and add-on modules that increase engagement capabilities.
Strategic goals overview (1–5 years)
SamiTech’s trajectory is grounded in recurring support revenue and scalable delivery capacity. In the next 12 months, the Company targets 22 MVP app builds delivered in Year 1 and strong traction in support retainers by Year-end, resulting in cash-flow positive operations after launch ramp. By Year 3, the aim is cumulative delivery expansion and a stronger installed base of support clients to reduce reliance on freelancers. By Year 5, the plan projects ZAR 7,200,000 revenue as a longer-term target in the original framing; however, the authoritative financial model projects ZAR 10,263,500 in Year 5 revenue—this plan therefore relies on the financial model figures for investment readiness.
Products / Services
SamiTech Mobile Apps (Pty) Ltd offers three primary services designed to match SME decision-making cycles: an MVP build to establish value quickly, retainer support to improve and stabilize the product, and performance add-ons to deepen engagement.
1) MVP App Build (fixed-scope)
Purpose: Launch a customer-facing app that addresses a defined business objective within a predictable timeframe.
What’s included in an MVP build:
- Discovery sprint (two weeks)
- Define the customer problem the app solves.
- Confirm target user journey and core screens.
- Identify success metrics (examples: lead capture, bookings, order conversion, retention).
- Produce an MVP feature list with “must-have” and “post-MVP” items.
- Solution design and UX alignment
- Wireframes and conversion-focused interface design.
- User flow validation with the client.
- Development and integration
- Cross-platform implementation to support mobile usability.
- Integrations with common SME needs such as lead capture pathways, messaging workflows (e.g., WhatsApp integration scenarios), and payment workflows where required.
- Quality Assurance & testing
- Functional testing, usability validation, and regression checks.
- Delivery and handover
- App submission and/or deployment support.
- Basic documentation and client onboarding for the retainer phase.
Timeline: delivered in 8–10 weeks, supported by sprint planning and project coordination.
Pricing approach: fixed-scope pricing to reduce financial uncertainty. The model translates MVP builds into a Year 1 total MVP revenue of ZAR 2,090,000, rather than presenting only unit-level assumptions.
2) App Support & Improvements (monthly retainer)
Purpose: Ensure the app stays stable and evolves based on real-world feedback and performance needs.
Support model features:
- Updates and minor bug fixes
- Maintaining compatibility with platform changes.
- Addressing defects discovered in real usage.
- Feature tweaks aligned to roadmap priorities
- Clients benefit from a structured improvement process rather than ad-hoc requests.
- Performance monitoring and responsiveness
- Monitoring reliability and usability outcomes relevant to customer engagement.
- Client feedback translation
- Client Support Specialist and Project Coordinator manage a clear intake process.
- Improvements are planned into sprints to preserve predictability.
Retainer cadence: monthly. This recurring revenue supports predictable operational planning and reduces delivery volatility.
In the financial model, support revenue for Year 1 is ZAR 2,400,000, which underpins cash-flow strength and operating margin consistency.
3) Performance Add-ons
Purpose: Increase app capability without forcing a re-build of the MVP.
Add-ons are modular and sold alongside support or shortly after MVP launch. They are designed for clients who already have initial traction and want to improve engagement efficiency.
Common add-on themes (examples used in delivery planning):
- Analytics setup to measure funnels and conversion points.
- Push notifications packs for retention and re-engagement.
- Loyalty/referral module for customer value accumulation.
- Other targeted modules based on client priorities and roadmap sequencing.
In Year 1, the financial model projects add-on revenue of ZAR 360,000.
Service packaging and differentiation logic
SamiTech’s packaging decisions are designed around the SME problem of choosing between “build everything now” versus “launch something quickly.” Many development competitors force clients to choose between low-cost freelancing (with variable scope and inconsistent support) or higher-cost agency work (with less budget predictability).
SamiTech uses a deliberate structure:
- MVP build establishes baseline value with measurable launch outcomes.
- Retainer support preserves quality and adapts the app based on customer behavior.
- Add-ons scale value without destabilizing core delivery.
Example client scenarios (South Africa SME contexts)
Below are concrete examples of how SamiTech’s offerings apply to SME operational realities:
Scenario A: Fitness studio with appointment-driven demand
- MVP goal: allow customers to view class schedules and book appointments.
- MVP approach: a conversion-focused booking workflow integrated into a simple customer journey.
- Support focus: iterate on booking flow performance, fix app usability issues, improve notification timing.
- Add-on potential: push notifications for reminders and special classes.
Scenario B: Retail services business seeking lead capture
- MVP goal: capture lead forms and route inquiries to the right team.
- MVP approach: a clean lead capture UI and fast submission funnel.
- Support focus: improve forms, optimize load performance, refine messaging integration.
- Add-on potential: loyalty/referral module for repeat customer retention.
Scenario C: Trades and services for order requests
- MVP goal: enable customers to request quotes and convert to booking/orders.
- MVP approach: quote request flow with clear steps, fewer screens, and faster submission.
- Support focus: enhance reliability and adjust workflows based on client team feedback.
- Add-on potential: analytics setup and engagement modules to drive repeat requests.
These scenarios reflect the Company’s differentiation: rather than building feature-heavy apps, SamiTech builds for a defined outcome, then iterates based on measurable behavior and client operations.
Market Analysis
Target market definition
SamiTech serves SME owners and operations managers in South Africa who want a customer-facing mobile app but struggle with budgeting, timelines, and technical uncertainty. The target customer profile typically includes:
- Age range 30–55 (decision-makers comfortable with mobile engagement but requiring clarity in project scope).
- Businesses in industries such as retail, services, trades, fitness studios, and local e-commerce.
- Metro-based companies where mobile customer usage is high (especially Cape Town, Johannesburg, and Durban).
The Company’s sales cycle is built for these clients: it emphasizes a structured discovery sprint, a fixed-scope MVP plan, and transparent delivery timelines.
Customer needs and pain points
SMEs typically require apps that solve operational problems, not just “nice-to-have” features. Their needs include:
- Time-to-launch certainty
- SMEs cannot afford multi-quarter delays because competition and customer attention move quickly.
- Budget predictability
- Unclear scope increases project cost and undermines ROI.
- Customer engagement outcomes
- Apps must support lead capture, bookings, orders, or retention—not merely display content.
- Post-launch stability and continuous improvements
- Support must be responsive so the app doesn’t degrade in performance or usability.
SamiTech’s approach addresses these pain points by building a roadmap linked to measurable outcomes, supported by monthly improvement cycles.
Market size and demand assumptions
SamiTech’s market sizing approach uses a practical pipeline logic grounded in SME concentration and adoption likelihood. The Company estimates 60,000 potential SME app buyers across Cape Town, Johannesburg, and Durban over a multi-year period. This estimate is used to frame the long-term TAM and to anchor sales strategy and expansion planning.
While not all SMEs will purchase a mobile app in the same year, the market size supports the assumption that recurring support retainers and add-on modules will compound revenue as the client base grows.
Market segments and service fit
Not all SMEs have the same need, and SamiTech segments buyers by operational demand and purchase readiness.
Segment 1: “Ready-to-launch MVP” SMEs
These clients have:
- A clear customer problem (e.g., booking, ordering, lead capture).
- Enough budget for an MVP build.
- A need for fast delivery.
SamiTech fits well because MVP builds are fixed-scope and delivered in 8–10 weeks.
Segment 2: “Post-launch improvement” SMEs
These clients already have an app or an early version and need:
- Bug fixes and updates.
- Conversion improvements and additional features.
- Analytics and engagement modules.
SamiTech fits through the monthly App Support & Improvements retainer and Performance Add-ons.
Segment 3: “Capability expansion” SMEs
These clients want incremental growth modules:
- Push notifications for retention.
- Loyalty/referral for repeat usage.
- Analytics for funnel and conversion optimization.
SamiTech fits because add-ons are modular and can be delivered without major disruption.
Competitive landscape in South Africa
SamiTech’s competitive environment includes agencies, mid-tier firms, and freelance developers.
Key competitors referenced in the Company’s positioning include:
-
iKasa
Strengths: delivery capability.
Weakness for SMEs: pricing can be less predictable, affecting budget control. -
AgileIT / similar mid-tier agencies
Strengths: reliability and experience.
Weakness for SMEs: lead times often exceed what small businesses can afford, impacting time-to-market. -
Freelance developers
Strengths: lower cost potential.
Weaknesses: scope control can be inconsistent and post-launch support may not be as structured or reliable.
Differentiation strategy
SamiTech differentiates through:
- Fixed-scope MVP pricing
- Two-week discovery sprint
- Support retainer including measurable improvements
- A roadmap tied to outcomes (leads, bookings, orders, retention)
This differentiation matters because SMEs compare proposals not only by cost but by risk and delivery certainty. If risk is reduced—especially scope and timeline—SMEs are more likely to proceed.
Go-to-market logic and defensibility
SamiTech’s defensibility is built around repeatable processes and customer retention mechanics:
- The retainer model creates recurring revenue and client stickiness.
- Each app build generates operational learnings and reusable patterns (UI patterns, QA workflows, deployment routines).
- Support retainers create ongoing relationships that enable additional add-on purchases once initial traction is proven.
The strategy avoids a pure “project-only” dependency and aims to convert one-time build revenue into multi-year support and expansion.
Market risks and mitigation
No market strategy is without risk; the plan addresses major risks:
Risk 1: SME budget uncertainty
Mitigation: fixed-scope MVP pricing and discovery sprints that define a minimal value package first.
Risk 2: Delivery delays or quality concerns
Mitigation: structured sprints, QA support through Zanele Gumede, and disciplined project coordination with Lerato Ndlovu.
Risk 3: Churn after MVP launch
Mitigation: retainers include structured improvement cycles and measurable outcome roadmaps; clients see ongoing value beyond launch.
Risk 4: Competitive undercutting
Mitigation: emphasize outcome clarity and predictability rather than competing on lowest price.
These mitigations are operationalized through the service model and team responsibilities described later.
Marketing & Sales Plan
Sales strategy summary
SamiTech’s sales strategy targets SME decision-makers who need clarity and fast execution. The Company uses a combination of digital outreach, local SEO, and partnerships, supported by a conversion-focused sales flow that includes a short proposal framework and a discovery-call booking process.
The approach emphasizes a simple narrative:
- Define the outcome.
- Confirm MVP scope.
- Confirm timeline.
- Provide fixed pricing.
- Start with a discovery sprint.
This reduces buyer risk and accelerates the path to agreement.
Target buyer and message
The target is an SME owner or operations manager, age range 30–55, in sectors including retail, services, trades, fitness studios, and local e-commerce. The message is tailored to their operational concerns:
- “Launch faster with a fixed scope.”
- “Avoid paying for the wrong features.”
- “Get support that improves measurable outcomes after launch.”
Marketing channels and campaigns
SamiTech uses multiple channels to create consistent demand:
- Local SEO
- Content and website pages optimized for queries like mobile app development in major metros.
- Google search ads
- Focus on high-intent keywords connected to service need.
- Example keyword themes referenced in channel planning include “mobile app development Cape Town” and “app development Johannesburg.”
- LinkedIn and Facebook outreach
- Target SME owners and operations managers with B2B messaging.
- Partner referrals
- Referrals with branding studios and IT consultants who do not build apps.
Conversion assets and sales enablement
To increase conversion, SamiTech provides structured assets aligned to SME decision-making:
- A clear website showcasing prior app work and packaged MVP options.
- A proposal framework that follows a consistent sequence:
- Problem
- MVP scope
- Timeline
- Fixed pricing
- Simple discovery-call booking flow to reduce friction.
Sales process and pipeline management
SamiTech’s sales process is designed for predictability and speed:
Step 1: Lead capture and qualification
- Track lead source (SEO, ads, outreach, partners).
- Qualification questions determine whether the client needs an MVP build, post-launch improvements, or add-on capabilities.
Step 2: Discovery call and discovery sprint proposal
- Confirm success metrics (leads, bookings, orders, retention).
- Confirm MVP feature list boundaries to prevent scope creep.
Step 3: Fixed-scope MVP agreement
- Provide a fixed-scope build agreement aligned to the discovery output.
- Schedule the build timeline into sprint milestones with QA and handover milestones.
Step 4: Launch and transition into support
- After MVP delivery, transition the client into the monthly retainer for improvements.
Step 5: Upsell to add-ons based on traction
- Add-ons are introduced when the client demonstrates early traction or needs deeper engagement.
Case-style evidence of sales fit (illustrative but practical)
SamiTech’s messaging tends to convert best when it demonstrates a clear MVP path and validates success metrics such as:
- booked appointments,
- lead capture funnel completion,
- order conversion improvements,
- and retention behavior changes over time.
This conversion logic reduces buyer skepticism because the app is positioned as a growth tool rather than a technology project.
Marketing & sales KPIs
The Company will track KPIs that align with its delivery and retention model:
- Lead volume by channel (SEO, ads, outreach, partners).
- Discovery call conversion rate.
- MVP build conversion rate.
- Retainer conversion rate post-launch.
- Add-on attachment rate per support client.
Although this plan uses a financial model for quantitative projections, the KPIs provide operational control and early warning indicators.
Budgeting and scaling approach
SamiTech’s marketing and sales expenses scale with revenue growth in the financial model. This ensures marketing spend does not outpace operational capacity.
For investment readiness, the Company’s model includes:
- Marketing and sales costs of ZAR 144,000 in Year 1,
- scaling to ZAR 195,910 by Year 5,
while total revenues grow from ZAR 4,850,000 to ZAR 10,263,500.
Sales expansion logic over time
SamiTech’s growth is structured around how support retainers compound demand:
- MVP builds generate new clients.
- Retainers stabilize monthly cash flow and generate consistent support revenue.
- Add-ons are sold to existing clients, reducing acquisition cost per incremental revenue unit.
This approach supports the five-year forecast’s revenue growth path and strengthens operating leverage.
Operations Plan
Operational model
SamiTech’s operations are structured around repeatable delivery workflows. The operations system is designed to:
- keep MVP build timelines within 8–10 weeks,
- ensure consistent quality through QA and sprint-based development,
- and provide predictable monthly service delivery through retainers.
Delivery lifecycle for MVP builds
The MVP build lifecycle includes:
1) Discovery sprint (two weeks)
- Output: MVP scope definition, success metrics, feature list boundaries, and UX flow plan.
- Goal: prevent “invisible scope creep” by confirming what is in the MVP and what is deferred.
2) Design and prototyping
- Output: wireframes and UI/UX design aligned to conversion goals.
- Review: client feedback is collected early to reduce downstream rework.
3) Development sprints (structured by milestone)
- Cross-platform build process.
- Integration tasks scheduled early for critical dependencies (e.g., lead capture flows, messaging pathways, payment workflows if required).
4) QA and regression testing
- QA plan includes functional tests, performance checks, usability verification, and regression runs before release.
5) Delivery and handover
- Deployment support and client onboarding into support retainer terms.
- Documentation to support ongoing improvements.
Retainer operations (monthly support and improvements)
Monthly support is delivered as a cycle:
- Intake of requests and feedback
- Client requests are collected in a structured way to avoid “priority confusion.”
- Planning into improvement sprints
- The Project Coordinator schedules tasks to keep delivery predictable.
- Execution and testing
- Developers implement changes; QA validates regressions and new functionality.
- Release and client communication
- Changes are communicated clearly, with an emphasis on measurable outcomes where possible.
- Roadmap updates
- Minor roadmap adjustments are made based on observed performance and feedback.
This operational structure is critical to the Company’s promise: clients should not feel like they “paid for a build and then disappeared.” Instead, improvements continue in a controlled cycle.
Performance add-on delivery
Add-ons are delivered using the same disciplined approach but scaled to a modular scope:
- Requirements are clarified at sales stage or during retention sprint planning.
- Delivery includes QA validation and integration testing so add-ons do not break core functionality.
Quality assurance and risk control
Quality is operationally guarded by:
- Zanele Gumede (Quality Assurance & Testing) leading testing workflows.
- Sprint-based milestones that reduce integration risk.
- Clear boundaries established in the discovery sprint to reduce “everything must be included” risk.
This approach reduces the chance of delays and reduces rework, protecting both customer satisfaction and operational profitability.
Tools and infrastructure (operational necessities)
The financial model includes capex for studio equipment and setup tools. Operationally, these enable development productivity and reliable delivery:
- Studio equipment (laptop, monitors, peripherals)
- Design and development tool licenses and setup
- Monitoring and mobile testing environments via recurring cloud hosting, monitoring, and testing costs
Even though the plan focuses on narrative operations, the financial model governs the actual investment amounts and running expenses used later.
Capacity planning and contractor interface
SamiTech’s model assumes that delivery is both operator-led and supported by contractor execution capacity. The plan relies on a structured coordination approach so that contractor output aligns with fixed-scope builds and predictable delivery milestones.
Capacity planning includes:
- aligning sprint schedules with discovery outputs,
- ensuring QA bandwidth is available before release,
- and maintaining retainer responsiveness without sacrificing build quality.
Geographic operating constraints and client delivery
Although the Company is based in Cape Town, the operations plan supports South Africa–wide clients through:
- remote communication,
- structured sprint delivery cadence,
- and documentation and handover processes.
This ensures clients receive consistent service regardless of location.
Operations timeline linked to financial assumptions
The five-year financial model assumes ramp-up across Year 1 with increasing revenue contributions from MVP builds and support retainers. Operations must support that ramp through:
- effective onboarding of new clients into discovery sprints,
- predictable delivery milestones for MVP builds,
- and consistent retainer delivery cycles.
This plan’s operational structure is designed to match that ramp in a financially responsible way.
Management & Organization
Organizational structure
SamiTech Mobile Apps (Pty) Ltd is structured to keep delivery quality high while maintaining clarity in customer success. Roles are intentionally mapped to the operational model of discovery sprints, fixed-scope builds, retainer improvements, and add-on delivery.
Leadership team (named roles and responsibilities)
The key team members are:
-
Sami Andreev — Founder and Managing Director
Responsibilities: sales, delivery oversight, and client success. Sami brings a software delivery background with 10 years’ experience in mobile and web product teams, plus hands-on project management for time-bound builds. -
Sipho Dlamini — Business Development Lead
Responsibilities: B2B sales and pipeline conversion into recurring service contracts. Sipho has 8 years of B2B sales experience in South Africa’s tech services, with a track record of converting SMB leads into recurring service contracts. -
Sibusiso Maseko — Mobile Developer
Responsibilities: cross-platform app development, integrations, and implementation quality. Sibusiso has 6 years of cross-platform app development experience, including payment and messaging integrations. -
Nomsa Mbeki — UI/UX Designer
Responsibilities: conversion-focused interface design and user experience. Nomsa has 7 years of UX design experience, specializing in conversion-focused interfaces for service-based businesses. -
Zanele Gumede — Quality Assurance & Testing
Responsibilities: mobile testing workflows, usability validation, and regression testing. Zanele has 5 years in QA and mobile testing workflows. -
Lerato Ndlovu — Project Coordinator
Responsibilities: sprint schedule coordination, milestone tracking, and documentation. Lerato has 9 years coordinating client projects, ensuring sprint schedules stay on track and documentation stays simple. -
Palesa Zulu — Client Support Specialist
Responsibilities: client support operations and translation of app feedback into planned improvements. Palesa has 4 years of customer support experience. -
Thandi Mokoena — Finance & Admin
Responsibilities: invoicing, reporting, cash-flow discipline, and admin compliance. Thandi has 10 years in SME finance and bookkeeping, handling invoicing, reporting, and cash-flow discipline.
Governance and decision-making
The governance approach ensures accountability in both delivery and financial discipline.
- Sami Andreev provides final oversight of delivery standards and client success outcomes.
- Sipho Dlamini ensures the sales pipeline aligns with delivery capacity.
- Lerato Ndlovu coordinates execution schedules to match the fixed-scope MVP timelines.
- Thandi Mokoena maintains invoicing, reporting, and financial tracking to protect cash flow as recurring support revenue scales.
Team capacity rationale
The team is intentionally structured so that:
- design and QA are not afterthoughts,
- project coordination maintains scheduling discipline,
- and finance & admin create predictable cash management.
This structure is essential in a service business where margins depend on delivery efficiency and repeatable processes.
Hiring plan and scaling assumption
As revenue grows, the Company expects to increase delivery capacity via:
- increased utilization of existing team members,
- and contractor support where necessary to maintain timelines.
The financial model already embeds an operational cost structure that scales with revenue while maintaining consistent gross margin levels.
Financial Plan
Financial model approach and key assumptions
The authoritative financial model provides the five-year projections for Revenue, Costs, P&L performance, cash flow, break-even analysis, and balance sheet structure. All monetary figures in this section are reproduced and used exactly as provided in the financial model.
Key model outputs:
- Gross Margin: 59.0% each year
- EBITDA Margin: increasing from 39.6% in Year 1 to 46.5% in Year 5
- Positive net income in each year, including Year 1 Net Income of ZAR 1,360,501
- Break-even timing in Month 1 (within Year 1)
- Cash flow includes operating cash generation and financing and capex flows
Year 1–Year 5 Summary: Profit and Loss
Below is the Year 1 / Year 2 / Year 3 summary table reproduced directly from the model requirement, including Revenue, Gross Profit, EBITDA, Net Income, and Closing Cash.
| Year | Revenue | Gross Profit | EBITDA | Net Income | Closing Cash |
|---|---|---|---|---|---|
| Year 1 | ZAR 4,850,000 | ZAR 2,861,500 | ZAR 1,919,500 | ZAR 1,360,501 | ZAR 1,254,801 |
| Year 2 | ZAR 6,314,094 | ZAR 3,725,315 | ZAR 2,707,955 | ZAR 1,939,723 | ZAR 3,112,120 |
| Year 3 | ZAR 7,510,375 | ZAR 4,431,121 | ZAR 3,332,372 | ZAR 2,399,198 | ZAR 5,442,303 |
Projected Profit and Loss (5-year projection)
The following table reproduces the model’s projected P&L figures with all required categories for investment readiness. Values are presented exactly as per the financial model.
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Sales | ZAR 4,850,000 | ZAR 6,314,094 | ZAR 7,510,375 | ZAR 8,843,301 | ZAR 10,263,500 |
| Direct Cost of Sales | ZAR 1,988,500 | ZAR 2,588,778 | ZAR 3,079,254 | ZAR 3,625,753 | ZAR 4,208,035 |
| Other Production Expenses | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Cost of Sales | ZAR 1,988,500 | ZAR 2,588,778 | ZAR 3,079,254 | ZAR 3,625,753 | ZAR 4,208,035 |
| Gross Margin | ZAR 2,861,500 | ZAR 3,725,315 | ZAR 4,431,121 | ZAR 5,217,547 | ZAR 6,055,465 |
| Gross Margin % | 59.0% | 59.0% | 59.0% | 59.0% | 59.0% |
| Payroll | ZAR 252,000 | ZAR 272,160 | ZAR 293,933 | ZAR 317,447 | ZAR 342,843 |
| Sales & Marketing | ZAR 144,000 | ZAR 155,520 | ZAR 167,962 | ZAR 181,399 | ZAR 195,910 |
| Depreciation | ZAR 30,800 | ZAR 30,800 | ZAR 30,800 | ZAR 30,800 | ZAR 30,800 |
| Leased Equipment | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Utilities | ZAR 114,000 | ZAR 123,120 | ZAR 132,970 | ZAR 143,607 | ZAR 155,096 |
| Insurance | ZAR 18,000 | ZAR 19,440 | ZAR 20,995 | ZAR 22,675 | ZAR 24,489 |
| Rent | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Payroll Taxes | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Other Expenses | ZAR 483,200 | ZAR 516,320 | ZAR 553,819 | ZAR 596,420 | ZAR 644,480 |
| Total Operating Expenses | ZAR 942,000 | ZAR 1,017,360 | ZAR 1,098,749 | ZAR 1,186,649 | ZAR 1,281,581 |
| Profit Before Interest & Taxes (EBIT) | ZAR 1,888,700 | ZAR 2,677,155 | ZAR 3,301,572 | ZAR 4,000,099 | ZAR 4,743,084 |
| EBITDA | ZAR 1,919,500 | ZAR 2,707,955 | ZAR 3,332,372 | ZAR 4,030,899 | ZAR 4,773,884 |
| Interest Expense | ZAR 25,000 | ZAR 20,000 | ZAR 15,000 | ZAR 10,000 | ZAR 5,000 |
| Taxes Incurred | ZAR 503,199 | ZAR 717,432 | ZAR 887,374 | ZAR 1,077,327 | ZAR 1,279,283 |
| Net Profit | ZAR 1,360,501 | ZAR 1,939,723 | ZAR 2,399,198 | ZAR 2,912,772 | ZAR 3,458,801 |
| Net Profit / Sales % | 28.1% | 30.7% | 31.9% | 32.9% | 33.7% |
Note on category mapping: The financial model provides line items for salaries and wages, rent and utilities, marketing and sales, insurance, professional fees, administration, other operating costs, depreciation, and interest. The above table maps these into the requested investment-ready categories while preserving the total operating expenses and gross margin relationships from the model.
Break-even analysis
The financial model provides:
- Y1 Fixed Costs (OpEx + Depn + Interest): ZAR 997,800
- Y1 Gross Margin: 59.0%
- Break-Even Revenue (annual): ZAR 1,691,186
- Break-Even Timing: Month 1 (within Year 1)
These figures indicate that once the early revenue from MVP builds and initial retainers is realized, fixed costs can be covered quickly within the first year.
Projected Cash Flow (5-year projection)
The plan includes the required cash flow categories. The values below are reproduced from the model. (Where the model provides totals rather than sub-lines like “Cash Sales,” the allocation remains consistent with the model’s total cash inflow and outflow logic.)
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Cash from Operations | ZAR 1,148,801 | ZAR 1,897,319 | ZAR 2,370,184 | ZAR 2,876,926 | ZAR 3,418,591 |
| Cash Sales | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Cash from Receivables | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Subtotal Cash from Operations | ZAR 1,148,801 | ZAR 1,897,319 | ZAR 2,370,184 | ZAR 2,876,926 | ZAR 3,418,591 |
| Additional Cash Received | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Sales Tax / VAT Received | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| New Current Borrowing | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| New Long-term Liabilities | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| New Investment Received | ZAR 300,000 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Subtotal Additional Cash Received | ZAR 300,000 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Cash Inflow | ZAR 1,448,801 | ZAR 1,897,319 | ZAR 2,370,184 | ZAR 2,876,926 | ZAR 3,418,591 |
| Expenditures from Operations | ZAR 194,000 | ZAR 315,000 | ZAR 395,000 | ZAR 445,000 | ZAR 500,000 |
| Cash Spending | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Bill Payments | ZAR 194,000 | ZAR 315,000 | ZAR 395,000 | ZAR 445,000 | ZAR 500,000 |
| Subtotal Expenditures from Operations | ZAR 194,000 | ZAR 315,000 | ZAR 395,000 | ZAR 445,000 | ZAR 500,000 |
| Additional Cash Spent | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Sales Tax / VAT Paid Out | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Purchase of Long-term Assets | -ZAR 154,000 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Dividends | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Subtotal Additional Cash Spent | -ZAR 154,000 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Cash Outflow | ZAR 40,800 | ZAR 315,000 | ZAR 395,000 | ZAR 445,000 | ZAR 500,000 |
| Net Cash Flow | ZAR 1,254,801 | ZAR 1,857,319 | ZAR 2,330,184 | ZAR 2,836,926 | ZAR 3,378,591 |
| Ending Cash Balance (Cumulative) | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
Cash flow integrity with model totals: The authoritative model’s net cash flow and closing cash are preserved exactly:
- Operating CF: ZAR 1,148,801 (Year 1) to ZAR 3,418,591 (Year 5)
- Capex outflow: -ZAR 154,000 in Year 1
- Financing CF: ZAR 260,000 in Year 1 and -ZAR 40,000 each year after
Projected Balance Sheet (5-year projection)
The authoritative financial model does not provide detailed balance sheet line-by-line values beyond the cash flow closing cash context. To provide the required investment-ready format, this section presents a balance sheet structure consistent with the model inputs and maintains cash as the known quantity from the closing cash.
| Category | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 |
|---|---|---|---|---|---|
| Assets | |||||
| Cash | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
| Accounts Receivable | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Inventory | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Other Current Assets | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Current Assets | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
| Property, Plant & Equipment | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Long-term Assets | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Assets | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
| Liabilities and Equity | |||||
| Accounts Payable | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Current Borrowing | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Other Current Liabilities | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Current Liabilities | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Long-term Liabilities | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Total Liabilities | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 | ZAR 0 |
| Owner’s Equity | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
| Total Liabilities & Equity | ZAR 1,254,801 | ZAR 3,112,120 | ZAR 5,442,303 | ZAR 8,279,229 | ZAR 11,657,821 |
Liquidity and coverage
The model includes DSCR:
- DSCR Year 1: 29.53
- DSCR Year 2: 45.13
- DSCR Year 3: 60.59
- DSCR Year 4: 80.62
- DSCR Year 5: 106.09
High DSCR indicates strong coverage capacity relative to debt service, supporting investment resilience.
Funding Request
Total funding requested
SamiTech Mobile Apps (Pty) Ltd requests ZAR 300,000 total funding, sourced from:
- ZAR 100,000 equity capital
- ZAR 200,000 debt principal
The financial model indicates debt structure as 12.5% over 5 years.
Use of funds (exact allocation from the model)
Funding will be used as follows:
- Studio equipment (laptop, monitors, peripherals): ZAR 55,000
- Design and dev tools (annual licences + setup): ZAR 18,000
- Legal, registration, and initial compliance: ZAR 12,000
- Website + branding + domain: ZAR 9,000
- Initial marketing launch (ads + content): ZAR 20,000
- Working capital reserve for Q3 operations buffer: ZAR 40,000
- Q3 through Month 6 running costs buffer: ZAR 146,000
Total funding use: ZAR 300,000
Why the funding is required now
The Company needs startup and working capital buffers to:
- establish productive development capacity (equipment and tools),
- enable market presence (website, branding, initial ads and content),
- cover early legal and compliance,
- and maintain cash flow stability through the ramp-up period until recurring support retainers drive predictable operating cash generation.
The model’s capex outflow of -ZAR 154,000 in Year 1 is directly aligned with the studio and tools allocation (ZAR 55,000 equipment + ZAR 18,000 tools + ZAR 12,000 legal + ZAR 9,000 website + ZAR 20,000 launch marketing + working capital reserved).
Expected impact on early traction and break-even readiness
Because the model indicates break-even timing in Month 1 (within Year 1), the funding supports early operations rather than waiting for later cash generation. It reduces risk during the period when MVP builds and first support retainers are being delivered and converted.
Appendix / Supporting Information
A) Service offering details and operational artifacts
To support investor confidence, SamiTech’s delivery model includes standard outputs during engagement:
-
Discovery sprint outputs:
- MVP scope definition and success metrics
- MVP feature list boundaries (in-scope vs post-MVP)
- UX flow outline
-
Delivery outputs:
- UI/UX design artifacts from Nomsa Mbeki
- Implementation delivered and validated through Zanele Gumede’s QA process
- Client handover documentation organized by Lerato Ndlovu
-
Retainer operations:
- A structured intake and prioritization process for improvements with Palesa Zulu
- Monthly improvement sprint planning and releases
B) Financial model source-of-truth statement
This plan’s monetary figures, margins, break-even values, cash flows, and funding amounts are taken from the authoritative financial model and reproduced without rounding in critical places. Key model outputs include:
- Year 1 Revenue: ZAR 4,850,000
- Year 1 Net Income: ZAR 1,360,501
- Break-even Revenue (annual): ZAR 1,691,186
- Break-even Timing: Month 1 (within Year 1)
- Total funding: ZAR 300,000
- Use of funds: exactly allocated across equipment, tools, compliance, website/branding, initial marketing, and running cost buffers
C) Team credibility summary
The management and delivery team is built to cover the entire lifecycle of mobile app development and operations:
- Product delivery oversight (Sami Andreev)
- B2B conversion and recurring client growth (Sipho Dlamini)
- Engineering implementation (Sibusiso Maseko)
- Conversion-focused UX (Nomsa Mbeki)
- Testing and regression safety (Zanele Gumede)
- Sprint scheduling and documentation (Lerato Ndlovu)
- Client feedback translation and support (Palesa Zulu)
- Finance discipline, invoicing, and reporting (Thandi Mokoena)
D) Competitive positioning recap
SamiTech competes against:
- iKasa (less predictable pricing),
- AgileIT / similar mid-tier agencies (lead times that may stretch SME needs),
- Freelance developers (scope and support consistency challenges).
SamiTech’s differentiators remain:
- Fixed-scope MVP pricing
- Two-week discovery sprint
- Retainer with measurable improvements
- Outcome-driven roadmap tied to client KPIs