Stein-cv

Strategic Case Study: Operational Architecture & Unit Economics

Author: Steinley Goh
Focus Areas: Business Intelligence Analytics, Multi-Dealer Routing Infrastructure, Systems Architecture, CRM Integrity


🏛️ Executive Summary

This case study outlines the end-to-end mapping, prototyping, and deployment of operational tracking infrastructures engineered to eliminate manual data entry, enforce regional data integrity, and provide granular financial visibility. Leveraging native prototyping tools (Figma) and rigorous functional requirements documentation (Google Docs), complex messaging pipelines and unit-economic reporting models were established to drive precise decision-making impact on business.


⚡ Section 1: Multi-Dealer WhatsApp Routing & Distribution Engine

The Architectural Infrastructure

Engineered a comprehensive lead generation pipeline linking the Official Yadea WhatsApp Business API (Meta) directly to a centralized Mekari Qontak routing engine via real-time webhooks. This architecture completely bypassed manual regional data collection, enabling automated ingestion and assignment at scale.

Intelligent Chatbot & Location Mapping

Competition Mode Mechanics (“First-to-Respond”)

To maximize response speed and ensure absolute fairness across dealer distributions, a native Competition Mode workflow was implemented:


🛡️ Section 2: CRM Business Logic & Automated Fraud Prevention

Data Integrity Enforcement

Operating across 110+ individual dealer accounts, automated validation loops were scripted to maintain system-level accuracy and eliminate manual audit dependencies:

Escalation Tiers (Mitigating Alert Fatigue)

To prevent notification blindness among operational leaders, customized alert pipelines were segmented into three priority tiers:

  1. Critical Alerts: Real-time push notifications delivered natively via WhatsApp for urgent workflow blocks.
  2. Warning Feeds: In-app operational dashboards tracking ongoing data validation discrepancies.
  3. Info Digests: Automated asynchronous email recaps outlining regional metrics for executive review.

📊 Section 3: Unit Economics & Decision-Making Visualizations

The Philosophy of Dashboards

Data visualization serves a singular, highly focused objective: transforming highly complex data streams into clean interfaces that give business leadership absolute clarity to make precise decisions.

The 10 Core Metrics Engine

Interactive reporting matrices built inside Feishu Base and Google Looker Studio model exactly how operational marketing spend translates into finalized sell-through performance. The analytics engine synthesizes 10 distinct variables alongside granular Lead Source ROI comparisons (benchmarking TikTok campaigns, Google Ads, and physical retail walk-ins):

  1. Total Event Spend: Overall corporate capital deployed per initiative, aggregated across monthly intervals.
  2. Dealer Support Cost: Capital subsidies allocated directly from headquarters to support active promotional operations.
  3. Baseline Dealer Cost: Fixed operational overhead mapped to individual retail points.
  4. Out-of-Pocket Dealer Spend: Independent capital spent directly by local partners to run marketing activities.
  5. Average Cost per Activity: Direct resource-efficiency tracking for specific promotional themes.
  6. Average Cost per Day: Ongoing operational burn rates across active campaign lifecycles.
  7. Cost-Per-Lead (CPL) Mechanics: Monthly absolute CPL tracking, paired with dynamic daily trendlines and visual charts to monitor acquisition velocity in real time.
  8. Total Activity Volume: Absolute numerical tracking of promotional pushes launched.
  9. Active Duration Days: Combined regional operational footprint measured in cumulative campaign days.
  10. Verified Outcomes: Absolute monthly lead generation quotas verified against finalized retail unit sales.

🔗 Section 4: Systems Architecture Blueprint (CRM to IoT Interface)

Native Figma Prototyping

To ensure customer sales metrics integrate seamlessly with physical inventory management, the complete 12-24 Month CRM Evolution Roadmap and hardware unit state flows were mapped out visually inside Figma (including customized interface layouts engineered specifically For mekari To view during vendor alignment).

[ Customer CRM Record ] ---> [ Finalized Sale Event ] ---> [ Hardware IoT Telemetry ] ---> [ Central Hub Ledger ]

The Hardware Integration Concept


🧠 Section 5: Personal Infrastructure Scale (The Sovereign Mesh)

To maximize personal operational bandwidth, a customized local digital ecosystem was built to coordinate workflows across decentralized reasoning models.