Private mentoring needs flexible schedules and service design, but an open marketplace still requires quality control, trusted payments, earning calculations, and delivery tracking.
Case Study 03 — Marketplace
Jalan Pintar
Marketplace and learning platform connecting mentor discovery, scheduling, payments, revenue sharing, payouts, classroom operations, and Android delivery.
70 / 30
Problem
Solution
I structured the product around marketplace flexibility with authoritative platform transactions.
Discover→Book→Pay→Learn→Earn→Payout
- Mentor quality gate and admin approval workflow.
- Flexible one-session and package scheduling.
- Platform payment lifecycle and 70/30 revenue share logic.
- Mentor earnings, wallet, payout, digital products, and classroom workflows.
- Web-first architecture with Capacitor Android distribution.
Engineering
The complexity comes from coordinating product, operational, and financial states across multiple user roles.
Marketplace architecture and business-model architecture have to agree.
My Role
Marketplace model, user roles, onboarding, scheduling, payment lifecycle, revenue share, earnings/payout workflow, digital commerce, classroom operations, and mobile delivery architecture.