Company: MainStory Pte Ltd
Description: Study Case
Role: Product Manager
Methodology: Agile
Currently, financial & performance reporting is handled manually and inconsistently across centers. SELF-OWNED centers require a P&L view combining revenue and expenses, while PARTNER centers only need a simplified revenue view. Automation is needed to reduce manual workload, improve accuracy, and ensure timely reporting.
Objective
Understand MainPartner & Partner pain points related to current financial reporting to design a self-serve, automated, and transparent financial dashboard.
Sneak peek from the research process. (Requirements Gathering)
Thought Process:
Problem → Partner Pain Mapping → Research Validation → Solution Design (As-Is/To-Be)
→ MVP Definition → QA & UAT → Launch → (Result & Measure)
The first thing to do is to gain data so I interviewed 3 partners and compiled all of the partners’ past complaints on email. After gathering the data, I make a comprehensive, easy-to-read table below to map out the partner’s pain points.
| Theme | Partner Pain Points (Examples) | Root Cause (Hypothesis) | Severity / Priority |
|---|---|---|---|
| 1. Transparency & Accuracy | “Boleh tolong di cek lagi pencatatannya kok beda dengan perhitungan saya.” | ||
| “Laba dihitung sebelum potongan fee.” | Manual Excel input, no link to source-of-truth (Xendit, Journal.id), inconsistent formulas. | 🔴 High – MVP Focus | |
| 2. Data Mismatch (Cross-Platform) | “Data di Xendit beda dengan laporan.” | ||
| “Refund tidak muncul di laporan.” | Manual reconciliation between systems, timing gap, no automation pipeline. | 🔴 High – MVP Focus | |
| 3. Fee & Revenue Sharing Clarity | “Fee MainStory dihitung dari pendapatan kotor atau bersih?” | ||
| “Kok management fee diambil sebelum diskon?.” | No standardized fee logic across contracts; unclear fee computation in reports. | 🟠 Medium | |
| 4. Timeliness & Accessibility | “Laporan dikirim H+30, tidak bisa akses sendiri.” | Manual reporting & emailing, no partner dashboard. | 🟢 Medium |
| 5. Insights & Actionability | “Kenapa biaya naik terus tapi revenue stagnan?” | ||
| “Tidak ada tren 3 bulan terakhir.” | Reports too accounting-oriented, no analytics or visualization layer. | 🟢 Low (Next Phase) |