The challenge
A sponsorship journey connects people, scholarship programs, contribution periods, payments, student progress, and follow-up. Staff needed to understand those relationships without piecing the story together across separate records.
Designing the core workflow
I centered the experience on the relationship between sponsor and student. A guided four-step pairing flow helps staff choose a Kakak Bintang, select the scholarship program, find suitable Adik Bintang, and define the support period with the relevant context visible at each decision.
From records to daily work
The platform brings sponsor and student profiles together with filterable dashboards, contribution and invoice status, donation tracking, progress reports, surveys, and practical export tools. Each area is organized around the tasks the team needs to complete, not the shape of the database.
The foundation underneath
I built the application as a Vue interface on top of Laravel, with role-aware administration and secure account flows. The modular structure lets the team manage people, programs, finance, and reference data in one place while leaving room for the operation to evolve.
What I learned
Nonprofit software carries human context that a generic dashboard can easily flatten. The work taught me to translate complex operational rules into small, legible steps—and to treat maintainability as part of the user experience for the team who keeps the program running.