ZOMOZOMO: From Platform Operator to Provider Custom Case Solution & Analysis

1. Evidence Brief: Zomozomo Case

Financial Metrics:

• Platform Take-Rate: Remained flat at 18% (Exhibit 2).
• Customer Acquisition Cost (CAC): Increased 22% year-over-year to $44.00 (Exhibit 3).
• LTV/CAC Ratio: Dropped from 4.2x to 2.8x over the last 24 months (Exhibit 3).
• Revenue Mix: 85% transaction-based platform fees; 15% advertising/promoted listings (Exhibit 2).

Operational Facts:

• Market Position: Third-largest food delivery aggregator in the region.
• Asset Base: No ownership of delivery fleets or kitchens; pure software-as-a-service model (Paragraph 14).
• Churn Rate: Restaurant churn increased to 12% annually (Paragraph 22).

Stakeholder Positions:

• CEO: Pushing for transition to a full-stack provider model (kitchens + logistics) to control the customer experience (Paragraph 30).
• CFO: Concerned about capital expenditure requirements for physical assets; prefers software-only margin expansion (Paragraph 32).

Information Gaps:

• Unit economics of pilot cloud kitchens (no data provided).
• Projected impact of full-stack transition on existing restaurant partner relationships.

2. Strategic Analysis

Core Strategic Question: Should Zomozomo transition from an asset-light aggregator to a capital-intensive full-stack provider to arrest declining LTV/CAC ratios?

Structural Analysis (Value Chain): The current aggregator model is failing due to commoditization. Competitors with proprietary logistics are delivering faster, eroding Zomozomo’s platform value. The current model lacks control over the final product quality, leading to high churn.

Strategic Options:

• Option A: Defensive Software Pivot. Invest exclusively in AI-driven demand prediction and logistics-matching software. Trade-offs: Avoids CAPEX but fails to solve the physical delivery latency issue.
• Option B: Full-Stack Integration. Acquire or build dark kitchens and delivery fleets. Trade-offs: High capital intensity and operational complexity, but allows control over end-to-end quality and unit economics.
• Option C: Hybrid Partnership. Partner with existing specialized logistics firms and kitchen operators. Trade-offs: Lower capital burden, but higher dependency on third-party performance.

Recommendation: Option B. The current downward trend in LTV/CAC indicates the platform model is losing its competitive moat. Control of the physical layer is now a requirement for survival, not a luxury.

3. Implementation Roadmap

Critical Path:

• Phase 1 (Months 1-3): Identify and secure leases for three pilot urban distribution hubs.
• Phase 2 (Months 4-6): Integrate fleet management software and recruit delivery personnel.
• Phase 3 (Months 7-12): Roll out in a single high-density metropolitan area to prove unit economics.

Key Constraints:

• Capital Liquidity: The shift requires significant debt or equity infusion.
• Operational Talent: The organization currently lacks expertise in physical logistics management.

Risk-Adjusted Strategy: Implement a phased rollout. If the pilot in the first metro area does not achieve a positive contribution margin within 180 days, pause further capital deployment.

4. Executive Review and BLUF

BLUF: Zomozomo must pivot to a full-stack model. The current aggregator business is structurally broken; LTV/CAC compression confirms the platform is losing relevance to operators who control their own logistics. The transition will be capital-intensive, but the alternative is managed decline. The CFOs caution regarding CAPEX is secondary to the existential threat of platform commoditization. Execute a phased entry, starting with a single-market pilot to validate kitchen and delivery unit economics before scaling.

Dangerous Assumption: The analysis assumes that Zomozomo can successfully transition from a software-focused culture to a logistics-management culture without significant turnover or operational failure.

Unaddressed Risks:

• Regulatory risk: Changes in gig-economy labor laws could render the delivery fleet model unprofitable overnight.
• Channel conflict: Existing restaurant partners may view Zomozomo as a direct competitor once the company launches its own kitchens, leading to a mass exodus of vendors.

Unconsidered Alternative: A white-label logistics play. Instead of building kitchens, Zomozomo could offer its delivery technology as a service to restaurants, keeping the platform asset-light while solving the delivery quality problem.

Verdict: APPROVED FOR LEADERSHIP REVIEW.